Related
hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?
Sure!
If you had backup everything (most important thing is ROM) and with the term everything I mean EVERYTHING (mp3, images on SD etc etc) you can now flash from CWM the .zip you want.
I'm on teamhacksung's one (still ICS) so I don't know well the procedure to flash it,
but on the thread it's all documented!
Hope to have another ICS soon !
ext4 doesnt matter?
i just flash roms thats it?
If you wanna be 100% sure "downconvert" to RFS again, backup again, then flash what you want!
2 backups is better than 1.
xunair said:
hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?
Click to expand...
Click to collapse
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!
ok im gona do it now
thanks alot guys
stesancri said:
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!
Click to expand...
Click to collapse
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!
bedo1987 said:
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!
Click to expand...
Click to collapse
True! Once you try that...you'll never come back!
be sure
just be sure of what you were doing read understand all of the instructions, im a bit confuse lately but the urge of me having a custom ROMs running on my GS make's me realize i can do it, but of course by the help of our fellow android user..if i can do it u can also..anyways give it shot...
you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week
pzayx said:
you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week
Click to expand...
Click to collapse
Hehe, more like 2 days it seems for me..
Good luck.
I did it yesterday for the first time... (flashing a Rom ofcourse ) And it was easier than I thought! Just do it.
It's just about follow the instructions!
bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And experience.
jsolhac said:
And experience.
Click to expand...
Click to collapse
bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And self research with the help of XDA and Google
People are saying its hard to brick SGS.
There is 1 golden rule backup whatever you can before flashing (most important thing is backing up /efs partition because there are all data describing your individual phone egz IMEI number).
When I flashed ICS I couldn't get network signal so I had to restore my /efs and it worked.
It is hard to brick when you can get inside recovery & download mode, otherwise not so much ;-)
Only play around with ROM's if the 3 buttons combo work
Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol
josueciz said:
Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol
Click to expand...
Click to collapse
Twice same phone? then it look like you didn't bricked it at all.
For me and probably most of people definition of bricking is:
-you cant get into download mode (semi brick)
-you cant get into download mode using a jig plug (only service can help you then but warranty doesn't cover this so it depends on luck)
-you lost your /efs (no backup anywhere) (only service can help you then but warranty doesn't cover this so it depends on luck)
-and I guess other option could be you messed up with bootloader and cant reflash it ;/
Ok my question seems trivial but I just need to know the proper way to flash roms on the Note. I am not new to flashing roms and coming from HTC phones it is very simple to me using AmonRa recovery. CWM is nothing new to me either.
My GNote is a XXKJ4. Can I flash a rom that is not a XXKJ4? Perhaps the XXLA6 or XXLA4?
I tried to flash Checkrom (LA6) from my external_sd location directly from CWM recovery and received a boot loop. I wipe the data, cache, dalvik cache and still get the boot loop. I made a CMW backup beforehand and was able to get back to normal for now. But I really want to try different ROMS.
Did I miss anything?
a little assistance please....
thanks.
Not to sound rude or anything but YouTube has all the answers.
The most important thing to do before flashing anything is to read and re-read the instructions provided by the dev.
There's no universal answer to your question, because different Roms have different flashing procedures. Criskelo, for instance, is a non-wipe one, Cassie's XtraLite has a 3-step rebooting protocol etc.
I cannot stress read and re-read bit enough. Each and every day here you'll see tons of retards who flash everything in sight without bothering to read the first (or 2nd) thread post where it is explained how it's done. Then there are cries for help, gripes, whines, women and song.
As for CheckROM, this is what they say about bootloops:
Q: After Installing your ROM I'm getting bootloops/boot issues?
A: Do the following steps:
Take out the battery
Put the battery back in
Get into Recovery
Wipe Everything
Flash my ROM <-----(meaning flash it one more time)
Done!
Hope this helps.
chasmodo said:
I cannot stress read and re-read bit enough. Each and every day here you'll see tons of retards who flash everything in sight without bothering to read the first (or 2nd) thread post where it is explained how it's done. Then there are cries for help, gripes, whines, women and song.
Click to expand...
Click to collapse
I could not agree more (and very eloquent!)
I read for days before going for root, and more days before going for the kernel. When doing that it worked well first time.
Next, ROMs ...
I also come from HTC and it seems strange when reading Samsung instructions with Otis and Kies and PDA. I assume essentially everything is the same as with HTC phones once you have a clockwork recovery you can flash and backup all you like.
I understand all information is already accessible through Google, but can someone explain the roles and importance of Otis and Kies.
As I see it Kies is like HTC sync, Otis is like fastboot or adb is this correct?
jambamkin said:
I also come from HTC and it seems strange when reading Samsung instructions with Otis and Kies and PDA. I assume essentially everything is the same as with HTC phones once you have a clockwork recovery you can flash and backup all you like.
I understand all information is already accessible through Google, but can someone explain the roles and importance of Otis and Kies.
As I see it Kies is like HTC sync, Otis is like fastboot or adb is this correct?
Click to expand...
Click to collapse
That's what i get yeah..i only install Roms through either mobile odin pro or cwm. I have never installed odin or kies for my pc.
Sent from my GT-N7000
jambamkin said:
can someone explain the roles and importance of Otis and Kies.
Click to expand...
Click to collapse
They are very important, they are the first thing one uninstalls from all Roms with Titanium Backup, Root Uninstaller or whatever.
I attempted to root my SGS (which had stock Gingerbread Value 2.3.6) using a guide on the Snappyguides blogspot page (the system won't let me, as a newbie, post the URL).
Odin did its thing and then the Samsung Galaxy screen came up (just the white lettering, not the multicoloured animated S) and then... nothing. It just stayed like that for about five seconds, then the white Samsung Galaxy S came up again, then the blank screen ad infinitum.
I can access the download screen and I can access the recovery screen (which does seem to indicate that ClockworkMod v2.5.1.0 has been installed). The trouble is that none of the options seem to do anything.
I have tried searching the forum for similar problems and have read the sticky. The only answers I seem to have been able to find so far suggest flashing a new Rom.
Before I go this far, is flashing a new Rom really necessary in this instance? I have never done this procedure before, so I'm wary of messing things up even further. But obviously if the phone is past the point of no return as far as the stock Rom is concerned, then that'll be what I have to do.
I'd appreciate some advice before doing anything else to my phone though.
I now seem to be able to get the recovery menu options to respond, so maybe all is not lost. Have set it to root and it's currently converting to EXT4 and is about halfway through that.
I'm hoping once that's done, it'll be bootable.
If not, what do I need to do to make the SGS boot again? Is there any way of getting back to stock or can I only flash a stock rom back on?
Nope, still not booting. It just keeps going to the Samsung I9000 white lettering, stays there for five seconds, goes blank for five seconds, then the white lettering goes back and on, off like that forever.
So... anyone willing to help?
...
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Lexrsk said:
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Click to expand...
Click to collapse
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
evilcartman2 said:
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
Click to expand...
Click to collapse
I'll help u, I went through this when I was a noob and because I didn't know about xda I had to just figure a way out, I am sorry to say but u have soft bricked your phone, luckily its not hard to unbrick, here's a link to a post i made the other day with proper guides that I use often and they are noob friendly, the files u need to download are there but it 2.3.3 and it JW4 but it will be a start to get ur phone back to life,
If you like my posts hit thanks
Here the link http://forum.xda-developers.com/showthread.php?p=25572245
If you like my posts hit thanks
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
evilcartman2 said:
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
Click to expand...
Click to collapse
Yip I guess that is right. I have never tried it but yes it should work
If you like my posts hit thanks
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Yeah that or the wrong root file for ur baseband
If you like my posts hit thanks
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Check in about phone for the kernel version. for example mine is 2.6.35.7-I9000TDVJV6-CL530973
The important part is the bold text.
search the link that i posted earlier for a odin version and flash as PDA
Good luck
Evilcartman, when u wanna get me help find me on the I9000 q&a-ask me anything I got the answer thread, it where I spend most of my time.
If you like my posts hit thanks
Okay so..
I have to spend my days serving my time in the finnish army, so I am a bit clueless of the GNote scene from time to time. I ran Midnote LPF (?) ICS for quite some time and then tried to decrease my DPI. Unfortunately, this resulted in a bootloop, and I tried to fix it by factory reset. Whoop-de-doo. I cancelled it mid way though, if I remember correctly.
8 hours later I got my hands on a computer and tried flashing a firmware with pc-odin. Didn't work. Here's where I've gotten so far:
Flashing PIT and CWM based recovery v5.0.2.7
Flashing Kingdroid ICS Via CWM based recovery or AbyssNote causes phone to reboot at "Flashing /system"
Trying to flash stock GB via Odin hangs at "factoryfs.img"
Tried to reflash bootloader, no help.
Currently trying out flashing GB rom via CWM recovery.
I need quick help as I am going to a Battle-excercise for two weeks tomorrow and I'd really appreciate have my GNote working by that time..
Thank you very much in advance
EDIT: I can confirm that the partinioning guide in http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12 IS INDEED an effective guide to un-superbrick. The guide can be very intimidating for beginners, so bear that in mind. I ran into a faulty partition on the UMS folder, and repositioning it did the trick. Then I just rebooted recovery and installed KingDroid 7.0 GB and it opened like a charm.
Big chance you have a superbrick now, sending it to Samsung repair center is the only option. Search for "superbrick" in this forum. You'll find my name also
I had to send in my device and probably get it back on wednesday...with a new mainboard. On my device a recovery always ended at /system and a pc odin reflash always stopped at factoryfs.img
The last option without sending in your device is following a few threads here. Some posters were talking about a possible solution.
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Yep, that's one of the posts. This was way too complicated for me.
I've send my Note to a samsung service center and they repaired it without any costs. I only reset the binary counter to zero and (partly...because of factoryfs.img) flashed a stock rom before sending the device.
Morality said:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Click to expand...
Click to collapse
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
joe2316 said:
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
Click to expand...
Click to collapse
Im not gonna lie, It was a scary as **** experience. Currently trying to install.. well.. anything.
oh
my
GOD
ITS ALIVE OH MY GOD ITS ALIVE...
the guide worked.. But definately not recommended for beginners, as the dos prompt might be quite intimidating. but the thing definately works.
I found a bad partition from UMS and just relocated it a bit. I think I lost 3gb of space (not sure, will check on that), and unfortunately it formats your INTERNAL sdcard, as i backuped my external one.. BUT WHATEVER
JESUS CHRIST IT WORKED. After following the guide, recovery needed to be rebooted and then I just installed Kingdroid 7.0 GB. The only problem that appeared was that the Samsung Logo screen lasted longer than usually when flashing new firmware. Will update OP.
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.