Related
Hey Guys
My Nexus one hangs at the startup screen and I can't seem to get it to start. So far, I have tried going into the quick boot screen and clearing the factory settings (i.e hard reset) but it did not change anything. I am bit out of ideas.
Did you do a nandroid, if so revert back to it and proceed forward from there.
sorry, I didn't do an nandroid. Can I do that now?
alright, I installed a recovery image and can enter the menu listed here.
Cyanogen's recovery source based on Amon_RA's post.
I restore the setting just fine but then when I reboot the phone still hangs. Is there another step I am missing? Is just having the recovery tool not enough? How do I restore the original settings?
same problem here did you manage to fix it ?
Same problem here. I have tried everything but I cant make it past the " X " - looking splash screen. If its of any help, the splash screen is STATIC.
Thanks in advance.
it almost sounds like either a bad flash or a bad wipe, if you made a nandroid, try resotring it. If you have not rooted or loaded any roms then the problem may be hardware side.
think the mobo is acting funny, i sent mines in for repair due to t his issue, but unlocked bootloader makes me pay $194..... im trying to figure it out before i pay as a last resort!
Hi,
I hope you can help.
I recently changed the ROM on my HTC HD2 to the Cruzer series. This worked fine. However, since the rom change, the phone itself has since been stuck in safe mode for all my Android Builds.
I have tried everything to get out of it, by holding down the menu and power keys on boot up, taking out the battery and leaving it out. I have also re-flashed the phone with the new wm ROMs several times, but it's still the same for me in Android
Do you think this is a genuine fault with the phone, or is it something to do with the Rom change and how to get out of safe mode? Any help would be greatly appreciated.
Thanks in advance.
Backup your sd card, then delete the old data.img out of the Android folder. There may have been something happen that makes it boot into safe mode.
You will loose all your setttings, contacts and apps installed and it will take a long time for the 1st boot as it is making a new data.img. This might help. At the very least you are assured that it is or isn't the data.img. And as you backed up its easy to replace if it still boots in safe mode.
ultramag
Thanks for the advice. I will try your suggestion. I have tried to reload numerous builds though, since this problem has plagued my android please. All of them complete re installs. With safe mode returning each time.
Marsbar
If the data.img isn't the culprit maybe the SD card needs to be formatted. I use the format utility in winmo (fd10 format utility if it isnt included in your winmo rom search the forums to download it). Just backup all your data, format it, and then load it back up. Hope this helps.
I have installed android rom on my sd card and it worked fine, I switched the phone off and then on again and it just keeps booting in a loop is there anyway to break in to this.
any help is needed.
regards
Have a good look at you battery oins that make contact with the battery and see if they are all aligned properly if not very carefully adjust the one that is not in line with the others. I really think your issue has nothing to do eith the SD Android you used as SD Android is very safe as far as not effecting the regular Windows Mobile OS cause it is on SD and does not touch the NAND memory wich is where the Win MO OS or what every primary OS resides.
carpy47 said:
I have installed android rom on my sd card and it worked fine, I switched the phone off and then on again and it just keeps booting in a loop is there anyway to break in to this.
Click to expand...
Click to collapse
thats exactly what happened to me whenever i tried to run android off an sd card.(which is why i didn't get a working android rom for months until nand came along)
On the few occasions I managed to get one to boot, i ended up having to hard reset winmo to escape from boot loop, which is probably what you will end up doing.
I have checked that and it appears ok but it still reboots if there is a problem would it help if I installed an official rom update from htc.
It wont even boot with the sd card out and soft reset doesnt help
thanks for the help
carpy47 said:
I have checked that and it appears ok but it still reboots if there is a problem would it help if I installed an official rom update from htc.
It wont even boot with the sd card out and soft reset doesnt help
thanks for the help
Click to expand...
Click to collapse
Yes install the updat as Android builds really have to have a 3.14 Windows Mobile ROM to work well. It will also improve your expeince with Win Mo as the 3.14 ROMs run considerably smoother.
do you have it done through clockwork? I had the same issue and I had to wipe data and cache, then it worked fine. You lose all your apps and have to reinstall them but it works. this worked for me if someone has a better method feel free to chime in.
kevin37 said:
do you have it done through clockwork? I had the same issue and I had to wipe data and cache, then it worked fine. You lose all your apps and have to reinstall them but it works. this worked for me if someone has a better method feel free to chime in.
Click to expand...
Click to collapse
I think the OP is using a SD card Android build and not a NAND Android ROM.
Need some advice, phone running NexusHD2-ICS-CM9-V2.7, backed up using CWM and tried to flash nexus jellyBean by changing partirion to 400mb, phone would not boot passed cyanogenMod screen, wiped system changed back to 250mb partition and restored system but now phone will not boot passed ICS screen, have tried reflashing ROM but still same problem, any thoughts please.
I believe I should have said that the phone is in ICS animation and that is it, cannot get passed this, have tried everything apart from dropping the phone in a bucket of water. Have cleaned out everything but the restore will not work.
Is there a solution?
IMO you should try a fresh installation of whatever ROM you want: wipe everything(including microSD, but before do a backup) and install it from scratch!
Good luck!
bib*oops said:
IMO you should try a fresh installation of whatever ROM you want: wipe everything(including microSD, but before do a backup) and install it from scratch!
Good luck!
Click to expand...
Click to collapse
does not seem to recognise computer or show charge now, I have made a full backup but even after a full restore with everything loading okay still cannot get past ICS animation screen.
hardav said:
does not seem to recognise computer or show charge now, I have made a full backup but even after a full restore with everything loading okay still cannot get past ICS animation screen.
Click to expand...
Click to collapse
This is getting very frustrating having checked dozens of posts cannot find a logical solution, tried every possible solution I can find. I can get into all features of system,2.08HSPL shows, CWM, MAGLDR, usb screens okay, in short everything okay bar cannot fully load any ROM past animation screen, have tried task 29 but will not load RUU just sits at HTC with bar and the has communication error. Can the the phone be bricked when all functions are available? Any suggestions would be appreciated.
Can you run SD roms past boot anim?
Have you performed a NAND check from MAGLDR? Might be bad NAND blocks.
Well guys after hours of trying to sort this out I have come to the sad conclusion the phone is stuffed which has left me depressed, I have tried:
Restore from my original backup all loads good but does not bootup
task 29 (error 262) does not seem to recognise windows sync
Tried loading from cd using nbh but tri-colour boot loader will not search for file
It is a shame as I can get into all the bootloaders which people tell me should load but no luck
Thanks for your help HD2 goodby
hardav said:
Well guys after hours of trying to sort this out I have come to the sad conclusion the phone is stuffed which has left me depressed, I have tried:
Restore from my original backup all loads good but does not bootup
task 29 (error 262) does not seem to recognise windows sync
Tried loading from cd using nbh but tri-colour boot loader will not search for file
It is a shame as I can get into all the bootloaders which people tell me should load but no luck
Thanks for your help HD2 goodby
Click to expand...
Click to collapse
you're probably using too big an SD card, is it bigger than 8gb?
If so, put the LEOIMG.NBH file on an 8gb or smaller card, and get into tricolor, it should load.
Yes I am using a 16gb card, in the meantime I have managed to restore the phone back to ics nexus v2.7, not sure how I did it but in case anybody has the same problem here goes'
I had to get back to WM 6.5 no matter which ROM I tried could not get the custom RUU to load, (probably due to the sd card size) but I noticed I had a custom RUU sitting on my desktop (not sure why there but probably from past messing about) as a last resort I loaded this and bingo within a short time windows loaded up and from there reflashed ICS and restored from backup, working perfectly what a relief. Goes to show ignorance sometimes wins. Details of the custom RUU used.
LEO CUSTOM RUU
[email protected]
File 1.1.0.0 921KB
This worked with the 16gb card, I would like to go to jelly bean but am I pushing my luck. Can you just reload CWM with a 400 partition?
Have a nice day
Cheers from kiwiland
hardav said:
Need some advice, phone running NexusHD2-ICS-CM9-V2.7, backed up using CWM and tried to flash nexus jellyBean by changing partirion to 400mb, phone would not boot passed cyanogenMod screen, wiped system changed back to 250mb partition and restored system but now phone will not boot passed ICS screen, have tried reflashing ROM but still same problem, any thoughts please.
I believe I should have said that the phone is in ICS animation and that is it, cannot get passed this, have tried everything apart from dropping the phone in a bucket of water. Have cleaned out everything but the restore will not work.
Is there a solution?
Click to expand...
Click to collapse
I had a problem with that one, so i decided to use this one:http://forum.xda-developers.com/showthread.php?t=1584160, and i think that is working much better than Nexus.
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?