Ok so I'm fairly new to the rooting scene, and these forums, but so far everything has been pretty good, except for one small problem. I installed a custom boot logo, and afterwards my phone was lagging a bit. I contacted the boot logo programmer, with no response, so I decided to wipe my system and use the backup from right before I installed the custom boot logo. Unfortunately, the boot logo has not changed, and my phone 'fails' whenever I try to flash something from Odin. Anyone know what to do in this situation.
If you want to do a full wipe of you device,cos it sounds like tha boot logo is corrupt,then boot to recovery and wipe cache partition and dalvik cache.then go to "storage and mounts" and format system,data and cache.Select "Go Back" and factory reset your phone and reboot.If it doesnt go past the boot logo after 1min then pull the battery,put it back in and turn it back on.Its a pain in the arse but it will completely clean up your device and if you where rooted you will need to probably reroot but berfore hand plug in your phone to your PC so it gets recognized again.
EDIT:Just incase,first of all download titanium backup from the market and backup your apps!!!!
Sting Rray said:
Ok so I'm fairly new to the rooting scene, and these forums, but so far everything has been pretty good, except for one small problem. I installed a custom boot logo, and afterwards my phone was lagging a bit. I contacted the boot logo programmer, with no response, so I decided to wipe my system and use the backup from right before I installed the custom boot logo. Unfortunately, the boot logo has not changed, and my phone 'fails' whenever I try to flash something from Odin. Anyone know what to do in this situation.
Click to expand...
Click to collapse
You need to wipe usb storage, sd card, then put phone in download mode, flash stock ROM using Odin. You need to fully wipe everything.
Sent from my Sexynos SGH-i777 using XDA Premium.
I've trying reflashing the stock ROM and kernel; however, it gives me a FAIL and says can't open the serial (COM) port.
I have solved the problem by closing Samsung Kies and wiping the system, thanks for all the help offered.
Figured out that I posted in the wrong section(mods please remove that thread)
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root(rooting & unlock from this thread:http://forum.xda-developers.com/showthread.php?t=1182871)
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
12.Entered Recovery mode to try stable Nutrino ROM, same problem (stuck @ M logo screen which says unlocked)
13. Cleared data, cache and tried restore and now my phone boots up with flashing M screen.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Hmm... I would "fastboot -w", wipe cache/dalvik/data again, and try restoring your nandroid backup. (Or was that your Neutrino attempt?)
OR, do the wipe again and flash a 2.3.6 fruitcake to see if it boots normally. Just to see if there's some issue with your rom download or if it's really the phone.
The only way to hide the unlocked text is to flash an SBF using RSD Lite, which runs the risk of bricking your phone if you flash the wrong version.
Download a Fruitcake from here > http://forum.xda-developers.com/showthread.php?t=1163009 and put it on your sdcard.
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
Let your phone sit until it boots up completely, then let it sit for another 10 minutes. Remember, your phone can take 15 minutes to boot up the first time after flashing a ROM, especially if a new kernel was flashed with it.
Yeah I would try a fast boot wipe the whole shabang fastboot -w and then fastboot erase preinstall
Then also erase boot
System
Cache
Userdata
Web top
Then go into cwm and do the wipes you've been doing then flash the rom
Sent from my MB860 using XDA App
jonnyboyC13 said:
Yeah I would try a fast boot wipe the whole shabang fastboot -w and then fastboot erase preinstall
Then also erase boot
System
Cache
Userdata
Web top
Then go into cwm and do the wipes you've been doing then flash the rom
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Think I covered all that already, and fastboot -w just wipes cache and userdata anyway, so no need to do a fastboot -w. What I have in the post before you is the cleanest way to wipe and flash a new ROM.
Thank you....I haven't tried the soft brick fix yet.
But from reading one other thread which had similar problem, it looks like after installing romracer's CWM, things got fixed.
http://forum.xda-developers.com/showthread.php?t=1527453
Will be trying this tomorrow.
Hmm.. this thread seems to be dead..
This treads seems to be dead... I was hoping to get some help with some soft bricked atrix HD... any suggestions?
Pharawer said:
This treads seems to be dead... I was hoping to get some help with some soft bricked atrix HD... any suggestions?
Click to expand...
Click to collapse
This is the Atrix 4G board, not Atrix HD.
ravilov said:
This is the Atrix 4G board, not Atrix HD.
Click to expand...
Click to collapse
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Pharawer said:
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Click to expand...
Click to collapse
No. Totally unreleated hardware. There's an Atrix HD section you can ask in over here, which you clearly already knew about because you've already asked your question in it. Why spam over here? I'm sure somebody who actually knows the device you have will answer your question, but this is not the place to ask it.
Edit: But feel free to flash an Atrix SBF/Fruitcake on your Atrix HD if you'd like to actually brick it.
Pharawer said:
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Click to expand...
Click to collapse
You should take your question back to the HD Thread, a discussion at this one is TOTALLY off topic for this thread due to the entire device being different.
Thanks!
P.S. Closing thread
So my Evo LTE is running 2.13.651.1, and is on what I understand to be the newest HBOOT (1.19). Naturally, I have S-ON as a result. This is my first Android device, and I've had it about a week since switching from an iOS device. I have root and the Teamwin recovery, which I used to backup the phone. I understand this is called a nandroid backup?
I plan to flash Cyanogenmod 10, in fact I already tried once. It resulted in a bootloop, and I restored from the nandroid backup. I have since learned I need to flash the boot.img from CM10 using fastboot, Flash Image GUI, or any other alternative. Once I do this, if I want to go back to Sense 4.1 like I have currently, how would I do so? Once I flash the boot.img from CM10, I won't simply be able to restore to my nandroid from teamwin, will I? I assume that if I tried to restore from the nandroid, due to S-ON I would be unable to write to the boot partition from a recovery utility and I would be left in another bootloop. How can I get a boot.img corresponding to my stock Sense 4.1 rom in the event that I want to revert to stock?
In the folder containing my nandroid backup, I see a file called boot.emmc.win and a boot.emmc.win.md5. I understand what the MD5 is for, but is the boot.emmc.win what I will need to undo the effect of flashing CM10's boot.img? If so, how would I use it (I do not recognize that file extension, and Flash Image GUI does not seem to like it either)? If not, where would I get something that will work?
I've done several searches here and on other forums, but I can't seem to find what I need. If someone has already answered this question, could you simply point me in the direction of that thread?
Thanks in advance,
Kristoffer
I have yet to restore a back up but to avoid any issues I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
When you reboot, do not boot to recovery, the boot partition has been replaced with a temporary twrp and all you need to do is reboot normally
om4 said:
I would use dumlock. Install it from twrp advanced menu and reboot, open it in cm and it will backup boot and overwrite it with a temporary recovery, you then reboot and go back to dumlock and restore the back up, then you are free to flash the nandroid backup and reboot
Click to expand...
Click to collapse
Once I flash CM and its boot, the boot for my Sense 4.1 will have been overwritten, no? I opened Dumlock in my Sense rom (as I have not yet flashed CM successfully), and it gives me a warning to make a backup of boot PRIOR to using the app, then just under that says the app will make a backup of the boot. If I go ahead and run Dumlock, I'm not entirely sure what is going to happen. It seems that it will move my recovery (TeamWin at the moment) onto the boot partition? If this is the case, why is this something that needs to be done? Does moving the recovery onto the boot partition allow the recovery to write to the boot without S-OFF, thereby allowing a simple restore of the nandroid to replace my rom AND boot at the same time, as if I were restoring with S-OFF? Sorry if I'm not making sense, but I don't really know what I'm talking about here, and thats the only thing that makes sense to me.
I see a button in Dumlock that says "restore original boot." If I install CM and the CM boot, will pushing this "restore original boot" button give me back the boot setup for the stock Sense rom? If it does, then I could just push that button, let it do its thing, and then restore my Sense nandroid with my recovery, right?
Thanks for your help, and quick response.
Install HTC dumlock
Open the app and back up boot
Once back up is successful, press execute
Once the phone restarts it will only boot to twrp, you then go to dumlock menu again and restore boot
Now flash a Rom or restore back up and reboot
Sorry to sound ignorant, but will this method will restore the stock boot regardless of what rom/boot combination I'm currently running? Or is this creating a backup of the currently installed boot, and saving it somewhere for future use? Specifically, do I want to follow this procedure before I upgrade to CM so I have a backup of the current boot, or is this something I want to do if/when I want to go back from CM to Sense that will magically put the boot back how it was from the factory?
Yes, its a workaround that gives access to boot partition and will let you flash normally, I would only use it for stuff like nandroids rather normally flashing because it writes to boot 3 times. It's a lot of unnecessary wear and tear
Awesome, thanks alot for your help. I'm excited to go and try my CM10 rom, now I know how to get back to stock if I don't like it.
Thanks again,
Kristoffer
Hmm. Now I don't know what I've screwed up. I flashed the boot.img from the CM10 zip using Flash Image GUI, then rebooted to recovery and wiped the System partition and cleared dalvik/cache. Then I flashed the CM10 zip using twrp, cleared dalvik/cache, and rebooted. Now, I'm stuck at the CM boot animation again, just like last time. This does not seem terribly complicated, and I don't know what I've done wrong.
I understand twrp cannot flash the boot due to S-ON, but I thought flashing the boot from inside my Sense rom using Flash Image GUI would fix the problem. I restored the Sense nandroid like before, rebooted, and then I got the Recovery boot logo (htc logo, with red text underneath). After maybe a minute, that went away, and I got a Sprint logo and then the normal boot screen with only an HTC logo. The phone then restarted, and this process repeated several times. So, apparently whatever I did to the boot sector with Flash Image GUI wreaked whatever was there before, and failed to replace it with something that would play nice with CM.
A factory reset won't fix the boot, will it? All it will do is overwrite my system partition and internal sd with the default files, and I still won't be able to boot. Any idea what I've screwed up, and how I can fix it?
EDIT:
I reflashed the CM10 zip, and it still gets stuck at the CM boot logo (spinning blue thing). What are the chances my CM10 download is corrupt? Is it worth trying to redownload it, reflash boot with fastboot, then move the new zip to the phone and flash that?
What version of twrp are you using, some people have had issues with the older 2.1.8
Ok, progress. I'm on twrp 2.2.1. I wiped everything again (wiped cache and dalvik, Factory Reset, and then wiped System) and reflashed CM10. It booted this time, so I assume the boot partition is fine. Apparently I'm the retard that can't understand a point-and-click system and follow simple directions
Once it boots, however, I instantly see an error "Unfortunately, the process com.android.phone has stopped." Once I click Ok, the error will either pop back up immediately, or wait for an indefinite period and them come back. Possibly this is the result of the CM10 release not being entirely stable as of yet, I don't know.
But thanks again, your help and your fantastic Don't Panic post together fixed the problem. I think I can figure out what is going on with this error popup and fix it. So long as I have voice service in the interim, which I do, all is well in the world.
It's normal, it pops up when you lose signal, its a bug but its technically a feature. If the phone loses signal, normally android is supposed to prompt you so you are aware. I think its for debugging purposes, normally this is disabled. Not sure if its really a bug in cm or they just haven't gotten around to disabling it, but its normal. It's not a real priority either since it doesn't adversly affect the phone
Hmm. This just gets better and better. So CM10 ran nicely for awhile, then last night I rebooted the phone and the internal SD card failed to mount. Both twrp and the actual OS cannot get it to mount properly. Is this something I broke, or does it sometimes occur at random? I read the following, but I don't quite know where to go with it.
om4 said:
You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Click to expand...
Click to collapse
Repartitioning seems simple enough; twrp> advanced >partition SD card>swipe (leaving all settings default).
After that, I can flash the new rom and boot using fastboot from my PC, right? I'm confident that my nandroid of the stock rom is clean, because I didn't develop this problem until after I had been using CM10 for awhile. Could I use fastboot to flash the boot, data, and system from the nandroid, and be good to go? If not, is the most current file avalible to download at http://stockroms.net/file/HTCEvo4GLTE/RUU? the appropriate file I would need to restore the phone to its stock unrooted state.?
Also, none of my nandroid files have a .img file extension. Is this normal? It has the normal .md5 files, but everything else has a .win extention. I've never heard of this one. My boot, for example, seems to be backed up as boot.emmc.win, with a boot.emmc.win.md5 corresponding to it. Cache, data, and system backups are named <option>.ext4.win. Does ext4 has something to do with the filesystem of the backed up partition? If this is the case, what is a .emmc? Can I flash these files with their strange (to me, at least) extensions using fastboot as if they were all .img files?
I can't imagine any of this is really as complicated as it seems. I've used a PC and a jailbroken iDevice extensively, and never managed to break something I couldn't fix. I guess Android just doesn't like me, or something.
Thanks again for all your help.
EDIT:
Apparently physically removing the external SD from the phone allowed me to mount the internal SD as a USB device. The phone still refused to allow me to read/write data to the memory, but somehow managed to allow my PC to see it. I formatted the internal SD to fat32 (one of the limited options) using Windows, and rebooted the phone to recovery. Now, it suddenly can detect its internal SD. I was able to wipe everything, and restore my Cyanogen backup and the SD card now works again. Weird...
Since I didn't have to repartition anything, was the "physical address linking the card and or entire card" corrupt, or did I have some other issue? Also, I'm still curious about my above question pertaining to file extensions and restoring a nandroid via fastboot.
Hey,
First off i hope i have put this on the right sub forum.
I've been stupid (I Think) I've olso looked around on the forum and the [READ THIS] Got a Boot Loop? Don't post a New Thread!
topic.
I'm using my SGS2 for a year now and was using the ressurexionRimix rom for a while.
I've been plaing around with my phone so i got lots of folder that were not used etc, so I wanted to get it back to factory settings, here is when all went down.
Via Settings-Backup and recovery i gave my phone a factory reset (while using the latest ressurexionremix rom, i think this is the misstake i made) When my phone went into the reboot is got stuck on the splash screen, it kept reapeeting the boot animation.
The second mistake i mad was not puting back my back-up but thought well i want it back to it's first state so i'll use ODIN to flash the stock ROM onto it. now, 4 hours later and about 10 trys with diferent versions of the stock roms i'm still stuck on the boot screen.
I've also tryd flashing a cwm so i could get in cwm recovery, this also without any luck
Does anyone have a idea what to do!?
go back to recovery - mounts andstorage and format the following :
cache, system, data, sdcards if you have it in recovery. reboot
you have a bkank screen as your phone has been wiped. reboot into download mode.
Connect odin and flash a stock rom. reboot and your phone should work provided that you have not damaged the flash chip on the motherboard.
Is this in CWM? the problem is i dont have that anymore because i've flashed it toc stok. I now get in the Android system recovery
The option i get there ar:
Reboot system now
apply update from external storage
Wype data/factory reset
Wipe cache parition
apply update from cash
test redbend fola[FS]
Will try this, thank..will let you know if it worked
Wiped data/factory reset and cache after this i ebooted my phone and i got the message installing application, now i'm in the setup menu. Looks like it is working.
Did'nt realice there was a recovery besides CWM Thank yoy so much Cosmic Blue!!! You saved my life!!