Related
I really hate to do this, but i've searched for a while now and can't seem to find anything that matches my situation.
i'm on stock 2.3.4, but rooted with a different kernel, boot image, and a different radio flashed. I realize that i'm not going to be able to install the update directly from my phone, but I can't seem to install the signed update file through cwm or the stock recovery I just flashed. cwm fails with a status 7 error, and stock recovery won't even let me bring up the menu to manually install the update.
i'm just wondering if I should flash a stock rom with recovery and then try to flash the update that way, or is there some other way that I could do it? I don't want to lose any data from my phone, and I would flash the full 2.3.6 rom instead, but I can't connect to the download link in this thread http://forum.xda-developers.com/showthread.php?t=1063664.
once again, I really hate to do this, but I am pretty much stuck right now.
thanks
hoponpop said:
I really hate to do this, but i've searched for a while now and can't seem to find anything that matches my situation.
i'm on stock 2.3.4, but rooted with a different kernel, boot image, and a different radio flashed. I realize that i'm not going to be able to install the update directly from my phone, but I can't seem to install the signed update file through cwm or the stock recovery I just flashed. cwm fails with a status 7 error, and stock recovery won't even let me bring up the menu to manually install the update.
i'm just wondering if I should flash a stock rom with recovery and then try to flash the update that way, or is there some other way that I could do it? I don't want to lose any data from my phone, and I would flash the full 2.3.6 rom instead, but I can't connect to the download link in this thread http://forum.xda-developers.com/showthread.php?t=1063664.
once again, I really hate to do this, but I am pretty much stuck right now.
thanks
Click to expand...
Click to collapse
Sent from my Google Nexus S using XDA Premium App
The 2.3.6 update for the i9020a was pulled by Google. There will be a new update released soon. I would wait.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
The 2.3.6 update for the i9020a was pulled by Google. There will be a new update released soon. I would wait.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
i'm pretty sure it just got re-released. i'm guessing it isn't causing issues anymore either
Ok just got this phone and have decided to go with Phoenix Blood rom, but how do i start? I have to be on froyo to root? Im coming from samsung epic on sprint that i flashed so im not completely retarded. Thanks for any help
Use superoneclick to root on froyo.
If your on 2.3.3 gb there's a flashable. Zip in development section to root.
Also you will want to use tgagunnmans nvflash method to install clockworkmod recovery in dev section.
Phoenix blood is a great choice btw, enjoy!
Sent from my LG-P999 using xda premium
You're still on Froyo? To my understanding it's a good idea to flash the OTA GB first so that you'll get the up to date baseband. Once that's done just go ahead and flash PB.
no im on gb jsut thought i had to go back to froyo to root, so i just flash clockwork mod then pb and thats it?
reeshmd23 said:
no im on gb jsut thought i had to go back to froyo to root, so i just flash clockwork mod then pb and thats it?
Click to expand...
Click to collapse
Yes, but make sure you're using NVFlash to get CWM. Don't use Rom Manager.
Easiest way is using the tool unlockroot. It supports gb on the G2X. Or you can use nvflash, whichever you prefer.
Sent from my LG-P999 using XDA App
redmonke255 said:
Easiest way is using the tool unlockroot. It supports gb on the G2X. Or you can use nvflash, whichever you prefer.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
If he wants to change Roms he will still need Nvflash regardless how he gets it rooted.
GTWalling said:
If he wants to change Roms he will still need Nvflash regardless how he gets it rooted.
Click to expand...
Click to collapse
Agree. Nvflash=bullet proof.
what is nvflash?
reeshmd23 said:
what is nvflash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1056847
From that thread:
Flashing the custom recovery using NvFlash is the only way to ensure that in the case your phone will not boot up, you will be able to get into recovery to fix the issue / flash a ROM / restore from nandroid backup. That is what this app will do for you.
If you flashed the ClockworkMod recovery from ROM Manager it does not flash the recovery to your phone, it fake flashed it. The only way you can gain access to ClockworkMod recovery is through ROM Manager at that point. Using this method is the only way to flash recovery so it is persistent and accessible booting to recovery.
If you have already flashed through ROM Manager you can still proceed with this method. Flash Away!
(You can use both ROM Manager CWM and have the nvflashed version working together. You just access either or one at a time, having the nvflashed one means you can boot to CWM. Welcome to Tegra2)
Click to expand...
Click to collapse
Follow the link. This is a must for tegra 2 based phones. It is always better to be safe than sorry and it also allows you to do a ton of other things, such as making backups and flashing roms. Let us know if you need help. The phone is pretty much unbrickable after you do this. It gives you the ability to recover from any major mistake.
Its in the dev thread, it low level flashes clockworkmod recovery to our phones internal memory partition. You need to install apx drivers first in order for the g2x to be nvflashed.
Sent from my LG-P999 using xda premium
thanks for the help guys got it all set up
Just to add in, nvflash allows u to boot into cwm recovery whenever u want and u don't need to be next to a computer. I think that is how it worked for Samsung phones and Odin, where u needed a computer, but haven't used a Samsung phone so I could be wrong. Remember always make a back up of everything and play around with the different roms, not every rom works for everyone
Sent from my LG-P999 using xda premium
Actually Odin is just like nvflash. It is used to put cwm on you phone and to put the stock recovery back on.
Once you have cwm you can flash what ever rom or kernel without the need for root. Just back up your stock unrooted stock rom before flashing anything else.
If you do that you will have your own stock backup with no need of finding it in the forums if you need to go back to stock.
Sent from my LG-P999 using xda premium
Yikes, am I in a predicament.
So, here I am, with my Nexus S I9020A on Koodo in Canada, rooted with TWRP v2.2.0 recovery and stock 4.0.4; well, with all the JellyBean buzz going about I figured, hey, why not, and I made a nandroid backup using TWRP, and copied said backup onto my PC for an extra copy.
Well, after playing around with an AOSP rom of 4.1.1 I want the stock OTA, but restoring the backup I made yields no results, touting "no recovery or img" as an error. So now I have no idea how to get to either stock JellyBean (which is where I want to be) or at least stock 4.0.4 for the I9020A so I can get the OTA.
What do I do?!
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm trying to reflash TWRP and restore again - fingers crossed.
What happened to that list of all official OTA variants for the Nexus S?
I'm referring to that list that had for instance :
Nexus S - I9020A:
2.3.4 - Download link
2.3.6 - Download link
etc, etc.
I just want to get back to stock 4.0.4 so I can get the 4.1.1 OTA :S
Or have any way to get to STOCK 4.1.1 for the I9020A Nexus :S
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's exactly what I was looking for, thanks, ended up just taking the long road there and back from Gingerbread to JellyBean, so far so good!
Thanks for everyone's help!
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Hey guys! Maybe I am really bad at finding stuff, but could someone clearly post the stock ICS software for the blaze? For all the recoveries to go back to stock, I keep finding the gingerbread ones. I currently am running CM 11, and if anything goes wrong, I know that I need to use the ICS recovery, rather than the gingerbread one. Thank you in advance for helping a helpless noob! XP
Sent from The Doctor's Nexus 7
This is what I used for a cwm flashable stock ICS ROM http://forum.xda-developers.com/showthread.php?t=2329081
For recoveries they should be listed in the blaze bible
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
champ784 said:
Hey guys! Maybe I am really bad at finding stuff, but could someone clearly post the stock ICS software for the blaze? For all the recoveries to go back to stock, I keep finding the gingerbread ones. I currently am running CM 11, and if anything goes wrong, I know that I need to use the ICS recovery, rather than the gingerbread one. Thank you in advance for helping a helpless noob! XP
Sent from The Doctor's Nexus 7
Click to expand...
Click to collapse
FOR EVERYONE HAVING ANY PROBLEMS RETURNING TO STOCK FIRMWARE READ THIS
So first register at www.sammobile.com, then search SGH-T769 under firmware and download the August 2012 ICS or The Feb 2013 ICS Firmware, wait for the download to finish (took me 30 minutes) then extract which ever firmware zip you downloaded then using Odin click on PDA and select the .md5 file which is located in the extracted ICS Firmware Folder that you've downloaded from sammobile.com
Download the PIT file here
http://forum.xda-developers.com/showthread.php?t=1919228
Click on PIT in Odin and then select the one downloaded from the link above
Edit: I believe the pit file download link at that thread no longer works but if I remember correctly the pit file isn't needed (it's not do or die) you can continue without it your phone will be fine
then make sure re-partition isn't checked and start the flashing process after it is done flashing and reboots you'll have stock ICS.
*IF YOU WANT TO ROOT IT READ BELOW*
to root it simply follow the instructions over at the root ics stock thread found here
http://forum.xda-developers.com/showthread.php?t=1919228
This will flash a custom recovery and once the recovery is flashed using Odin reboot into recovery and flash the superuser.zip then you'll have Rooted Stock ICS Firmware
*BOOT LOOP MIGHT OCCUR*
To fix boot looping after flashing stock ICS just boot into stock recovery and wipe data and cache then reboot or on custom recover wipe cache and dalvik cache reboot and you're good to go.
If I helped you in anyway don't be afraid to hit thanks!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Thanks a lot man! I was rooting my mom's phone (we all got blazes... Go figure!) and ran into an issue when I ran into a bootloop the first time I tried rooting... When I tried undoing the softbrick, I accidentally loaded the gingerbread stock back on, rather than ICS, and found that her SD partition was inaccessible. Thankfully, using the stock ICS, I reverted back to it and then rooted again when done with that. She's now on ProvisionMod, and its running smooth as butter! I was hesitant to put her on Kitkat cuz I know the camera bug still needs to be worked out... But when that's fixed, I plan on putting her on something like CM 11 when its all said and done. Thanks to all the helpful developers who made all of this possible! You guys are the best!!!!!
Sent from The Doctor's Nexus 7