Question about Master's Kana - Vibrant Q&A, Help & Troubleshooting

I see that the topic has been closed due to some people claiming it bricks devices when you try and flash something over it. My question is to Master, will you continue to support and update this ROM? I didn't plan on flashing Kana 2, but Kana 3 would have been what I flashed since I like to flash every other upgrade.
If not, could it be possible that the people who claimed to be bricked didn't disable Voodoo before they flashed another rom?
Lastly, can I ODIN back to JI6 even though the Kana rom was a 2.2 rom with Voodoo enabled?

I guess I'll just try ODIN'ing later.

I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin

jmcghee1973 said:
I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin
Click to expand...
Click to collapse
The ROM didn't even have the Sbl.bin

Masterâ„¢ said:
The ROM didn't even have the Sbl.bin
Click to expand...
Click to collapse
Right..I know which made the stories even better...lmao

Master! Do you plan on updating Kana? I love the rom.

jmcghee1973 said:
I just think its people not following directions and new people just wanting to have the newest, latest thing and have no idea what it is they're doing. Its just easier to blame the mistakes on a faulty bootloader then to accept the fact they screwed up....just sayin
Click to expand...
Click to collapse
No. It's not because "directions were not followed properly" or because I "had no idea what I was doing". I personally at this point am not blaming Master for what happened either. As strange as it sounds and as much as I know it's easy to think "oh well they must have done something wrong" I assure you I didn't. I flashed a rom through clockwork the exact same way that I and everybody else does and has done countless times before, the install finished, I selected "reboot system now" from the clockwork recovery main menu, and that's it, phone was DOA. Trust me, I know what I am doing.

Alkaloid said:
No. It's not because "directions were not followed properly" or because I "had no idea what I was doing". I personally at this point am not blaming Master for what happened either. As strange as it sounds and as much as I know it's easy to think "oh well they must have done something wrong" I assure you I didn't. I flashed a rom through clockwork the exact same way that I and everybody else does and has done countless times before, the install finished, I selected "reboot system now" from the clockwork recovery main menu, and that's it, phone was DOA. Trust me, I know what I am doing.
Click to expand...
Click to collapse
I didn't single you out....and don't feel in any way that I was personally attacking you..I wasn't. I tried to help you on your problem yesterday but I don't feel the majority of the "bricks" happening can be blamed on a new sbl.bin...It may contribute to a few...possible... and this was a ROM without that file added...
So my comments are pertaining to this rom since this rom was the one in the subject line.

jmcghee1973 said:
I didn't single you out....and don't feel in any way that I was personally attacking you..I wasn't. I tried to help you on your problem yesterday but I don't feel the majority of the "bricks" happening can be blamed on a new sbl.bin...It may contribute to a few...possible... and this was a ROM without that file added...
So my comments are pertaining to this rom since this rom was the one in the subject line.
Click to expand...
Click to collapse
I know, and I appreciate you trying to help me. I apologize if I came off like an asshole. I'm just frustrated as hell, and on edge.

I think we got off track. Could I ODIN this back to stock with Voodoo enabled or do I have to turn it off before I do? LoL

No need to disable voodoo when flashing through Odin. It formats the partitions affected by voodoo back to the standard rfs file system.

*sends thanks*
I appreciate it. I don't mind ODIN'ing first before I flash a new rom just in case. I plan on sticking with this rom for a bit, it's nice.

It's generally a good idea to To flash back to stock via Odin between roms. I can tell you that I will never make the mistake of not doing so ever again.

Related

[Q] What is the best way to backup my LG P500?

Hi everyone,
I want to root my phone (will use this tutorial http://forum.xda-developers.com/showthread.php?t=1200167 - I dont understand much about this but ohh well) and i read this thread (http://forum.xda-developers.com/showthread.php?t=900905) so i kinda knew what i was doing. And as i understood from that thread, the best way to backup all my data (like creating my custom rom right?) is with nandroid! But what is nandroid and how can i backup my data with it?
I just would like some suggestions from you! what i should do and how i should do it before i root my phone?
Thank you in advance!
After root install custom recovery, reboot phone to it and choose backup, wait and its done.
send from Andy's PHOENIX.
i didnt quite understood the install custom recovery! how can i install it? i can only do a backup of my recovery when i root my phone?
would be awesome if i could have a private chat with someone who could lose some of their time explaining me this!
Palmaaa said:
i didnt quite understood the install custom recovery! how can i install it? i can only do a backup of my recovery when i root my phone?
would be awesome if i could have a private chat with someone who could lose some of their time explaining me this!
Click to expand...
Click to collapse
After rooting your phone, please read this how-to and you should able to install recovery just fine
http://forum.xda-developers.com/showthread.php?t=1146566
BTW, prefer installing TWRP v1.0.3.13b recovery instead of the buggy CWM or old amonra
I forgot to mention that my knowledge about this is basically "0"! So i would thank you if you could explain a little better!
Sorry and thank you once again for understanding!
Palmaaa said:
I forgot to mention that my knowledge about this is basically "0"! So i would thank you if you could explain a little better!
Sorry and thank you once again for understanding!
Click to expand...
Click to collapse
ok, my understanding is that in order to use nandroid backup, your phone has to be rooted first.
in the link you posted about rooting GB 2.3.3 ROM, it only mentioned using astro file manager to backup the apps. nowhere it mentioned nandroid backup.
if you are rooting a froyo(2.2/2.2.x) based phone, it is really quite simple. I do not think any kind of backup is needed at all.
Well i finished rooting my phone. Went well with no problems. Quite simple in fact, but what i wanted to know is, imagine i install a custom rom (btw, i know kernel improves the performance of your phone, so what does a custom rom does?) that i suddenly dont like, so i want to get back to my hold one. How can i backup my original rom?
Palmaaa said:
Well i finished rooting my phone. Went well with no problems. Quite simple in fact, but what i wanted to know is, imagine i install a custom rom (btw, i know kernel improves the performance of your phone, so what does a custom rom does?) that i suddenly dont like, so i want to get back to my hold one. How can i backup my original rom?
Click to expand...
Click to collapse
OK, my suggestion is to use ROM manager from market. quite noob friendly.
it has backup/restore option right there. just follow the menu.
Oh ok! thank you very much for your time! i'll remember myself to use that app when i think of getting a new rom! probably tomorrow or so!
again, thank you!
Palmaaa said:
Oh ok! thank you very much for your time! i'll remember myself to use that app when i think of getting a new rom! probably tomorrow or so!
again, thank you!
Click to expand...
Click to collapse
To use ROM Manager features you must inevitable flash CWM recovery and to do so you have two options, first beign flashing it via ROM Manager that can cause a bricked phone, or use recovery flashing how-to i posted earlier and install buggy and crappy CWM from there, thats why i recommend TWRP recovery
YOU HAVE BEEN WARNED
TakamineSubasa said:
To use ROM Manager features you must inevitable flash CWM recovery and to do so you either have two options, first beign flashing it via ROM Manager that can cause a bricked phone, or use recovery flashing how-to i posted earlier and install buggy and crappy CWM from there, thats why i recommend TWRP recovery
YOU HAVE BEEN WARNED
Click to expand...
Click to collapse
thanks for the warning, but CWM has been working great for me. no problem at all.
yeah, do proceed with caution.
calhotel said:
thanks for the warning, but CWM has been working great for me. no problem at all.
yeah, do proceed with caution.
Click to expand...
Click to collapse
Ya, its not that it'll break phone but many features dont go well like zip signature verification which verifies that everything is correct in the zip and so the flash process will not cause a corrupted filesystem, mmm the amount of "No" confirmations are frankly ridiculous... some users reported flashing problems with the last version 5.0.2.0... Cannot repair SD Card, doesnt have touchscreen support and it cannot make selective backups which frankly s%x cause you wasted time and space... (also the fact that doesnt have themes support and cant compress backups...)
And also the fact tha maaany maaany users including me have bricked their phones flashing via ROM Manager... And also the fact that wiping cache & dalvik with CWM will cause conflict with a2sd script users...
Anyway @Palmaaa if you want to risk your phone flash via rom manager... if you want a crappy recovery flash CWM.... if you want the best and safest recovery then prefer TWRP v1.0.3.13b, your phone and your physical keys will say thank you
I appreciate your warning! ill try to search a bit more about what im going to do next!
Never use ROM manager. It breaks the phone and it gets stuck at LG logo on boot. Many users have reported the issue. Use the recovery for flashing and taking backups.
gkarthik16 said:
Never use ROM manager. It breaks the phone and it gets stuck at LG logo on boot. Many users have reported the issue. Use the recovery for flashing and taking backups.
Click to expand...
Click to collapse
it never happened to me. look at the rating on market, do you think all the users are morons?
yeah, you guys had some bad experiences and hated this thing with a passion, but get the fact straight. sometimes it may not be rom manager but something else that bricked your phone.
not trying to argue or anything. just present with another opinion.
calhotel said:
it never happened to me. look at the rating on market, do you think all the users are morons?
yeah, you guys had some bad experiences and hated this thing with a passion, but get the fact straight. sometimes it may not be rom manager but something else that bricked your phone.
not trying to argue or anything. just present with another opinion.
Click to expand...
Click to collapse
sorry that you dont want to argue but, boy are you kidding me with that rating thing?? do you really think that every single person in market (and that rated that thing) has an Optimus One?? you are sooo naive....
In our phone p500 or optimus one, 01, OO, ROM Manager is very well known for bricking our devices....
Oh, and btw seems that you doesnt have a clue on how benefical is to have a properly working zip verification feature and also the plethora of other useful functions TWRP has..
kthnxbye
calhotel said:
it never happened to me. look at the rating on market, do you think all the users are morons?
yeah, you guys had some bad experiences and hated this thing with a passion, but get the fact straight. sometimes it may not be rom manager but something else that bricked your phone.
not trying to argue or anything. just present with another opinion.
Click to expand...
Click to collapse
Yeah, none of them are morons. For every other widget and live wallpaper app, the 'intelligent' users rate the app 1 star just because they cannot find it under the app drawer. So keeping in mind the 'intelligent' users on the market, I don't give a **** about the ratings.
It doesn't make a difference if you did not face issues. There are many people who have faced the issue and ONLY because of ROM manager. Just wanted to prevent another user from facing a similar issue and instead use the clean and safe method of custom recovery.
You tone showed that you're arguing. That last sentence doesn't make any sense.
TakamineSubasa said:
sorry that you dont want to argue but, boy are you kidding me with that rating thing?? do you really think that every single person in market (and that rated that thing) has an Optimus One?? you are sooo naive....
In our phone p500 or optimus one, 01, OO, ROM Manager is very well known for bricking our devices....
Oh, and btw seems that you doesnt have a clue on how benefical is to have a properly working zip verification feature and also the plethora of other useful functions TWRP has..
kthnxbye
Click to expand...
Click to collapse
statistically, I trust that rating more than you guys' opinion. sorry to tell you the truth.
TWRP, yeah, that's nice. but CWD worked for me, so?
calhotel said:
statistically, I trust that rating more than you guys' opinion. sorry to tell you the truth.
TWRP, yeah, that's nice. but CWD worked for me, so?
Click to expand...
Click to collapse
Dude you are not helping.... encouraging users and specially new users to install something that has a high risk to screw and brick ur phone is not a way of helping them, if rom manager worked for you its fine, but maybe for another user it'll break his phone, ROM Manager is an unreliable app and method to use recoveries....... Ohh and btw user can install whatever he wants im just guiding and encouraging him to install the safest and most trustworthy and functional recovery of all, and is TWRP v1.0.3.13b
Have phun when ur volume keys, menu or any other button stops working LOLz
cya
TakamineSubasa said:
Dude you are not helping.... encouraging users and specially new users to install something that has a high risk to screw and brick ur phone is not a way of helping them, if rom manager worked for you its fine, but maybe for another user it'll break his phone, ROM Manager is an unreliable app and method to use recoveries....... Ohh and btw user can install whatever he wants im just guiding and encouraging him to install the safest and most trustworthy and functional recovery of all, and is TWRP v1.0.3.13b
cya
Click to expand...
Click to collapse
thanks, I think you already scared a lot of ppl off. lol. maybe I will try TWRP one day.
for me, that's fine. I have no axe to grind.

Why does CM mess up sooo many noobs phones?

100% of every person I read , get tweeted on or emailed...
that has messed up their phone and needs help.. is always involving a CM rom..
the reason I never have messed with CM is it seems so unstandard and I continue to see phone issues either during flash to or ppl trying to get back to stock or back to a CWM style ROM..
what gives?
G1toVibrant said:
100% of every person I read , get tweeted on or emailed...
that has messed up their phone and needs help.. is always involving a CM rom..
the reason I never have messed with CM is it seems so unstandard and I continue to see phone issues either during flash to or ppl trying to get back to stock or back to a CWM style ROM..
what gives?
Click to expand...
Click to collapse
Because they're noobs and fail to read the op, and just do what they want, and when they mess up, they have no clue what they've done, nor howto even begin to troubleshoot their own mistakes.
Cm is non-standard because 1. It's entirely different code and 2. The partition types, and format/filesystems has changed from bml/RFS/ext4 to mtd/yaffs2. And because of the partition stuff, you MUST use Odin or heimdall and jfd to go back. And they don't read the giant red letters in the op and then complain about stuff when it "doesn't work".
Sent from my HTC Sensation 4G using XDA App

Reverting to Stock Issue Inquiry

Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.

Modem Re-Partition Help

Alright I need some help please. First off i need to re-partition my modem and i have no idea how to. Due to constant flashing it screwed something up and i can no longer receive data coverage. Now i looked and looked and i couldn't find anything. So i decided to start a new thread. I need a step by step walk through this will be my first time doing it. And i really don't want to say this cuz i am myself a noob (please no noob's on this one i cant afford another phone). i have had some help by some other people witch was good advice but i have exhausted my options here. I have tried everything from flashing new modems to flashing new ROMS to odin'ing back to stock A.T.T. I'm Stumped i have done absolutely everything i can think of to this phone and still no data. I have the correct apn settings i know that. I'm just completely stumped i dont know what to do.
Phone: Att Samsung Galaxy Note SGH-I717
Android Version: 2.3.6
Okay brother ....I've been digging for gold, And to clarify your issue, you do not need to partition a modem.
You need to repair the device partitions.
Now, this doesn't mean that you should just start changing partitions using CWM or TWRP, or ODIN.
What it does mean, is you need to let Odin do it for you.
I won't take the time to go into PIT files and mapping, as we both would explode from boredom in 10 seconds.
But I will tell you that there are different levels of depth regarding roms and how they flash.
Odin stock roms go pretty deep, but sometimes not deep enough, and Odin will sometimes ignore the PIT remapping function during the flash if the file structure is already present on the device.
That being said, an Odin return to stock is not always successful when seeking a complete restructuring of the device partitions.
However, I have located a rom (factory ICS leak) that contains the entire device partition package, the PIT.IMG Package, baseband, and factory ICS image.
By using this one click Odin file, you will force the device back to factory status using ICS.
This will allow you to push the UCLE2 modem again once you root using CWM.
The ICS root method is slightly different than GB, so check the ICS root info in the super thread before rooting again. This will prevent errors or worse if done incorrectly.
The link below is the most complete package I can find, and includes files not found in the GB Odin.tar.
The file is good. And has been used many times to repair issues we see here.
Take your Time, and read read read....especially when rooting again.
Note: prior to pushing this Odin file, you "MUST" wipe all data and factory reset the device to ensure a "CLEAN" build of the file structure.
And once flashing is complete, follow the root method for ICS... And once rooted, flash the modem by using CWM.
You will need to manually add and save your new APN settings.
Once these steps are complete, you should have a working device with data..
If not, you may have device damage of some kind, which requires a repair of the device by an authorized service center.
I'm uncertain of the software having the ability to damage hardware, but I'm certain it is possible, and you may have this issue.
But if you are willing to try this rom, it will likely help.
Beyond my advice above, I've got nothing more to offer, other than moral support.
Of Course, standard disclaimers apply, and you do this at your own risk ...
Best of luck to you ....g
http://rootzwiki.com/topic/25980-sgh-i717ucle2-official-leak/
alright how do i flash in odin just like a normal .tar file????
nope didnt work
alright man i fill completely stupid 180% i put my girl friends att micro sim in my note it turns out my sim card is bad cuz i got her 4g as soon i i put her sim in but thank u at the same time as i apologize to you cuz i have learned alot from u and u have helped me alot through this issue of mine i fill so dumb right now i truly am sorry for the hassle i have put u through in the last couple of days
Deleted... not a useful comment
Sk84all20 said:
alright man i fill completely stupid 180% i put my girl friends att micro sim in my note it turns out my sim card is bad cuz i got her 4g as soon i i put her sim in but thank u at the same time as i apologize to you cuz i have learned alot from u and u have helped me alot through this issue of mine i fill so dumb right now i truly am sorry for the hassle i have put u through in the last couple of days
Click to expand...
Click to collapse
Dont feel stupid.
We all come here to learn about devices, and the problems that are associated with them.
If nothing else, you've learned many things about Odin, and the importance of taking your time with these things, and about proper setup of the device.
I'm pleased to hear that your device is not damaged, and you are up and running.....g
gregsarg said:
Dont feel stupid.
We all come here to learn about devices, and the problems that are associated with them.
If nothing else, you've learned many things about Odin, and the importance of taking your time with these things, and about proper setup of the device.
I'm pleased to hear that your device is not damaged, and you are up and running.....g
Click to expand...
Click to collapse
agreed, OP my last post wasn't intended to make you feel stupid, I do things exactly like this more than I'd care to admit and I facepalm a lot. I completely forgot to recommend trying different sim chip which is one of the things I always check. My brother gets tired of me stealing his sim card to test my phone haha.
Happy to hear your phone is working!
Thank u all for ur help greatly appreciate it
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I717 Back from the Dead....AWESOME THANKS!!!
WoW I just about wrote off my I717 after a botched JellyBean upgrade. Came across this file and thought it was too good to be true...but is wasn't...GREAT THANKS!!!

[Q] Upgraded to 2.3.6 Tried to unroot Ran Odin SOC doesn't work

Okay, before any of the regular contributors here say something nasty to me for asking a question that's been asked and answered, I want you to know that I have spent 2 days reading through -all- xda forums that might even -remotely- relate to my problem, without finding any answers. I also spent several hours searching all the common Android forums elsewhere, as well as, silly sites like Yahoo answers, etc., but have not been able to find the answer to my question. I'm the first to admit that reading the exorbitant amount of information in here causes my brain to short circuit due to all the numbers, versions, etc. It's like reading tax code; use C1.4.6 unless you've submitted b45.1. In that case, use d16.9, unless you've also filed a p32 in the last 2 years...if so, then....blah blah blah.
I love all you cell phone OS gurus and am quite envious of your ability to effortlessly wade through the technology involved in these phones. I wish, wholeheartedly, that I didn't have to ask any questions here because I know how irritated many of you become over people like me asking stupid questions, but I have no where else to turn. Believe me, if I could go elsewhere, I would, for your sake.
I was running 2.3.4, rooted, stock ROM. Froze the system with TB Pro to prevent the upgrade to 2.3.6. Unfroze it. Upgraded. Decided to unroot so I could sell my phone in favor of another. Ran Odin. Ran SuperOneClick. Ahhh...and there's the problem. SOC doesn't work with 2.3.6. So now, I don't know what to do. My phone is half rooted. I can't unroot and I can't reroot. I get the triangle, but TB Pro doesn't work because I'm not rooted, well. sort of not rooted. I guess I'm a little rooted. I don't know what to do next mainly because, every time I find what I think is a solution, I find another source that says, "DON'T DO IT! YOU'LL BRICK YOUR PHONE!" So, here I am, hoping someone will point me in the right direction without chastising me for asking a stupid question. I checked the solution in here and it's great, except, and I quote "Not working for KK6 2.3.6"
Thanks for any help....
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
tunie said:
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
Click to expand...
Click to collapse
You can't have a "half rooted" phone, and it wouldn't matter at all anyway since you're going to be booting into download mode in order to flash to stock.
Sent from my Zanpakuto using Getsuga Tensho!
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
When I rooted so very long ago, I used SGH-I777_ClockworkMod-Recovery_5.0.2.3 that I downloaded with su-3.0-efgh-signed. At the time, I didn't understand what this was. I only understood that this would root my phone. I didn't want to flash any custom ROM's because, to this day, I really don't understand what a ROM is. Yes, I've read about it. Still don't get it. So, did I flash a custom ROM? As far as I knew, all I did was root so I could use TBPro to backup and freeze, and use LBE to keep my information as private as possible.
<edit> So I've just reread many of your posts. You really are great at explaining this stuff and I thank you for that. It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Thank you, again. I swear I'll be out of everyone's hair in here as soon as is humanly possible.
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Pirateghost said:
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
Click to expand...
Click to collapse
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
tunie said:
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
Click to expand...
Click to collapse
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
tunie said:
It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Click to expand...
Click to collapse
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Pirateghost said:
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you. I give up. Really, I do.
creepyncrawly said:
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Click to expand...
Click to collapse
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
tunie said:
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
Click to expand...
Click to collapse
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Pirateghost said:
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Click to expand...
Click to collapse
Just want to insure that I've relayed all the necessary information, correctly. I guess I have. Thank you and I'm sorry I took anyone's time.
tunie said:
Well thank you. I give up. Really, I do.
Click to expand...
Click to collapse
That dreaded yellow triangle show up when you flash a custom (non-stock) kernel. When you flash a stock kernel, it will go away. So... if you flash back to stock like I suggested, it will go away.
Pm me if you need more assistance
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Thank you. It worked like a charm. Back to stock. Wonderful. Thank you so much. It wasn't as much a nail-biter as I thought it would be.

Categories

Resources