Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!
TWong1200 said:
Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!
Click to expand...
Click to collapse
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.
RikRong said:
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk
TWong1200 said:
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.
RikRong said:
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.
Click to expand...
Click to collapse
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk
I was, for some reason, able to get it to boot up once today. I was able to get to the 'Power off and Insert SIM' screen. After powering off, though, it would no longer fully boot into the OS. Still bootlooping.
Less than an hour later, i got it to boot up yet again. Not sure how, but it's booted up and now with my SIM installed. I know if I reboot, it'll happen again.
Anyone have a clue what it could be? Anything I can do before shutting it down that could help?
TWong1200 said:
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
you can re-write the partitions using this tool, for the 926 only
https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar
Related
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Natural_born_chilla said:
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Click to expand...
Click to collapse
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
gee2012 said:
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
Click to expand...
Click to collapse
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Natural_born_chilla said:
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Click to expand...
Click to collapse
Go into recovery and clear the caches and do a data factory reset and see if it boots, if it doesn`t go into fastboot and flash a Google factory image. A good advice = DO NOT USE TOOKITS. Good luck bro
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
xsteven77x said:
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it through fastboot
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Rushing said:
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not real familiar with using fastboot, when I put this recovery on and unlocked the phone was the first time I ever used it. So how would I go about doing that and what does it do
Clockworkmod
Clockworkmod recovery is available for the M8 but it is not the official version. Link: http://forum.xda-developers.com/showthread.php?t=2708520
reaper420 said:
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Click to expand...
Click to collapse
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
berndblb said:
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
Click to expand...
Click to collapse
Yeah it doesn't wipe anything the phone restarts and all my apps and their data is still intact. I just finished recovering from a bad situation. I flashed philz touch recovery using flashify and when I went to the recovey to do a backup the screen went black and booted staight into the hboot screen, every time I tried to reboot the phone it would send me to the hboot screen. I finally got twrp back by fasboot from my computer it was the newest twrp I got to flash I believe 2.7.1.0 I tried to restore a backup but all it would was restore the system and stop when it got to system data. I even tried flashing a new rom and that failed also. I then installed the other twrp 2.7.0.2 because I read most people are still ueing it because of problems with theother one. The phone still wouldn't boot or flash a rom but I got the restore to work by choosing not to restore data after rebooting two or three times the phone finally rebooted and all my apps and their data were still the even though I tried to install and new rom three or four times. Im a little worried now about trying to flash anything now. Im not new to android but my last phone was rock solid and I never had to deal with this many head aches. Thanks for any insite you can offer and sorry for such a long post
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
reaper420 said:
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
Click to expand...
Click to collapse
That file downloads as 0 kb
QUOTE=berndblb;54407730]That file downloads as 0 kb [/QUOTE]
I tried a reset again (which didn't work) then I tried for a log and the phone just reboots the second I touch the slider to make a log
ok I can get a log if I dont do anything else so I have a log before the attempt to factory reset but I can't get one after I try to reset. Will that do any good
https://docs.google.com/file/d/0B620epsnenvUeER0aERrYlRSUUU/edit?usp=docslist_api
RUU back to stock using the thread in the development forum. At the end of following the RUU instructions it gives you the option you flash a recovery. Select yes and flash twrp
Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?
Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app
I've already tried that, didn't work :crying:
Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.
Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.
_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.
Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.
Replace internal storage, nothing else you can do
Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good:
Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk
bucketheadmjs said:
Hi all,
I have been struggling with an issue for several months. Everytime I restart my phone the phone boots to my ROMs lock screen freezes and reboots again. Sometimes I can get my pin entered and sometimes not. Even if the phone unlocks it freezes and reboots shortly after.
I have had this issue on every ROM I have tried (Exodus, Euphoria, CM nightlies). I am currently running fastboot flashed stock COS 12.1, no root, stock recovery. My modem is current and I don't use any battery saving apps.
Has anyone experienced a similar issue?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.
If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.
Heisenberg said:
When flashing are you wiping properly (system, data, cache, dalvik cache)? Flashing the stock images with fastboot doesn't wipe data so unless you wiped data with TWRP first that hasn't happened and could be causing your problems.
Click to expand...
Click to collapse
I didn't realize that flashing image files didn't completely overwrite the partition. I did a cache wipe today but it didn't seem to work from the stock recovery.
I have data encryption enabled BTW...
Sent from my A0001 using Tapatalk
Thymo said:
If after trying wiping data it still doesn't work. Upload /proc/last_kmsg (dmesg from last boot) and the logcat.
Maybe we can find out what's going on by looking in the logs.
Click to expand...
Click to collapse
I need to be rooted to provide the kernel logs and logcat correct?
Sent from my A0001 using Tapatalk
I will clean flash wiping and formatting everything this morning just to make sure and report back. Thanks for the support!!!
Sent from my A0001 using Tapatalk
Just a quick update... I took my OPO all the way back to stock using OnePlus's patch files that @Heisenberg re-posted. I did this after a full format of all the usual suspects. I then updated via OTA all the way to COS 12.1.
Prior to installing any apps I started experiencing the "double reboot" issue. I then erased and flashed both the persist image and reserve4 image.
I have since rooted, flashed twrp, and slowly begun to rebuild and test COS 12.1. So far no double reboots (which will now start to occur since I said that).
Admittedly, I don't completely understand the persist and reserve4 roles being played in all of this...
Sent from my A0001 using Tapatalk
I would like to go out on a limb and say my issue is fixed! Thanks to everyone for their help. This issue had plagued me for months through countless flashing...
Sent from my A0001 using Tapatalk
I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.
TeoJohn92 said:
I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.
Click to expand...
Click to collapse
Doesn't look like battery issue.Maybe caused due to xposed.
Mr.Ak said:
Doesn't look like battery issue.Maybe caused due to xposed.
Click to expand...
Click to collapse
After a clean flash, the phone worked smoothly for a whole day; but last night it restarted and began to reboot and lock on the unlock screen. (After the clean installation, I restored the apps and data via Titanium and the old Nandroid Backup). Now I'm installing a new rom, I'll see if the problem persists. Have no idea how this problem occurs.