I cannot get JB still. I bought the phone from rogers and just use it on Telus.
Always when I try it gets stuck on bootloop.
Could I just borrow somebodies sim from rogers or fido and let them get the OTA?
not really sure how to get JB. Nothing has worked so far.
The OTA has absolutely nothing to do with what SIM you have in your device.
martonikaj said:
The OTA has absolutely nothing to do with what SIM you have in your device.
Click to expand...
Click to collapse
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Mackie011 said:
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Click to expand...
Click to collapse
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
martonikaj said:
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
Click to expand...
Click to collapse
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
And that is pretty much where I am at right now.
Not really sure how to make it work.
Mackie011 said:
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
Click to expand...
Click to collapse
Likely didn't wipe properly, chose the wrong ROM, or tried to switch between ROM makers unsuccessfully.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
Click to expand...
Click to collapse
When you flashed back to stock it didn't flash properly, or missed part (like recovery, bootloader or radio), so the OTA won't install properly.
If you want stock 4.1.1, just flash it completely. Stop trying to mess with an OTA.
This is the only guide I'd recommend: http://forum.xda-developers.com/showthread.php?t=1626895
Factory images... including 4.1.1 are right here: https://developers.google.com/android/nexus/images
As well, some have reported issues trying to flash JB if they had an old bootloader. Make sure you flash the LC03 bootloader before trying to flash a JB ROM. (It's already part of the guide mentioned above.)
Sent from my Galaxy Nexus using Tapatalk 2
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
So i have to give a little history here. A while ago i put CM on a buddies phone, he didnt care for it, and we put it back to stock and i think we just left it rooted (this was months ago, so im not completely sure) anyways hes been doing OTA no problem, and the other night i guess he did the new one from ATT. i think this is 4.4.2, from doing tons of research it looks like his Knox got tripped, no big deal he just wants the phone to work.
As of now it boots up to the ATT logo and the globe freezes and thats it.
I was able to install TWRP, and then reinstall CWM (through Odin) thinking that might help. I've tried to flash i think 4.3 JB stock on there and then i get the "Auth Failed" line at the end.... i've tried factory resets, and attempted to update from his sd card but the files zip files are not being recognized...
in case its not obvious, ATT, Galaxy s3
Any ideas???
petersami said:
So i have to give a little history here. A while ago i put CM on a buddies phone, he didnt care for it, and we put it back to stock and i think we just left it rooted (this was months ago, so im not completely sure) anyways hes been doing OTA no problem, and the other night i guess he did the new one from ATT. i think this is 4.4.2, from doing tons of research it looks like his Knox got tripped, no big deal he just wants the phone to work.
As of now it boots up to the ATT logo and the globe freezes and thats it.
I was able to install TWRP, and then reinstall CWM (through Odin) thinking that might help. I've tried to flash i think 4.3 JB stock on there and then i get the "Auth Failed" line at the end.... i've tried factory resets, and attempted to update from his sd card but the files zip files are not being recognized...
in case its not obvious, ATT, Galaxy s3
Any ideas???
Click to expand...
Click to collapse
You can try to flash a NE4 ROM on it through TWRP or CWM. If that doesn't work, try to flash NE4 with Odin.
Have you tried a factory reset?
crazymonkey05 said:
Have you tried a factory reset?
Click to expand...
Click to collapse
ya tried everything, tried flashing through odin... absolutely nothing. i think guess my buddy has done the 4.3 updates for a while, and the latest bricked his phone... i guess we may have left it rooted, im not entirely sure. but he went and got an s5. i feel bad since i originally rooted it. but he's been doing updates without taking any time to research if he was causing any problems.
My current concern is my s3 was rooted as well and was thinking of going back to a stock rom and bootloader, but im worried if i update to 4.3 if that will cause a brick.... anyone know??
Have you tried the 4.3 firmware? Enewman17 has it in a thread in the development section I think.
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
droidian1441 said:
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
Click to expand...
Click to collapse
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
On this tablet I tend to prefer stock roms however I'm not against custom roms. I will give your suggestion a try. Thanks a lot.
Sent from my VS985 4G using Tapatalk
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
Okay. I flashed TWRP recovery however my touchscreen is not working. So I am now back in the corner.
Do you happen to have any other suggestions?
EDIT: Now the screen is working.
It worked! Thanks a lot. I appreciate it.
Sent from my VS985 4G using Tapatalk
OK, after trying everything that I could think of, including suggestions to get my phone to be recognized by the computer on USB and the fast charging working again (only thing I have not done is replace the battery). I am on the Deodoxed [ROM] [Touchwiz-PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016] ROM currently. I still have the original nandroid I made when I purchased the phone last year and made right after rooting. It is the AK3 firmware. Can I wipe everything and do a clean flash of the original ROM to try from scratch and see if that helps without breaking the phone?
Thanks!
h4kudoshi said:
OK, after trying everything that I could think of, including suggestions to get my phone to be recognized by the computer on USB and the fast charging working again (only thing I have not done is replace the battery). I am on the Deodoxed [ROM] [Touchwiz-PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016] ROM currently. I still have the original nandroid I made when I purchased the phone last year and made right after rooting. It is the AK3 firmware. Can I wipe everything and do a clean flash of the original ROM to try from scratch and see if that helps without breaking the phone?
Thanks!
Click to expand...
Click to collapse
I'm pretty sure anything before OK1 firmware won't work anymore. Samsung or Sprint made the new bootloaders block anything older from working, for security reasons I guess.
Will your phone connect to odin? If so flash back to one of these stock roms. Here.
I do remember seeing some post of people with bad batteries causing weird problems though. You can maybe look into that more deeply.
Hope this helps!
I cannot connect to a computer at all. I always get USB device not recognized error. I've tried on a few computers. So no, I cannot odin at ll. Is there a flashable stock I can try?