So I did an OTA to ICS, and it was working fine. So I rooted, safestrap'd, and loaded Eclipse 1.3 Hybrid. Was working ok. Messed with the DPI a bit, and got itself stuck in a bootloop.
So I tried a nandroid restore - boot loop.
Tried reloading Eclipse 1.3.2, wiped data et. all - bootloop.
Tried restoring my stock build - bootloop.
Went back to safe mode off - black screen, no boot anim, PC gets motocrap popping up.
Fastbooted back to 217 - black screen, PC gets motocrap popping up.
Suggestions?
Are you still getting the safestrap splash screen?
My advice would be to do a factory reset in stock recovery. If that doesn't fix it, fastboot everything manually. If by chance you did it manually the first time, this time use RSDlite.
It sounds to me like you either missed something the first time (it happens to the best of us), or you got really unlucky and developed a hardware problem randomly. Since it sounds like safestrap was coming up before, I doubt it's hardware.
Sent from my Amazon Kindle Fire using xda app-developers app
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
mxgoldman said:
No safestrap anymore. I did the factory reset in stock to no avail through RSD and the MotoICS tool. And unfortunately, I can't send it in for warranty repair because it has an unlocked bootloader.
Click to expand...
Click to collapse
How did you get an unlocked bootloader?
Also, what happens when you try to boot into fastboot mode?
Sent from my XT894 running ICS
Internal Engineering sample. It'll go to fastboot mode, but it does give a warning about the bootloader being unlocked. I've done the fastboot with the 217 files, then booted to recovery and wiped data/cache. No luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Sent from my Amazon Kindle Fire using xda app-developers app
you need to flash fastboot files immediately until battery will be discharged. or you have to make motorola factory cable
Yes, the rate of discharge the D4 suffers from when OFF is ridiculous. I once had the phone discharge 40% in 24 hours...with the phone turned OFF
You really should have a factory cable or adapter and you will be able to fix it very quickly with RSD Lite and the full XML.zip of fastboot images.
The factory cable will bypass the battery and charging circuit and power the device directly, allowing you to flash and recover it no matter what state the battery is in.
That's a very unusual device and it would be a shame not to be able to fix it.
There is no reason, with a factory cable, a complete recovery would not be possible if you can get to the boot menu as you have shown in your pic.
podspi said:
Where did you get that?!
Also, that could have to do with the issue I guess. Try fastbooting GB instead of ICS, then reinstalling the ICS patch like you did before, maybe?
Click to expand...
Click to collapse
Holy snackycakes, that worked! AWESOME.
... I want that bootloader! :good:
Glad to hear you are back in business!
Related
I was about to buy my friends N1, after he cleared the data, it is now stuck on boot screen, he has sent this to me to try to fix since he is not a technical person at all, but I am also dumbfounded by it.
here is what happened:
1.) He went to settings and clicked restore to factory defaults
2.) It rebooted and got stuck to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
He send unit to me just now.
1.) Removed bat to turn off since power button no longer works to shut phone off
2.) Pressed POWER+Vol Down to enter Menu
3.) Selected Clear Storage
4.) asked to confirm, so I did, it said it will reboot in 5 seconds, so it did and still stuck with this screen.
Alternatively,
I chose recovery, then wiped everything, reboot still the same.
Tried downloading multiple roms, renamed to update.zip, but it will give me an error in recover mode, not signed.
This N1 is unlocked.
Now, I want to follow the instructions here but I am wondering if it is worth it or I will just return the n1. Certainly a bad sign having seconds thoughts on moving to Android
How To: Load a Custom ROM on the Nexus One (Updated 1.11.10) | TheUnlockr
Had the same issue
Had *exactly* the same issue a few weeks ago and tried dozens of different options but eventually gave up. I sent it back to HTC for repair and it came back in two days *with a new screen* (which I didn't ask for). The screen replacement cured the screen alignment/keyboard offset issue that I was getting multiple times a day. So I was happy Excellent service from HTC!
I had a similar problem. Reflashing the recovery image, then reflashing the ROM fixed it for me.
Try pushing over Clockwork recovery, or at least reflashing Amon_RA's recovery image. If you stick with Amon's, upgrade to 1.7.0.1 while you're at it.
The reason to try Clockwork, though, is that it allows you to disable signature checks. Plus, ROM manager integration is awesome. It saves time if you flash a lot!
FIRST, try renaming the zip file just "update". NO .zip or quotes. Sometimes the PC OS adds an extra .zip.
Ken
Gave up on it too, sent it back to HK yesterday, hopefully, they will replace it too. Thanks everyone!
I would have flashed the stock factory image on to it. That's different from flashing a zip, in that the image copies the sector bit by bit, so if there is any kind of bug, it gets overwritten.
ATnTdude said:
I would have flashed the stock factory image on to it. That's different from flashing a zip, in that the image copies the sector bit by bit, so if there is any kind of bug, it gets overwritten.
Click to expand...
Click to collapse
I assumed that would have worked for me too, but it didn't. Had to send it back....
I would have flashed boot, system and userdata, it was in the recovery so it wasnt bricked...
ah well
Update your recovery first.
Well, it seems like my phone has had its last drop. Now it's just stuck in a boot loop. I tried taking it into bootloader and reflashing, but no dice. It's been a good 2 years, you will be missed. The crappy photoshop doesn't do it justice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It was weird, its had way worse drops than on the dirt, but I guess it had its fun. Its been real guys.
I don't wanna get the samsung moment
How far does it boot before it loops?
Maby your button to enter bootloader is dead. I had this with my on/off button, it was easy to fix if you have little soldering skills.
That it hangs in a loop could be because of a brocken memory module but it could also mean that a bad reset because of the shake just corrupted the memory and its nothing to bad.
I have had this happen on my kaiser before, what fixed it was to erase the files android create on the SD card (booting from Nand). Maybe it will work for you?
dertester123 said:
How far does it boot before it loops?
Maby your button to enter bootloader is dead. I had this with my on/off button, it was easy to fix if you have little soldering skills.
That it hangs in a loop could be because of a brocken memory module but it could also mean that a bad reset because of the shake just corrupted the memory and its nothing to bad.
Click to expand...
Click to collapse
The thing it it goes into bootloader, and I can flash it, but when it starts up it still loops at the boot animation. It shows the green droid animation over and over again.
bandur said:
I have had this happen on my kaiser before, what fixed it was to erase the files android create on the SD card (booting from Nand). Maybe it will work for you?
Click to expand...
Click to collapse
Yes, I've tried this. It still loops the boot animation :/
Thanks for trying to help guys, I really appreciate it. Definitely gonna miss xda!
did you try flashing back to windows mobile?
manifest3r said:
The thing it it goes into bootloader, and I can flash it, but when it starts up it still loops at the boot animation. It shows the green droid animation over and over again.
Yes, I've tried this. It still loops the boot animation :/
Thanks for trying to help guys, I really appreciate it. Definitely gonna miss xda!
Click to expand...
Click to collapse
It seems that there is just something wrong with your actual installation. Have you cleared dalvic cache and loadet a new androidinstall.tar/gz on the sd?
I would suggest you try to flash a orginal Windows Mobile rom like thoughtlesskyle said. Try a radio update too if this will not help alone.
What to you mean with loop? does it show and staysa at the green android all the time and cant go further? or does it really reboot at some point and load untill the android pic again and again?
try to change the setup file..another builds
So my brother saw my phone sitting on my desk, and he turned it on. Lo and behold, it worked! Unfortunately, I'm loving my samsung moment too much to switch back to a qvga screen lol. I already rooted & flashed it, works like a dream
Ill just use my vogue as a backup now in case anything happens to my moment. Hopefully nothing will!
Sent from my SPH-M900 using XDA App
Hi guys,
I have bricked my phone and would love to know if anyone has a solution to unbrick it. Love the SII but didn't anticipate upgrading just yet.
I have had a custom JVT ROM running on my phone, with EXT4 enabled, and decided to revert back to stock. So I went to the EXT4 app installed on the rom and clicked convert to RFS. The phone booted into recovery where it did it's thing, and then tried to reboot, but froze on the boot image for about 20 minutes. I rebooted it, but it did the same thing. I went into recovery to try to disable the lagfix there, but it wouldn't allow me to. I tried to wipe everything but said it couldn't mount /sdcard. I then tried to flash stock JVT with Odin, and it was not able to set partition, and from this point on I have only been able to get to download mode, both recovery mode and booting lead me to the phone and computer with broken cable screen. I've since tried flashing roms and kernels on my phone but it always freezes / fails.
If anyone has any idea what has happened, and how i can fix it, please let me know. Otherwise I guess I had better start saving.
Cheers, Robbo
keriangrobinson said:
Hi guys,
I have bricked my phone and would love to know if anyone has a solution to unbrick it. Love the SII but didn't anticipate upgrading just yet.
I have had a custom JVT ROM running on my phone, with EXT4 enabled, and decided to revert back to stock. So I went to the EXT4 app installed on the rom and clicked convert to RFS. The phone booted into recovery where it did it's thing, and then tried to reboot, but froze on the boot image for about 20 minutes. I rebooted it, but it did the same thing. I went into recovery to try to disable the lagfix there, but it wouldn't allow me to. I tried to wipe everything but said it couldn't mount /sdcard. I then tried to flash stock JVT with Odin, and it was not able to set partition, and from this point on I have only been able to get to download mode, both recovery mode and booting lead me to the phone and computer with broken cable screen. I've since tried flashing roms and kernels on my phone but it always freezes / fails.
If anyone has any idea what has happened, and how i can fix it, please let me know. Otherwise I guess I had better start saving.
Cheers, Robbo
Click to expand...
Click to collapse
Did you try to re-flash stock JVT with Odin and using a pit file? It seems that the lag fix wasn't disabled on your phone. My understanding is that if you re-flash stock JVT with Odin, with re-partition, that should remove the lagfix...
http://forum.xda-developers.com/showthread.php?t=1102881
Yeah i tried that.. Over and over again. Nothing I did was working, and then finally, randomly, rather than freezing on set partition or downright failing, it decided it would proceed with flashing and is now working!! so moral of the story - just keep trying i guess. Wooo! Case closed.
Your sd card maybe damaged.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good day. I had cyanogen 9 on captivate. I tried to make backup through recovery menu and it said it was done successfuly . But after that the phone cannot boot and i only see the boot logo that appears and disappears. The problem is that usb in my phone after service center repair works only like a charger. When i try to load recovery (volume up and down and power on) i see this image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. What it is possible to do there? Is it possible even to get data from the phone? Thanks a lot in advance.
techno0007 said:
Good day. I had cyanogen 9 on captivate. I tried to make backup through recovery menu and it said it was done successfuly . But after that the phone cannot boot and i only see the boot logo that appears and disappears. The problem is that usb in my phone after service center repair works only like a charger. When i try to load recovery (volume up and down and power on) i see this imageView attachment 1803967 . What it is possible to do there? Is it possible even to get data from the phone? Thanks a lot in advance.
Click to expand...
Click to collapse
Woah, first time I see this screen. Without a working usb, you can't do much to recover on the captivate. What did you do other than a nandroid?
If you can somehow get your usb to work, getting in download mode and using Odin KK4 (without bootloaders) would bring back your phone. Otherwise, you'd need to be able to get in recovery, wipe cache/dalvik and try to boot. If that doesn't work, restore your nandroid backup.
BWolf56 said:
Woah, first time I see this screen. Without a working usb, you can't do much to recover on the captivate. What did you do other than a nandroid?
If you can somehow get your usb to work, getting in download mode and using Odin KK4 (without bootloaders) would bring back your phone. Otherwise, you'd need to be able to get in recovery, wipe cache/dalvik and try to boot. If that doesn't work, restore your nandroid backup.
Click to expand...
Click to collapse
Thank you but now it is Ok. After 10 minutes of booting it surprisingly booted and i wary to turn the phone off now . The only thing i did is making backup in recovery and the phone said it had been done successfuly . After that the phone didn't want to boot.
Help
I had my phone rooted however recently it started rebooting every hour or so with sometimes rebooting back to home screen and sometimes giving this error
It also gets pretty warm
secure fail modem
Security Error: This phone has been flashed with an unauthorized software
I tried flashing the latest firmware and factory resetting
and even then the same symptoms however surprisingly when its setting up on optimizing app screen it doesnt reboot
or when its twrp it doesnt restart. I can sucessfully spend enough time to optimize 300+ apps and restore backups without worrying that itll reboot
I am not sure what to
Can someone please help me
this is what it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I can't say that I have a solution for you, or even that I'm right. But the first thing that popped into my head is that you Flashed something (Root?) when the BootLoader is still Locked.
That, or something won't work with the version of BootLoader that's on your device. For example, not every ROM available for a phone, will work with every version of BootLoader that could be on that phone and so to install "X" ROM, you have to (first unlock it) change to "Y" BootLoader.
I updated to MM and hated it. But in order to go back to KK, I had to fool my phone into thinking it's a T2 first.
TTYL
muneebrocks said:
Help
I had my phone rooted however recently it started rebooting every hour or so with sometimes rebooting back to home screen and sometimes giving this error
It also gets pretty warm
secure fail modem
Security Error: This phone has been flashed with an unauthorized software
I tried flashing the latest firmware and factory resetting
and even then the same symptoms however surprisingly when its setting up on optimizing app screen it doesnt reboot
or when its twrp it doesnt restart. I can sucessfully spend enough time to optimize 300+ apps and restore backups without worrying that itll reboot
I am not sure what to
Can someone please help me
this is what it looks like
Click to expand...
Click to collapse
Had a family member come to me with this issue. Assuming you have custom recovery go here and flash this
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
That will allow you to boot and use phone. If you want root afterwards then re flash SuperSu (systemless version if on stock kernel).
Ser0mancerXXIV said:
Had a family member come to me with this issue. Assuming you have custom recovery go here and flash this
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
That will allow you to boot and use phone. If you want root afterwards then re flash SuperSu (systemless version if on stock kernel).
Click to expand...
Click to collapse
thanks man but I sold it for parts long time back couldnt deal with this on a daily driver
now happy on s7 active
but curious I made sure I factory resetted it and flashed firmware which wipes the internal memory how would this tool be superior to a full wip?