So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Storm0203 said:
So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Click to expand...
Click to collapse
Try this http://motofirmware.center/files/file/50-1ff-obake-maxx_verizon-user-444-su6-7-release-keysxmlzip/
I actually used this on my Maxx (I believe it's the mini image, but it works fine, I may try the maxx version linked above if I run into any issues) http://motofirmware.center/files/file/52-cfc-obakem_verizon-user-444-su6-7-release-keysxmlzip/
Just use RSD to flash the image (you'll need to edit out the line in the XML file that reads <step operation="getvar" var="max-download-size" />)
osucowboy96 said:
Try this *link removed because of XDA's rules*
I actually used this on my Maxx (I believe it's the mini image, but it works fine, I may try the maxx version linked above if I run into any issues) *link removed*
Just use RSD to flash the image (you'll need to edit out the line in the XML file that reads <step operation="getvar" var="max-download-size" />)
Click to expand...
Click to collapse
Well, now the phone will boot, but I keep getting a "com.android.phone" forceclose every time the phone attempts to connect to data (it'll show the "no sim" icon, that will go away, it will get 1x, try to connect to 4G, then the process crashes, and the whole process starts over again).
I just don't understand how a completely stock image on a non-rooted phone doesn't work. The ONLY modification I have right now is the unlocked bootloader. Sigh.
Did you try a full wipe/factory reset?
osucowboy96 said:
Did you try a full wipe/factory reset?
Click to expand...
Click to collapse
Yup. No dice. It'll work fine, and then at some point (at random), it will start the FC loop again.
Did you try both images I provided, and did you edit out the line beforehand? I don't know what else to suggest, other than maybe a hardware issue?
osucowboy96 said:
Did you try both images I provided, and did you edit out the line beforehand? I don't know what else to suggest, other than maybe a hardware issue?
Click to expand...
Click to collapse
I didn't try the mini image. I'll give that a shot. And the MAXX image does not have that line in the first place.
Storm0203 said:
I didn't try the mini image. I'll give that a shot. And the MAXX image does not have that line in the first place.
Click to expand...
Click to collapse
Alright, so I tried the Mini image as well. That one automatically factory resets when I reboot.
I don't know what else to suggest. I searched for quite a while to find those images when I needed one. I guess I got lucky on using it for mine, it's been solid with no issues. Literally the only issue I have had was one force close of "contacts" when I made a call, but that only happened once. It's been a long while since I used House of Moto, not sure if it's even relevant anymore, but you might research it.
Storm0203 said:
So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Click to expand...
Click to collapse
Hardware or rather memory issues!
Did you check the md5 of each xlm.zip?
Related
Had just flashed the latest CM9 nightly (clean install, fresh wipe) yesterday and everything was running fine.
This morning, woke up, my phone was turned off. When powering it on it hung on the google screen. Fastboot still working, booted into recovery only to find that I would get error messages when trying to load my backs "E:unable to mount /sdcard". Apparently it also couldn't mount /data. So I was unable to flash any images or restore or boot up.
Seeing that fastboot was still working I assume I'm not bricked yet. I tried flashing a new boot and cwm recovery via fastboot - no dice. Same errors.
I don't have a recent backup of anything in sdcard, but at this point I'm willing to sacrifice it.
Found this thread http://forum.xda-developers.com/showthread.php?t=1078213
and I'm trying to follow the steps to flash back to stock GB. using the GRJ22 images
It flashed the boot and recovery without issue but seems to hang while flashing the system.img. I know it's a big file, but it was up to ~2hrs with it still transferring. I pulled the plug on it and tried again, lost patience after an hour.
Now I had the idea of maybe locking and unlocking the boot loader would help things.....not sure why I thought this. Anyway, now it seems to hang on the unlock bootloader screen.
So my question now - am I screwed?
- anything else to try?
- is it really "hanging" or do I need to give it more time?
- have I screwed myself even more by now locking my bootloader and flashing the stock recovery?
Any help would be very much appreciated....
Some new additions and new insights from the reddit android community:
- this probably has nothing to do with CM9. My phone has been wonky for about two weeks - random reboots, sometimes rebooting into recovery. That's why I thought I'd throw on the latest nightly and do a fresh wipe yesterday.
- There's definitely something up with /data. Anytime I tried wiping all/factory reset in cwm recovery I got errors about not being able to mount /data or being able to find files in /data
- basically anything I do involving /data partition causes the phone to lock-up -- flashing the boot.img and recovery img worked, but not system. Also, I think the reason I can't re-unlock the bootloader is because during the unlock process it tries to do a factory reset/data wipe
Basically I think there are two things I need to know if I can do - 1) unlock the bootloader again, via some way that won't try to reset the /data partition and thus won't freeze the phone. 2) try repartitioning /data
I really hope I didn't screw myself by locking the bootloader. I'd actually feel a lot better if it was something in my phone that just failed hardware-wise rather than something I could've fixed if I wasn't too quick to try poorly thought out ideas.....
Any help at all would be appreciated!
Possibly (and likely) a corrupted nand flash. Fairly common problem sadly. I'd say it's a good thing your bootloaders locked, no dramas sending it back to samsung. It might've been possible to reset the partitions and flash fastboot images but i don't think i've seen anyone who has done this to sort any similar problem. Hopefully your phones still under warranty
Well thank God that it turns out that I'm still on warranty.....sending the phone back to Samsung tomorrow.
Like you said, it's actually a good thing the bootloader is now locked and the stock boot img and recovery img are now back on! Hopefully this makes it more likely that they weren't turn away my phone.
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Harbb said:
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Click to expand...
Click to collapse
I bricked my nexus s 4 days before Christmas last year... and i was using a custom rom obviously with an unlocked bootloader and custom recovery image, and i handed it to vodafone, and guess what? they repaired without asking any questions, and the day before Christmas! sooo happy maybe because i was thirteen then, they didn't suspect a thing
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah
Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that
Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5
Might be helpful to others to explain exactly what you did to your phone.
lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7
aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.
Glad it's working finally
Sent from my Nexus 7
Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!
aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.
You guys unlocked the bootloader first right?
Sent from my SGH-I747
This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me
WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk
So I'm S-off, Firewater, SuperSU, CWM, stock software, I have not loaded a ROM, fastboot flashed the nohbootimg firmware update, added the HTC browser, and flashed the OTA-killer.
Can I do a Factory reset without it messing something up? I'm having 3 issues that I want to see if a reset will fix, one is my alarm clock keeps turning itself off, another issue is that when I turn the phone on it seems to take a long time to "Prepare Sim card" , and the last issue is that I get a email "login failed" notice which is poping up before the phone starts seeing the data connection.
Thanks
Dragbike Racer said:
So I'm S-off, Firewater, SuperSU, CWM, stock software, I have not loaded a ROM, fastboot flashed the nohbootimg firmware update, added the HTC browser, and flashed the OTA-killer.
Can I do a Factory reset without it messing something up? I'm having 3 issues that I want to see if a reset will fix, one is my alarm clock keeps turning itself off, another issue is that when I turn the phone on it seems to take a long time to "Prepare Sim card" , and the last issue is that I get a email "login failed" notice which is poping up before the phone starts seeing the data connection.
Thanks
Click to expand...
Click to collapse
If you are simply stock and rooted... you can factory reset using CWM without any issue.
Worst case scenario if you are backed up...
http://forum.xda-developers.com/showthread.php?p=52115727
Since you have not installed a ROM I would think a factory reset would be a good first step. You will probably lose some if the customization you have done, but I wouldn't think you would lose root or anything like that. I believe a reset will just wipe the data partition ( maybe dakvik and cache as well).
Sent from my VZW HTC One (M8)
dottat said:
If you are simply stock and rooted... you can factory reset using CWM without any issue.
Worst case scenario if you are backed up...
http://forum.xda-developers.com/showthread.php?p=52115727
Click to expand...
Click to collapse
Thanks! Just curious, I'm trying to learn as fast as I can , how does CWM reset differ from the the stock one?
And do you think that the CWM reset could help with the issues?
Dragbike Racer said:
Thanks! Just curious, I'm trying to learn as fast as I can , how does CWM reset differ from the the stock one?
Click to expand...
Click to collapse
They both typically wipe the same partitions however the stock recover also resets some radio elements which is why you will always see me suggest to someone with radio issues to do a factory reset from stock recovery.
Sent from my HTC6525LVW using Tapatalk
I used the reset in CWM and I'm going through the setup now, I guess we'll see if this helps. Thanks guys!!!
Well the alarm is staying on so far and I'm not getting the email login failure but I think I lost my CWM, guess I'd better reload it.
Interesting, I can't seem to get into my hboot mode? hmmmm
nevermind, I'm a dolt, forgot to turn off fast boot and I Still have CWM but when I select reboot I get a message "Root access possibly lost. Fix?" Anyone know what this could mean? Should I Pick "Yes - Fix Root" . I'd assume so, what the heck lets see what happens. lol
I have had nothing but issues with this phone upgrading. Every time it bricks, the first time I got it working by reformatting DATA partition. The other times basically gave up and 2-3 days later I come back and it magically starts working again. The day that 5.0.1 came out I downloaded the FUU, well everything looked good the it gets stuck at the Android is upgrading starting apps. Since then I have redownloaded all 5.0.1 files I could find on XDA, and the same results. I tried different roms, using TWRP to wipe and rewipe and format and do it again and again. I have tried to downgrade to 4.4.2 and 4.4.4 but i get the process system isn't responding when it boots up. I am unsure what to do now, anything will help.
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
berndblb said:
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
Click to expand...
Click to collapse
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
dab1414 said:
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
Click to expand...
Click to collapse
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
andybones said:
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
Click to expand...
Click to collapse
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
dab1414 said:
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
Click to expand...
Click to collapse
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
andybones said:
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
Click to expand...
Click to collapse
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
dab1414 said:
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
Click to expand...
Click to collapse
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
andybones said:
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
Click to expand...
Click to collapse
Yes I am S-OFF since the day I got the phone. And I have been using RKND roms, but I downloaded and tried all the 5.0.1 roms to see if anything would help. At this point I just want my phone working again, but preferably with the ability to change roms when i want to which is about once a month or two.
So I had tried everything I knew how to do again with no luck. Then I just let my phone sit for the last week. Then I decided to turn it on last night and it works fine. Is there any reason why I had to let the phone stay powered down for days for it to start working? This is the second time I had to do that when upgrading the firmware.
Thanks for bringing this up and I'm glad to hear it worked out for you even tho it took some time. My bro just ran the vzw update while on viper 4.1.0 and now he says his screen is unresponsive. He said it ran through all the normal start up procedures but the welcome screen is shaded (like it's in the background) and he says it won't respond to any touches whatsoever. I won't get a chance to see it until I return to work on Wednesday but if it does the same as yours maybe it'll fix itself by then. :fingers-crossed:
Edit: I just realized that you ran the FUU. He went and said yes to the stupid OTA! Hopefully I'll be able to do something with it when I get back but I'm thinking that running the OTA while rooted and S-Off'd might've screwed it up.
Update: I'm a moron! :silly: It didn't do anything to his phone. I just had to reinstall the recovery and viper 4.3.0 and it's working fine again. I think actually it might've been a good thing he did cause now the phone had the right firmware on it for LP so it all worked out. Sorry for cluttering up your thread.
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....