Related
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
No CWM for me? Primo not going into CWM recovery any way I try
So I unlocked the prime after realizing root was not the only thing I needed to start flashing ROMs.. TRUE
I rooted using Sparky's method, so easy too. I also tried to root with viper mod one time when apparently Sparkys wasnt working again after I did something like un-root for fun. But Vipermod failed due to drivers that weren't installed and still haven't, reason: could not figure out how or what part was the driver to be installed nothing i clicked on (in XP) worked to download the drivers. however XP does recognize the prime after Windows Media Player update 11 . it said flash complete or successful . I've flashed CWM from the app itself but the only real function I have from it is fixing permissions...
So should someone like me who just reads downloads and flashes (like a madman flasher) to just wait for a newer version that is fully functional so I dont mess things up and need to learn hours of great knowledge to unbrick the TFP/???
I've read that its not really working all the way is this true???
and another ?Q: I want my web to be speedy like Speedy Gonzales so what do I delete from it and what is the best web browser for speed surfing... this prime was crawling around untill I deleted some things that were uselessly running it seems to have worked a bit but not enough a delete list would be rad. Also one other question was it my order of operations which led to a faulty CWM? though I ve reflashed it several times to no better result.. And also if you are still reading (and thank you very much if you are) I dont know how to manually give CWM a go or how to manually get into recovery--- volume up and down plus power seems to soft brick the Prime untill I hold down the power button for a while untill it vibrates for a second then release and push it again to turn it on....and I held power plus volume down but such small print showed up on the upper left corner that i couldn't really know what to do... I also saw the symbols one was a USB symbol,Q: What is this function? WHat would happen should I push the USB symbol ???... ALso can I get updates from Asus after the unlocker app has been used EDIT: DON"T need them however I will find out how to turn these FOTAs off . And Q: does anybody know how to keep the Logitech keyboard connected it times out so when you go back for it it can take a good thirty seconds recovering from its nap... any fix? thanks alot I cant wait to start flashing better ROMs than stock, mine is fairly buggy
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Juggernaut 5.0
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Thanks
tedr108 said:
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Click to expand...
Click to collapse
Im giving it a go now thanks for the CWM instructions that part is solved however I asked like ten questions though and am thankful for your answers
I just did a backup in CWM thanks a lot I' d hit thank you again but its gone THANKS!!!
*If I helped hit thanks*
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Darkside
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
I had a similar problem. Bought my Prime from Amazon in the USA and it came preloaded with Honeycomb - imagine that!!! Anyways I struggled as a result to flash a recovery...I seemed to get root quite easily using NachoRoot and ViperMod methods but flashing a recovery and trying to boot into recovery had me ending up with an exclamation marked Android on boot! 1 day of persistent trying and searching high and low, and am glad to report I finally have a rooted Prime with working recovery (just about to flash Touch Recovery now and then a custom ROM...) running ICS 4.0.3...
My steps:
Trying to flash a custom recovery on HoneyComb really was the show-stopper here, using NachoRoot, Memphi*, nor ViperMod...it just wouldn't work using ADB, fastboot etc
So after 1 day of trying and almost dreading having to send the device back to the US for a swap out, I decided to focus instead on upgrading my firmware to 9.x.x.15 (just below the .21 version which has no root tool at the moment!)
So downloaded a pre-rooted ICS 9.x.x.15 custom ROM from somewhere (google is your friend here) and then followed this tutorial here: http://forum.xda-developers.com/showthread.php?t=1492887
Once I was on ICS, it was then easy to use ViperMod (excellent tool!) to quickly get rooted and successfully flash CWM
Great work to the devs of the different tools I have come across and used.
great
fyi, you only need root to flash cwm FROM rom manager, otherwise you can use fastboot to flash cwm manually.
Sent from my TF201
I was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Put your phone in download mode. (power it off, hold down the volume down button and insert the usb cable)
Flash this with Odin in the PDA slot, auto reboot the only thing checked:
http://d-h.st/UWm
So I'm assuming seven hours is a lot for you? I've been reading here for over a year and I'm still learning. Really to root all you would have had to do is flash a kernel in .tar format with Odin (our kernels come with cwm built in remember) obviously you would want one that's compatible with the version of android you're using. There is a lot of information here. But to say the " attitude here sucks" like you did..... Yer wrong. I know sometimes it seems harsh, but we're just trying to get people to do things for themselves and thus learn even more, positively influencing them in the end.
I think I see your problem. Perhaps if you drop the entitlement attitude you might get more help. No one here is obligated to help anyone. The people that do are unpaid volunteers willing to share their expertise. This is NOT the Help Desk. Remember that before you consider making another ungrateful post like this one.
XDA-dev's are free volunteers, first of all.
We are here for the last someyears and we had providing the best help for anyone related to the phones, eventough devs always repeat that dont mirror us, many people do mirror thier works and someone claims tgat they had done it and yet this site is considered as the best resources for android fanboys.
The another thing is that we are professionals who spare our minute free time for the betterment of phones and to.unlock the hidden capabilities of phone.
I could say to you that have patience and patience never makea you sad.....
BE GOOD
Sent from my GT-S5360 using xda app-developers app
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
rodimus_prime said:
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Ever hear the expression "you catch more flies with honey than vinegar" ?
Everyone on this forum has been able to load custom firmware using the posts you've been linked to -- everyone except you. So, instead of getting upset with everyone else, take a deep breath and try again.
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently.
Click to expand...
Click to collapse
Thankfully you're not a moderator.
rodimus_prime said:
Ok so I've been unhappy with the 4.0.4 official ATT update and its caused my phone once or twice a day to shut off and I have to pull the battery out. So I got the bright idea to root it. I'm not a stranger to this I had the captivate and infuse before this phone. I had roms on those with no issues. Now I followed this thread http://forum.xda-developers.com/showthread.php?t=1746181 and the phone crashes on bootup saying google account manager has stopped and wont even let me get past it. Then I tried another kernal SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar and that just has a yellow ! up and never even gets any further
I've spent 7 hours now in a row reading posts, to be frank, the attitude here SUCKS. Instead of people answering the question they point you off to some post you already read 10 times before, already tried and it doesnt work. I've also tried just putting it back to factory with I777UCKH7-CL503881-No-BL.exe and that doesnt work either
Click to expand...
Click to collapse
Use the return to stock guide to go back to stock GB. Never go to another site other than ours as the other sites have ad kernels which break wifi or brick phones. Once you flash the GB stock go into 3e recovery and wipe by holding power and both volume buttons. Use the volume keys to move up and down and power to select. If power doesnt work then use home. Once you boot up you can set up or whatever. Next follow the Flash Custom Firmware Without Incrementing Flash Counter. Make sure to use a GB kernel in Mobile Odin. Now you can flash custom roms using CWM if you did it right. If you flash an ICS rom you can use Triangle Away to remove that triangle at boot up. You can also use a jig which is safer and able to be used on any version.
r00t4rd3d said:
If I was a moderator, the last 3 posters would be banned, permanently. Don't you guys have something better to do then to pick at the frustration comments of user who's phone is not working at the moment?
Click to expand...
Click to collapse
You need to be here more than a month to understand where those 3 posters are coming from.
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
jthatch12 said:
7 hrs wasted. If you want help, shoot me a pm and I'll help you before I get hammered tonight. You have 4 hrs and counting....
Click to expand...
Click to collapse
Or PM me cause I won't be hammered. Also reference the guide I posted as well.
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
rodimus_prime said:
I managed to get Serendipity 9.4 loaded on it and its seeming to work however I dont seem to be able to get anything else to not boot loop or fail
I'd be happy with a rooted ICS, dont really need all the fancy stuff but when I try to use this http://forum.xda-developers.com/showthread.php?t=1746181 I cannot get it to load stable, I get bootloops, non stop force closes.
I did seem to fix the power button issue, took it apart and swapped the button with a damaged i777 I had laying around here and thats working now, so really I just need the stock ICS on it and thats the extent of any tinkering I ever want to do with this phone again.
I picked up a Optimus G today as a replacement, god I hate it, the music sounds like garbage and the camera is worse. Theres about zero cases made for it. I have 13 days now to return it so I'm hoping I can resurrect my GS2.
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
If you wish to be on stock ICS go ahead and reboot into recovery and factory reset. Next turn off the phone and remove the battery. Plug in the usb to the phone while it's connected to your computer while holding both volume buttons. You should be in download mode now once you press the correct volume button. Now you can use Odin/Heimdall to flash Stock ICS. Note this does contain the EMMC Superbrick bug which is why you factory reset prior to flashing it. If you want a custom rom PM and I can tell you
rodimus_prime said:
It says to If flashing this from another base, you should perform a wipe data/factory reset before you flash this package, should I flash the package first? Seems like after that I only have 3E recovery instead of clockwork mod, which I need to flash the kernal, or should I do the kernal first? These things are not really detailed
Click to expand...
Click to collapse
Seems like your answer is in there already. Kernels can be flashed after with Odin. Use a kernel with CWM if you want that.
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
unorthodocks said:
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
Click to expand...
Click to collapse
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom. Also, Im not familiar if NK1 can use towelroot and safestrap well. My recommendation would be to
1. clean wipe to nc5
2. towel root
3. install safestrap
4. flash ONLY roms that say they were safestrap compatible.
5. Flash any patches, modems, etc.
Weeks? How about spending a few hours reading up on what you can and can't do with your phone.
Raymondlikesroot said:
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom.
Click to expand...
Click to collapse
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
unorthodocks said:
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
Click to expand...
Click to collapse
The reason that LS did a full boot is because certain aosp roms can function with a touchwiz kernel. However, the result is always buggy. There is s4 verizon general thread talking about this.
There are many other tw roms. Just go to andriod devlopment! On the top of my head, I can think of eclipse, hyperdrive, echoe, and empty galaxy.