Hi,
I impulsively updated my stock 3053 Gtab to 3389 via OTA this weekend. Everything was working OK with 3053, but since the update, I've had slowdowns, crashing to reboot, and some other problems. I'm aware of the kernel lag thing, but I've been monitoring cpufreq when some of these happened, plus it's not sleep-related, so I just want to go back to 3053.
I want to stay stock, and still have OTA, so I think the best way to go back is to put the 3053 update.zip in /sdcard with a /recovery/command file, but wanted to confirm that before I did that.
Can someone here confirm?
Thanks,
Jim
jimcpl said:
Hi,
I impulsively updated my stock 3053 Gtab to 3389 via OTA this weekend. Everything was working OK with 3053, but since the update, I've had slowdowns, crashing to reboot, and some other problems. I'm aware of the kernel lag thing, but I've been monitoring cpufreq when some of these happened, plus it's not sleep-related, so I just want to go back to 3053.
I want to stay stock, and still have OTA, so I think the best way to go back is to put the 3053 update.zip in /sdcard with a /recovery/command file, but wanted to confirm that before I did that.
Can someone here confirm?
Thanks,
Jim
Click to expand...
Click to collapse
Yep. Should do the trick... Hopefully you won't have issues afterwards...
jimcpl said:
Hi,
I impulsively updated my stock 3053 Gtab to 3389 via OTA this weekend. Everything was working OK with 3053, but since the update, I've had slowdowns, crashing to reboot, and some other problems. I'm aware of the kernel lag thing, but I've been monitoring cpufreq when some of these happened, plus it's not sleep-related, so I just want to go back to 3053.
I want to stay stock, and still have OTA, so I think the best way to go back is to put the 3053 update.zip in /sdcard with a /recovery/command file, but wanted to confirm that before I did that.
Can someone here confirm?
Thanks,
Jim
Click to expand...
Click to collapse
Sprdtyf350 said:
Yep. Should do the trick... Hopefully you won't have issues afterwards...
Click to expand...
Click to collapse
Thanks. Re. Your last point, I'm kind of worried about that, but given I want to stay stock, I don't see much choice. This is behaving badly.
Jim
jimcpl said:
Thanks. Re. Your last point, I'm kind of worried about that, but given I want to stay stock, I don't see much choice. This is behaving badly.
Jim
Click to expand...
Click to collapse
I only said that because you just never know.. Without clockwork it would be tricky to fix. But if you run into troubles install clockwork, do the 2 wipes on the first page, or a partition of the sdcard if you end up bootlooped. After that install the 3053 update.zip from clockwork and it will overwrite clockwork and put you back to stock...
Sprdtyf350 said:
I only said that because you just never know.. Without clockwork it would be tricky to fix. But if you run into troubles install clockwork, do the 2 wipes on the first page, or a partition of the sdcard if you end up bootlooped. After that install the 3053 update.zip from clockwork and it will overwrite clockwork and put you back to stock...
Click to expand...
Click to collapse
Well, now you've made my day even worse... I wasn't even thinking of boot looping, etc. I was more worried that doing the recovery to 3053 wouldn't take me back completely (cleanly) to where I was before the 3389 update ...
Oh well.
Darn! I really wish there was a more convenient way to do a real "bare metal" image, which is what I wanted to do before I tried the 3389 update. I know that I could've tried to do an nvflash to do the image, but wasn't quite sure how, so I (again, impulsively) just went ahead and took the OTA.
Darn again!
Jim
jimcpl said:
Well, now you've made my day even worse... I wasn't even thinking of boot looping, etc. I was more worried that doing the recovery to 3053 wouldn't take me back completely (cleanly) to where I was before the 3389 update ...
Oh well.
Darn! I really wish there was a more convenient way to do a real "bare metal" image, which is what I wanted to do before I tried the 3389 update. I know that I could've tried to do an nvflash to do the image, but wasn't quite sure how, so I (again, impulsively) just went ahead and took the OTA.
Darn again!
Jim
Click to expand...
Click to collapse
Haha! Sorry! Maybe I should just learn to shut up sometimes and hope for the best.. Then help ya fix it later if it goes bad..
Sprdtyf350 said:
Haha! Sorry! Maybe I should just learn to shut up sometimes and hope for the best.. Then help ya fix it later if it goes bad..
Click to expand...
Click to collapse
No, I was just kidding. Being aware of possible problems helps me set my own expectations. Although I did say that I did the OTA "impulsively", I had followed the 3389 stuff for about a week before doing the OTA. I guess that since things seemed to working so well for me with 3053, I had a hard time understanding the lag problem and other things that people had mentioned, so I didn't think that it was going to hit me. Now I know better...
Jim
i still dont get why you just dont use one of the custom roms? why stay stock when the custom roms operate 1000000X better than stock and are updated more frequently?
ddarvish said:
i still dont get why you just dont use one of the custom roms? why stay stock when the custom roms operate 1000000X better than stock and are updated more frequently?
Click to expand...
Click to collapse
I would guess because it is his, and he wants to, and so he can.. Why does it matter? Not everyone puts a supercharger on there stock cars either...
ddarvish said:
i still dont get why you just dont use one of the custom roms? why stay stock when the custom roms operate 1000000X better than stock and are updated more frequently?
Click to expand...
Click to collapse
Hi,
To answer your question, I can't give you a good/particular/overwhelming reason.
I've seen almost all of the debates ("discussions") about stock vs. non-stock, and it's just what I've chosen, for now.
I guess that if I *had* to answer your question, I'd say that I still consider myself new to the Gtab and to Android, for one thing, and I've done a lot of embedded programming (on custom, dedicated controllers), I'm still not totally familiar with and comfortable with the "tools" that are available for the Gtab.
If you go back to some of my earlier posts, esp. with roebeet, I'm particularly interested in learning ALL of the ins-and-outs about nvflash, APX, stock recovery, CWM, etc. When *I* (again, this is "my" answer) feel comfortable enough with all of those, then I'll probably start experimenting more outside of stock.
Until then, I want to continue to have the Gtab available for my secondary reason, which is that I'm doing some Android app development, and just got tired of waiting 5+ minutes for the emulator to start ...
Anyway, like I said, this is just my answer, from my perspective. I'm sure others who are sticking with stock have their own, but I felt that you deserved an answer.
Jim
You don't have give anyone an answer - if that's what you want, that's your choice.
There are other stock users and that's one of the reasons why we keep the links for all the stock firmware revisions, here.
roebeet said:
You don't have give anyone an answer - if that's what you want, that's your choice.
There are other stock users and that's one of the reasons why we keep the links for all the stock firmware revisions, here.
Click to expand...
Click to collapse
I knew that , but I appreciate your comment.
Jim
Now with 3452 you may not even have to go back to 3053.. Have you tried it yet?
Sprdtyf350 said:
Now with 3452 you may not even have to go back to 3053.. Have you tried it yet?
Click to expand...
Click to collapse
Yes, per the other thread, I just got it updated. I'll work with it for a few days, to see if the problems are gone. Figured that if I was going to do a recovery, might as well go forward, rather than backwards.
Thanks,
Jim
Well, I would not assume 3452 is official - my guess is that it's UAT, given that the build date is today. Usually a build would take a few days from the build date to release, at least from past experience.
jimcpl said:
Yes, per the other thread, I just got it updated. I'll work with it for a few days, to see if the problems are gone. Figured that if I was going to do a recovery, might as well go forward, rather than backwards.
Thanks,
Jim
Click to expand...
Click to collapse
Yeah I thought about your dilemna when I saw the update. Then I saw you say you were trying it. Maybe they have fixed all the issues you had.. We can only hope right?
Sprdtyf350 said:
Yeah I thought about your dilemna when I saw the update. Then I saw you say you were trying it. Maybe they have fixed all the issues you had.. We can only hope right?
Click to expand...
Click to collapse
As long as I don't get into one of those situations like you mentioned earlier, I'm no worse off ...
Jim
Related
Hey everybody I finally figured out how to fix the line 5 boot error that I myself had and a lot of other people are experiencing while trying to flash some roms. I was experiencing this problem for about a month while trying to flash ava v7 and v8. What bothered me the most is I could flash fresh rom. So I tried everything I could think of and nothing worked. Then right when I was going to give up I thought to myself what do I got to lose let me start from scratch and see what happens. So I unrooted using this method http://forum.xda-developers.com/showthread.php?t=780141 after I unrooted I upgraded to the new ota getting the new pri 1.77. After that was completed I rooted my phone using this method http://forum.xda-developers.com/showthread.php?t=776477 and when that was complete I booted into recovery wiped everything and flashed ava v8 which was giving me the same line 5 boot error everytime before and it WORKED!!! It worked for me and several other people so far hope it works for you. I would also like to say thanks to ava for making such a great rom it really is awsome.
Why does this work?
Also why is ava so bad at making zips but not fresh... and lastly why does ava not do something about it....?
Sent from my PC36100 using XDA App
novanosis85 said:
Why does this work?
Also why is ava so bad at making zips but not fresh... and lastly why does ava not do something about it....?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I don't know why it works it just does. I'm not a dev I'm just a regular guy who tries a lot of different things and found this out so I thought I should share it. As far as ava making bad zip files I wouldn't talk bad about one of or devs who work so hard on their own time to make us roms for free.
AssAssiN FtC said:
Hey everybody I finally figured out how to fix the line 5 boot error that I myself had and a lot of other people are experiencing while trying to flash some roms. I was experiencing this problem for about a month while trying to flash ava v7 and v8. What bothered me the most is I could flash fresh rom. So I tried everything I could think of and nothing worked. Then right when I was going to give up I thought to myself what do I got to lose let me start from scratch and see what happens. So I unrooted using this method http://forum.xda-developers.com/showthread.php?t=780141 after I unrooted I upgraded to the new ota getting the new pri 1.77. After that was completed I rooted my phone using this method http://forum.xda-developers.com/showthread.php?t=776477 and when that was complete I booted into recovery wiped everything and flashed ava v8 which was giving me the same line 5 boot error everytime before and it WORKED!!! It worked for me and two other people so far hope it works for you. I would also like to say thanks to ava for making such a great rom it really is awsome.
Click to expand...
Click to collapse
u dont really need to go over and do this whole thing... its just something in the update script that was probably off.
im assuming u dont know how to look at the update-script and such... thats why the whole long way of doing what u did... but hey... im happy u got it to work for u.
next time u might wanna try looking at the script in the zip file and maybe edit it a little your self and resign the zip... it not so hard to do, but i guess if u not sure how than your way would probably be ok.
novanosis85 said:
Why does this work?
Also why is ava so bad at making zips but not fresh... and lastly why does ava not do something about it....?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ouch so harsh. i use the same thing fresh does. its all about the size and the script. i never used clockwork so to be sure that it would work on the recovery i changed things. this caused some issues.
I am doing something about this but its hard when i dont get the error and people that do get the error, report it fixed with V8 and some dont.
also i learned everything from flipz so its hard to surpass the master
ill be releasing a fix tonight along with some other things im sure you and everyone will enjoy
aamikam said:
u dont really need to go over and do this whole thing... its just something in the update script that was probably off.
im assuming u dont know how to look at the update-script and such... thats why the whole long way of doing what u did... but hey... im happy u got it to work for u.
next time u might wanna try looking at the script in the zip file and maybe edit it a little your self and resign the zip... it not so hard to do, but i guess if u not sure how than your way would probably be ok.
Click to expand...
Click to collapse
I figured there was a better way I will look into doing it this way I'm just not familiar with editing scripts so I have to do a little research on it but thank you for your input. The way I did it was probably long and could be shorter but it its still a good way for someone who isn't familiar with scripts.
I used the file at this link and my problem was solved. I was an un revoked user... http://forum.xda-developers.com/showthread.php?t=752832 this doesn't require any data loss so maybe try before going through the whole hoopla of a un-root followed by re-root. Just my .02¢
AssAssiN FtC said:
I figured there was a better way I will look into doing it this way I'm just not familiar with editing scripts so I have to do a little research on it but thank you for your input. The way I did it was probably long and could be shorter but it its still a good way for someone who isn't familiar with scripts.
Click to expand...
Click to collapse
coojoe1000 said:
I used the file at this link and my problem was solved. I was an un revoked user... http://forum.xda-developers.com/showthread.php?t=752832 this doesn't require any data loss so maybe try before going through the whole hoopla of a un-root followed by re-root. Just my .02¢
Click to expand...
Click to collapse
I didn't root via UnrEVOked and I had the Line 5 error as well... while unrooting & re-rooting may take a while, it's the only thing that has worked for me to fix the LINE 5 error on the AVA8 install. Being that i'm not a dev, I don't know what AVA could or couldn't have done wrong with the ROM, but the problem with the install was not affecting everyone, and those that it did affect achieved root through different methods. So thank you AssAssin for figuring out a workaround, however rudimentary it may be.
blozout said:
I didn't root via UnrEVOked and I had the Line 5 error as well... while unrooting & re-rooting may take a while, it's the only thing that has worked for me to fix the LINE 5 error on the AVA8 install. Being that i'm not a dev, I don't know what AVA could or couldn't have done wrong with the ROM, but the problem with the install was not affecting everyone, and those that it did affect achieved root through different methods. So thank you AssAssin for figuring out a workaround, however rudimentary it may be.
Click to expand...
Click to collapse
Your welcome glad to have helped.
Avalaunchmods said:
...ill be releasing a fix tonight along with some other things im sure you and everyone will enjoy
Click to expand...
Click to collapse
Has there been a fix for the Line 5 error added to V8 yet?
I'd say no since I'm getting the line 5 error now. I even switched to amon-ra but i'm still getting it.
When you get the line 5 boot error it doesn't matter how many times you switch back and forth from amon ra or clockwork or wipe or do whatever you are still going to get it. I tried all of that even turn sign on and off and nothing the only way that I managed to get past it and flash the rom I wanted (ava v8) was to do what I explianed in the op. Hope it works for you too.
As the title says, here's the Rom.zip extracted from RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe for those that don't use Windows, or prefer to have their RUU in zip format.
This will flash your phone to 2.31.651.7 STOCK.
http://www.mediafire.com/?m6x4sr682ruk027
Simply rename this to HERCIMG.zip and place on the root of your SDCard.
Power your phone completely off.
Press and Hold VOL DOWN and POWER until your phone boots into HBoot mode.
Wait for it to verify the zip, then click <ACTION> (Trackball) to update, or <SEND> (Green Call) to cancel.
Enjoy!
Here's my guide to rooting .7:
http://forum.xda-developers.com/showthread.php?t=804296
Personally..I want to say THANK YOU, THANK YOU, THANK YOU.
I have spent the last four hours searching for this. This needs to be stickied. I'm bookmarking it for sure. This got my phone unbricked..I thought all hope was lost and I would have to call in for warranty support (I got mine refurbed through Sprint last October..so I don't even know if I would still have any warranty support), and see if I could try my luck and getting it replaced, since that is what others have said to do as apparently this file from OP, did not exist.
And so for future reference, so that others don't go mindlessly searching through the forums.
If you
a.) Managed to overwrite your Recovery some how or completely delete it. (I did..and from searching this and many other forums over the past couple hours..I can see I wasn't the only one), and also have no boot (or a corrupted boot loop)
b.) Still have S-ON (You can find this out by powering off your phone and then pressing and holding the power button and the lower volume button), I recommend you turn S-Off for future reference if you're going to be dealing with customer ROMs a lot (so you don't have to go through the hell I just did..). See here..
http://forum.xda-developers.com/showthread.php?t=759955
c.) Have an updated Hboot (1.47) (you can also find this info. in part b.)
....then you KNOW that you are stuck. Because you
a.) Cannot flash a ROM in Recovery because you cannot access it.
b.) You cannot access ADB because your phone won't go that far and will only go into fastboot..
c.) But even though you have access to fastboot you can't do ANYTHING like flash a recovery image or a ROM..or anything for that matter..because S is still ON. (this is the "not allow" messages you will see pop up.)
d.) You have bootloader 1.47 so if you for example, were like me couldn't use this file here.. (http://forum.xda-developers.com/showthread.php?t=657086), because it would say there was a newer version and wouldn't install it.
So this file right here..was the only thing getting my phone back to a usable state. And considering that my searches have shown to pretty much give up all hope and have it sent it for warranty repair, then I think this thread deserves a bump for all those that have screwed up.
Yeah..I have to start ALL OVER now from a stock ROM (thank god for nandroid), but at least my phone isn't a dead brick.
Just thought this needed a well deserved bump.
I wonder if there is a RUU for the latest .2?
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
Forgive me for seeming NOOBish... but I can use this to do the same, then restore Nandroid back and it will keep the PRL/Profile update?
Just wondering... lolz, thanks!
Yup But you will have to reroot. This takes root from you. You will have to reroot with the Hero rooter from Reg or Z4 or one click root. But read read read. And as far as the prl/profile yup it will stick. When your phone boots up after running this just go into settings and updates and choose update profile and update prl don't update firmware. I repeat don't update firmware. After that just reboot and check your prl should be 60675. After that reroot, then flash a recovery and then nand restore. Hope this helps good luck
Remember this returns you to stock you will loose root and recovery..
Yea it's me Again. With the
Modified .HERO.
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
jckeyser said:
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
Click to expand...
Click to collapse
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Thanks for the reply's all... I like Sense and have NFX rom on my Hero, loaded a few ROMS but they won't update, so no worries, when I have some free time I'll sit and do it then. I don't like the one click rooters nor the clockwork recovery, I guess I'm old school and do it the hard way, lol, but thanks for letting me know it'll work (prl update) and stay on the handset!
Regards!
Without opening a huge can of worms I would like to know whats the best newest rom out there with sense I just searched for like 3 hours and lot of threads are old and I want what ever is new with sense also would like to upgrade to 2.2 im on Honeybun v.-2 lite firmware 2.1 update1
Gelladuga69 said:
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
Click to expand...
Click to collapse
you got a link ? Im searching now
laie1472 said:
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
No need to reroot because it was a nandroid. Can't make a nandroid if you're not rooted.
Sent from my HTC Hero CDMA running Android 2.3
Does anybody have the original MD5 checksum for this file? I wanna make sure this file downloaded properly. Thanks in advance!
EDIT: efa439da700b5fad7ea49915ef7d2866
Sent from my HTC Hero CDMA running Android 2.3
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
mrtimo said:
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
Click to expand...
Click to collapse
What? Is your phone even rooted? Sprint upgraded to 2.1 a LONG time ago, the update is available at www.htc.com
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
systemshock869 said:
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
Click to expand...
Click to collapse
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
il Duce said:
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
Click to expand...
Click to collapse
According to the OP this one was extracted from the RUU, so it *should* work S-ON.
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
can you get it into download mode...?
if so run the one click again and you might have to check the box for bootloaders, on the second run...meaning I would run it twice...
It does that immediately on power up. Doesn't even get to the Samsung screen. Odin will recognize the phone, but when I try to flash a return to stock package (which I used earlier perfectly fine), it says the md5 is invalid.
Like I said, I never even got to the point of installing the bootloader since I forgot about the drivers. Are you saying I should install the drivers and try to flash the bootloader again?
Thanks so much for the help! I've never had this much trouble with a phone before
EDIT: I'm a dumbass. since I couldn't see the screen, I forgot to press up again after entering download mode. Odin is now in the process of installing the aforementioned return to stock package. And I think it worked!
You have no idea how grateful I am of you for pointing that out! I feel kind of dumb for not trying it, but when the screen looked like that I could only assume there was no functionality!
THANKS AGAIN! Times a million!
Lol ok let us know when you get it up and running....kk
Sent from my SAMSUNG-SGH-I717 using xda premium
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is my IMHO...as is yours
+10 Char
bigjoe2675 said:
whooo there...slow your roll...
the op has the options to put what he wants, and actually if you have not been tracking the ICS/CM9/AOKP threads they have made leaps in the smashing of bugs....actually very stable and good to go now, seeing how just months ago we didn't even have any ver of ICS, and yes it takes homework to install..
and you kept stock on your friends Mommy phone well that was between you and him and Mommy...
so long story short....as far as unpopular, I see this device being sold and for a high demand on CL and Ebay...with all the support given here...that is plenty IMHO...as is yours
Click to expand...
Click to collapse
This makes about as much sense in English as it does in Japanese.
wayzata said:
This makes about as much sense in English as it does in Japanese.
Click to expand...
Click to collapse
You are a smart guy... i am sure you understood me....
Arigatou gozaimasu btw...just leave it as that....
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
mvgc3 said:
I was trying to update my mom's Infuse to ICS, then all of a sudden this (attached) happened. Heimdall had just given me the libusb.dll error (I needed to update the bootloader cause I kept getting rainbows in CWM), so I was unplugging the phone so I could get the right drivers.
I have a horrible feeling I did something very wrong. I can't imagine why what I was doing would have caused this though, since the cmd had gone back to a default state after giving the error.
Is there any way to fix this?? Thanks a ton in advance!
Click to expand...
Click to collapse
Same thing happened to mine when i flashed back to stock. Kept trying download mode and finally worked. Keep trying and also try recovery. Worked for me
Sent from my SAMSUNG-SGH-I717 using xda premium
wayzata said:
What EXACTLY gave you the idea to put your mother's phone on a ROM that half works and has many bugs? Just trying to understand... I could have done this to my friend's mom's atrix, but I didn't because the stock ROM will always have the least bugs for unpopular devices like ours. (ones that don't get official support for CM or AKOP or anything)
Click to expand...
Click to collapse
First of all, every once in a while, she asks me if there are any updates yet.
Second, there's only a short list of insignificant bugs mentioned in the ICS topics.
I flashed GB on it a while back, and I figured since CWM and everything was set up already I wouldn't have a problem; flash, reboot, flash again, done. Unfortunately, it wasn't flashing the second time for whatever reason, and I figured it had something to do with the now half-functional CWM.
Anyway, to those of you who weren't unreasonably judging me, and rather decided to help: Thank you, the phone is now back up and running!
Prometh1216 said:
Hajimemashita Joe sama
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
LOL, woooooooootttttttt
Same thing happened to me. What I did was send my phone back to Samsung tell them everything ( except about rooting) they will email you a label then ship it off and get back in about 1 week. They will put stock gingerbread on it. Hopes this helps.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
My wife recently updated her phone via wifi to JB from ICS and her phone is damn near unusable. She wants to throw it out on the freeway. Her phone since the update is sluggish, and a constant headache for her. Her phone is stock, and unrooted. Do I need to root it in order to go back to ICS? Sorry in advance if this has been asked before.
SouthStockton said:
My wife recently updated her phone via wifi to JB from ICS and her phone is damn near unusable. She wants to throw it out on the freeway. Her phone since the update is sluggish, and a constant headache for her. Her phone is stock, and unrooted. Do I need to root it in order to go back to ICS? Sorry in advance if this has been asked before.
Click to expand...
Click to collapse
You could flash in an ICS factory image using the built-in recovery (or at least I seem to remember doing something like it). But before anything, you need to know which variant of the phone you're dealing with (i9020a/i9020t/i9023/etc.) Just turn off the phone and check below the battery for the exact model. Once you have that, I (or somebody else around here) can link you to the right image for the device. :laugh:
nightsky87 said:
You could flash in an ICS factory image using the built-in recovery (or at least I seem to remember doing something like it). But before anything, you need to know which variant of the phone you're dealing with (i9020a/i9020t/i9023/etc.) Just turn off the phone and check below the battery for the exact model. Once you have that, I (or somebody else around here) can link you to the right image for the device. :laugh:
Click to expand...
Click to collapse
Sorry about the missing info. Her phone is the NS4G model SPH-D720. Hope that may help.. Thanks for the reply Night.
SouthStockton said:
Sorry about the missing info. Her phone is the NS4G model SPH-D720. Hope that may help.. Thanks for the reply Night.
Click to expand...
Click to collapse
Oh, there seem to be no full recovery-flashable images for the NS4G. You could install a full image using fastboot but that would require unlocking your phone's bootloader (which more or less voids any warranty) and would also wipe all the data. If you're not particularly attached to all the data in the phone, you could try a factory reset to see if JB problems get resolved. Otherwise, maybe some other forum member might have a better idea.
OK, thank you. I'm about to go to sleep, and I'll ask her in the morning how she feels about the phone being wiped. In the meantime, maybe others can shed some info also. Again, thanks for the replies.
My wife and I both have the NS4g from Sprint, but our approach as to how we use the device is very different. She doesn't like change, simply wants the parts of the system that she uses, to work ... mainly tethering, mms, camera, phone. If your wife is anything like mine ... make your life a little easier, and just root the phone. It will give you so much more flexibility and choices. About a week ago, OMJ posted a stock, rooted rom in the NS4g development thread that would be perfect for her. It's all there ... smooth ... quick ... everything works.
i think before trying anything that could avoid your warranty you should do a factory reset ... it probably could solve all your wife issues ... it will just delete all your app but not photo or documents ( unless you select that option ) and you could after reinstall just the really needed apps your wife need ...
@wmdunn - She mainly uses her camera as well.
@kriout - doing a factory reset will still give her back JB tho wouldn't it? I'll ask her just to try it, and if it still runs slow, I guess root it?
SouthStockton said:
@wmdunn - She mainly uses her camera as well.
@kriout - doing a factory reset will still give her back JB tho wouldn't it? I'll ask her just to try it, and if it still runs slow, I guess root it?
Click to expand...
Click to collapse
The camera software in JB is really nice. As for rooting ... I have rooted every phone we've owned, and never had any problem with warranty issues. The rooted versions of the stock JB rom are smoother and quicker than the ota.
wmdunn said:
The camera software in JB is really nice. As for rooting ... I have rooted every phone we've owned, and never had any problem with warranty issues. The rooted versions of the stock JB rom are smoother and quicker than the ota.
Click to expand...
Click to collapse
reinstall the stock image via fastboot, u will get a buttery smooth experience
Unfortunately, she is going to just deal with it and doesn't want to redo all the game play she has worked for for the last year. Thank you for all your input, I'll be sure to recheck this thread should she change her mind and re-read your help.
Cascabreu said:
reinstall the stock image via fastboot, u will get a buttery smooth experience
Click to expand...
Click to collapse
To do that via fastboot, Would I have to root?
/thread
No just an unlocked bootloader (wont void your warranty)
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
I'm on the OTA JB and stock. Is there anyway to gain root without having to go back and then reinstall JB? I had hoped someone would have come up with a straight forward means of rooting this device as with the old one click. I hope it's in the works.
ergon said:
I'm on the OTA JB and stock. Is there anyway to gain root without having to go back and then reinstall JB? I had hoped someone would have come up with a straight forward means of rooting this device as with the old one click. I hope it's in the works.
Click to expand...
Click to collapse
Well I guess I should have kept the phone I had. I bought this thing at retail and no help from the home team. What th hell. Either noone knows the answer or gives a ****. If there's no way just say so.
ergon said:
Well I guess I should have kept the phone I had. I bought this thing at retail and no help from the home team. What th hell. Either noone knows the answer or gives a ****. If there's no way just say so.
Click to expand...
Click to collapse
sorry that is the only way at the moment
I had tried to "save root" on ICS beforehand but because I flashed JB through an SBF it did not work to retain it. I flashed SuperSu through CWM recovery and got root on stock JB.
My bootloader is unlocked BTW.