Hello all!
I was trying to replace a .9 file when everything force-closed on me, so I could not go into Clockworkmod Recovery to restore the NAND.
I restored with Odin, but during the messages tell me that the "data wipe" has "failed" in red text. The phone boots up through the stock animations and pink text, but I'm greeted with a blank screen no matter how long I wait. The bottom buttons light up.
What should I do?
EDIT: Yes, I've done it multiple times, each with the same outcome. I'm sort of frantic right now. Recovery mode works fine, but I don't think there's anything I can do there to unbrick my phone. I wiped all user data and the cache and rebooted, but no avail.
EDIT2: Never mind. Mods please close this thread. I restored the kernel image, and it is working like a charm now.
EDIT3: Never mind yet again. I followed instructions from androidforums. com/vibrant-support-troubleshooting/186959-samsung-vibrant-bricked.html#post1662645
but I end up with a bad kernel that asks me to force close every process over and over. I'm desperate as of now.
Have you tried Jacs/Kings kernel? WCS use the Froyo method in Sombionix ROM thread. Good luck...
Ok so here is what is going on with my ATRIX... I have searched for answers and not found any so here I am. I wonder if anyone else has seen this. Please note I am not new to flashing, rooting, romming, etc... This week is my first go around with the ATRIX (or any other moto for that matter).
So I went from rooted 1.8.3, unlocked the BL, and was immediately prompted for the 4.51.9 OTA upgrade. I did this and everything was fine when done. No data loss or issues. I of course lost root and the unlock, so I went to taking care of this.
I rerooted but waited a few days and read more before unlock because of known brick issues. I didnt want to be there!
next I decided to try ROM MANAGER to flash CMW. Flashed but of course needed to unlock BL so I used the auto method by mramirez (auto script for known methods). Anyway no matter what I did after unlock I had to reflash everytime the recovery to be able to boot into it. It would not hold, and after 1 or 2 boots I would be back to android stock recovery.
So then I decided to try a rom or to. Flashed ninja and gingerblur with no issues, wiped data, cache, dalvik and rebooted into new rom with all my data still intact!!!! I wiped again, factory reset from recovery... still there! I did a factory reset from within android... still there!!!!
SO.... next I decided I need to flash moto firmware 4.51.9 to get back to stock. Did this and rebooted. Back to stock YES. Rooted-NO. All data still there!
SO... I reunlocked with the method that should have wiped my device and rooted again, install tenfar's CWM. Rebooted and all my stuff is still there!
Guys I am talking everything, accounts, wifi settings, alarms etc. All this flashing and wiping and resetting and I still retain everything!
Anyone care to take a stab at why?
EDIT: So far this time around CWM has stayed put after several reboots but I have not tried a reset today. (It is kinda nice not losing all that but I am pretty sure I should have lost it!)
You just need to delete the following file first:
/system/etc/install-recovery.sh
then you need to install again CWM as you did before.
What is happen is everytimr you reboot the phone is checking the recovery partitions and if the check is different it will rewrite the stock recovery, so you need to delete or rename that file and that will solve the issue...
Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP
EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!
Ok, I think I'm in a deeper trouble than usual.
I've made a nandroid backup like usual and flashed the latest Dirty Unicorns ROM (http://forum.xda-developers.com/nex...-dirty-unicorns-v10-0-official-6-0-1-t3326798). It didn't work as well as I had hoped - was getting force-closes on practically everything. So I wanted to restore the backup. It restored, but didn't load. Odd, so I thought let's restart the phone. So I did, but the phone just kept sitting on the DU logo and not load at all. Ok, so let's clear both Dalvik and Cache. Still doesn't boot, just sits on the logo. Ok, let's factory-reset the phone, re-download, re-install the ROM, clear everything and try again - still the same, never boots. Ok, super weird by now, never happened to me before. Already took out the trusty old Nexus 5 as the backup, as things are getting more complicated.
So I tried flashing two other ROMs (CM13 and Exodus), but the same thing happens - it just sits on the respective ROM's logo. Can anyone tell me what's happening? I'm including a pic of my bootloader. Looking at the BL and Baseband values, they looks different - are they supposed to be the same?
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Ok, don't know why or how it happened, but my TWRP version was still on 2.8.x.x, even though I'm sure I flashed the newest one. I flashed the 3.0.2.0 again, but the situation is still the same.
brichardson1991 said:
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Click to expand...
Click to collapse
From here? http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
From here sorry: https://developers.google.com/android/nexus/images#angler
if you get stuck follow Heisenberg's guide step 10 :
10. How To Flash The Factory Images (And Return To Stock)
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Yep, all good now. Followed all the steps, loaded stock images, flashed custom recovery, followed by the ROM, all good now. Thanks a bunch!
Was too quick to report success - now my SIM doesn't work. It populates the APNs, says LTE from the quick slide menu, but stays on no signal in the status bar, plus errors out when refreshing web pages, etc.
I've tried flashing different (including the latest) vendor images as well as different radios.
EDIT: never mind; the freaking Mobile Data was turned off (why the **** does it happen?). Turned it back on; all good now.
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted