I have searched with what I can on a mobile device, but I haven't found an answer for my situation.
What happened was I installed AOKP and then installed the new recovery. Then halfway through the say I found my transformer boot looping so I flashed back android revolution on a data/cache/system wipe.
Unfortunately after booting up, the wifi did not work, and it now says turning on but it never does. Does anyone know of a similar problem or point me in the right direction?
Oh and I am also unable to reboot properly with this recovery, I have to hold down and power and then cold boot every time. :/ any help would be greatly appreciated.
Sent from my Galaxy Nexus using xda premium
Flash revolution Rom again without wipe, that should fix your wifi problem.
For your cwm recovery loop go here
http://forum.xda-developers.com/showthread.php?p=23256536
baseballfanz said:
Flash revolution Rom again without wipe, that should fix your wifi problem.
For your cwm recovery loop go here
http://forum.xda-developers.com/showthread.php?p=23256536
Click to expand...
Click to collapse
Thanks! I'll try and then report back!
Sent from my Galaxy Nexus using xda premium
had to nvflash back to prime 1.6.2 and start from scratch but the tf is alive again.
FaithCry said:
had to nvflash back to prime 1.6.2 and start from scratch but the tf is alive again.
Click to expand...
Click to collapse
LOL, you could have NVFLash the newer ICS ROM
I had a very early iteration of CM9 running on my Galaxy Tab 10.1 from like February I think. I could not get the nightly to flash so I unrooted, rerooted and then the flash took but now it is stuck on the CM9 boot animation and no matter what nightly I use I get the same thing. I also tried AOKP and it does the same thing (sticks boot animation). The stock ROM boots fine. If I try to go back to my backup of the running CM( I get a md5 mismatch error. If there is another thread that addresses this issue I could not find it. Any help would be appreciated.
Do you have it plugged in while you are trying to flash? I know when I put CM9 on my EVO if I had it plugged in it would get stuck on the boot animation, but as soon as I unplugged it, it worked. And I have seen lots of others have the same problem.
I have tried it unplugged as well and no change.
You sure you flashed it right? Reflash and see what happens. If it happens again then run a logcat and post it here
Sent from my Desire HD using Swype beta for Android!
?
Sent from my Desire HD using Swype beta for Android!
Go to clockwork recovery mode and clear cache , it should help
stewie_atrix said:
Go to clockwork recovery mode and clear cache , it should help
Click to expand...
Click to collapse
+1 to this
Sent from my Desire HD using Swype beta for Android!
My TF101 hasn't been working for about 2 weeks. I've tried flashing ARHD, Revolver, Team EOS 3, and Team EOS 4 (Android 4.2), Rayman's android 4.2, and some other ICS roms. I've also tried restoring some backups. My tablet has the ClockworkMod Recovery v3.1.0.1 (solarnz-R3-230511-1902). When I turn on my tablet it loads up that recovery. When I press reboot system now, it just boots into recovery again. The only way to try and make my tablet boot is by powering it off and then holding volume down + power, then cold booting. After flashing Team EOS 4, I've managed to at least get into a boot loop. Then, I flashed an ICS 4.0.3 ROM and it actually booted into the Android is upgrading... starting apps but it won't get past that. I have the TF101 dock and an 8GB micro SD card if that helps. Any help is appreciated, I really want my tablet to work again... :fingers-crossed:
Is your bootloader unlocked? If so you have to fastboot the boot.img file into the tablet after installing the rom from recovery.
Sent from my EVO using xda app-developers app
onlybob said:
Is your bootloader unlocked? If so you have to fastboot the boot.img file into the tablet after installing the rom from recovery.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
...uhh what!? Idk if my boot loader is unlocked, I'm pretty sure it is. I rooted this thing over a year age, I don't remember if I unlocked the boot loader
just try easyflasher by whitekidney, restore to stock, then install twrp latest and you are good.
Oh gosh sorry about that fastboot is not for the TF101 xD(I'm still in HTC mode)
Sent from my EVO using xda app-developers app
The thing is:
I accidentally deleted the twrp backup of the stock JB rom,and i was using Cyanogenmod rc4
So I wanted to return to stock JB,but when i flashed the stock firmware over Mobile ODIN,it was stuck at the boot anmiation.
So i went to do it over ODIN on PC,but it ended up with the same problem.
Now i cnat go back to full stock.
Please,if anyone can help me.
Thank you.
It's been discussed like a hundred times already. Get into recovery and clear data, cache and factory reset.
canis999 said:
It's been discussed like a hundred times already. Get into recovery and clear data, cache and factory reset.
Click to expand...
Click to collapse
And I tried that, I am not a noobie, otherwise I would ask you how to flash a recovery image -.-
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
And I tried that, I am not a noobie, otherwise I would ask you how to flash a recovery image -.-
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Heres what I would do.... Get into recovery mode. Flash cyanogen mod and gapps again. Then download a stock jellybean rom. Then flash the stock rom.
Here is a stock rom:
http://forum.xda-developers.com/showthread.php?t=1704668
noahthedominator said:
Heres what I would do.... Get into recovery mode. Flash cyanogen mod and gapps again. Then download a stock jellybean rom. Then flash the stock rom.
Here is a stock rom:
http://forum.xda-developers.com/showthread.php?t=1704668
Click to expand...
Click to collapse
I will try that later...
Sent from my GT-P5110 using XDA Premium HD app
I didn't suggest you are a noob. I only suggested that starting another thread about this seems quite unnecessary. You see, I had exactly the same problem you do, going from CM 10.1 to stock JB, I got stuck on boot animation. So I used the search button, found like a hundred threads describing this situation and in 90% of them the solution I gave you worked. Sorry it didn't for you.
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