All,
Just reading through my usual half dozen threads here and I got all angered up and decided post this critical piece of advice - don't report an issue, any issue, if you didn't wipe before a firmware flash. There it is - simple enough for any idiot to understand.
There are many different code bases out there right now and unless you stick with one and don't modify it in any way, you will likely have some form of anomalous behavious if you don't wipe. I have flashed probably a dozen firmware versions and I have seen all sorts of behavior, from radio issues to "core" apps such as Mail that existed in the former firmware showing up in the new firmware until after a subsequent reboot.
The behavior creates problems and confusion, so please consider this as a good way to help yourself and the community.
vj99
I like it..
That's straightforward enough.
great job on this i agree.
to many same post complaining about these issues.
this deserves to be stickied or atleast addid to that read before posting thread
.....Amen!
When I put out RC33 with no MT I had to say that people do this.
There is no such thing as a no-wipe build....every esoteric issue arises with no wipe and is fixed with a wipe.
I seem to get lucky with flashing and not having to wipe. Even when jumping back and forth from dudes and haykuros roms every other day.
well said but i think that it really depends whose firmware you're flashing, in the thread where u find your firmware the developer will usually tell you if its a wipe or no-wipe version, or does that only apply to if you're already using one of the firmwares that developer released?
alritewhadeva said:
well said but i think that it really depends whose firmware you're flashing, in the thread where u find your firmware the developer will usually tell you if its a wipe or no-wipe version, or does that only apply to if you're already using one of the firmwares that developer released?
Click to expand...
Click to collapse
Well, either way. . . if you flashed you're phone and it has issues booting, your last resort will have to be wiping whether or not the build was a wipe/no wipe. Asking for help on the board will result in ppl telling you to wipe anyway. Usually, a wipe will cure most issues. If not, then using the search feature would be the next step prior to asking for help. Ppl need to learn to troubleshoot themselves before asking. It'll help them learn more about their phone just a much as typing a bunch of scripts blindly w/out knowing what it executes.
please sticky this!
Im a noob to G1 and thats the first thing I did after my phone was stuck at the "Android" screen
Let's see how many times this comes up even just today now that there is yet another (JF) version out. Over/under is 20.
Yeah your telling me, they are asking questions about stuff already that is clearly posted on JF'S blog, right before the 1.5 download !!!!!!!!!!! Guess its really that hard to read huh?
Related
Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.
I successfully flashed a custom Froyo ROM on my MyTouch 3g and was quite happy. I did it by following step by step instructions, and while it worked, I didn't understand what I was doing. Now I have a Galaxy S 4g and plan on flashing Gingerbread, but before I do, I would like to understand the process.
I don't want anything specific like instructions on a particular device and ROM, just a general idea of the process, like "Flashing ROMs for Dummies". Then I can come back and re-read some of the threads and know what the posters are talking about.
Question: Where can I find a general tutorial on the process of flashing ROMs to Android devices? I'm an IT consultant so I have a fairly high tolerance for tech-speak. Thanks.
I'll be waiting for the answer to this one too.
It usually works like this:
We root our device to have full access with all priviledges and be allowed to i.e. exchange the kernel.
Now we exchange the kernel against one with an advanced recovery mode (i.e. clockwork mod recovery from cyanogenmod), it allows you to flash unsigned (not official signature) ROM files.
From the new recovery we install a ROM of our choice which can also replace the kernel again.
The recovery mode basicly executes a small script, contained in the ROM file, that copies all the files to the correct location, sets up the partitions and wipes previous data on occasion.
The other possibility would be to use a flash program like odin/heimdall and have your computer setup and write a new firmware onto the device unlike the first method where the device does the setup work.
This is a very broad explanation, i have only flashed an sgs2 and sgs1 so far, so there might be small or huge differences between devices.
Maybe you could ask a more specific question about a particular step if things are not clear.
I'm not 100% sure, if i missunderstood something myself, someone please correct me .
Thanks, Dark3n. That was a very good explanation, in layman's terms, of the process. What I am looking for is one place to learn about what is happening technically; not a developers guide but something sufficient for me to understand.
For example, I've seen threads where someone had a problem with a ROM because they didn't have the right bootloader. What is the significance of bootloaders in changing ROMs? How does the backup/recovery process work? What is the Dalvik cache and why clear it? What is Dalvik?
I found the answer to these questions by Googling them one at a time. I was just wondering if there was one place to go that covers the entire process.
I know that most of the members here are very well informed and get tired of the same questions over and over. If this is the wrong place to ask, let me know and maybe point me in the right direction. Thanks.
lewis750 said:
Thanks, Dark3n. That was a very good explanation, in layman's terms, of the process. What I am looking for is one place to learn about what is happening technically; not a developers guide but something sufficient for me to understand.
For example, I've seen threads where someone had a problem with a ROM because they didn't have the right bootloader. What is the significance of bootloaders in changing ROMs? How does the backup/recovery process work? What is the Dalvik cache and why clear it? What is Dalvik?
I found the answer to these questions by Googling them one at a time. I was just wondering if there was one place to go that covers the entire process.
I know that most of the members here are very well informed and get tired of the same questions over and over. If this is the wrong place to ask, let me know and maybe point me in the right direction. Thanks.
Click to expand...
Click to collapse
I don't think there is such a place. But you could help out others and create a wiki page on the topic.
We have a slightly underused xda wiki
Hello all,
I've been lurking the XDA forums for a couple months now. I had a couple posts in the past referring to my phone and my girlfriends phone and was looking for help mainly with hers at the time... Hers is fixed... Perfectly even, despite her phone being a total piece of garbage (an LG Optimus.... *barf*).
I have a SGH-T959V.
I have read the 10 commandments.
I KNOW my phone is NOT a Vibrant OR an i900.
I have read the noob guides.
I have become completely confused.
Here's my details:
I have running the stock GB that I installed with Kies Mini some time ago.
Phone Data:
Firmware Version: 2.3.6
Baseband Version: T959VUVKJ6
Kernel Version: 2.6.35.7-T959VUVKJ6-CL694130
Build Number: GINGERBREAD.VUVKJ6
I rooted my phone with one of the one-click apps after the stock GB update so that I was at least able to overclock it and get rid of the T-Mobile bloatware, etc.
I notice that my phone reboots entirely on it's own completely randomly, has random application hangs, all the bad icky stuff that sucks... (right????)
Anyways, I've looked at some of the Custom ROMs available and I'd like to check out some of them, but I'll be quite honest, I've read the instructions for how to do it, but I'm getting extremely confused as the current instructions seem rather daunting.... It's like information overload...
Now, don't get me wrong, I'm not some kid that really doesn't know what he's doing... I'm 33 and work in IT for The Nielsen Group... so I kinda know what the heck I'm doing MOST of the time. This is something I'm unfamiliar with and am being EXTREMELY cautious about because i don't want to brick my phone....
Question time!:
1. Is there a COMPLETELY SIMPLE step-by-step process/Video Demonstration for the CORRECT method of how to put a custom rom on the SGH-T959V?
2. Does it matter that I ALREADY rooted my phone in respect to me loading a custom rom? (ie. is my already rooted phone going to have issues loading a different rom?)
3. I would like to stay with a GB based rom unless there is absolute NEED to use a Froyo based Rom - Or is this a non-point when using custom roms?
4. If i want to load a custom rom to my phone, do I need to use a specific loader? (Like, does Odin work for everything??? Loading roms and unbricking your phone? Or do I have to have different loaders for the specific roms that I want to load and try out????)
5. Please don't jump down my throat with the "read the guide" responses... I HAVE been... really. As many as I've found... and every time I read a new one, rather than feeling like I'm coming out of the darkness of knowledge and into the light of understanding the correct process for how to do this, I feel like I'm being cast deeper down the confusion pit.
Would someone KINDLY please help me. Really... I don't want to screw up this thing... I'm not worried about the warranty. From what I've read, these things are mostly fixable unless it's an actual hardware issue or if it's totally fried. I just want to do it once, do it right, move on to my next project.... Dig?
First and foremost, we keep the most updated information in the wiki:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G
We've been updating it a lot lately so you're better off checking there. I'm sure you'll wanna bookmark it since you know what you're doing already.
1) Specifically you'll want to look at this section:http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#Installing_a_ROM
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running.
3) For our phone you're either going to use Odin/Heimdall (learn Heimdall, it's much more useful) and CWM Recovery. Most roms available right now are for CWM.
Here's the list of custom GB roms:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G_ROMs
4) Honestly the forums are too cluttered and as I stated above, knowledgeable senior members are the ones who update the wiki, so that'll be your most useful resource.
If you already have some experience with computers I'll gladly help you, you're already asking the right questions.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
FBis251 said:
First and foremost,
...
2) If you're using Odin/Heimdall you won't need to be rooted since this bypasses the phone's OS and flashes firmware directly to the phone which may or may not be pre-rooted. The only Odin 2.3.6 KJ6 rom that's out right now does NOT come with root though, it's just the stock version you're already running...
Click to expand...
Click to collapse
When I last played with my phone, I had used Odin on Windows... I have replaced Windows with Linux... I have installed Heimdall and did an initial test. So it is working.
My question is: Is Heimdall a valid replacement for Odin? In other words, I am wanting to use your guide, but it only refers to Odin. Can I go through those steps replacing Odin with Hamdall?
Yes it should work fine. The csc files for kc1 should be extracted over the pda files though
Sent from my SGH-T959V using XDA App
FBis251,
Thank you so much for the quick reply! I had seen it immediately after you responded, but was driving home from work and went right to bed. I'm back at the office now for the evening and perhaps may have some time to look into these tonight... I don't know as of right now.
If you are serious about the offer of some assistance, I would be more than open to it if I honestly felt it was needed. I am MORE than experiences with computers, i'm a full on uber-geek (just not with smartphones...... yet....), so VNC, etc would not be an issue.
I will most certainly get back to you about this in the next few days (perhaps even tonight). Let me see how my work load looks this evening and I will update the thread later.
Thank you again so much!
I'm usually in #teamnerd on freenode if you do IRC.
It doesn't take much to confuse me these days...
Moved my issue into a new question in the Q&A forum...
Hey, just an FYI (even tho I'm sure that ultimately you don't really care - just being realistic, not a douche... ), I haven't had a single moment to look into this beyond briefly skimming the Wiki's you linked up for me. (thanks for that one). I've had a butt-load of server issues at work that have taken a lot of my time. I'm HOPING to be able to look into some of this stuff a little deeper tonight (god willing)....
I will drop a note if I have issues....
Thanks again!
Hi guys!
I've seen quite a lot of positive about the last update and ICS and I've been crying for days (well... since friday) to download it. But I got no notice and when I look for a firmware update, it says there aren't any.
If it's normal, for my version, I can wait but if I have to do something to get the update I'd like to do it now.
I'm on HTK75.TB_epad-8.6.5.21-20111216... (TB never seen elsewhere but I'm Belgian and, you know, we're weird.)
I've rooted my device this morning (really early). Don't know if it might help to get a solution...
I've been looking for a solution but I'm scared of doing something wrong with my ****ing TB version...
Thank you for your attention anyway!
EDIT: The serial starts with B80...
You rooted.
Next step is to flash CWM and then flash ICS. Kinda obvious...
Many guides have been posted on this forum since the release of ICS. You literally have to be blind to not find them.
Read the guides. Follow the instructions carefully.
Almost forgot--for the love of god, factory reset your TF before flashing ICS. The tards who didn't are having problems.
Thank you for your answer.
But I'm sorry not to be as pro as many of you are... What's obvious for you might me quite complicated for me. And I've found guides, but I'm just scared of doing something wrong with my TB version 'cause I didn't find information about it. But I will look further (and factory reset even if I don't believe in god...).
Thanelien said:
Thank you for your answer.
But I'm sorry not to be as pro as many of you are... What's obvious for you might me quite complicated for me. And I've found guides, but I'm just scared of doing something wrong with my TB version 'cause I didn't find information about it. But I will look further (and factory reset even if I don't believe in god...).
Click to expand...
Click to collapse
Guide here http://forum.xda-developers.com/showthread.php?t=1494230
Or here http://forum.xda-developers.com/showthread.php?t=1515727
For files
Try here http://forum.xda-developers.com/showthread.php?t=1518768
Or here http://forum.xda-developers.com/showthread.php?t=1245892
Or here http://forum.xda-developers.com/showthread.php?t=1514658
Only panic if you cant power up if you can get to recovery you can save your tablet
Sent from my Transformer TF101 using Tapatalk
I've done the reset to the factory settings but still don't have anyway to do the official update. I'm sorry to bother you but I've read the links you gave me and only found custom roms to install.
I've tried a lot of things but always fails.
I just want to update my transformer... It's not complicated, is it? Why I don't have the notification? Why do I get "there's no update available for your device"? Can aynybody explain me why?
I've spent 2 days to install it and I'm still at the same point (but rooted). I might be totally stupid but don't blame me if I am asking for help.
Hi Thanelien,
I'm also from Belgium and actually our Transformers have a different SKU... which means that we don't have exactly the same updates as the rest of the world.
So, usually we, poor Belgian, get the update more or less 6 days after the others... which means probably this Thursday.. You can also find an info on Twitter fron ASUS BENELUX confirming that "our" update will arrive end of the week... Otherwise the only other option is to change SKU... which means root the tablet...
Cheers
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Please be sure and thank the person who decides to do your homework for you.
:laugh:
FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)
Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.