First off, I wanted to say that the XDA developers "Video for Noobs" was absolutely hillarious and informative at the same time. Great idea. NOW, on to the source of my infinite frustration.
I decided today that I wanted to root my Galaxy Vibrant that I got yesterday, and install a ICS ROM on it. I had no clue how to do anything as regards this, but I'm fluent with computers and I have a very good knowledge of Android in general. I don't know details on the coding side, but I have a good base of background knowledge. So, I started work around 3:00EST today. I've been working constantly SINCE THAT TIME (now 9:30 EST) trying to get root and install ClockWork Mod. But it will not work.
So, the details. I'm running Windows 8, 64-bit by the way. The first thing I tried, after looking up many guides and tutorials, was to install the Samsung USB Drivers and to get root and ROM manager. After some trial and error using SuperOneClick (2.3.3.0), I achieved root access, but I didn't have SU so I installed the app from the Play store. Then, I tried installing ClockWork Recovery from the ROM Manager, and I tried rebooting into CWR through the ROM manager. No dice, I got the standard "Android System Recovery" software. e3 variant (I've read up a bit on the different types, but I'm not too fluent in them yet). I tried the "Reinstall Packages" option so I could flash CWR, but that led to a certification error. No clue how to get around it.
I then figured out that I needed to have the DDM (Dalvik Debug Monitor) running to get proper root access. So I did that, and tried EVERYTHING again. I have wiped my phone about 5 times by this time. I went through a bunch of crap and eventually got it so that I CWR would TRY to flash once I got into the recovery screen. Basically, when I hit the "Reinstall Packages" button it goes through a few steps, a progress bar appears, and it says something along the lines of "Replacing stock recovery manager with ClockWork recovery". After just over a second of this, the phone restarts into the plain old recovery screen with no progress whatsoever.
I have ClockWorkMod 2.5.1.2 downloaded through ROM manager.
I have left it alone at this point.
I've tried using ADB, but there are no real guides that are up-to-date with the latest software and manually flashing an image from ClockWork Mod doesn't seem to work as they don't have image files anymore, just .zips with a bunch of single files and folders. I have no clue about Odin.
The ROM I'm trying to flash is Ice Cream Zenwich, which looks to be pretty promising. But I haven't even been able to get any kind of recovery manager working, so that doesn't help much.
Link: (add www) rootzwiki.com/topic/21742-romimm76i-iczen-rc18-the-hammer-of-buddha-5-26-12-deficient-development
I have tried manually flashing, but I haven't really made any progress in that area. I've tried ABD, I've tried CWR, and nothing I've been able to think of seems to work. SO I NEED HELP!
Just to state my system specs and software:
PC:
Windows 8 Consumer Preview, 64-bit
Android SDK and tools
Java JDK 6u29 ]______will this cause problems? Version 6 and 7 Java?
JRE Version 7 ]
Ice Cream Zenwich ROM (RC 1.8)
Phone:
Samsung Galaxy Vibrant, running Android 2.2
ROM Manager, ClockWork Mod Recovery 2.5.1.2 Downloaded
SuperUser
Titanium Backup
Root Tester
Absolutely ANY help would be insanely appreciated, I just can't work at this anymore.
Thanks in advance!
I know this is a bit early to bump, but I really need help with this still. Haven't made any progress.
Sent from my Vibrant using XDA
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Thanks for all the help
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Thanks for that, I'll definitely take a look at this. I was pretty sure I was overthinking things, I think this might be a simpler solution.
I was following general instructions from various places (the ICZen page, etc), and at first I was following guides from all over the place. After I got my legs, this was the main rooting guide that I followed:
(add www) forum.xda-developers.com/showthread.php?t=1438478
And I was loosely following this guide for the ROM manager, CWR, etc:
(add www) androidauthority.com/vibrant-t959-ice-cream-sandwich-install-56729/
Woodrube said:
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Click to expand...
Click to collapse
Thanks a lot for that, it does help a lot. I'm taking a look at that guide right now. Hopefully I can get through it without as much trouble as I had this time around (and without as much frustration). Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
And in response to your comment on my OP, yes - I don't like it myself when people leave out information that may be critical to diagnosing their issue. It just prolongs things, makes the situation difficult, and its simply annoying. So I didn't want to be that guy. It looks like it worked!
mohitmoudgil said:
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
Click to expand...
Click to collapse
Thanks, if I do get stuck again I'll give this a try.
I appreciate all the help. I'll report on my progress soon. Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Im probably late to the party but the way i get CWM is simply that i run the recovery 3e to 2e batch file (google 3e to 2e recovery) from my computer and then flash the CWM update.zip (its inside the clockworkmod folder ththat should be in the root of your sd) using reinstall packages, sometimes twice.. this should take you to CWM mod, after which i can flash the root package pretty easily
sent from the xda app on my android smartphone.
CWalkop said:
Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
...Snip...
Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Click to expand...
Click to collapse
No problems man. I am usually scanning the General and Q&A sections during the days to see if anyone needs help. At night I turn it over to others to troubleshoot.
I do have to tell you about a certain caveat in the ICZen flashing that is different than the others and almost everyone misses it on the first time they try.
Steps
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset <---You must do this
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again <---AND this
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
Click to expand...
Click to collapse
Most of the other ICS ROMs only have you Factory Reset once but you'll need to do it twice in ICZen, otherwise you'll get stuck in a bootloop.
W00T
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash. Interesting how booting into Recovery is built right into Cyanogenmod, I like that.
Anyway, I just performed a factory reset from the prompt that popped up right after I tried to flash ICZen (Deficient Touch Recovery, 5.5.0.4). I remember from the ICZen page that they told you to make SURE you had a CLEAN phone to start from, but I missed the second wipe step. Thanks for reminding me. I'm rebooting now, hopefully this'll work!
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Thanks for all your help. I'll post screenshots afterwards
CWalkop said:
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash.
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Click to expand...
Click to collapse
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Woodrube said:
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Click to expand...
Click to collapse
Ah, sorry for the confusion. I did in fact flash the GB bootloader, and it worked fine. I was confused for a bit because I thought I needed to choose a specific bootloader from the page you provided, but then I just chose one and it went through fine.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Click to expand...
Click to collapse
That's not exactly what happened; it just rebooted into the recovery manager again after I told it to reboot normally.
But...as you probably garnered from this post, everything worked perfectly after that! I booted into ICZen, setup the phone (no bloatware is nice), and started using it! Its even compatible with some apps that it wasn't before, which is great!
I attached some screenshots. It felt like the right thing to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*cheers*
Thanks for all the help! You were great. I have over locked a bit; now I'm trying to set up Chainfire 3D so I can run the Tegra apps I bought for my previous tablet (ASUS Transformer, sold to save for the Infinity). I can probably find a guide of some kind online.
Sent from my SGH-T959 using XDA
Kind of random, but I find it really interesting that you can adjust the display color balance on ICZen. That's an absolutely incredible feature; I was actually hoping to find an app that would accomplish this but the built-in control seems to work great! Tweaked to my hearts desire.
Sent from my SGH-T959 using XDA
Related
Lite'ning ROM v6.1
12/20/2011 - ROM hasn't been updated, but due to some users not having much luck with the included stock modem I've added a CWM flashable UCKK6 modem. I've also added the stock for those that need/want it for some reason. The download links are available at the bottom of this post.
11/27/2011 - Updated with haptic fix (credit to amtrakcn) and Entropy512's latest kernel (11/23/2011). Download link at the bottom has been updated to this one. Enjoy!
11/12/2011 - Updated image with fixed root!
The previous image was almost impossible to get root working. On the surface it was installed, but wouldn't / couldn't gain root access. After many attempts I finally decided to build the port from scratch again. Fixed a couple of file issues, build.prop edits, script tweaks, csc, etc. The result is better WIFI establishment and root that works from install.
This time I didn't use Hellraiser files, but definitely continue to use Entropy512's awesome kernel. No issues with Hellraiser as I've used it to Hellraise other I9100 ROM's without issue, I just didn't need its files in this go around. You should check Hellraiser out. It is an awesome tool.
This ROM is a port of Lite'ning Rom v6.1 XXKH3 found here made for the SGSII I9100. This is a single CWM install of the ROM.
New download link is at the bottom of this post.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit and thanks to LitePro for his image source, and to Entropy512 for his awesome kernel!
Donations are appreciated, but not required. Thanks is good enough
Save the Zip to your internal SD Card
Boot into CWM
Highly recommended doing a format /data in Mounts and Storage
Do a install zip from sdcard
Point to the downloaded Zip file
Install the Zip package
This CWM package will wipe your cache, system and Davlik-cache for you
Download link: (11/27/2011)
http://www.multiupload.com/74QB78HAI3
Modem downloads (12/20/2011)
UCKK6 Modem
UCKH7 Modem stock
What good is a CWM package if you don't have CWM?
CWM = ClockWork Mod
Note: Your phone needs to be rooted for a non-Odin install. There are many threads in this forum on how to root so I won't get into it here.
Now you need to obtain a kernel that has CWM included. I recommend the latest kernel from Entropy512's thread located here.
You'll want to extract the zImage file out of the Zip and save it on your computer.
If you have the Android SDK installed and working on your computer then save the zImage in its tools directory and then type the following command from this location:
Code:
adb push zImage /sdcard/zImage
Otherwise you'll want to plugin your phone to your computers USB connection and paste the zImage file in the root of your internal SD Card.
Next you need to flash the kernel.
Via ADB (press Enter after each line):
Code:
adb shell
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Via a Terminal Emulator installed on your phone (If you don't have one download "Android Terminal Emulator" from the Market and install it. It's free):
Code:
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Reboot.
Note that in the above two code examples when you type su you'll get a prompt to allow the "Superuser Request" if its the first time you invoke it from either program.
To boot into CWM in ADB type:
Code:
adb reboot recovery
Or, unplug your USB cable if plugged in, and press and hold vol UP + vol DOWN + Power buttons. Wait until it reboots and you see the Samsung Galaxy S II boot screen and release all 3 buttons. This should place you in your CWM menu.
Doing it this way should keep you from getting an exclamation point on your boot screen which is the main reason why I explained how to do this in this manner. If, by chance, you still get an exclamation point or already had one to begin with the only option I can think of is to use a jig. Not that a jig isn't a good thing to have anyways. Any ROM you flash from within CWM will not be added to your Custom Image count and will not produce the annoying exclamation point on the boot screen.
Absolutely first thing you want to do is boot into CWM.
As of this writing, press the Home button to choose an entry and press your Power button or the back button to go back to the previous screen.
Go to: backup and restore
Choose Backup
This will take a few minutes, but is well worth it. Now if you ever mess up your install you can always boot into CWM and restore the image you backed up. This, however, doesn't protect you from flashing bad bootloaders so word to the wise... DO NOT FLASH BOOTLOADERS!!! At this point and time there is no need to.
Reserved for awesomeness
_______________________
Fresh Install:
Home button has a bit more of a delay to it. - Fixed
Quite a few services running.
Broke my Root. - Fixed
I would recommend someone putting more than the 10 minutes I did into this ROM.
Going back to UnNamed, dont have to the time to mess around too much. Getting late, and Skyrim is coming...
I wont be using this rom but wanted to give serious props for getting this working! Awesome job to everyone involved!!
Sent from my SAMSUNG-SGH-I777 using XDA App
Sweet... wouldn't mind giving it a shot. Thanks for sharing
Is this a sign that we'll be seeing more OGSGS2 ROMs coming over? How hard was it to port?
Sent from my SAMSUNG-SGH-I777 using XDA App
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
simpl3lang said:
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
Click to expand...
Click to collapse
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Thanks !!!
Cozmo1 said:
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Click to expand...
Click to collapse
backing up right now to have a go at it.
when you get the time have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1334124
it seems someone has continued to tweak and update the litening rom. what do you think?
downloading now. Reporting back soon.
I was waiting for something like this to come along
Sent from my SAMSUNG-SGH-I777 using XDA App
cwc3 said:
Fresh Install:
Home button has a bit more of a delay to it.
Quite a few services running.
Broke my Root.
Click to expand...
Click to collapse
While initially the home button does have a little lag to it didn't seem to persist after using it a little bit. However, I do recall reading that there was a fix for the issue. I will look into it.
It does have many processes listed in the background, but I didn't see it being different than a standard ROM install with a basic selection of apps. Mine currently has 59 in the background, but only 4 in actual use. It's how Linux based systems handle processes and it tends to do a real good job which is why task killers are frowned upon. So I tend to not be concerned with background processes, but more with how the battery consumption is on the ROM. It was rather good in that.
I installed this ROM several times in my testings of it and never had my root broken. I could've just been lucky. It comes with Entropy's daily driver kernel which includes root injected in initramfs as well as CWM. Still, strange things can happen. Did you wipe /data before installing, by chance?
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
cwc3 said:
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
Click to expand...
Click to collapse
LoL - I hear you. I can guarantee you that once Diablo 3 comes out my time on XDA will be severely cut
root not working here. great rom though. fast and smooth.
about to test. if you lost root, wouldn't installing entropy512 kernel fix it? let me try that for you
you think you could fix the home button haptic? its not a big deal but itd be nice lol
Also wifi wasn't working for me so I decided to nandroid back to UnNamed for now
confirming update of kernel bb and su did not give root. I was wrong, but will check back!
This is interesting. On the surface it looks to be rooted, but when you actually try using root capabilities it doesn't work. Not even when flashing a new rooted kernel. This will need some investigation to provide a fix. Will work on it tomorrow after work.
Help Needed, I am, lost!
Ok, first things first, I am now on version 1.2.4349 of what I am not sure. I think it is a factory ROM.
I restored from a bricked device, using nvflash and the update Rom 1.2.4349. Since I have been trying to install Clockmod. I can't get it to work.
Every time I boot per instructions here, nothing happens...either it freezes on the first screen with the birds, showing update kernel found.. or it starts the update then freezes. I have tried internal boot file and external boot file... even tried clockmod v8. with same results.
There are so many post about rooting this device and do's and don'ts that now I have become confused.
Can someone please point me in the right direction. I want full market access, and a workable rook. Where do I need to start?
Thanks
This will get you going in the right direction.
http://viewsonic-gtablet-for-dummies.webs.com/
ok, I must not be your average dummy. I followed directions to the word. Trying to install Clock work mod via option three(3) nvflash. Everything goes well... flash runs and does what it should. I only saw a brief blimp of a dos window when it ran. Next tried to boot using power and v+.... It said "Recovery key detected", I released buttons...now it says "booting recovery kernel image." And it just sits there, is still there now while I type this post.
When I looked at the version it says I am on version 1.2.4349, so I used the 1.2 side of the chart.. Could I have it all clogged up from all the prior failed attempts.
thanks for any help
The "dos window" should stay up for a minute or two. Are you sure your initiating the nvflash correctly? I think it's something like "nvflash.bat"
the dos window was only a flash, and the instructions said less than a second, and you might not even see it.. I used "nvflash_gtablet.bat" to start the flash.
I am lost still
It looks like you've selected the "flash clockwork with nvflash." This requires that you already be on a custom rom, which I don't believe you are.
There is a full nvflash available which will install clockwork AND completely wipes your tablet back to stock. (an excellent baseline to flash a new ROM)
This is the correct tutorial.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
You'll want to use the 1.2 version with clockwork.
After that, I recommend the Flashback ROM if you're looking for Honeycomb. That ROM includes a text file with a very literal step by step process for installing the ROM. It will walk you through partitioning your SD Card (which is important) and flashing the ROM.
for helping out a noob that didn't thank you, brett.
I thank you for 'im.
If I may say so, I am sorry I can't be on 24/7 and only now have reviewed this post.
Thank you for thanking brett, for me, but there was no need, Because I can and do and will thank all for all they do in this forum. If you care to look at any of my post you will see I do thank everyone.
lasersc said:
If I may say so, I am sorry I can't be on 24/7 and only now have reviewed this post.
Thank you for thanking brett, for me, but there was no need, Because I can and do and will thank all for all they do in this forum. If you care to look at any of my post you will see I do thank everyone.
Click to expand...
Click to collapse
it's okay, laser. nbd. I did it half jokingly. Usually courteous to thank people that help you out...
lasersc said:
thanks for any help
Click to expand...
Click to collapse
Your all good lasersc
Happy to contribute qkster, I'm not quite advanced enough to troubleshoot most problems, so I like to jump on the easier ones when they go otherwise unnoticed.
brettdwagner said:
Your all good lasersc
Happy to contribute qkster, I'm not quite advanced enough to troubleshoot most problems, so I like to jump on the easier ones when they go otherwise unnoticed.
Click to expand...
Click to collapse
You gave good advice, brett.
On the flashback update thread, there is a recovery package.
Included in the package is easy step by step instructions that spells out everything that you need to follow to nvflash and flashing.
I refer to that frequently.
I hope laser was able to go thru that package.
.39 kernel is almost done. HC 3.2 or ICS is just around the corner.
You rock Brett, Thank you so much. I did as you suggested this morning and everything went well. If you only knew, how long I have been fighting this deal, but with your couple of post...Everything is Well
Thank you again!!!
i have searched everywhere i cannot find a solution. i still have the old market. i tried downloading the apk file and putting it on the sd card. when i locate the file on the phone and click on it i get a parse error. i am using the sgs unlock tool/ galaxy s unlock. plsssssss help.
Do you have a themed market? You need to push the vending.apk to /system/app and set permissions and reboot (can do this with any file explorer that has root). If you have a themed market, it will not update when the normal market does. And you cannot generally just push install to make it work.
You are getting that parse error b/c it needs to be pushed to /system/app and not just "installed".
What ROM are you running btw?
Woodrube said:
Do you have a themed market? You need to push the vending.apk to /system/app and set permissions and reboot (can do this with any file explorer that has root). If you have a themed market, it will not update when the normal market does. And you cannot generally just push install to make it work.
You are getting that parse error b/c it needs to be pushed to /system/app and not just "installed".
What ROM are you running btw?
Click to expand...
Click to collapse
i have no idea if i have a themed market. i remember using the one click root. but i dont know which rom iam using. my phone interface is like the stock vibrant. how do i check which rom i have? anyways i push the vending.apk file to system apps, changed the permission to rw-r-r and rebooted the phone. nothing happened. then i tried intall it with the root explore but i get that same pharse error. what next? sorry for the noob questions
oh yeah i am still using the firmware version 2.1-update1 , you think i should update?
Go to settings>about phone and it will tell you the ROM name there. A themed market will look different than the normal. It will either be darker, lighter, a different color altogether, inverted,...
Since you pushed it to /system/app and it didn't work try this. Do the same but before you fire up the market go to settings>apps>market and clear cache and data. If that doesn't work then go back there and hit Uninstall Updates. Then fire up the market, resign in and let me know.
Maybe it is because you're running 2.1, I was never able to upgrade to google play while on 2.1 eclair. I'm not sure why either, it would never work for some reason. I have no problems upgrading to google play now because I'm running a 2.2 ROM. Just in case you decide to upgrade, DO NOT upgrade with samsung kies, it has been hard bricking phones a lot lately. I would follow woodrube's advice before a attempting an upgrade though.
Sent from my SGH-T959 using xda premium
Woodrube said:
Go to settings>about phone and it will tell you the ROM name there. A themed market will look different than the normal. It will either be darker, lighter, a different color altogether, inverted,...
Since you pushed it to /system/app and it didn't work try this. Do the same but before you fire up the market go to settings>apps>market and clear cache and data. If that doesn't work then go back there and hit Uninstall Updates. Then fire up the market, resign in and let me know.
Click to expand...
Click to collapse
i don't think i have a themed market. mine is the standard shoping bag with mr android on it and all in normal colors. ok i tried what you said above and it didnt work. after i uninstall updates. i fired up the market and signed in. i was in the old old android market, then it crashed. i fired the market again and it self updated to the latest android market on its own. the one i had before i did uninstall update. so i am back to square one. i have a feeling its because of the eclair 2.1
the reason i am even doing this is because i cant download instagram. its not on the normal android market only on google store. so i downloaded the apk file, and tried to install it through root browser but i get that pharse error. its annoying.
i dont think i am using any rom. its say ECLAIR. I ONLY ROOTED THE PHONE TO UNLOCK THE SIM. i used the sgs unlock tool
iTz KeeFy said:
Maybe it is because you're running 2.1, I was never able to upgrade to google play while on 2.1 eclair. I'm not sure why either, it would never work for some reason. I have no problems upgrading to google play now because I'm running a 2.2 ROM. Just in case you decide to upgrade, DO NOT upgrade with samsung kies, it has been hard bricking phones a lot lately. I would follow woodrobe's advice before a attempting an upgrade though.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
thats what i am thinking too. damn i am now confused now. how can i update then? with out kies?
gabriox said:
thats what i am thinking too. damn i am now confused now. how can i update then? with out kies?
Click to expand...
Click to collapse
To tell you the truth, I would just flash a custom 2.2 ROM like Fishman Bionix Redux or Moped_Ryder's ROMs. If you have been on 2.1 for this long, I would think that you will be blown away with a fully functioning, rooted and stable 2.2's that are available. They have been nearly perfected and get outstanding battery life. Chances are why you cannot install Instagram is maybe because it doesn't support 2.1 (only 2.2 and above). Just a thought, I don't use it so not sure why it wouldn't be showing up but that is my guess as to why).
Flashing a custom 2.2 is fairly simple nowdays. Just download the ROM.zip from the thread and put in in a folder on your internal. Download the CWR zip from my signature and put it on your interanl_sd (make sure it is the only thing on your internal_sd labeled Update.zip). Boot into recovery and hit Reinstall Packages. It will cycle through (might have to do it twice) and then your recovery will go from stock (blue) to CWR (green). Scroll down to Install from SDcard and find your custom ROM and flash it. Read the OPs but that is the gist of it.
Woodrube said:
To tell you the truth, I would just flash a custom 2.2 ROM like Fishman Bionix Redux or Moped_Ryder's ROMs. If you have been on 2.1 for this long, I would think that you will be blown away with a fully functioning, rooted and stable 2.2's that are available. They have been nearly perfected and get outstanding battery life. Chances are why you cannot install Instagram is maybe because it doesn't support 2.1 (only 2.2 and above). Just a thought, I don't use it so not sure why it wouldn't be showing up but that is my guess as to why).
Flashing a custom 2.2 is fairly simple nowdays. Just download the ROM.zip from the thread and put in in a folder on your internal. Download the CWR zip from my signature and put it on your interanl_sd (make sure it is the only thing on your internal_sd labeled Update.zip). Boot into recovery and hit Reinstall Packages. It will cycle through (might have to do it twice) and then your recovery will go from stock (blue) to CWR (green). Scroll down to Install from SDcard and find your custom ROM and flash it. Read the OPs but that is the gist of it.
Click to expand...
Click to collapse
aight, you got any link to thread that has a tutorial. or download for the 2.2 roms? and if i do it can i keep the standard vibrant interface? lol i just noticed i could click the roms you mentioned above lol. should i odin to stock?
The OPs will tell you how to install them, coupled with what I wrote above. It is really a piece of cake. Might want to YouTUBE it. I think I saw a tut on how to install Bionix on there the other day. Just search Samsung Vibrant and one will pop up. I don't suggest you install ICS at this point. Get your feet wet first. Downloads will be in the ROM's OP that I linked above.
All the 2.2 are customizable. If you like Touchwiz, (shoot me now but...) there's an app for that. I use ADWex as my launcher and both it and LauncherPro are extremely customizable launchers.
Woodrube said:
The OPs will tell you how to install them, coupled with what I wrote above. It is really a piece of cake. Might want to YouTUBE it. I think I saw a tut on how to install Bionix on there the other day. Just search Samsung Vibrant and one will pop up. I don't suggest you install ICS at this point. Get your feet wet first. Downloads will be in the ROM's OP that I linked above.
All the 2.2 are customizable. If you like Touchwiz, (shoot me now but...) there's an app for that. I use ADWex as my launcher and both it and LauncherPro are extremely customizable launchers.
Click to expand...
Click to collapse
wait will this work? i Odin back to stock. then update to froyo 2.2 via kies, then use superoneclick to root the froyo 2.2 and then use the sgs unlock. because i am just rooting to unlock the sim. what do you think?
You don't need to use Kies. Go to 2.1 and then flash custom ROM and if you somehow get locked, just use the unlock app again, although flashing ROMs *shouldn't* lock down your phone. Does for mine at least. If you use my method I posted earlier, you don't need Root to flash and all our custom ROMs are pre-Rooted.
Edit:: Re-read your post. If you are going to stay on stock 2.2 ROM, then not sure about the SGS unlock tool. This thread is straying from the OP about the market. Think about what it is exactly that you want out of your phone and ROM and then we'll go from there. I believe there is a pre-rooted stock 2.2 floating around. Search Moped_Ryder's threads and he has it loaded up.
gabriox said:
thats what i am thinking too. damn i am now confused now. how can i update then? with out kies?
Click to expand...
Click to collapse
Yea you should flash a custom 2.2 ROM. Just get the cwr file from Woodrube and download a Rom through your phone. Get into recovery mode and follow directions for whichever ROM you choose to flash. I am running 2.2 Blue Frankenstein, it is blue themed all the way through, check it out if you like blue http://forum.xda-developers.com/showthread.php?t=1531237 there are pictures in the thread.
Sent from my SGH-T959 using xda premium
Woodrube said:
You don't need to use Kies. Go to 2.1 and then flash custom ROM and if you somehow get locked, just use the unlock app again, although flashing ROMs *shouldn't* lock down your phone. Does for mine at least. If you use my method I posted earlier, you don't need Root to flash and all our custom ROMs are pre-Rooted.
Edit:: Re-read your post. If you are going to stay on stock 2.2 ROM, then not sure about the SGS unlock tool. This thread is straying from the OP about the market. Think about what it is exactly that you want out of your phone and ROM and then we'll go from there. I believe there is a pre-rooted stock 2.2 floating around. Search Moped_Ryder's threads and he has it loaded up.
Click to expand...
Click to collapse
obviously the thread strayed away because there is no way i can get the new goolge market or instagram because i am on 2.1 eclair, to get it i have to update to 2.2 froyo. now here is the main problem. my phone is a t-mobile vibrant and but i am using AT&T on it thanks to sgs unlock tool. if i update to 2.2 and sgs unlock doesnt work. iam screwed. it means i cant call with the phone anymore. so what i want is 2.2 stock froyo rooted so that i can have the new market to download instagram and sgs unlock tool to work, so that i can continue using my AT&T sim. finish. so i guess i will use that pre- rooted stock 2.2 you mentioned.
Found it ---> [ROM][2.2 Froyo][Stock] T959UVKB5 [Deodexed w/Lockscreens+Power Menu] Good luck and make sure you read the OP. Since it has Voodoo Lagfix, the intial boot up will take slightly longer.
Woodrube said:
Found it ---> [ROM][2.2 Froyo][Stock] T959UVKB5 [Deodexed w/Lockscreens+Power Menu] Good luck and make sure you read the OP. Since it has Voodoo Lagfix, the intial boot up will take slightly longer.
Click to expand...
Click to collapse
how do i flash the first download ? the odin and heimdall downloads are corrupted. i have only used odin before.
gabriox said:
how do i flash the first download ? the odin and heimdall downloads are corrupted. i have only used odin before.
Click to expand...
Click to collapse
The thread will tell you.....Usually all you have to do is boot into recovery and choose "wipe data/factory reset" then click yes now go back and "wipe cache partition" and click yes now go back and click "advanced" then "wipe dalvik cache" choose yes. Now go back and choose "install zip from sd card" choose where you downloaded the ROM to (usually "Download" folder if you downloaded it from your phone) pick the file and say yes and it will flash away. Note: you don't really have to do the wipe cache and dalvik cache steps but i do anyway just to get a fresh install, you can even format the system partition if you want a really fresh install. Some people recommend wiping cache and dalvik cache AFTER you flash the ROM, if the thread says to do that then do it.
gabriox said:
how do i flash the first download ? the odin and heimdall downloads are corrupted. i have only used odin before.
Click to expand...
Click to collapse
Hmmm... That's odd, apparently they are both working now. Anywho here's a direct link to the Odin image download: http://apolo.hotshare.net/download/.../UVKB5_Deodexed_Stock_Voodoo_odin.tar.md5.zip. Although the "flashable" method of installation is also rather easy. Actually, there is a guide on flashing roms stickied in the Q&A section. Here's a link: http://forum.xda-developers.com/showthread.php?t=849028. Since you're already rooted and on 2.1 the process of upgrading to 2.2 (Froyo) is shorter. In terms of the guide, you can skip straight to "OKAY, I HAVE ROOT - NOW WHAT? BACKUP!!!". Oh, BTW, seeing that you haven't posted in almost a year...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME BACK!
N00B_IN_N33D said:
Hmmm... That's odd, apparently they are both working now. Anywho here's a direct link to the Odin image download: http://apolo.hotshare.net/download/.../UVKB5_Deodexed_Stock_Voodoo_odin.tar.md5.zip. Although the "flashable" method of installation is also rather easy. Actually, there is a guide on flashing roms stickied in the Q&A section. Here's a link: http://forum.xda-developers.com/showthread.php?t=849028. Since you're already rooted and on 2.1 the process of upgrading to 2.2 (Froyo) is shorter. In terms of the guide, you can skip straight to "OKAY, I HAVE ROOT - NOW WHAT? BACKUP!!!". Oh, BTW, seeing that you haven't posted in almost a year...
WELCOME BACK!
Click to expand...
Click to collapse
hmmmm i cant reboot in clockmod recovery and worst of all i cant download rom manager. its not on my market, only the premium one. **** my life. i am stuck
edit: ok i got into clockmod recovery phew
I posted this at the same time you edited yours. You say it doesn't work. Where is the problem?
*********
You are already on stock 2.1, pull the update.zip and follow my previous directions. No need for Odin and ROM Mgr doesn't support 2.1 anymore.
Step by step:
1 Download ROM (flashable version and not Hem or Odin) to your phone.
2 Pull Update.zip from my signature and put it on your internal_sd.
3 The Update.zip IS Clockwork Recovery
4 Boot into Recovery and hit Reinstall Packages (maybe twice) and your recovery will go from stock (blue) to Clockwork (green0)
5 scroll down to Install from SD and find the ROM that you downloaded in step 1. Hit it and flash it.
6 It will reboot
7 Profit
It is really easy to do, just try it, you'll like it. Don't complicate it more than you need to. Be safe but try not to over think it.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.