Database Info

If you didn't WIPE before a firmware flash, don't post an "issue"!!!!!

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?

[Q] Flashed to cm-10.1.0-d2vzw.zip, Now The Camera Doesn't Work.

Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10

Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1

CZory91 said:
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
Click to expand...
Click to collapse
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.

Sythrix said:
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Click to expand...
Click to collapse
Well. Good and bad news. Good news is it's fixed. Bad news is there is no way that I can find of updating the firmware/modem while running an AOSP ROM. The first try worked great, wanted to see if I could update the firmware, no go. Restarted from the beginning again to see if taking the OTA updates while not rooted would allow me to have it work when rooted. Updates went through, everything went fine. Camera didn't work on AOSP still. So at least it works... I can deal without the firmware I guess, definitely worth a working camera and fully stable CM10.1.
Had some issues with the root, however a few tries at it and it eventually worked. This requires no input on your screen (first try SU popped up on me and I granted access, it rebooted and didn't root correctly) Edit: This time around I granted it and it worked. Heck if I know what/why. Just just keep doing it until it works, worked for me. Don't press anything the first try, then do so the second, etc.. Start it as soon as your device is connected to your computer and let it do it's thing. Don't let it have the chance to switch from its "installer" mode on the phone to a media device (unsure if that was the problem, but that seemed to be the reason why after the second round, 4th attempt).
Also, I had to battery pull and wipe data on the stock recovery listed as optional on the first link after it was rooted (WAIT UNTIL ODIN SAYS PASS before pulling the battery out when it's at the boot logo).
The only other thing I would say is that my phone initially came with the VRBLK3, and that may be the reason why this worked for me. Don't know. If your phone shipped with a different version, and my process doesn't work for you, try finding an MD5 with your shipped firmware version that will odin you to that version, and then continue with the root.

This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip

Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.

Sythrix said:
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Click to expand...
Click to collapse
It's in the first post on both CM10.1 threads (Q&A and Developer forums).

Sythrix said:
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Click to expand...
Click to collapse
Props on providing all that data with your question.. wish everyone was as thorough as that when needing help..
Sent from my Nexus 7 using Tapatalk 4 Beta

Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Did not and still does not work for me.
Sent from my SCH-I535 using Tapatalk 4 Beta

[Completed] Please help, anyone. Please!

Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!

RikkyRoe said:
Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!
Click to expand...
Click to collapse
You have already found good threads.
To recover a soft-bricked device, you basically have to flash back an official firmware for your device.
The guide you found was for the GT-I9100G, which is a little bit different from your exact device model.
Here is another guide for other variants of the S2: [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED) by Phistachio.
As there is no "ready-to-go" recovery package available for your device model, you have to get an official/stock firmware for your device.
A link to possible firmware sources is in the first post of the guide you posted.
Flashing the stock firmware with Odin should fix the soft-brick.
If not, maybe a wipe data (= factory reset) in recovery mode (long press Volume UP + HOME + POWER) is needed additionally.
And rooting your device seems to be working with this too: [ROOT] Framaroot, a one-click apk to root some devices by alephzain ... I found some users confirming it working fine to root your device model.
If you still have issues and need further help, please ask in the [Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread by It_ler thread.
There we try to give detailed help for all variants of the S2.
Good luck !

Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.

RikkyRoe said:
Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.
Click to expand...
Click to collapse
As you have already posted in the help thread, this thread can be closed now.
Let's continue in the S2 help thread.
Thanks for your understanding!
Signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v9.1
Kernel: Stock XXU1BOE6 kernel
Recovery: TWRP recovery by Ktoonsez
Modem: XXU1POG1

Error! message when updating to 6.0.0(MRA58N)

Hey! I don't know if this is the right place, but I'll try to explain my problem.
Yesterday I got a notification of an update(think it's 6.0.0 (MRA58N)). Today, when I tried to install it I just got an "Error!" message.
I tried to reboot the phone, but nothing happened. It doesn't turn on. However, I can get it into that fastboot screen or what it's called.
Haven't had any problems before, and Im kind of a beginner on these technical issues regarding phones.
So could someone please explain what I should do(hopefully nothing to complicated).
Thanks!

That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?

dahawthorne said:
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
Click to expand...
Click to collapse
It was new when I bought it (april 2014). I have only installed updates when getting a notification on the phone. I got a notification to do an update yesterday. Did it today. But while updating it just stopped and said "Error!". Turn the phone off, tried to turn it on but nothing happened.
What's the easiest way to make the phone work again?
Have in mind that Im not experienced at all with these stuff . Never had had any problems before
Thanks

Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
(Oh, and at worst you can probably flash a new ROM. Don't get too worried just yet... )

dahawthorne said:
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
Click to expand...
Click to collapse
Yes, I updated to marshmallow a couple of weeks ago.
Yes, I was on about 75% battery when trying to update.
As far as I recall it was just the android guy and a red text saying Error! (well it said Fel! because it's in swedish.)
It started to install the updates, but just stopped halfway(rough estimate).
Hmm :/
EDIT: Yes, I've asked on other forums, and they have been saying to flash(it's called taht right?) But since I'm new to this stuff, I want to check all possible alternatives first. And if I decide to do this, I'll have to feel fully prepared on what to do, don't want to screw up things even more

To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.

dahawthorne said:
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
Click to expand...
Click to collapse
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?

I don't know - I suppose it's worth trying. But if the phone doesn't turn on, you'll have to go through the PC setup anyway so that you can work on the phone. Besides, it will come in very useful when you need to do any maintenance on the phone in future (if that's what you want).
Or is there a factory reset in stock recovery? I don't use it myself, so I don't know.

CoJonees said:
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
Click to expand...
Click to collapse
Wug's toolkit needs a fix. It will not load the new Mashmellow either

Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Both these threads are unavailable, possibly deleted.
Sent from my Nexus 5 using Tapatalk

beekay201 said:
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
@beekay
"Want to learn something instead of using a toolkit to do stuff for you?"
You convinced me, but I think that the NRT has a lot of great help in setting up a PC so that you can actually start learning about ADB/Fastboot manual commands.
Although I'd done some minor fastboot stuff before, I'd never done the full Monty and installed a ROM, but I found the experience strangely pleasurable...

@op found help yet :what::what::what::what:

I need help with upgrading - Samsung Galaxy W (SGH-T679M)

I'm searching these forums, the web, every single website, and I still haven't came across a solution. Cyanogen, clockworkmod, they don't want to cooperate. I really am desperate now.
I'm trying to find a way to easily run a ROM on my phone, or maybe just install it. I'm aiming for Kitkat, but I have no idea how, as almost all of the posts on this forum contain broken links. Please, someone help!!!
Alex

Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer

Pachacouti said:
Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer
Click to expand...
Click to collapse
Okay.
My phone is a Samsung Galaxy W. It's model number is SGH-T679M and it is currently running Gingerbread.
And so I wanted to change that version because... Gingerbread is unsupported, right? So I landed on this forum first, trying out all the ways that I could, and most of them lead me to dead links as I said.
So I went on different web pages, the Android subreddit, all that. Ended up finding this zip file supposedly containing KitKat or something earlier.
I tried to install it how they told me. Already knew how to go into recovery mode, then it told me to go to the apply update from sd card (used the internal storage instead because i could) and it said the MODEL NUMBER WAS WRONG.
It was for the Samsung Exhibit II, model I8150, and that makes no sense. Because they are LITERALLY THE SAME PHONE.
Thought this was gonna be simple but it was being rough on me. This is why I need help, because I honestly don't know what to do anymore. It is so confusing.

Look at this:
h**ps://www.youtube.com/watch?v=et0AnYkBlc4
correct the link above copy n paste in your browser
Then say if you can handle the work, nothing more. If you are up for it, your best here

Pachacouti said:
Look at this:
h**ps://www.you tube.com/watch?v=et0AnYkBlc4
Then say if you can handle the work, nothing more. If you are up for it, your best here
Click to expand...
Click to collapse
Thank you, I will try it. I'll keep you updated if i didn't mess something up lol
Sincerely, Alex