Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
I have a rooted Amaze with just some bloatware removed. Yesterday I received a notification in the status bar that a system update was available. When I try to run the update the phone reboots and then freezes with a big green X on the screen. Doesn't look like something official. Has anyone seen this before or know what it's about? I'm thinking maybe it's just failing to run the update because of being rooted or a related issue but can't find any info on Google about the green X.
I finally pulled the battery out because it wouldn't respond and then turned the phone on again. It booted fine and I still have the notice about the update. I'm reluctant to try again until I find out what's going on. Thanks.
I don't think you're able to install an update through a custom recovery..There should be a ROM with that update already in it.
If you have a Custom ROM you can't take the update that is intended for stock unrooted ROMS.
Sent from my HTC Amaze 4G using xda premium
Thanks for the feedback. I don't have a custom rom - just the stock minus some bloat. I can see how the custom recovery, however, might interfere.
I can't find any info on the update and what it includes or why I might want/need it but assuming it would be good to install then is there an easy way to remove the custom recovery? Would running the stock update.zip do this or do I need to go through the full un-root process?
If you have CWM recovery already,
1. Go to /downloads folder inside the internal Storage. You can find the OTA.
2. Rename it to "update.zip" and copy to External SD.
3. Reboot the device to recovery.
4. Select update.zip and update manually.
5. After update & reboot, delete both original files to get rid of notification.
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
droidux said:
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
Click to expand...
Click to collapse
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
skr_xd said:
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
Click to expand...
Click to collapse
Yes, I removed facebook and friendstream. Not sure why those would be necessary to run a system update but you may be right about not being able to update a modified phone. Maybe the update isn't anything I need anyway if it wants to update an app I don't want.
Thanks for the help.
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
droidux said:
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
Click to expand...
Click to collapse
yes its the custom clockworkmod i made
xboarder56 said:
yes its the custom clockworkmod i made
Click to expand...
Click to collapse
Thanks for the confirmation and awesome software. I noticed there is work on version 5.0.2.7. Assuming it would be wise to update once released.
Same issue here. I have stock rom without any bloatware removal.
I just unlocked the bootloader than installed CWM and rooted the phone.
when I try to update phone OTA it stucks in splash screen (With Big Green X logo)
Flash prerooted rom you good to go
Sent from my HTC Amaze 4G using xda premium
I just spent abut 4 hours trying t figure this out...
This is my journey..
Relock bootloader
Flash one of the stock tmobile ruby rom in development section
Did the OTA update on stock
Unlocked my bootloader again
Then i tried to root using one click zerg method but it didnt work
So i flashed clockwork mod using fast boot
Then applied a su binary update i found in the development section.
In less than a minute i got root back.
Then i restored my data from nandroid backup.
My phone is pretty much rooted, bootloader unlocked, bloatware free alongside having the ota update that enabled wifi calling installed.
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
bmbrad said:
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
Click to expand...
Click to collapse
working on a way maybe this weekend will have it ready
xboarder56 said:
working on a way maybe this weekend will have it ready
Click to expand...
Click to collapse
NICE! Dude you must never sleep! Always the first to get something done!
I figured out what to do. You just need to rename this update file to update.zip. then reboot in recovery and choose install update from sd card. Next navigate to download folder and install update.zip file. You will be updated and stay rooted at the same time.
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
darll said:
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
Click to expand...
Click to collapse
Maybe, but 8m I've got another problem after updating this way. Wifi doesn't work anymore. I receive an error while trying to switch on wifi.
Hello all. I am on stock 1.13 and had Google wallet set up on EVO LTE release day. Since then, of coursem Wallet quit working due to an error on boot saying the device isn't certified. The new 1.22 has come out that FIXES Wallet, but before flashing stuff I am supposed to clear Wallet's security settings so I don't brick the secure element forever.
Well I can't open Wallet since it says the device is not certified (blah blah blah). So am I safe to flash a new ROM? Remember, I had Wallet set up originally before it became "Not certified" so I am worried about flashing!
If you're stock then just let the OTA run and it will work since it's not doing a hard reset or flashing a new rom. If you were rooted, before it stopped working, you could flash a zip that only contains the OTA and you should be good to go. However if you flash a full ROM that includes the OTA then it will brick it.
Thanks Cordy. The OTA fails for me. I tried twice now and it will get about 1/4 progress bar when applying OTA update and then I get an error screen.
Am I safe to install TWRP in order to manually flash OTA zip?
Thanks again for your response!
NP before I answer that question, I guess it would be easier if you tell me what your setup is.
Stock shipped ROM 1.13 - Root, SU, and LazyPanda S-OFF. Google Wallet Setup prior to device blocking error.... Can't install OTA...
Wondering if TWRP will brick Wallet
Well twrp will just flash to your recovery partition. I assume what bricks the secure element is not being able to clear settings through the app to let it do it properly and then wiping the data partition. That said if your S-OFF check the dev section there is a thread that has the files and info you need. You can update your firmware through the bootloader and when one is available just flash an update.zip that only adds the OTA stuff and doesn't wipe your data. Yes you will need a custom recovery such as TWRP to do the latter.
Again, what bricks the secure element is still unconfirmed. I've flashed many ROMs without first clearing my Wallet settings, and I've flashed ROMs just clearing data in Settings -> Apps -> Manage Apps, and my Wallet still works fine. But I don't imagine applying the OTA would brick your secure element, as that's an update directly from the manufacturer.
Install TWRP. Flash Captain's 1.22 firmware zip. Download the 1.22 OTA zip and remove the firmware package out of the zip... then flash the 1.22 OTA zip in receovery.
You don't want to take the OTA via recovery in its original form. It contains the firmware package with hboot and stock recovery. Thats why I advised to flash Captains firmware first that does not contain hboot and recovery. Then remove the firmware package out of the original 1.22 OTA and flash the OTA through recovery.
Hopefully that works.
leerage said:
Install TWRP. Flash Captain's 1.22 firmware zip. Download the 1.22 OTA zip and remove the firmware package out of the zip... then flash the 1.22 OTA zip in receovery.
You don't want to take the OTA via recovery in its original form. It contains the firmware package with hboot and stock recovery. Thats why I advised to flash Captains firmware first that does not contain hboot and recovery. Then remove the firmware package out of the original 1.22 OTA and flash the OTA through recovery.
Click to expand...
Click to collapse
But I also took out the boot.img from that firmware.zip, which will need to be flashed for the device to boot after the OTA is applied. And I don't think TWRP will allow firmware to be flashed, so it would have to be done through the bootloader.
Captain_Throwback said:
But I also took out the boot.img from that firmware.zip, which will need to be flashed for the device to boot after the OTA is applied. And I don't think TWRP will allow firmware to be flashed, so it would have to be done through the bootloader.
Click to expand...
Click to collapse
Oh man now I'm really confused!
What is the best option you can think of for my scenario? (to not brick wallet security module)
Thanks all
Kujila said:
Oh man now I'm really confused!
What is the best option you can think of for my scenario? (to not brick wallet security module)
Click to expand...
Click to collapse
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Captain_Throwback said:
Again, what bricks the secure element is still unconfirmed. I've flashed many ROMs without first clearing my Wallet settings, and I've flashed ROMs just clearing data in Settings -> Apps -> Manage Apps, and my Wallet still works fine. But I don't imagine applying the OTA would brick your secure element, as that's an update directly from the manufacturer.
Click to expand...
Click to collapse
I respect that. I honestly stopped keeping up with the whole thing since I wasn't rooting just yet. Interesting you were able to do that without bricking your secure element. From accounts I read early on including the posted sticky about it if you didn't clear settings through app and flashed a new Rom it would brick it. Also why ppl were warned that if they used Wallet prior to it being unavailable and then S-OFF without being able to clear settings first that resulted in a Secure Element brick. I'd say be safe rather than sorry.
Sent from my EVO using xda app-developers app
Captain_Throwback said:
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Click to expand...
Click to collapse
I think he is concerned about flashing a full Rom based on the earlier conversation. As you stated flashing the OTA won't break anything so if you flash a rooted version of the update you will be fine which is what he is looking for. He is concerned about someone releasing a full Rom that includes the update that will clear data that has the chance to brick his secure element.
Sent from my EVO using xda app-developers app
Captain_Throwback said:
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Click to expand...
Click to collapse
Cordy said:
I think he is concerned about flashing a full Rom based on the earlier conversation. As you stated flashing the OTA won't break anything so if you flash a rooted version of the update you will be fine which is what he is looking for.
Click to expand...
Click to collapse
I can not apply the OTA update to 1.22, as it gets 1/4 of the way through and then provides a red device "warning" screen and stops dead.
So I should be patient and wait for a "root version" of the update like Cordy says?
Thanks all! :highfive:
Kujila said:
I can not apply the OTA update to 1.22, as it gets 1/4 of the way through and then provides a red device "warning" screen and stops dead.
So I should be patient and wait for a "root version" of the update like Cordy says?
Thanks all! :highfive:
Click to expand...
Click to collapse
If I'm not mistaken you said you're on stock recovery, did you do a check for update and try installing it that way? Actually now that I think of it if you're trying to flash the OTA as is, have you modified anything in your system folder like status bar mods, tether mods stuff like that. If you have any mods chances are that's what's causing the update to fail. Either way I'd hold off. You already said you flashed Captain Throwbacks firmware zip through the bootloader so you're good as far as having the latest radios and what not. Next is to just wait until someone makes a rooted OTA update.zip and flash that. Curiously how is the newer firmware reacting with the older software base?
I actually have TWRP. I do have a tether mod so that might mess it up too
There's someone uploading a root version so I will try that when it gets posted:
http://forum.xda-developers.com/showpost.php?p=28609753&postcount=55
Thanks!
Kujila said:
I actually have TWRP. I do have a tether mod so that might mess it up too
There's someone uploading a root version so I will try that when it gets posted:
http://forum.xda-developers.com/showpost.php?p=28609753&postcount=55
Thanks!
Click to expand...
Click to collapse
Ok so those two would've been you're issues. Had you put back stock recovery it would've still failed when checking the signature of the files that the tether mod uses. Once xHausx uploads his update.zip you should be good to go since you already have the firmware.
Fixed it by installing the 1.22 root zip OVER my existing 1.13 installation, without wiping anything.
Wallet is OK!
Also I got 4G now :highfive::good::highfive::good:
The file : http://forum.xda-developers.com/showthread.php?t=1766628
Hey guys I woke up this morning with a update from at&t so i tried to install it, the phone reboots and then says Signature verification failed installation aborted. My Galaxy S 3 is currently rooted. Anyone else have this problem?
It's much easier to flash a rooted stock ROM containing the OTA. There is at least one in the development section with more to follow.
THE HARDER (BUT NOT HARD) WAY:If installing the latest OTA update, you need the latest version of cwm for AT&T phones for the OTA to install. It's in the development section. You may also need voodoo OTA root keeper app to backup your root. The OTA WILL break your root.
Sent from my SAMSUNG-SGH-I747 using xda premium
Sweet thanks for the help, I flashed back to stock rom, got the update and rooted back to what I had before. It only took 10 mins to do