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
Related
Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App
hey i rooted my lg g2x and installed cm7 after some error
while i was turning it on first time after install it bricked and i had to use nvflash to fix it
after that it looked like my phone updated to cm7(not sure) and it says 2.3.3 in phone software
i want to update to the jellybean cm 10 but it says my phone isnt rooted anymore, happened after i nvflashed it
want to know if this is normal and if not how do i reroot it
The nvflash put you back to stock download the rom you want boot into recovery wipe cache data flash rom flash gapps .should be good you might need to reflash cwm recovery if you pushed the wrong button in nvflash.
Sent from my SGH-T999 using xda premium
monte666 said:
The nvflash put you back to stock download the rom you want boot into recovery wipe cache data flash rom flash gapps .should be good you might need to reflash cwm recovery if you pushed the wrong button in nvflash.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
i cant, it says error while attempting to run privileged commands in when i try to go into recovery from rom manager
cybertecnus said:
i cant, it says error while attempting to run privileged commands in when i try to go into recovery from rom manager
Click to expand...
Click to collapse
nvm, i fixed it by using nv flash, and going into cwm recovery, then installing cm10, but still thanks for your help
cybertecnus said:
nvm, i fixed it by using nv flash, and going into cwm recovery, then installing cm10, but still thanks for your help
Click to expand...
Click to collapse
Rom manager doesn't work on this phone since you nvflash back to stock it cant gain root access hence your error.
Sent from my SGH-T999 using xda premium
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
Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP
Jz flash any cm rom zip just a soft brick easily recoverable
Shibazeet said:
Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP
Click to expand...
Click to collapse
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Can you sideload in TWRP?' It's even faster than pushing for the unpatient folk like me. lol
And yeah jd I still have the Rocket.
that was his first and only post, i bet he wont be back. sounds like a root toolkit child.
How?
Having said that I cannot detect the phone in the PC, how can i put the ROM in a folder?
Guess what? He's back!
@Shibazeet
You need to follow this thread to setup adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2588979
Use NRT nexus root toolkit 1.8.4
& recommend to install stock image nexus from official google website , just search " stock image nexus 5 "
SORRY FOR MY BAD EN !!
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
Lokke9191 said:
http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
Click to expand...
Click to collapse
My friend, you don't use fastboot to flash "ROMs".
Sorry woke up 5min before writing that. Running on 4hrs sleep now. Meant use fastboot to install stock image, flash a recovery. Then use custom recovery to flash future roms. Just pointing him in the right direction. With a little reading, he'll figure it out.