EDIT: Let's keep this thread focused on how we can move past old methods, and make some progress towards modding. Thanks, and any relevant input is welcome.
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
lkrasner said:
Alright. we can get recovery most likely on MF3. many locked moto devices do with a bootstrap. the problem is that if the system breaks, so does recovery, so the actual part about recovery is useless. therefore, in order to be safe, we need a signed stock firmware. this is how it works with My A2. we have a solid recovery that just hijacks the boot, and if you bootloop, you can FXZ (similar to flashing with odin) back to stock. We can now even get custom kernels through kexec, but even without it, there were working aosp/cm based roms.
So, what we really need here to make any progress is a flashable MF3 firmware, so we can get out of soft bricks. Anyone got any ideas?
Click to expand...
Click to collapse
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
scott14719 said:
There's a few threads about this already which contain several ideas...some tried, some theorized. Why make a new one if it isn't bringing anything new to the table?
Don't get me wrong, your help is MUCH appreciated, it's just a problem when the forum starts getting filled up with information that already exists in other threads.
I think Adam Outler's "Let's get this bootloader unlocked" thread in the "Development" section would be a good place to contribute or maybe even the 'Software Update" thread in the General section.
Click to expand...
Click to collapse
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Part of the problem is...this isnt motorola...from what ive been reading is the bootloader checks the phone on boot and overrights any custom recovery with a stock one. Im nkt saying it isnt possible to get a recovery with out an unlock or loki like exploit because I really dont know...actually, isnt the previous loki exploit prettt mucg what your talking about? A way to get recovery and flash with out a bootloader unlock
Although I do agree we need a safe way to return to stock (firmware leak/upload for odin) before we can even try and start experimenting
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it. I am trying to learn quickly, and as you all know, devices are very different.
From what I understand, LOKI allows recovery to be overwritten, or is at least more permanent. What happens if you were to totally kill your system, could you still get into recovery with loki?
I understand that this is not motorola, and I am not trying to be stubborn here, but I fell like the same basic boot hijack that a ton of locked devices use should work.
lkrasner said:
Well, if anyone has a link to something that actually explains how loki works, I would appreciate it.
Click to expand...
Click to collapse
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
and http://forum.xda-developers.com/showthread.php?t=2292157
lkrasner said:
Sorry, I will admit I jumped in a little quick here. My main point is that it should not be too difficult to get custom recovery working. I am just afraid to do it until I know I can recover, as I am sure the process will involve multiple bricks.
Click to expand...
Click to collapse
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
scott14719 said:
Please don't apologize, I have no doubt you are going to be a valuable part of what is going to go on with this phone. The only reason I brought up not making a new thread is because of the fragmentation of information different threads cause. Here is the link to Adam's Bootloader Unlock thread:
http://forum.xda-developers.com/showthread.php?t=2255644
Adam has requested (though many didn't respect his request) to not post anything in that thread that doesn't make progress in unlocking the bootloader.
That is why I also mentioned maybe using the "software update" thread as a thread to keep everything together in:
http://forum.xda-developers.com/showthread.php?t=2357039
This thread we are in now can be used as such a thread as well, I just think it is counter productive to have 3 or 4 or more threads going about the same (general) thing. The fragmentation it creates is confusing and time consuming.
So maybe we all need to decide where (which thread) to put all of the bootloader unlock / recovery information into to prevent fragmentation? Maybe rename this thread something like "Bootloader unlock discussion thread" so that ideas and discussion can occur here and any firm findings can be transferred to Adam's thread? If we do this, it will be important to import or at least take into consideration what has already been mentioned and tried in all of the other threads so we don't waste time on something that has already been done or tried.
Here is a link to the "LOKI" thread:
http://forum.xda-developers.com/showthread.php?t=2292157
There are links in the OP of that thread to give better technical information about what LOKI does and how it is used.
Click to expand...
Click to collapse
Thanks, It still looks to me like loki is a bit more advanced than what I am talking about, though the underlying principle is the same. LOKI allows the phone to actually boot a kernel (or recovery kernel) a boot hijack just loads some files on top of what is already running.
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
ashaton said:
Here is Adam's post where he sums up the boot sequence for the S4: http://forum.xda-developers.com/showpost.php?p=40980436&postcount=46
That may give you some guidance. Towards the end of that thread, Aou posted a possible leaked Samsung PIT file signer but I tested it and confirmed it wasn't actually signing PITs - just making them without the signature. I'm still doing a lot of research and don't have anything more to contribute right now unfortunately.
Click to expand...
Click to collapse
Thanks, I am sure that will prove helpful.
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
The entire thread is very interesting. Starting around "Post# 115" and beyond there is talk about (what i believe) you are trying to do with the bootstrap idea. Maybe it will help you.
scott14719 said:
This is Adam Outler's Samsung Galaxy S3 bootloader unlock thread. Though it is for the Verizon S3, it still goes very in depth about how the hardware and software are tightly interconnected. Many of the principals still apply to the S4 bootloader. As you can see, the S3 was unlocked via a leak (which is what I think it will take for the S4), but the information in this thread can be very helpful, especially the bootloader sequence parts.
http://forum.xda-developers.com/showthread.php?t=1769411
Click to expand...
Click to collapse
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
lkrasner said:
Thanks, this is what I like to see. the more info the better. If we can make sense of everything and compile a list of useful info, we aught to be able to get something done.
Click to expand...
Click to collapse
I edited my above post. I believe around post 115 and beyond of the above linked thread there is some information about the bootstrap idea you have.
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
I had edited my last post but I think this was missed
Theres instructions here on here to pull a firmware from a device...can anyone on mf3 try it? http://forum.xda-developers.com/showthread.php?t=1348392
-from there maybe we can package it into an odin tar, as heimdall currently can not flash system partition as our device isnt supported
At least that way we can possibly have a safe way back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
scott14719 said:
One potential problem is that bootloaders can not be pulled from devices. They have to be obtained through official firmware releases. I'm not sure if pulling the bootloader(s) from the MF3 OTA and inserting them into an MF3 image pulled from a device will equal an ODIN flashable TAR? I think the bootloader(s) in the MF3 OTA are somehow altered once flashed onto a phone. And because the altered bootloader can not be pulled from the device after the flash it could pose a problem to try and put the unaltered version (from the pre-installed MF3 OTA into a device image and create an ODin flashable TAR. Basically, I'm not sure the phone will accept a pre-flashed MF3 bootloader onto a phone that has already experienced a post flash MF3 bootloader. If that makes any sense? (LOL)
Click to expand...
Click to collapse
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Ahhhh I see...makes sense
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I'm just theorizing there from what I "think" I know. It still might be worth a try. The resulting TAR could:
1. Work, and if so we will have an ODIN flashable firmware for MF3. It doesn't matter if it is 'Frankenstein'd" or not...if it works it works!
2. Not work, but only fail in ODIN not causing anything to change or brick.
3. Not work and cause a soft or hard brick that can not be recovered from because it didn't work.
So, once again, finding someone to test the finished product out would be an issue. I'm guessing someone that is already hard bricked and already previously on MF3 could test because they already have nothing to lose (with JTAG not working for MF3).
I think Aou has deconstructed the MF3 OTA and pulled the bootloader(s) out of it. If someone can pull an MF3 image from their device and the bootloader can be added to it...and it can be made into a flashable TAR, maybe it would work. I don't think it will because of the reasons I listed in my last post...but it might.
Anyone willing to put it together and try it?
I think the problem is that it won't be signed. That is how it was with the a2. We just used fastboot but it would not flash an unsigned image
Sent from my Nexus 7 using xda premium
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
Click to expand...
Click to collapse
ashaton said:
I think Aou already made some MF3 tarballs for Odin in his stock MF3 thread: http://forum.xda-developers.com/showthread.php?t=2378946&highlight=mf3
He says they don't work because they aren't signed:
Click to expand...
Click to collapse
Yup, that's what I was saying. I can try to port a bootstrap cwm, but I really do not want to be the one to test it
Sent from my Nexus 7 using xda premium
Related
So I have been reading over in the development forums and it seems like a lot of users are having issues restoring backups with jt's recovery.
Most of them have ended up with bricked phones and no way to fix it cuz we are still lacking a full odin package for the charge.
Has anyone had success doing a restore in CWM?
Anyone? Please
This is something I'm going to get with imnuts on to fix. Just waiting for my charge to come in.
boostedjti said:
This is something I'm going to get with imnuts on to fix. Just waiting for my charge to come in.
Click to expand...
Click to collapse
Ok I figured someone would be working on it I just didnt know if everyone was affected by it or just a few people because i havent seen much talk about it. Also I figured maybe we should put a warning up so more people dont attempt to restore just to end up with a bricked phone.
Manjews said:
Ok I figured someone would be working on it I just didnt know if everyone was affected by it or just a few people because i havent seen much talk about it. Also I figured maybe we should put a warning up so more people dont attempt to restore just to end up with a bricked phone.
Click to expand...
Click to collapse
I made a post similar to this in the cwm thread. Thanks for posting it up here too. I have a feeling it's more then just user error, which is the first thing everyone wants to blame something on, and typically the case. Just not feeling like this is the same situation. Good lookin out for everybody!
It sucks for them but we really do need the odin package just in case for future bricks lol
Sent From My VooDood Charge
Based on the one post I saw, it seems like it has to do with restoring /data with the error message that popped up. I'd guess that this is an issue with CWM, but it is hard to say for certain. For now though, I'd just avoid restoring anything, and it's this reason I'd rather use Titanium backup to back up stuff than CWM.
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Mine bricked from attempting a restore with CWM
But the file that imnuts made fixed it.
Sent from my Droid Supercharge.
RaptorMD said:
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Click to expand...
Click to collapse
Not sure where the stock ODIN images have come from, but tech support @ verizon should have access to them, should only be a matter of time b4 one gets leaked
RaptorMD said:
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Click to expand...
Click to collapse
Odin images are not source code, they are binary files. The Odin images come from Samsung, but there are people that have access to them at VZW. Getting a full stock Odin would have to come from one of the two places.
Hello,
I have bought a North American (Canadian, to be exact) Galaxy Gio (S5660M, with an additional "M" from the European model).
There are lots of tutorials about S5660 rooting and unlocking, but none for S5660M. There has been some reports that flashing S5660 firmware on S5660M to root and unlock made their phones unusable (randomly changing screen brightness, etc).
I tried searching on google and XDA, but could not find any relating to S5660M.
Is it too early to see any rooting/unlocking on S5660M?
Thank you very much!
Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (EDIT: Check out this one instead, perfectly safe.) (It turns out that the Gravity Smart, Galaxy Q, 551, 550, Mini, Ace, Fit, and Gio are siblings in a few respects. They all share Qualcomm 7x27 family SoCs.)
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware. Updated versions of SuperOneClick do work with the firmware. Worst case scenario the program won't finish gracefully, but you'll have a root shell and you can work from there.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode. Removed - the superuser files within were long obsolete. Get the current ones through proper channels.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose. Backup made a long time ago and SamMobile has had an official Odin image for some time as well.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (Many ROMs initially posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado
Thank you for the reply! I have successfully rooted & unlocked using the modified zip. I am not sure if it was your's (I have done it prior to looking at your reply... ), but it worked!
thank you!
Darkshado said:
Hello,
After some reading on here to compare unlock methods, I decided to take the leap into the unknown. I used the one published in this thread. (It turns out that the Mini, Ace and Gio are siblings in a few respects.) Make extra sure to follow the steps intelligently, especially the bit right after you get your code.
One deviation from the above linked thread is that SuperOneClick does not work on the 2.3.4 MUGK3 firmware.
I've uploaded my modified superuser zip that'll work with the 5660M. Install through recovery mode.
I wouldn't risk flashing the ROMs posted here until we can get a complete backup ROM, either from samfirmware.com (they don't have one yet) or through efforts here. I'll be starting another thread here for that purpose.
There's been some issues reported with the 5660M, ranging from odd screen brightness behavior to bricking. (The ROMs posted for the 5660, left "as is" also flash both the kernel and radio: not good.)
Goodbye,
Darkshado
Click to expand...
Click to collapse
could you tell me how I could unlock my phone too.
New tonight
Just picked up a GIO here tonight.
BTW Future Shop in Canada has these on for $80 right now.
I think this is a great deal, for a very responsive 2.3 android phone.
OK,
So S5660m - is the version in canada it would seem.. I think there are going to be quite a lot of owners because of the pricing.
We should use this thread or another to setup a difinitive list of what works.
1. How to root the phone.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion?
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
This is my wish list.
James
Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Biker1bob said:
1. How to root the phone.
Click to expand...
Click to collapse
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
2. Unlocks that work - I have heard some methods brick Ms very easy. What is the best unlock method specific to the M
Click to expand...
Click to collapse
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
3. What ROMs can we use? do we need to have our own set of modified roms because of the modem portion
Click to expand...
Click to collapse
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
4. Overclocking.. I have heard these can clock up to 1100 and run awsome!!
Click to expand...
Click to collapse
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.
Just to clairify darkshadow, by "bml5 method" you mean this ?
0) brand new locked GT-S5660M phone frome the store
1A) root the device using this zip
http://forum.xda-developers.com/showpost.php?p=16962635&postcount=2
simplest method :
1.1 To begin, download the zip file from the link above and copy it to the root of your SD card.
1.2 Power the phone off.
1.3 Boot into recovery mode by holding the middle button and pressing the power button.
1.4 Once in recovery mode, select update from sdcard and choose the update.zip that you copied to your SD card.
1.5 Let the file flash and once done, reboot your phone.
OR
1B Follow EDIT2, for temp rooting on same URL below
2. Follow exact instructions as per here:
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
(with the slight modification for HEX code to search specified here http://forum.xda-developers.com/showpost.php?p=17311381&postcount=358 )
Question: Does it matter if there is a SIM card in the phone when following these instructions ?
Any thoughts about "Network Lock Control Key" ?? ( ... would appear that this shows up as a separate issue for some users some time after unlocking see:
http://forum.xda-developers.com/showthread.php?t=992564 )
THANK YOU so much for confirming I got this right....I just want to make sure I am not missing anything, and these instructions are really safe as far as you know before attempting anything.
Darkshado said:
Hello James. Welcome to XDA.
Whoa there early thread starter! Use the search engine before even thinking of starting another thread. We don't have a dedicated Gio forum at the moment so things are scattered all over. Advanced search is handy as it outputs threads instead of posts.
Same as a lot of other phones, apply a zip file through CWM. You could also flash an already rooted ROM with Odin.
The bml5 method is safe. I noticed I had left a link to the older and unsafe stl5 method in my post above and removed it.
And keep your unlock code accessible somewhere on the phone. This phone is known to relock itself to Bell in some specific scenarios.
Yes, and no. If you only flash system.rfs, and maybe boot.img, it should work based on what others have reported.
I've cooked up a ROM for the 5660M that's called ArpegGioMod if you want to have a look.
Another point to consider if you want to run your phone in French: the Eurasian ROMs may or may not have that locale, and will likely have an AZERTY keyboard instead of a QWERTY one.
Do not flash radio (AMSS) or the other bootloaders from the Euro 5660. The former will make you lose all cellphone connection, the latter is unnecessary and increases your chances of bricking.
Where'd you get that? The only kernel mods I've seen so far for any Gio are all ramdisk modifications that left the stock kernel untouched.
Click to expand...
Click to collapse
so i'm pretty new here... i have a gio n my usb port is messed up.. i wiped tha phone the other day n the network lock came back on.. so seeing that i can't use any usb what should i do?
thanks in advance
IMEI: Mod Edit: IMEI # Removed...not a great idea to post them on a public forum
Let me start with things you shouldn't do:
-Resurrect two year old, stale, threads.
-Post your IMEI for everyone to see.
Exactly *how* is your USB port messed up? Just not talking to the computer or not working at all?
Are you rooted? If not, get that sorted out by using one of the exploits that worked on Gingerbread. You'll have to do it manually, no SuperOneClick for you. (Although the binaries included might come in handy.)
It is possible to do the commands to get bml5 via a terminal emulator app, and then transfer that file over wi-fi. (Samba, WebDAV, FTP, Dropbox, etc...)
I'm not sure anymore if this is possible in GB, look into using ADB over wi-fi instead of USB. I've sold my Gio months ago, and all of my current devices run 4.1+.
I currently have ICS theme installed via flash.
Simple... restore your backup. You do have a backup right? I mean everyone takes a backup before they flash don't they? Umm, maybe not everyone.
Nevermind, if you don't have one, just reflash your original ROM, or push the relevant files which were over-written by the theme using ADB or a file explorer with root permissions.
Nope...I don't have my original ROM, however...any UK stock theme will do to be honest because ICS is pretty noticable, I just need a link to a Uk stock theme for the Galaxy note or even Android 2.3.6 as I have updated my firmware for my phone.
KKA, or which version exactly?
The rom is...
Baseband version: N7000XXKK5
Build number: GINGERBREAD.XXKKA
Another option would be to re-flash my current rom (updated firmware) however...the phone doesn't allow that, unless I can find one from somewhere.
I am doing this all because of...
http://forum.xda-developers.com/showthread.php?p=20067262#post20067262
First day i get my phone and the screen plays up, never ever had this problem before with any phone I have got, only this one, unlucky I guess.
Cool,
Did you by any chance root using Chainfire's method? If you did, just use the CWM app that comes supplied when you flash his kernel to flash the original KKA firmware (the one you are using). It is non-wipe and will be rooted by his app.
To download the KKA firmware, click here. Sign in to download.
Then read Chainfire's instructions about flashing firmware using the CWM app VERY CAREFULLY in his thread here. Read the first few posts... and then read them again
Unfortunately I am not at work and don't have unmodified system apks to provide you with a flashable zip to replace the theme.
Alternative to the above... ask around and see if anyone has unmodified apks from KKA which you can flash. You will need all of the files which were contained in the themed zip you used.
EDIT: About those dark lines, are you sure it's not colour banding. All Note users get them (they are often feint). Most Note users won't admit to it though
I used 'The Easy rooting Toolkit' method, will have a look at replacing files in the theme, btw...I can look in the ICS rom and replace the exact same files from the KKA ROM (the link you provided), so is that the best idea?...to me that sound easy and then I would just need to flash it from CMW
SealsNavie said:
I used 'The Easy rooting Toolkit' method, will have a look at replacing files in the theme, btw...I can look in the ICS rom and replace the exact same files from the KKA ROM (the link you provided), so is that the best idea?...to me that sound easy and then I would just need to flash it from CMW
Click to expand...
Click to collapse
true it will work
lalitsehgal21 said:
true it will work
Click to expand...
Click to collapse
Not quite that simple.
To do that you will need to unpack the .img files contained in the zip that I linked to, which is a bit of a nightmare if you aren't sure what you are doing.
nobnut said:
Cool,
EDIT: About those dark lines, are you sure it's not colour banding. All Note users get them (they are often feint). Most Note users won't admit to it though
Click to expand...
Click to collapse
They can only be seen in the dark and when the phone has a very dark background with the backlight lit, they aren't straight lines, they start from the top right hand corner and each is about 3cm long, I have 3 lines showing at the moment. Also...I have noticed a dozen little dots in the same condition (dark background and in the dark), hope that helps what the problem may be
Bah! Annoying.
In that case I would go back to stock (making sure your flash counter says zero after) and return it. I'm a fussy SOB and that would annoy me.
I don't have the stock ROM though, only the update (firmware)
How do I know how much the counter is?...is that the number at the end of the 'Kernel version'? Btw...does a theme flash count add to the counter?...because I have #2 on mine.
SealsNavie said:
I don't have the stock ROM though, only the update (firmware)
Click to expand...
Click to collapse
I know. That is why I suggested using Chainfire's rooted kernel and CWM app. It allows you to flash and root a stock firmware, without increasing the flash count.
If you boot into download mode you can see your flash count.
No, flashing a theme doesn't increase the count... basically what does is flashing a non-stock kernel (except Chainfire's) via ODIN.
nobnut said:
I know. That is why I suggested using Chainfire's rooted kernel and CWM app. It allows you to flash and root a stock firmware, without increasing the flash count.
If you boot into download mode you can see your flash count.
No, flashing a theme doesn't increase the count... basically what does is flashing a non-stock kernel (except Chainfire's) via ODIN.
Click to expand...
Click to collapse
To be honest...I have no idea what to do in regards to using this Chainfire thing, if it was CWM then I wouldn't have a problem with flashing, if you can provide links to help me that would be great, thank you.
Btw...I really appreciate the help, its nice to know someone cares that my phone is playing up (the screen)...its very hard to swallow the thought that i'm in this situation and I could be stuck with this phone.
To make life easy for you. Why not flash the firmware using ODIN which will take you back to stock.
You can then either re-root, or return the device
I suggest you find KJ4 from that site I linked to, as we know it can be rooted without any issues. You can always update if you want to keep the Note.
I strongly recommend that you root using Chainfire's method if/when you re-root. It will prevent your flash count increasing and also allows you to flash firmwares from the device without ODIN etc
Just have a read of his thread that I linked to. Read the first few posts very carefully a few times until you get the hang of it. It is very simple, it just sounds complicated.
nobnut said:
To make life easy for you. Why not flash the firmware using ODIN which will take you back to stock.
You can then either re-root, or return the device
I suggest you find KJ4 from that site I linked to, as we know it can be rooted without any issues. You can always update if you want to keep the Note.
I strongly recommend that you root using Chainfire's method if/when you re-root. It will prevent your flash count increasing and also allows you to flash firmwares from the device without ODIN etc
Just have a read of his thread that I linked to. Read the first few posts very carefully a few times until you get the hang of it. It is very simple, it just sounds complicated.
Click to expand...
Click to collapse
Thanks, I shall give that a go
Hey everyone.
Im generally pretty savvy with androids. I rooted and S-offed my HTC Desire, I had a nexus S for a bit until it got ran over... Now im stuck with this Galaxy S 4G, which has been nothing but headaches because for some reason... this thing is impossible to root to me. Ive tried Hemidall, Super1clicks, Odin etc..
Can someone please just point me in the direction of rooting this POS? Im hoping that once its rooted and running stock, I wont hate this thing as much... because so far, Its a horrible purchase.
I just need someone to post a link to where I need to be. Ive searched.. and im absolutely lost. Even the Rootz wiki was useless to me.
Thanks.
Model Number - SGH-T959W
Android Version 2.3.6
You might not have any luck this is the T-959V and your phone might not be supported
Sent from my SGH-T959V using xda app-developers app
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
eollie said:
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
Click to expand...
Click to collapse
I have no idea what youre talking about. Sorry
I used the Hemidall, and only got an unrooted Tmobile rom.. Im not sure where exactly i get root from this
Meh, forget it... im selling this phone. There is no convincing me to ever buy anything from Sammy again unless its a Nexus line.
HTC or Nexus forever.
Thanks guys
Reading is hard
"Can I get step by step directions please?"
Sure, here you are!
"What?! Your not going to remotely root my phone for me? F this place"
Good luck sir, you have the patience of a saint and the drive of a tiger!
OK let's be honest you gave up kinda quick.......
The forum that eollie linked you to was a forum talking about the phone that you bought, which is an apparent offshoot of the t-959v and according to what Masonite found out, "our" roms work on the t-959w but you cannot flash the bootloaders.
Here is the one click link http://forum.xda-developers.com/showthread.php?t=1358498 just boot into download mode and use this but absolutely don't flash bootloaders and it should be OK, no promises.
Eollie was right for linking you there, all the info you needed about your model phone was on that forum, that one click is in the dev sticky which everybody should read.
There has been a flood of people not researching a little bit first before posting and that's why people flamed you but you should not give up, its a good phone and our devs are dedicated and have put in a lot of time on this model, you should be happy your phone can even support all the great roms that are available.
I'm not being mean but seriously, come on, all the info is there, no need to get mad.
Sent from my cm_tenderloin using xda premium
Edit: or Google search how to use heimdall if your confused, I learn off a damn YouTube video..........
Our devs didn't create heimdall and don't support it but it is a great program and the dev has to build the individual one click for the phone, we should be happy to have it that easily available.
Reading the whole thread you got linked to is really hard. Phone-bricking hard
FBis251 said:
Reading the whole thread you got linked to is really hard. Phone-bricking hard
Click to expand...
Click to collapse
Hahaha I know but but I believe in you lmao
Sent from my cm_tenderloin using xda premium
You'll need to flash one of the back to stock files that you got linked to in that thread which will put you on stock GB with no root. DO NOT FLASH THE BOOTLOADERS. You'll very likely brick if you do.
After this download the AntonX kernel from bhundven's one click thread and flash that. That will give you a custom kernel with CWM built in and root.
Needless to say, this is all for the SGH-T959V which theoretically should work on the SGH-T959W. As you'll read any disclaimer on this forum, you're resposible for anything you flash and the damage that may occur to your device.
Thanks for that fb I forgot a few steps if he wants to be on mtd roms, I assumed he could read from that point............ but your right for knowing better
Sent from my cm_tenderloin using xda premium
Thank you very much, and I'm sorry for getting angry. I've had this phone for almost 4 months now, and haven't been able to do anything with it. Quite frustrating.
So, I currently have the Tmobile ROM on my phone, so I'm halfway there it appears!
I'm going to download the other ROM as soon as I get home.
Thanks so much! Next up.. Learning to flash with Odin, and not ROM manager.
It seemed like everything I tried wasn't working with 2.3.6. Superoneclick etc.
I was waiting for a new exploit, but it never came. I tried YouTube tutorials, text directions.. Everything would fail, or give me "read only" errors. I feared bricking, so I stopped.. But I searched the forum and came across the thread he linked me to, but it said no bootloaders, and all the ones I saw had bootloaders. Wasn't until tonight that I noticed it's a 2 part flash process, with the second being the bootloaders.
I think I started this thread at 3am.
Lesson learned.
In heimdall, you can click a little box that says "flash bootloaders" to toggle flashing them on and off! .... or maybe it was odin? I can't remember... been a while since I used them!
After being away for the weekend, I came home, and BAM... fully rooted. Amazing! and FINALLY!!!
Thanks everyone for your help...
I just have another issue.
I wanna flash this ROM http://forum.xda-developers.com/showthread.php?t=1305145
It says its CWM.. but there is a huge disclaimer that we shouldn't use ROM Manager on the development page, which is a bit confusing. Since this ROM isnt Odin flashable... what do i do?
Thanks again.
So I was confused about this when I first started. I'm not at my computer but I can help. In order to flash Roms via cmw you have to turn off your phone hold both volume rockers on the phone then hold the power button and hold till you get into cwm recovery. That will get you into cmw recovery mode. Then wipe data factory rest, from there go back to the main menu and select the install zip from sd card and find the zip file you want to flash and select it and install. Should be good to go.
Sent from my SGH-T959V using xda app-developers app
Nevermind... im a complete goon. I got it, lol.
Thanks
I am fairly certain that simply using Odin 3.07 to change the recovery from stock/OEM to CWM 6.0.1.3 touch and than using that (CWM recovery) to flash the "SuperSU + Unlocked bootloader" found in the thread telling you how to flash the JB update with no data wipe is all I need to do (right?)...
Does anyone have any pointers or tips, or am I the first in line with such a thing? (i.e. JB pre-installed on a "Certified Like New" phone)
Check this out:
http://forum.xda-developers.com/showthread.php?t=2046439
Or your way also works.
MUST use ICS bootchain to flash custom recovery in JB ROM (at least for now)
aooga said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2046439
Or your way also works.
Click to expand...
Click to collapse
Thanks, much! "My way" does NOT work, actually: the way layed out in the reference you linked DOES work, however. :highfive:
Interesting that they added a little booger that sees that the "CWM 6 Touch" recovery is invalid and will not allow Odin to flash it. Fortunately, somebody is already ahead of me in the line and already figured out how to jump through the hoops to 'get 'er done'!
Sorry I had to create a new thread, I tried to find anything that related to my specific scenario even using the search properly. I guess his write-up doesn't specifically address my situation (receiving a newly "CLN" phone with VRBLK3 firmware already on it), but it certainly does the trick. I'll add a comment "over there" as well.
As always - the XDA-Dev community rocks! :victory:
Now, upward and onward with my 5th VZW GS3... Time to unleash Titanium Backup on it and restore my most recent copies of everything. Ah, the sweet smell of excess.