Hi, i recently acquired a RAZR HD (xt925), and since i had a great experience with CM on my previous phone, a Samsung GS2, I immediatly unlocked the bootloader, flashed clockworkmod recovery, and installed CM10.
the installation finished without errors, but when the device rebooted, the splash screen kept spinning endlessly, so i had to hard reset it, got back to recovery mode, tried to flash a stock rom only to find out that stock roms should be flashed through RSD Lite. when i tried to go that way, the process failed at first step of 15. have in mind that i never had troubles going back and forth between modes.
silly me, i didn't cared for using the backup tool from the recovery, so now i'm kinda stuck in here.
all i can think of now, is borrowing a RAZR HD from a friend and backing up his system to a SD card, putting that SD card on my phone and then try to use that backup, but i don't know how dangerous that procedure.
to make things worse, i'm not sure if my phone was ICS or JB, but probably ICS
NOTE: i know i did things hastly and recklessly. no need to point that out.
You need to edit the firmware and delete the 'getvar' line for work with rsdlite.. And you need to be on a jelly bean firmware to install cm..
But why you tried to install a very OLD version of cm? Why don't install CM11?
If you want cm11 be sure to have a updated recovery and install a moto_msm8960_jbbl build.
And I recommend learn to use fastboot commands, sometimes it's better and quicker than rsd lite
Enviado desde mi RAZR HD mediante Tapatalk
Wrong info posted on my behalf - Ignore this. oops!
JoseBerga said:
You need to edit the firmware and delete the 'getvar' line for work with rsdlite.. And you need to be on a jelly bean firmware to install cm..
But why you tried to install a very OLD version of cm? Why don't install CM11?
If you want cm11 be sure to have a updated recovery and install a moto_msm8960_jbbl build.
And I recommend learn to use fastboot commands, sometimes it's better and quicker than rsd lite
Enviado desde mi RAZR HD mediante Tapatalk
Click to expand...
Click to collapse
yes, i actually did that, and instead of failing at the first step, it failed at the second one.
anyway, i decided to cut the losses and sent it for repairs, didn't to risk making it worse.
mgzfoto said:
yes, i actually did that, and instead of failing at the first step, it failed at the second one.
anyway, i decided to cut the losses and sent it for repairs, didn't to risk making it worse.
Click to expand...
Click to collapse
you have an unlocked bootloader. the only way you could have made it worse is flashing the wrong phones software to it. there may be other ways, but basically, you have to do something inherently stupid to brick it.
you just wasted easy money getting it fixed. they will flash it in 5 minutes and send it right back to you.
not trying to be harsh, hastily flashing it was a bad move, but throwing your hands up in defeat before following advice to fix it is just sad.
why not try and lean how to fix it so you can in the future with ease?
just my advice/opinion, not meant to be taken in a bad way.
1526
bweN diorD said:
you have an unlocked bootloader. the only way you could have made it worse is flashing the wrong phones software to it. there may be other ways, but basically, you have to do something inherently stupid to brick it.
you just wasted easy money getting it fixed. they will flash it in 5 minutes and send it right back to you.
not trying to be harsh, hastily flashing it was a bad move, but throwing your hands up in defeat before following advice to fix it is just sad.
why not try and lean how to fix it so you can in the future with ease?
just my advice/opinion, not meant to be taken in a bad way.
Click to expand...
Click to collapse
no, it's ok, i agree with you. a friend even told me that i'm getting old and wallet-happy.
Related
http://androidcentral.com/team-hydro-bootmanager-coming-soon-puts-end-bootloops-forever-hacking
Very interesting... so if we get stuck in a bootloop we could just recover from a Nandroid backup without having to revert to stock, etc.
Sent from my MB865 with Tapatalk... pardon my swype!
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
I am pretty sure my phone was bootloop and how would you get it into recovery right now? i had to use the fastboot files to do it. it is a good idea though
jimbridgman said:
Too bad that wont work for us... it is in the boot.img, and we can't touch that until we get the bootloader unlocked.
Good find though.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
cogeary said:
Ah, nevermind
But just wondering... if it's based off of CWM, and we can reboot into CWM, and we can get CWM to appear on every boot... then shouldn't we be able to get something like this to work without modifying the boot.img?
Click to expand...
Click to collapse
Nope, if you use the razr boot hijack, it is exactly that, a hijack. It uses several "android/Linux" binaries that it "hijacks", to allow you get into CWM, just before the android UI comes up, but after the kernel is started. To get the particular hack you mentioned, working, you will have to modify the boot image, to include the recovery on boot, that will start just before the kernel is actually started/starting.
Like others have said, that since we have the fxz it does not really matter. Since I have really been doing some serious hacking and development on this phone, I have soft bricked or boot-looped my phone I can't count how many times, and even the razr CWM on boot does not always help. A good backup from CWM, and the fxz is where it is at, and really the best solution for things like this.
Most people on this site who have this phone really should not worry too much about these things, because the likelihood of doing this is very small unless you really are doing some serious hacking or development work like lfaber06 and I are. We will usually not release something to the rest of the world without testing it first, and giving explicit directions on how to do the job without bricking the phone. For those brave souls that are trying to do some dev work, and are new to it, until we get the bootloader unlocked, again the best bet is the fxz and a good backup from CWM.
I screwed up my phone, I rooted it and was uninstalling some bloatware that came with it (sound hound, check-in app etc) but I deleted something important and for some reason I my internet browser was uninstalled and I cannot install CWM (will clarify below). Before my brower was uninstalled I was unable to install any more apps (things from the Market would download, but never install), so I tried a factory reset (being stupid since I uninstalled so much from the stock ROM) and then my browser was gone.
Being a total moron I did not back anything up, so I thought I could install CWM to just reflash the stock ROM. I rooted my phone successfully (following htc dev) but could not install CWM, after flashing the .img file and rebooting it just reboots as normal and shows no evidence of CWM being installed.
My phone is a Rogers HTC One X and I've been making sure to find the guides for Rogers/AT&T HTC's, but I'm still failing .
Use ADB to push the missing apps to the phone?
But it sounds like you want to restore the phone to the state it was before you removed apps?
If so, first step is to get a working recovery. Can you get Rom Manager on your phone? If so, you could flash CM from there.
If not, find a thread on flashing recovery. I have not yet rooted mine so can't be more specific.
And you do know how to get into recovery by holding volume down and power etc? Sorry if I underestimate your experience but sometimes people miss basic stuff.
Sent from my EPAD using Tapatalk 2
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Edit: I see from comments below it appears that some people think I was being sarcastic in making this post: however, see this thread:
http://forum.xda-developers.com/showthread.php?p=22897771
I have seen a number of other warnings over the years of inexperienced users who try to get out of trouble by simply applying manufacturers' updates or factory images to an unlocked phone with a custom recovery and make things much worse.
Sent from my EPAD using Tapatalk 2
How do I use ABD to push missing apps back? Don't worry about underestimating my knowledge at all, this is my first android phone.
I googled how to install custom ROMs and CWM and TWRP came up, I tried both and neither installed. I unrooted my phone successfully and started phone in fastboot, flashed the .img files and then restarted but nothing new was installed.
tangiers said:
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Why are you saying that? Nobody is hard bricking a phone by flashing the correct RUU.
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting. <br />
<br />
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Funny guy.
Sent from my HTC One X using xda premium
The FUD is strong in this one...
So what do you guys suggest I do? Should I just bring it back to the store? I got it like four days ago. How do I unroot it? I can't access the market (no brower or market app) so I can't get SU to unroot.
to get back to factory you can do the following
relock the bootloader.
reboot to bootloader and use the command fastboot oem lock
after that install the 1.85 RUU from here http://forum.xda-developers.com/showthread.php?t=1670238
it will take longer than the 10 minutes it says it will take so don't worry.
after that you can unlock again with that same token you used to unlock in the first place.
I'm at work right now so I can't do that yet
If I bring it in without doing that stuff will they know or even care? I have some BS story made up D). Also mine is a Rogers, but the AT&T stuff works with it right?
I appreciate your quick responses
Rogers phone would need rogers ruu loaded
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
bman3k said:
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
Click to expand...
Click to collapse
why do you want to return it? For this problem or is there something else?
Yes it is for this problem (and all the ones in the first post) I tried for several hours last night to fix it, but couldn't.
I followed the guides for how to install CWM and TWRP to the word and they would not install. If I cannot install them, I cannot reflash stock RUU right?
I still want the HTC One X... just one I didn't screw up XD.
This will put you back to stock and you won't need to return anything
http://forum.xda-developers.com/showthread.php?t=1658929
Ok, I'll try that when I get home, thanks for your help.
PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.0... from http://forum.xda-developers.com/showthread.php?t=1543593 is what I'll need right?
Correct.
Thanks for your help, that last guide you linked solved it. The first time I looked at it I misread "lock" for "unlock", but I got it to work now . Thanks for your patience and help gunny.
No problem. I'm glad you got it sorted.
I just got my rogers one x and, I'm fairly disappointed in the storage capacity. What advantages would I gain from routing a phone that is already as fast and responsive as it is?
Sent from my HTC One X using xda premium
hi guys i really need help with my Motorola razr hd lately its been running really slow and freezes and every time i do a soft reset or a reset the phone completely does a factory reset all the time and it takes me ages to get it up and running because when i turn it on the green android with the spinning gear comes up it takes a while then the phone turns off again and a few times after it was loading a red x appeared on the back of a lying android then im back to square one i was wondering if anybody would no whats wrong with it because it doesn't make sense to me at all cheers
ibbi891 said:
hi guys i really need help with my Motorola razr hd lately its been running really slow and freezes and every time i do a soft reset or a reset the phone completely does a factory reset all the time and it takes me ages to get it up and running because when i turn it on the green android with the spinning gear comes up it takes a while then the phone turns off again and a few times after it was loading a red x appeared on the back of a lying android then im back to square one i was wondering if anybody would no whats wrong with it because it doesn't make sense to me at all cheers
Click to expand...
Click to collapse
I think the Rogers/Fido Jelly Bean OTA update broke the recovery. Your best bet is to flash the stock firmware using RSD Lite.
Here is the post to find the stock firmware based on your location:
http://forum.xda-developers.com/showthread.php?t=2032284
Here is the post on how to flash that stock firmware:
http://forum.xda-developers.com/showthread.php?t=2176753
I'd avoid doing a factory reset even after flashing the stock firmware. If the is running slow, try disabling some apps.
Root for 4.1.2 is available here:
http://forum.xda-developers.com/showthread.php?t=2228098
With a rooted phone, you can freeze some systems apps using Titanium Backup. Here is a post that lists all apps that can be safely frozen.
http://forum.xda-developers.com/showthread.php?t=2222480
Just a word of caution. Before doing anything listed above, make sure to read and re-read everything. I'm not responsible for anything that happens to your phone.
Hope this helps.
thank you
india23 said:
I think the Rogers/Fido Jelly Bean OTA update broke the recovery. Your best bet is to flash the stock firmware using RSD Lite.
Here is the post to find the stock firmware based on your location:
http://forum.xda-developers.com/showthread.php?t=2032284
Here is the post on how to flash that stock firmware:
http://forum.xda-developers.com/showthread.php?t=2176753
I'd avoid doing a factory reset even after flashing the stock firmware. If the is running slow, try disabling some apps.
Root for 4.1.2 is available here:
http://forum.xda-developers.com/showthread.php?t=2228098
With a rooted phone, you can freeze some systems apps using Titanium Backup. Here is a post that lists all apps that can be safely frozen.
http://forum.xda-developers.com/showthread.php?t=2222480
Just a word of caution. Before doing anything listed above, make sure to read and re-read everything. I'm not responsible for anything that happens to your phone.
Hope this helps.
Click to expand...
Click to collapse
thanks you for the help and im sorry for the late reply its been pretty crazy at work im going to try this tonight and hopefully it all goes well once again i really appreciate the help
no good
i attempted to flash the phone but i kept getting a failed flash i took a screen shot of the RSD LITE ive read everything over and over and im not sure whats happened tempted to just break the phone and move on lol
What's up,
So here is the deal,
For whatever reason, RSD lite does not like the <get var> command in the XML file you used to flash the stock rom. You have two options:
1) Open the XML file in notepad and remove any lines with a tag labeled <get var> (I think there's two in there)
Or...
2) Download a utility like Matt's or my own, which does the work for you. In mine for example, you go into fast boot mode on your phone, and press two buttons in the utility, and presto!
You're gonna need to do some exploration to find the threads with the utilities in them, I can't provide links since I'm on my mobile, but generally look in the "Razr HD Original Android Development", you should find a couple.
Cheers!
Sent from my DROID RAZR HD using xda app-developers app
ibbi891 said:
thanks you for the help and im sorry for the late reply its been pretty crazy at work im going to try this tonight and hopefully it all goes well once again i really appreciate the help
Click to expand...
Click to collapse
No problem. Happy to help. This happened to me as well and freaked me out the first time.
ibbi891 said:
i attempted to flash the phone but i kept getting a failed flash i took a screen shot of the RSD LITE ive read everything over and over and im not sure whats happened tempted to just break the phone and move on lol
Click to expand...
Click to collapse
Look at Mr. Parkinson's reply. Step (1) is your best option. That's exactly what I did. There are two <getvar> lines. Delete those and you should be good,
zzz
india23 said:
No problem. Happy to help. This happened to me as well and freaked me out the first time.
Look at Mr. Parkinson's reply. Step (1) is your best option. That's exactly what I did. There are two <getvar> lines. Delete those and you should be good,
Click to expand...
Click to collapse
i tried to do it but im having problems again in that xml file i can only find one getvar line
<step operation="getvar" var="max-download-size" /> which is the one here and ive deleted and i get another problem now ive taken a screeny do u guys reckon im missing something and im really sorry for busting your balls but im pretty bad at this stuff i really really appreciate your patience with me
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part
So I've been waiting on a unified firmware before trying CM. Don't judge me. However, I can't get it to boot. CWM recovery works fine, wiping /data and /cache works fine, as does installing the zip.
I tried both nightlies, and both won't boot beyond the Moto 'BOOTLOADER UNLOCKED" warning. This is the Verizon RAZR HD.
Any thoughts?
same for me
I got the exact same behavior. I think todays nightly should be sorted out.
Ask in QA
Saludos
gustrick said:
Ask in QA
Saludos
Click to expand...
Click to collapse
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the storage and mounts section of your recovery
SCFirefighter said:
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the mounds section of your recovery
Click to expand...
Click to collapse
Use philz 6128 w/cwmr 6047.
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
XBlackChaosX said:
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
Click to expand...
Click to collapse
The dt is for the Moto X I believe.
Sent from my DROID RAZR HD using Tapatalk
I can't see, to be able to get this rom to detect my T-Mobile Sim.
Sent from my Droid Razr Maxx HD
Hydr0id said:
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
Click to expand...
Click to collapse
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
MauricioBR said:
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
Click to expand...
Click to collapse
I thought I was the only one, I can confirm the problem still persists on 2/24 nightly, on today's one I haven't tried yet. Also, the format/system is under mounts & storage in the main menu of CWM. I did a clean install of the unified nightlies, that hasn't solved my problem, I'm really concerned of what could happen if my phone powers off and there is no way to past the "bootloader unlocked" screen.
Sent from my RAZR HD using Tapatalk
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
eta: http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
Find your original Motorola usb cable. I've seen a lot of posts over the years because of bad cables.
Make sure you have the right one, and re-flash CWM recovery. Check its md5 before flashing using the one from my earlier post.
Boot into CWM and format /data and /cache, and then find the option to format /system.
Flash the nighly from http://get.cm/?device=moto_msm8960
Flash the gapps package for CM11: http://wiki.cyanogenmod.org/w/Google_Apps
Reboot
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
SCFirefighter said:
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
[...]
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
[...]
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
Click to expand...
Click to collapse
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
MauricioBR said:
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
Click to expand...
Click to collapse
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
SCFirefighter said:
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
Click to expand...
Click to collapse
The unified versions do not show up on the updater.
I tried to search another way to do the OTA, but had no luck. I tried installing the unified from the 24th over the non-unified (without wipes), but the charging problem came back.
Next step is to try flashing CWM over again and will go from that -- although I find hard to believe that the same CWM that works for one version is causing the other to bug out.
I've pushed and merged the fix for charge only mode: http://review.cyanogenmod.org/60302
It will be fixed in the next nightly.
kabaldan said:
I've pushed and merged the fix for charge only mode: [...]
It will be fixed in the next nightly.
Click to expand...
Click to collapse
Wow, thanks so much!
I saw it was added on the nightly and I'm downloading right now to test it.
Edit: It's fixed! Thanks again!
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
SCFirefighter said:
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
aviwdoowks said:
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
Click to expand...
Click to collapse
Flashing back to stock results in a fully functional phone. When I boot into the custom recovery and format everything followed by the zips I just don't get it to boot at all.it just hangs at the unlocked boot loader warning.