Hey people, another nub here with phone troubles.
History
Early on (years ago) I installed a i9000 kernel and Darkyrom, and have since moved on to Semaphore and Cyanogenmod 10.x and 11.x.
I've been updating to the latest CM11 nightlies (galaxysmtd) for a while without any issues, but several months ago I started seeing a lot of lagginess in responsiveness. I continued with nightlies for a bit until that became too annoying, and I attempted to go back to the full 10.2 galaxysmtd package.
After the flash I was just stuck on the Cyanogen loading screen and because of the cross-flash (i9000 on T959d) I have never been able to get into recovery.
Current
Anyways, since then I'm sure I've managed to make things worse for myself.
I've been all over these forums (T959 One stop shop, stock files, etc) and have attempted to implement the solutions provided myself, but there always appears to be a problem at the start of the instructions that invalidates the solution for me.
All I want to accomplish at this point is to essentially wipe the phone and install the latest/greatest ROM available (Cyanogenmod 11 was previously used, but I'm not particularly attached to anything).
ADB is installed and working
Heimdall works, but will not repartition (I think during the course of my work I've uploaded the wrong PIT or broken it somehow)
Odin will detect my phone when connect, but will not upload files to it
As I've said, I'm a nub and this is clearly beyond my ability to fix so any help would be appreciated. If someone is willing to take this on I can also let you remote in so it can be fixed with a minimal amount of fuss.
So....... since clearly no one here is willing/able to be of direct help perhaps someone can point in another direction?
Related
I've been having some issues with constant reboots and phone signal strength after installing ICS. I have tried both methods (fastboot flashes and CWM flash) and still have the same problems.
Unfortunately, I'm a newbie, and was an idiot and did not create a backup.
I would like to be able to revert to the last stable official Gingerbread. Any recommendations on version to revert to? I'm been searching here for hours, and every time I think I find a good thread on how to do this, the links to the files are all dead.
Can someone please steer me in the right direction.
Also, again, I am willingly admitting that I'm an idiot for not making the backup in the first place. I saw that so many people were having no issues at all, so I assumed I would not either.
Thanks.
slim26 said:
I've been having some issues with constant reboots and phone signal strength after installing ICS. I have tried both methods (fastboot flashes and CWM flash) and still have the same problems.
Unfortunately, I'm a newbie, and was an idiot and did not create a backup.
I would like to be able to revert to the last stable official Gingerbread. Any recommendations on version to revert to? I'm been searching here for hours, and every time I think I find a good thread on how to do this, the links to the files are all dead.
Can someone please steer me in the right direction.
Also, again, I am willingly admitting that I'm an idiot for not making the backup in the first place. I saw that so many people were having no issues at all, so I assumed I would not either.
Thanks.
Click to expand...
Click to collapse
I recommend you the ROMs NottachTrix, it has Aroma installer and lets you configure it to your own taste. Guess this one is the best, if not you could go with a stock GB, search for fruitcakes (don't like them because the bloatware).
I'm assuming that you already have or know how to install a recovery. If it's not the case, let me know and I'll help you.
Thanks. I have CWM loaded so I shouldn't have an issue.
I think I would have the best luck with a stock ROM for now. The problem is finding a stock unlocked ROM for GB that still has a valid link. 90% of the links I'm coming across here including fruitcakes are all dead links.
http://samcripp.com/files/
you can find fruitcakes here. works from your phone or computer.
be sure to thank Sam Cripp for hosting the files for us. and the project in the first place.
Thanks. I was able to restore back to GB, but unfortunately still have the same signal strength issues.
have you tried to flash a new radio? there are plenty of radios on that website as well.
The following is provided FYI
I have been using the ROM here: http://forum.xda-developers.com/showthread.php?t=1773362 version 8.1 with great success for a while now, but when I decided to try another ROM, I got into major trouble and barely escaped.
My chronicle of woe began when I decided to first update to indirect's latest CWM release. I'm not criticizing him at all, he has done incredible and ground-breaking work on the NT, but in latter developments, I do think this was the source of the problem, and I cannot comment on his Dev thread about it.
After this I tried to flash an AOSP rom - I truly can't remember which anymore - and found myself stuck in a boot loop. I've flashed several roms in the past, so I tried again and got the same symptom. No biggie, back to 8.1 I go...
Except it had the identical problem. Now I'm worried, so back to the trusty team-B CM7...
Uh-oh, now I'm out of the boot loop, but the touchscreen is dead, and I cannot access recovery. If I'd thought this through better, I'd have realized the 5-point touch firmware upgrade made CM7 incompatible. Blast...
After some fiddling around, the NT started booting again into CWM (yay) all on it's own. I restored 8.1 again, back to the boot loop, but at least I can reliably reach CWM again.
Next, I tried Adam Outler's famed Ubuntu restore SD. Many have been saved by this clever piece of code, and I am not criticising him either (in fact, I'm hoping he'll produce a full Ubuntu eventually). But between CWM and Cyanoboot, his card would not work it's magic for me...
As a last ditch effort, I hunted around on the web and found this: http://forum.xda-developers.com/showthread.php?t=1640958 (gotta love XDA)
I followed the instructions for flash_CM9_CM10 version, rebooted back into recovery, installed 8.1, and voila - got my nook back.
Was it Indirect's update that got me in a pickle, or some combination of things I did? Was my new ROM not compatible somehow? I dunno, would take a mightier mind than mine to sort that out. My take-aways are as follows:
1. Consider carefully before flashing Indirect's CWM update.
2. Mr Outler's Ubuntu recovery is not a universal "get out of jail free" card. Remember, there can be consequences and repercussions for tinkering with your NT's innards.
3. When you get something that works satisfactory, consider sticking with it - refer to #2 above.
Thanks,
TM
I appreciate your sharing of your experience, and I wholeheartedly agree with your point 2.
There is no such thing as a 100% get out of jail card!
Therefore you need to do research and read up before you start poking around. Something you didn't do, and almost had to pay for. That's the lesson to be learned from this and what needs to be pointed out in big letters. Not to avoid a specific app/script.
For example: If by Indirect's CWM you mean his app it's pretty clear if you read the topic that it's out of date and that it could also possibly cause trouble. I make it a habit of always checking out the last few pages/comments/reviews of anything I'm thinking of installing/flashing to get the latest news on it. My tip for future explorations, should you decide to not go with your no.3, but keep having fun trying new stuff!
Also this is yet another reminder that people need to be aware what they are doing when installing multitouch! Don't just click "yes I understand" (or whatever it says) unless you at least have thought about it!
Glad you got away with just a raised heartbeat this time! I've had couple of hickups myself when getting careless (starting to do something when I REALLY should have gone to get some sleep instead...), and the repart.img has done good things here as well!
---------- Post added at 03:23 PM ---------- Previous post was at 03:04 PM ----------
To clarify: I have tried Indirect's app (if that is what's referred to here) recently and posted in the topic about it. It didn't cause me any trouble at all, but it didn't install CWM 6.x.x like I hoped it would. It installed 5.x.x and to flash CM10 ROM you need CWM 6.x.x. Even though it says on the first page it does flash 6.x.x all I could see in the topic was that no one actually had any success with that lately. Maybe the OP's bootloop was caused by trying to flash a ROM that required CWM 6.x.x. with CWM 5.x.x?
Hi Asawi,
Thanks for the reply. To put my experience in context, the devs here are the guys who build custom hot rods for street racing, and I am the guy who can change his spark plugs, but just barely. I readily admit 90% of everything goes right over my head around here.
It's more about "read carefully" in my case rather than "research", and even more specifically, "check the date". Exactly as you say, I saw a post from Indirect stating "Safety Fixes, PLEASE DOWNLOAD!" (his caps, not mine), and plunged in without noticing that the post was nearly a year old.
As I said, no disrespect to anyone, I wish I had the skill the devs here demonstrate every day. This misadventure was my fault, not Indirect's. One quibble - I stand by my statement to carefully consider the update, because if I had carefully considered it, I'd have caught on that it was old
I guess my attitude towards trying new roms and such is that there are always going to be bugs, it's just a question of can you live with them? I tried 8.2 and 8.3 in the post above, and both had issues relative to 8.1, so I rolled back. I'll probably try 8.4 when it comes out as well, just because I'm a fan, and I love seeing what these guys can accomplish.
Besides, it's self-correcting: I got in trouble with XDA, I got out with XDA. Gotta love XDA
As for multi-touch, I did read the info on it, and was aware that going back to an older ROM would create a problem - I just plain forgot about it in the panic. Meh, I'm only human. Since I'm at no harm now, if anybody reads this and takes heed, then it's all good.
Lastly, yes it's the CWM app exactly as you describe, and behaved as you describe. Interestingly, though, I was unaware it took CWM6 to flash a CM10 mod. I've been using the CWM from Indirect's very first root how-to from over a year ago to flash CM10 without troubles, and that was 5.x.x.x. I don't know how I got away with it, but that's where I was when all of this started.
Thanks again for the response
TM
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!
Hello everyone.
As the title says I recently got my hands on a Samsung Vibrant. I have it from a friend who just left the apartment we lived in together for 5 months as she didn't need it anymore. It currently has a MIUI ROM on it and I'd like to change it to sada23's unofficial CM 11.0
The problem is however that my only previous experience with flashing ROM was with a Samsung Galaxy Chat when I slapped Jelly Bean on it which was only released in a few countries. So I went right ahead but found the amount of things I have to do overwhelming compared to when I just used ODIN on the old phone.
I'm trying to tell what the current status is of the phone and this is what I've been able to come up with so far. (also after googling what everything is and does lol)
- MIUI present so custom ROM install definitely possible
- When I booted into recovery mode I saw it has: "Semaphore CWM Recovery v6.0.1.9" (which I presume is outdated)
- BY default the MIUI ROM apparently has a superuser app (which lead me to think that the device is rooted), however everytime I try to use an app that requires root I encounter errors.
I just did a backup using the recovery mode with semaphore cause I saw this is usually a first step in all the guides I've read. However from here on out I am completely clueless on what to do because all the guides were so different from eachother and I have a feeling my phone is in a vague situation. (root/not rooted?)
So I was hoping someone here could point me into the right direction and help me get to CM from MIUI. Thank you in advance.
I'll be following this thread.. kinda in a similar situation. Although a bit worse. I had an old vibrant in a drawer from years back in mint condish!.. last thing I did was root and install recovery. Unfortunately I'm a stooge and without thinking threw a 4.4 rom zip on the phone.. booted to recovery and cleaned and tried to flash.. bottom line i'm in a bootloop now... and I gave up when odin wasn't detecting the phone.. I"ll figure that out eventually, but it would be great to just have a 4.4 Odin tar for a quick and painless install... or at least a tar from a 4.0 with root and recovery to make the 4.4 upgrade easy.
Also would be interested in knowing if the 4.4 roms work well.. Gps will be most important to me since I plan to use this as my jogging phone.
alrighty.. let's get this party started!
Edit - I think the best thing for you to do is odin back to stock then root install custom bootloader and then flash your new rom, I've heard that you can go straight to kk from stock but the guy who posted above me has problems because of that so I would try flashing an ICS ROM for the recovery first, and don't forget to make a nandroid backup
You can find all the files and programs you'll ever need here http://forum.xda-developers.com/showthread.php?t=1982728 in NOOB_IN_NEED 'S ref thread
Hope I was of some help if I was hit the thanks button
sent from the depths of paradise - Jamaica
using SGH-T959
ROM: unofficial CM11 4.4.4 by sada
Kernel: stock
Hello everyone,
I've been scouring XDA for a while trying to solve my problem, and just finally became a member so I could try to deal with my particular situation directly with whatever help you guys can provide. Thanks in advance.
HTC 10
Unlocked
S-ON
No ROM installed
TWRP installed and funtional
(Can provide any more info--if I can get it from Download Mode, Bootloader, or TWRP)
My skill level is not very high as far as this stuff is concerned, but I can follow directions. Here's my story:
I first successfully unlocked and rooted my HTC 10 a couple years or so ago (i.e. installed TWRP, ROM, Viper for Android). It was great, until things began to malfunction a bit. I messed around, but eventually decided to go back to stock. I was successful in this, as well.
Fast-forward a while, and I was missing my custom set-up, so I thought I'd wade back into these complex waters. To make a long story short, I screwed up and bricked it. I wish I has more specific details about how it went wrong, but throwing my hands up in frustration, I simply dug out an older phone and began using that instead.
As of a few weeks ago, I decided I was going to give another go at fixing my HTC 10. After all, it is a beautiful piece of hardware, and I'm still paying the thing off.
I've tried installing ROMs every way I know how, via EXEs from the PC, sideloading, wiping caches, trying system restore images from TWRP. . .no dice. I expect even by this point you can tell I'm pretty amateur.
I suspect I may be forgetting some way I cut a corner or ran into some irregularity I ignored when I returned it to stock, but it's just been too long, and I can't remember.
Would greatly, greatly appreciate any help provided.
Cheers,
tra1neus