So I was having some issues with feedback during calls with almost all custom ROMS. I reverted back to the gingerbread stock rom via odin to see if it was just a ROM problem and I found the source of the initial problem. But now when I boot into the recovery, it won't flash any new ROM I want to go back to. I do the normal flash/wipe + the cache for good measure, and apply the zip and It'll say "Short write of /tmp/sideload/package.zip (no space left on the device)." But I have 4gb free on my phone so i'm definitely not out of space. I've tried the AOKP JB rom, shoshock, and the newest cyanogen mod. No luck on any of them.
What am I doing wrong?
Tell us more details about your process, from stock through root and kernel, and we can help you out better.
aspen1135 said:
So I was having some issues with feedback during calls with almost all custom ROMS. I reverted back to the gingerbread stock rom via odin to see if it was just a ROM problem and I found the source of the initial problem. But now when I boot into the recovery, it won't flash any new ROM I want to go back to. I do the normal flash/wipe + the cache for good measure, and apply the zip and It'll say "Short write of /tmp/sideload/package.zip (no space left on the device)." But I have 4gb free on my phone so i'm definitely not out of space. I've tried the AOKP JB rom, shoshock, and the newest cyanogen mod. No luck on any of them.
What am I doing wrong?
Click to expand...
Click to collapse
cyril279 said:
Tell us more details about your process, from stock through root and kernel, and we can help you out better.
Click to expand...
Click to collapse
Well the process is fairly straight forward. I think Ive explained the details as well as I can. I flashed the stock firmware through Odin and can't reflash any new rom or kernel. I made a nanbackup before doing this but the factory stocks kernel doesn't support backup/restore. I need to go from this old stock gingerbread rom back to shoshock or anything else to restore my backup.
In your explanation, I didn't see mention of how you rooted the device, or what custom-kernel you chose, or how (or if) you flashed the custom kernel. The stock recovery won't allow the installation of firmware that was not signed by Samsung, and Odin-flashing custom firmware is not the preferred method.
>>This Guide<< is the most up-to-date, and straight-forward method that I'm aware of for the I777, I highly recommend it.
aspen1135 said:
Well the process is fairly straight forward. I think Ive explained the details as well as I can. I flashed the stock firmware through Odin and can't reflash any new rom or kernel. I made a nanbackup before doing this but the factory stocks kernel doesn't support backup/restore. I need to go from this old stock gingerbread rom back to shoshock or anything else to restore my backup.
Click to expand...
Click to collapse
Once you're rooted and kernel'd, and can tell us what android version firmware you're trying to get to, we can better suggest which custom kernel to flash prior.
cyril279 said:
In your explanation, I didn't see mention of how you rooted the device, or what custom-kernel you chose, or how (or if) you flashed the custom kernel. The stock recovery won't allow the installation of firmware that was not signed by Samsung, and Odin-flashing custom firmware is not the preferred method.
>>This Guide<< is the most up-to-date, and straight-forward method that I'm aware of for the I777, I highly recommend it.
Once you're rooted and kernel'd, and can tell us what android version firmware you're trying to get to, we can better suggest which custom kernel to flash prior.
Click to expand...
Click to collapse
Sorry for not elaborating. The stock ROM (the one i'm on now) thats flash-able through odin, is pre-rooted.
I got it from this thread here: http://forum.xda-developers.com/showthread.php?t=1286432
But other than root, its completely stock gingerbread, Stock kernel, Bloatware, ETC. I'm trying to get to at least jelly bean or higher. I was on the shoshock rom before I decided to revert to the factory rom to test some things out. The signed package thing you mentioned makes sense because signature verification fails whenever i try to flash a different kernel. But it wont let me flash any of the jelly bean ROMS either (refer to my first post's error).
I visited the link you provided, and want to give the method a try. But mobile odin lite has been giving me constant trouble. it keeps saying I need to install another ad on in order to flash stuff and when I hit OK, the link takes me to my browser, but doesnt direct me to the web page that provides the ad-on download. Where do I go from here?
The add-on that mobile odin is trying to download is the i777 flash kernel that it needs to perform its magic. It's in post #10 of the mobile odin thread. Whether you use mobile odin lite or pro, you need this flash kernel. I'm not sure why it wouldn't download it from within the app.
aspen1135 said:
Sorry for not elaborating. The stock ROM (the one i'm on now) thats flash-able through odin, is pre-rooted.
I got it from this thread here: http://forum.xda-developers.com/showthread.php?t=1286432
But other than root, its completely stock gingerbread, Stock kernel, Bloatware, ETC. I'm trying to get to at least jelly bean or higher. I was on the shoshock rom before I decided to revert to the factory rom to test some things out. The signed package thing you mentioned makes sense because signature verification fails whenever i try to flash a different kernel. But it wont let me flash any of the jelly bean ROMS either (refer to my first post's error).
I visited the link you provided, and want to give the method a try. But mobile odin lite has been giving me constant trouble. it keeps saying I need to install another ad on in order to flash stuff and when I hit OK, the link takes me to my browser, but doesnt direct me to the web page that provides the ad-on download. Where do I go from here?
Click to expand...
Click to collapse
cyril279 said:
The add-on that mobile odin is trying to download is the i777 flash kernel that it needs to perform its magic. It's in post #10 of the mobile odin thread. Whether you use mobile odin lite or pro, you need this flash kernel. I'm not sure why it wouldn't download it from within the app.
Click to expand...
Click to collapse
Thank you thank you! I will try this out when I get a break from my classes. IDK why it wouldn't either. Much thanks!
aspen1135 said:
Thank you thank you! I will try this out when I get a break from my classes. IDK why it wouldn't either. Much thanks!
Click to expand...
Click to collapse
Just wanted to confirm that the mobile ODIN method worked and I now have my phone restored to how it was. Thanks again for all the help.
Related
Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.
hi,
I am sorry if this is a dumb question. But i have failed several attempts while shifting to ICS (RC 5 by team-nyx). Every time when i install ROM & kernel via CWM and boot the device (vibrant t959) it freezes on the screen with VIBRANT and SAMSUNG displaying WHITE on BLACK back ground.
i have gone back to JFD and tried several times BUT same result.
I was on froyo 2.2 (build UVKB5) updated via kies and did it but no luck. I followed wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and did starting from No. 03 --
downloaded Cmenard's Kernel with the ClockworkMod Recovery 2.5
Heimdall Suite 1.3.2 for windows
AND upto No. 9 under Windows ONLY: section
the CWM installs as it says (A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically. )
after that i cleared factory, cache and dalvik cache.
then I select install Zip from SD card and chose the ROM (which is from team-nyx.com/index.php/releases).
after 3% it says rebooting and vibrant shuts down and reboots.. when after I clicked the combo (vol+vol-power) to enter the CWM its not there.. so I reinstall using [heimdall flash --kernel zImage] command in PC's cmd. then after i redid the same to select from SD and then ROM installed ok.
then I selected the kerenel which was taken by same source and installation went normal..
after I select reboot from CWM it reboots and hangs on vibrant screen.
I cannot figure OUT WHAT IM doing WRONG..
Please HELP ME..!!!
thank you for your time
I am moving to 2.2 via kies after going back to stock JFD. then i will root my vibrant. after that i will install ROM manager from market. THEN i will try to FLASH to ICS RC 5 + kernel from nyx TEAM.
I dont know what is wrong.. please HELP
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
iwillkillyou said:
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi,
thank you for the reply. No i havent tried a different ROM. yes I checked repartiton when ODin Y this is happening.. I have Flashed this ROM once.. but then when someone calls me they cudnt hear me clearly.. when i initiate the call its ok.. so I moved back to JFD..:/
kaiser_bun said:
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
Click to expand...
Click to collapse
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
haarsh said:
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
Click to expand...
Click to collapse
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Woodrube said:
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Click to expand...
Click to collapse
Thank you for the links.. I downloaded and place CWR inside SD. Without kies can we install official releases via Odin.. is there any way.. im sorry if that is a stupid question
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Woodrube said:
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Click to expand...
Click to collapse
thank you. btw can we Flash to 2.2 via CWM .. directly selecting the ROM from SD .. without Odin
If you can find it, you should be able to. Just put on your card and flash away, taking care to wipe accordingly.
A note on flow though:
2.1, 2.2 -can go into and out of any 2.2 there is laterally.
2.3-4.0 -will need to Odin to stock before going back to a 2.2 ROM. Can move laterally from 4.0 to 4.0 though.
(i.e DO NOT try to restore a 2.2 nandroid or flash a 2.2 ROM when you are on an ICS variant. the /system is completely changed and reformatted. You need to Odin to get it back.)
Moped Ryder uploaded a semi tweaked version of the stock 2.2 build. It's a zip that you can just flash using CWR:
http://forum.xda-developers.com/showthread.php?t=1674519
It comes rooted with busybox and some other goodies, but it's the stock kernel and whatnot. I'd highly recommend Fishman's Bionix-V Mod or Moped Ryder's Slim_Ryder ROMs if you're going to be on Froyo though. They're both great, but I went with Fishman's latest Bionix Mod since I couldn't get bluetooth to work on Moped Ryder's ROM. Which is really unfortunate because I loved Moped Ryder's otherwise.
And you don't have to Odin back to stock if you're just bouncing around Froyo or Eclair builds; only if you're coming from Gingerbread or ICS (2.3 or 4.0).
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Is your Samsung Vibrant (T959) Rooted.?
iwillkillyou said:
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi.. I tried again with flashing semaphore kernel through Odin installed CWM version higher than 2.5 to install ICS RC5 by nyx --sorry i need that soo badly so didnt checked anything else ..
@that time I was on vibrant 2.2 UVKB5 (stock)
NOT rooted
I didnt had so called
bootloaders
Click to expand...
Click to collapse
(i dunno what it means though--have to search )
BUT it didnt worked for me instead freezes at Vibrant start-up screen. So i Couldnt switch back to CWM. I Odin back to JFD with repartition clicked and my vibrant was locked (network lock). Finally, I got it cleared by application named Galaxy_S Unlock by Helroz from the market.
Now I am at the very beginning again. I am now on 2.1 JFD. I dont know WHY this happening to me .. :crying:
gonna try again with GB bootloaders.. BUT Im sick of failing and going back to 2.1 (my friends who are having captivate had no problem)
Speedy5150 said:
Is your Samsung Vibrant (T959) Rooted.?
Click to expand...
Click to collapse
At the time i was trying it was NOT rooted.. But now i have it rooted because i needed to unlock the network . which happened me for the very first time after flashing back to JFD using Odin..
Thank you guys for the links and thoughts on 2.2 ROMs.. I am not that expert . Thats why i was updating to 2.2 via KIES -- which is not a good idea as it seems with the ability 2 brick the device. I am going to get Bionix-V FishmanMod V4 FULL and install as http://forum.xda-developers.com/showthread.php?t=1441976 says..
It says Boot into clockwork recovery and i think i found something to do that in this thread http://forum.xda-developers.com/showthread.php?t=734164
I have to get ROM manager from market and go through it..
BUT Im damn upset with the RC5 ICS update by nyx being unable to installed into my device.. I will try with GB bootloaders flashed ..
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Woodrube said:
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Click to expand...
Click to collapse
thanks alot for the info brother.. some guys told me STUPID.. but YOU guys are awesome.. I am a newbie to this flashing and stuff.. but learned a lot from XDA . Thanks again for the reply. now I have stock 2.1 with ROOT . (rooted cuz i had to unlock the vibrant). I will flash to Fish's 2.2 ROM soon. BTW may i ask you after moving to Fish's ROM and later if i need to move to ICS still can I do it without messing with Bootloaders..
Thank you
That is what we are here for in the Q&A/General sections.
Regaring your question about Gingerbread bootloaders being needed:::Yes and No.
Gingerbread bootloaders were required in the infancy of ICS ROMs bc they prevented what is called "Rainbows" in your clockwork where you couldn't see anything. The options were there but you just couldn't see them. Then as ICS evolved, the need for GB bl's lessened and now you don't need them at all.
But...There's always a but...Gingerbread bl's are recommended by most of the devs for ICS builds because they seem to work better with the custom recoveries that come with some of the kernels. There is more to it but in short, GB bl's are not required but recommended.
If you go to my ICS install guide, in the middle pages and more again at the end, Yosup (highly respected user) and I have a detailed conversation about bootloaders and their installation. Once he got over the fear and did it, he was hooked and flashing ICS ROMs weekly if not more. It is a very informative section of that thread.
Hello, at the start i wanted to install some new ICS rom for my Vibrant..i try to root it with one click and i couldn't do that coz i had froyo(2.2update)..so i read some forums and found solution in odin...i used that to turn back to stock eclair where i rooted the phone ...but the problem is that now i can't install any application on the device(i need ROM manager)..i get to android market and ,click on application but nothing is happening, no download at all...than i try to use android injection with apks that i found on the net , but nothing, i always get INSTALL_FAILED_OLDER_SDK...so now i am stuck i have: fimware version-2.1 update 1,baseband T959UVJFD, kernel 2.6.29 can you tall me should i do?? thx
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Download the clockwork mod recovery file (update.zip) and save it to the internal storage on the phone. Then reboot into recovery and install packages. Might have to do it twice. Then you'll be in CWM recovery. Install from from there.
Sent from my SGH-T959 using XDA
The AIO Vibrant toolbox might be something you need to look at. you can find it here http://forum.xda-developers.com/showthread.php?t=954509
guide
i followed your guide...flashed CM7, than i try to flash Euphoria RM2.1(ICS) and flashing is starting all ok , than after 30 secs i see message 'Random offset 0x302' and it's not going forward with flashing,i pulled out battery and try 2 more times,and there is always the same problem, i'm on CM7 now(and i don't have google play what should i do? can you recoommand me some good and stable gingerbread ROM for Vibrant(if i goona be unable to install ICS Rom) thx
Woodrube said:
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Click to expand...
Click to collapse
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
Click to expand...
Click to collapse
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
stack
man, now i am completly stack, i try to flash slim ics, found the file for vibrant, but it culdn't flash , in the middle it just stoped..and phone is just rebooting it self when i enter cw mod i can't install any other ROM from internal sd, it says no files found ffs now i can't even use phone, i need help emergently
Woodrube said:
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
Click to expand...
Click to collapse
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
odin
ok i get into odin , marked repartiton but is sais fail ??? what should i do now?
Woodrube said:
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
Click to expand...
Click to collapse
If you do get past all of these, but this is unlikely for a normal flash, get either Iczen or chimera.
Sent from my SGH-T959 using xda app-developers app
Please refer to title. I need help. I have helped many people on this site and I have searched for the last 2 days and cannot find an answer. Thank you
casualt said:
Please refer to title. I need help. I have helped many people on this site and I have searched for the last 2 days and cannot find an answer. Thank you
Click to expand...
Click to collapse
In other words I can't find the proper kernel. Is there another one that's compatible. Siyah will not work.
casualt said:
Please refer to title. I need help. I have helped many people on this site and I have searched for the last 2 days and cannot find an answer. Thank you
Click to expand...
Click to collapse
In other words I can't find the proper kernel. Is there another one that's compatible. Siyah will not work.
Click to expand...
Click to collapse
You are in fact asking two different questions... If you are looking for a kernel to replace the stock one, I don't know the answer, as I have not tried a clean Canadian stock (I am in Canada, but using LSD-based Disaster ROM with the MA5 modem). I would think PhilZ, Jeboo and Speedmod should work perfectly fine with your ROM. I also don't see any reason why Siyah v6b5 wouldn't work on it, but again, I haven't tried...
However, if you only need root, you don't even need to flash another kernel -- you can keep it completely stock. Just search for signed SuperSU zip by Chainfire, flash it from the stock recovery, and you are get a 100% stock ROM, but rooted. And with SuperSU, you can easily unroot it anytime right from the app, if you need to.
So in case people have the same problem.
What i did was I
1. googled SuperSU zip by chainfire
2. changed file name to update.zip
3. I got a micro sd card and loaded the zip file onto it and put it in my phone
4. I then got into stock recovery mode by pressing the volume up and power keys
5. Then I went to update zip file through sd card in this case external
6. Rebooted
7. Went to google play store and downloaded ROM manager
8. Followed steps to load Clockworkmod onto my phone
9. Rebooted and made sure it was working.
10. Downloaded a ROM and flashed using CWM it changed my kernel and everything.
casualt said:
What i did
Click to expand...
Click to collapse
I didn't realize your goal was to flash a custom ROM... I thought you wanted to root the stock one. You could have done it easier, in just three steps:
1. Flash the temporary CWM from stock recovery.
2. Do a nandroid backup (optional, but highly recommended), and then a full wipe.
3. Flash any ROM of your choice.
BTW, as far as I knew, CWM can't be installed on SGS2 using ROM Manager, since our phone doesn't have a recovery partition, and a custom recovery must be integrated into the kernel...
As a follow up - I too have installed i9100MUGMA5 JB on my S2, which is 4.1.2.
I wish to upgrade to 4.2.2 - as there is a bug fix I need [the Android 4.2.2 Jelly Bean update as part of the Android Open Kang Project (AOKP) custom ROM which was based on the newly released firmware].
I need a Rooted kernel and CWM installed.
Would someone outline the steps I need to take.
I have used ODIN a few times but wonder what I need to do...
Many thanks.
I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.
I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.
fifthmanstanding said:
[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.
Click to expand...
Click to collapse
My advice is to avoid downloading ROMS from galaxys2root.com
If you want the insider scoop, keep up at xda or at each group's G+ community.
if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
cyril279 said:
My advice is to avoid downloading ROMS from galaxys2root
If you want the insider scoop, keep up at xda or at each group's G+ community.
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
Click to expand...
Click to collapse
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
fifthmanstanding said:
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
Click to expand...
Click to collapse
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
creepyncrawly said:
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
Click to expand...
Click to collapse
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
fifthmanstanding said:
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
Click to expand...
Click to collapse
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
creepyncrawly said:
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
Click to expand...
Click to collapse
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
fifthmanstanding said:
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
Click to expand...
Click to collapse
hint: http://forum.xda-developers.com/member.php?u=2916435
cyril279 said:
hint: http://forum.xda-developers.com/member.php?u=2916435
Click to expand...
Click to collapse
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
fifthmanstanding said:
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
cyril279 said:
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
Click to expand...
Click to collapse
I agree.
Which links?
I read through the notes on the repository:
There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.
"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"
And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.
What am I missing?
Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.
Edit:
Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.
Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.
update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?
fifthmanstanding said:
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.
creepyncrawly said:
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Click to expand...
Click to collapse
Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
EDITosted before I saw your edit
fifthmanstanding said:
Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
Click to expand...
Click to collapse
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
creepyncrawly said:
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
Click to expand...
Click to collapse
Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.
Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.
Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?
Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.
Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
fifthmanstanding said:
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
Click to expand...
Click to collapse
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
creepyncrawly said:
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
Click to expand...
Click to collapse
Ok by the looks of it that worked. Thanks for that.
In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?
Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.
Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.