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
Related
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Tried flashing another version of the recovery?
The K-Zoo Kid said:
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Click to expand...
Click to collapse
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
+1
I also made the experience that flashing recovery through rom manager doesn't always work...had the same problem, also using brainmaster's MIUI rom.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
How would i go about doing this?
Check the rooting guides for the directions.
Sent from my Nexus S 4G using xda premium
I tried looking for directions on how to do it and for some reason I can't seem to find them.
Sent from my Nexus S
You obviously didn't try very hard
http://forum.xda-developers.com/showthread.php?t=1067813
[REF] Complete List of Roms | Kernels | Rooting/Other Guides for Nexus S (GSM)
I am not linking you to the direct directions, but I hope you will find your answer by finding a root guide from the first post.................
Sent from my Nexus S 4G using xda premium
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
zenithz said:
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
Click to expand...
Click to collapse
You should make sure you are erasing the old recovery before flashing a new one. This can be done as a fastboot command or through the advanced options in rom manager.
Sent from my Nexus S 4G 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!
I am having trouble, and since I cant post on the page where this should be asked. (this is my first post) I am asking here hoping that somebody will look...
I have rooted my verizon S3 and it works great... I am however trying to install a CM10 Rom on my device. I have followed the instructions and get all the way to selecting the zip on the sdcard. it finds it, it opens it and after about 20 seconds it gives me a status 7 error and says error in XXXXXX\XXXXX .zip
I have done all the steps perfectly and have formatted and wiped it twice trying this... I even have my backup in place...
I have tried 3 or 4 different cm10 roms and they all give me the same error... What am i over looking?
Thanks
I think you need to flash a CWM/kexec hybrid recovery.
Download the app EZ Recovery and flash the hybrid CWM 6.0.1.0
Sent from my SCH-I535 using Tapatalk 2
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
DROID3R said:
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
Click to expand...
Click to collapse
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
kwiksilvr said:
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
Click to expand...
Click to collapse
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Marcismo55 said:
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
You could always Odin back to stock then re-root and install cwm again and restore your backup. May be an easier way not sure. But back up your files on a PC if you do that.
Sent from my SCH-I535 using xda app-developers app
kwiksilvr said:
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
Click to expand...
Click to collapse
I don't know how you are blaming me when I specifically told you to flash a ClockworkMod/Kexec recovery... not TWRP.
Seems your issue is lack of following directions. Good luck on solving your issue.
Sent from my SCH-I535 using Tapatalk 2
All of a sudden yesterday my phone started boot looping while I was running Invisiblek's CM10. I finally got that sorted out, and used ODIN to get me to the rooted version of the stock ROM. However, now when I flash custom ROMs, I get a boot loop and have to restore back to the rooted version of stock. I've tried Invisiblek's CM10 again, Bean's... oh, and my CWM background is missing and is just black. I've also noticed(not sure if this could be why) that when I go to the mount section under CWM, both system and data keep defaulting to unmounted. Any suggestions?
Have you been using ezrecovery to flash recoveries before flashing ROMs??
Sent from my SCH-I535 using Tapatalk 2
hopesrequiem said:
Have you been using ezrecovery to flash recoveries before flashing ROMs??
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Hm, no. The installation instructions never made any mention of ezrecovery. Is that my problem?
Flashed CWM through ezrecovery. CWM is working again it appears. Thank you very much!!
Krog216 said:
Hm, no. The installation instructions never made any mention of ezrecovery. Is that my problem?
Click to expand...
Click to collapse
What recovery are you using?
Sent from my Synergy GS3
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app