[Q] Numerous Questions (NAND & SD Builds & Wakeup lag) - HD2 Android Q&A, Help & Troubleshooting and Genera

Hello everyone
It's been a while since I've posted here so my apologies. I've been so excited with Android on my HD2 I haven't really gotten around to posting, Obsessive Flashing Disorder .
So I have numerous questions for y'all.
1) NAND is horrible for me. I flash MAGLDR, I've also used the Clockwork Mod, but whenever a build installs, it sticks on the white screen with the "htc" logo in green smack bang in the middle of the screen. Left it for over half an hour in school while in school, all that came up was the setup quiz, which btw was extremely unresponsive and as I pressed next it would go back to the white screen, then I'd wait 5 minutes, and I'd be presented with the next step. I've flashed a NAND ROM multiple times and tried a Clockwork Mod ROM and it's the same. However, on the Clockwork ROM I Managed to complete setup and could send a text, only because my girlfriend text me and I could pull down the "Notifications" tab. It stuck on the home screen saying "loading" constantly. SD Card was partitioned properly too...
2) Gave up with a NAND ROM and tried Windows Phone 7. Loved it! Just needed to activate it. Got skype, got the number, America and Canada only. No problems, the guy gave me the number for UK and I phoned it on my landline to be told to call between 8 and 6 Mon-To-Friday. Fine, I copy my old SD build of android to my SD Card and tell MAGLDR to boot from Android SD instead. It goes fine, loads up, then restarts and I'm told "cannot find zImage", this process just repeats and repeats. Did I do something idiotic or?
Note: The SD build is from the original way of booting WinMo then Android.
3) Wake up lag. Ugh, I get such bad wake up lag. Unfortunately it can take up to 2 minutes for my phone to unlock. Next time I'll try and grab a video camera and record it. Sometimes I also have to press the unlock key numerous times for it to actually even do anything. My phone, SD Card or? There was no lag on WP7, and my SD card is a 16Gb Class 4 card.
4) Colours on the display become inverted. Yeah, inverted, but more towards the whitish end. Again I'll try and get photo evidence next time, but I have to restart and then everything is fine. Kernel problems, or is my phone starting to give up the ghost?
Many thanks guys, I aim to start helping out a lot more!
Jake
An almost happy Android & XDA user.

J.Hendy said:
Hello everyone
It's been a while since I've posted here so my apologies. I've been so excited with Android on my HD2 I haven't really gotten around to posting, Obsessive Flashing Disorder .
So I have numerous questions for y'all.
1) NAND is horrible for me. I flash MAGLDR, I've also used the Clockwork Mod, but whenever a build installs, it sticks on the white screen with the "htc" logo in green smack bang in the middle of the screen. Left it for over half an hour in school while in school, all that came up was the setup quiz, which btw was extremely unresponsive and as I pressed next it would go back to the white screen, then I'd wait 5 minutes, and I'd be presented with the next step. I've flashed a NAND ROM multiple times and tried a Clockwork Mod ROM and it's the same. However, on the Clockwork ROM I Managed to complete setup and could send a text, only because my girlfriend text me and I could pull down the "Notifications" tab. It stuck on the home screen saying "loading" constantly. SD Card was partitioned properly too...
2) Gave up with a NAND ROM and tried Windows Phone 7. Loved it! Just needed to activate it. Got skype, got the number, America and Canada only. No problems, the guy gave me the number for UK and I phoned it on my landline to be told to call between 8 and 6 Mon-To-Friday. Fine, I copy my old SD build of android to my SD Card and tell MAGLDR to boot from Android SD instead. It goes fine, loads up, then restarts and I'm told "cannot find zImage", this process just repeats and repeats. Did I do something idiotic or?
Note: The SD build is from the original way of booting WinMo then Android.
3) Wake up lag. Ugh, I get such bad wake up lag. Unfortunately it can take up to 2 minutes for my phone to unlock. Next time I'll try and grab a video camera and record it. Sometimes I also have to press the unlock key numerous times for it to actually even do anything. My phone, SD Card or? There was no lag on WP7, and my SD card is a 16Gb Class 4 card.
4) Colours on the display become inverted. Yeah, inverted, but more towards the whitish end. Again I'll try and get photo evidence next time, but I have to restart and then everything is fine. Kernel problems, or is my phone starting to give up the ghost?
Many thanks guys, I aim to start helping out a lot more!
Jake
An almost happy Android & XDA user.
Click to expand...
Click to collapse
1) & 2)Stick with WP7
To boot from SD, make sure u set up magldr to boot from the correct directory by going into services, and choosing the folder. If it still doesn't work, then its likely you have to do the following mod:
This Thread
3) Got the same problem, 8GB Class 6
4) Got the same problem, happens randomly and so far only on sense builds for whatever reason.

Haha I would, if there was Angry Birds and associated games
3) Bizarre... I've read it's Kernel related so...
4) Yeah I only use Desire HD builds too. Looks like it is sense based.
Alright Moon2, thanks for your help!

Related

Yet another I did it, and think I have the answer thread

Guys,
I've been struggling with root for the past 4 days. I tried EVERYTHING. I want to point out a few things for people. I am pretty sure a new way will be released soon, but here is for all those who can't wait.
1) It's okay if you have 2 USB drives in recovery vs. the ADB Composite/Bootloader interface. Mine was rooted with the two drives
2) I don't think HTC Sync vs. Android drives matter, but I rooted mine with BOTH installed, but HTC drivers loading during the process
a) You DO! need the Google/Android drivers modified to Include the Incredible
3) Maybe the USB Connection timing does work for some, but when I rooted mine my phone was connected to the PC during the entire time.
4) The MicroSD card definitely matters, but from my experience you can get in using any card. I've been able to recreate it using the Sandisk 2GB card, a Maxell 4 GB card, and a non-branded 128 MB card
5) The TRICK is timing, and using the same process over and over while SLIGHTLY changing the timing. I've been able to recreate ADB in Recovery after about 2 - 3 tries to get the timing right every time using different cards. The trick is to the have the sdcard read and have the size recognized right after adb is recognized by the bootloader. If you've played around with dmesg you know what I'm talking about. The recognition HAS to be read by recovery exactly as the screen is changed from the white HTC screen to the black screen with red triangle.
So HOW do you do this?
Here is how I recreate it:
1) Plug in your phone to your computer while the phone is running normally. I had my wifi, bt OFF, though the phone was NOT in Airplane mode. SYNC and GPS were left ON. Make sure that the debugging is checked, and that the connection is set to Drive. You want to be able to access both your sdcard and phone storage on your pc.
2) Start the "adb shell" loop on your PC (the first time you do this, it'll go right into the "$" since your phone is booted normally. This checks to make sure that your drivers are working.... this will only work the 1st time)
3) pull the battery(still plugged into usb), eject your MicroSD card, put battery back in.
ps: my memory card is formatted in FAT32 1024 block. It was freshly formatted, blank with nothing on it
4) On the phone, boot into Hboot (Vol- and Pwr) and highlight recovery (hit Vol - once)
5) Ok, here is the meat: Open a clock on your PC, and watch the seconds hand. You're going to repeat steps 3 - 5 (this step) incrementing time. So at this second, your phone has recovery highlighted, it's plugged into usb, and your sd card is ejected. Now you're going to hit the power button to start recovery and you're going to insert the SD card in this manner:
You start recovery the instance the second hand lands on what ever second you want to start on. your first SD insert is going to be at 0 seconds. i.e. you're going to insert the SD card at the same time you hit the power button. Wait for ~ 10 seconds after the second pc chime (i.e. after the black triangle screen starts, this is the 2nd chime, the one that means that a connection has been recognized). If you don't get the magical error that you want. You're going to increase your insert time by 1/3 to 1/2 of a second depending on how paranoid you are. So, if you don't get the error you want:
Repeat step 3, 4.
This time on step 5.... you're going to insert your SD approx 1/3 - 1/2 of a second after you press the power button. If it fails, rinse/repeat (redo steps 3-5).
My SD cards ranged between 5.5 - 7.5 seconds.... so watching the clock, DON'T GUESS. I got that magical error inserting the SD Card into the phone anywhere between 5.5 - 7.5 seconds after I hit the PWR button to go into recovery. For best results use the same card every time. Took me about a half hour to get the timing right. Remember, I never pulled the usb cord during any of this, just the sd card. It's pulled out while battery is out, and put in sometime during recovery loading. God I hope this helps someone, and I didn't just waste my time writing this!
Thanks to everyone who got us root. If you get that error... DO NOT exit out of loop or close the command prompt. just follow the ton of instructions out there. I followed the instructions to root on some website.... maybe sodpit ?
[UPDATE]:
This is what I followed after getting the error we're all looking for. I recommend reading the whole thing though, even if you follow my method to break into recovery:
http://sodpit.com/inc/#4b
[UPDATE 2]
If you read the sodpit tutorial... there is a new payload that seems to allow you to install/delete apps from /system/app without having to be in Recovery. Trying... Nevermind, you can only backup apps w/o recovery.
[UPDATE 3]
Just to clarify:
This method isn't about popping in and out. Personally, I think that can damage your sdcard port. It's about inserting the card at the right time. When you hit the power button to go into recovery, that's 0. (0 seconds from when you hit power). If that doesn't work, you increase the time interval by 1/3 to a 1/2 second. So when you do the procedure the second time you're going to insert your sd card 1/3 to 1/2 second AFTER you hit power. If that doesn't work, redo and increase time again. Eventually, you'll either get the error you're looking for or get to about 12 seconds, at which time you have to restart at 0.
I'll be honest, it took me going from 0 to 12, 2 times before I hit the right time and got in. Took about 1 to 1 1/2 hours. My card throws the error between 7 and 8 seconds after I hit the power button. I know this now, and can recreate the error every time on 1 to 2 tries.
So far it seems like that there are two camps. The first camp gets the error somewhere between 2 to 5 seconds depending on card, and the second camp seem to be always between 7 and 8 seconds (rarely 6)..... if you read the replies of this thread, people have been listing the seconds and times. See if you can find your card in one of these replies.
Also, I recommend that you reformat your MicroSD to FAT 32, 1024 bytes and make sure that it's blank with nothing on it.
I hope this helps.
P.S.
If you've passed around 15 seconds (maybe truthfully 12 or so), you need to start back at 0. After 12 - 15 seconds I'm pretty sure you've already missed the window.
I'm not going to lie. I initially planned on bashing this post, until I read through it all. You are 100% (maybe 90%) correct as far as timing being the key. The snatch people are having is the randomness in their attempts. Putting in no effort find 'the sweet spot'.
Hope this helps a lot of people.
dreamersipaq said:
a) You DO! need the Google/Android drivers modified to Include the Incredible
Click to expand...
Click to collapse
Great post but this part is incorrect - several other guides are completed without even downloading the SDK Google drivers
But I agree on the timing. I kept not looking at the clock but counting before inserting the card and once I got in, I had done it so many times I forgot what I had done when it was all said and done. I have yet to be able to recreate it!
seanmcd72 said:
Great post but this part is incorrect - several other guides are completed without even downloading the SDK Google drivers
But I agree on the timing. I kept not looking at the clock but counting before inserting the card and once I got in, I had done it so many times I forgot what I had done when it was all said and done. I have yet to be able to recreate it!
Click to expand...
Click to collapse
And you don't need a linux driver modified specially for the Incredible. i don't believe there's anything HTC device-specific about starting an ADB session. In other words, anything the reports itself as an Android device is gonna get the same treatment from ADB and host OS w/r/t mode 0c94, or whatever it is that renders ADB Composite.
Good notes on the timing, as has been said. I had figured it @ 7-8s, no wonder I've been so hitting adb shell so spottily.
Didn't work for me... Went all the way up to 12secs.
try, try again
If it didn't work for you,
Restart at 0. The timing must be spot on since the window of opportunity is about < 1/2 a second. It's probably between 4.5 - 8.5 seconds depending on your card. But I was OCD so I started at 0 and went to 15. You probably missed it. My method took me 2 - 3 tries to get right. Patience is key!
I tried a few dozen times I'm 100% sure this method will work on my device cause i've already rooted by doing something similar. I'm just trying to get back to the recovery mode so i can remove some of this crap on the device..
The timing must have be down to the millisecond shoot maybe even the ns
dreamersipaq said:
My SD cards ranged between 5.5 - 7.5 seconds.... so watching the clock, DON'T GUESS. I got that magical error inserting the SD Card into the phone anywhere between 5.5 - 7.5 seconds after I hit the PWR button to go into recovery. For best results use the same card every time. Took me about a half hour to get the timing right.
Click to expand...
Click to collapse
Getting no love out of this method, and I wiped my DI to try it In my past attempts, I always counted from vibrate and inserted the card ~ 7s, although the first time I didn't pull the card at all, I just put the 4gig/class4 in and it worked with a loop & simple drivers in Win7.
I discovered this same method last night and found the timing to be around 7.5-7.8 seconds.
The only difference is that I can't listen for the hardware sounds as I am running osx.
Ah! It worked!! Mine worked at 2 seconds. First try. Thank you so much!
Forgot to mention.
I had my wifi, bt OFF, though the phone was NOT in Airplane mode. SYNC and GPS were left ON.
GLAD it worked.
If it got root for just one person besides me.... writing this up was worth it. CONGRATS!!!
dreamersipaq said:
If it got root for just one person besides me.... writing this up was worth it. CONGRATS!!!
Click to expand...
Click to collapse
That's what I thought about my method, until me & another guy couldn't repeat my initial result due to it being a different day than the day when I first make it work Hope yours is much more reproducable. *cry*
Good job. I will be trying this when I get home .
-------------------------------------
Werdadge
Kulaa said:
Good job. I will be trying this when I get home .
-------------------------------------
Werdadge
Click to expand...
Click to collapse
Same here. Thanks for write up. Now to find time when I get home
Rooting steps...
This is what I followed after getting the error. I recommend reading the whole thing though, even if you follow my method to break into recovery:
http://sodpit.com/inc/#4b
just as a side note, i was able to repro this two more times about 30 minutes later. this time it was around 2.5 seconds.
Great find and explanation. I NOW HAVE ROOT!!! Thanks!
Awesome
Mudavo said:
Great find and explanation. I NOW HAVE ROOT!!! Thanks!
Click to expand...
Click to collapse
Awesome

2 identical HD2s but one won't boot!

Both have 1.42 hspl, both have energy wm base rom. One will fire up the mattc 1.5 Android but when I remove the sd card and put in the other HD2 (even after a format) it just hangs at 'jumping to kernel'. Pop it back in the other HD2 again and everything is fine!!
Any explanations as I am stumped
Sent from my HTC Desire using XDA App
obvious question: radio version is the same?
Sorry. Yes both the same (12.50)
Sent from my HTC Desire using XDA App
hmmm.. tried with another SD card as well?
- ROM, RADIO, HSPL VERSION, SD CARD are ALL THE SAME?
if not, look in to that first.. Second, maybe try with another SIM card.
Tried different sd card as well. So really odd. The phone can't be broken nor the SD slot as it reads and executes other files.
Sent from my HTC Desire using XDA App
happens...
i wonder if for the hd2 that does not boot, have u tried using the exact same sd card which boot the "bootable" hd2?
if so, and the phone is still unbootable into hd2, does any1 else know of any way to extract out a log for the devs/kernel coders to take a look?
Have you tried to switch batteries between the devices?
Have tried using exact SD card. It won't boot. Have not however tried swapping batteries. Will try in 45 mins and post result!
Sent from my HTC Desire using XDA App
Hi,
You should try to make a "clean start" with Android and the second HD2 :
Delete everything on the SDcard and copy back the Android build on it.
Then, start Android normally in the second HD2.
My point is that, at first launch, each build creates some data before Android appears, MAYBE this data is in a way related to the phone it has been created with, explaining why you can't run an already "ready" build on another phone.
Thanks but youll see from original post that I even reformatted the same SD and then copied the build across. It won't boot. I assume that's what you meant.
Sent from my HTC Desire using XDA App
Yes, that's what I meant, sorry I read your post a little too quickly.
You could also try another build :
Yesterday my phone ( using android ) froze, so I restarted it and it became IMPOSSIBLE to start Android again ( white screen, black screen, before and after reformatting the SD card ) so I tried a different build and it worked.
There are times when it just won't boot. Be gentle with it in WM and it'll boot fine
try same SIM card
The one that won't boot task 29 it and put the same ROM back on it might have some stuff hanging around in root of phone that's causing issues
when i had jumping to kernel issue it was because i forgot to rename the .txt file in android folder to startup.txt. maybe a silly question but did you do that?
Super Octet said:
Hi,
You should try to make a "clean start" with Android and the second HD2 :
Delete everything on the SDcard and copy back the Android build on it.
Then, start Android normally in the second HD2.
My point is that, at first launch, each build creates some data before Android appears, MAYBE this data is in a way related to the phone it has been created with, explaining why you can't run an already "ready" build on another phone.
Click to expand...
Click to collapse
+1 on that. Up to now I wasn't able to copy my fully configured and working FroyoStone installation from SD card to HDD and back without getting problems sooner or later (although no hardware was changed at all!). I had boot problems when doing so several times. So you might consider to set up Android on the faulty device from scratch (without copying anything from the other device). I'd also start with a freshly formatted SD card...
HTH!
Dont quote me on this, but I believe the HD2 has two variants (again, dont quote me) they use 2 different types of LCD (I believe one has a blueish tint to it). So maybe your problem lies with the screen? When I bought this phone for my moms birthday, i noticed that the screen was a little blue no matter how I tweaked the settings, but mine, if anything has a little yellow to it. Again not sure, remember reading about the 2 variants of LCD causing certain problems with certain builds. Hope it all works out for you
There are definitely different hardware suppliers.
I bought my HD2 in the UK in november last year. 1 month ago I bought a second one for my father. The display of the new device had far better colors and contrast. Besides having some other minor problems with the device, that was the last straw, so I sent it to HTC for repairs. They replaced the screen and the colors are now even with my fathers HD2, however the color of the LCD panel itself, when switched off, is different. So still different LCD screens ...
But its not only the screen: My fathers HD2 boots up twice as fast as mine; same radio, same hspl, same rom, same configuration. From the moment the red letters on the bottom appear, it only takes ~15 seconds for that HD2 to get past the splashscreens. Mine takes ~30 seconds. However, the odd thing is, in all benchmarks I ran, both got the same results ...
Am working on this now. It has a fresh Energy Rom on it (build 23128 - same as working one). I am now in process of reformatting the SD card (the long slow version). I will then copy mattc 1.5 on to card and try again. Saw a post about renaming .txt to startup.txt. It's already called that and works on the other phone anyway.
If this doesnt work then I'll do a Task 29 although I've no clue what that actually is
You should do a Task 29 before putting the Energy rom on. Task 29 wipes the phone.
http://forum.xda-developers.com/showthread.php?t=644781

[Fix]boot freeze-up

hello folks,
I have seen some threads talking about some WM device freezing in bootup, and stick in the 1st screen when it says "stick together", I had the same problem, and I did contacted HTC for support, it seems they dont have a solution for that problem but to send the phone to them, whicj gonna take around 10 or 15 days to get back -if the warranty still in effect- and they probably gonna charge you something more than the shipping back fees, cause you flashed your device.
I was Planing to send my phone this monday, but i though lets try something and see what gonna happen, so what i did is :
1 - take you SIM card and your SD card, (don't connect your phone to your PC)
2 - While holding the VolUp press the Power button, you will see a screen with your device information
3 - Now connect your device to you PC, and use one of the Wm costume ROM, don't worry about the guide line, and about the winSync instruction, cause it do work without windows Sync
4 - follow the instruction on the costume ROM application, and just ignore the WmSync one.
your phone will reboot, and you probably gonna see your device radio and room information.
I just did the sameting to fix my device, I don't know if just got lucky
But I do have a problem now, I cant install android on my device, and when i try to lunch CLRCAD, it does not start, even when i lunch haret, the device reboot, if someone know a fix to that problem, so may help me.
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
bravo261 said:
dude, out of your three posts, two have been new threads that are strictly related to user-problems in a developmental sub-forum, which just isn't cool.
its like someone walking into your work meeting and asking about the lunch schedule (not the best analogy, but you get the point)
if you're really stuck in something, a hard reset always restores things nicely
Click to expand...
Click to collapse
i'm just trying to stay in the dark, waiting for the moment to say something useful, by the way hard reset does not work all the time
The only time a hard reset does not work is if there is something wrong with your phone or somehow you corrupted your ROM. In that case going into Bootloader and upping a new ROM does the trick. A Task29 will really fix things well.
As far as "launching" CLRCAD...it does nothing ANYWAY! You just tap it and that is it...it merely sets up the phone for Android to have sound, nothing more...no prompts, no hour glass nothing. (A SEARCH or reading the first post would have told you this.)
If you get resets in Haret then Android did not load correctly. Merely delete your data.img and start over. If that does not work then you likely corrupted your Android build....format your SD card and reload Android from scratch.
I personally have backed up my working daily build on a weekly basis so in case my Android gets hosed, I merely have to copy my entire backup (which is just a copy of my SD card on my computer) back to the SD card after a format (but have yet to really have a need for this except months ago).

[Q] help for a nooby please

hey guys, trying to do my first upgrade to get win 7 on my very slow buggy hd2, i am following the guide
http://forum.xda-developers.com/showthread.php?t=971478
and i am stuck on the first step, i have checked the SPL version, 1.42.00 i think it was, had phone on, connected up the usb, then downloaded and ran HSPL2_Run from my pc, and it fails on the usb connect, stuck on what to do
Edit>
I have now rebooted phone, held down the volume key and entered the coloured screen, connected usb, says usb at the bottom of the screen, and re ran the program, still no joy
Edit>
I have now tried using a different file on the link HSPL and i get past the USB connect and get a large loading bar but then get another error
Unknown error
Error Code: 0x80003
Always reference this code for eventual requests
Link used and used both downloads at bottom of page>
http://forum.xda-developers.com/showthread.php?t=611433
Boot screen shows
PB81100 SS-BC
SPL-1.42.0000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x50
USB
Can't speak for anyone else's guides but this YouTube tutorial with links to the needed files was the one I used and it works perfectly...
hey mate, thanks for the reply, i spent a good hour trying all different things and doing them over and over and all of a sudden it worked, done all the things on the video, and now i have win 7 on my phone, i am sooo pleased with my self lol
only thing is my sd card is 2gig so will need to buy a bigger one when i got some cash, when i get a bigger one can i just use the pc, drag and drop the files on the card to the pc and then back onto the bigger card, or is all the needed files saved on the phone?
cheers
I think I did read something somewhere about someone using a partition tool to do something similar, but for all practical purposes you should assume a hard reset is required to allow WP7 to format and set up the card properly.
Donketdaz said:
hey mate, thanks for the reply, i spent a good hour trying all different things and doing them over and over and all of a sudden it worked, done all the things on the video, and now i have win 7 on my phone, i am sooo pleased with my self lol
only thing is my sd card is 2gig so will need to buy a bigger one when i got some cash, when i get a bigger one can i just use the pc, drag and drop the files on the card to the pc and then back onto the bigger card, or is all the needed files saved on the phone?
cheers
Click to expand...
Click to collapse
Ywe drag and drop will work with photos, videos, documents, and etc. Or you can use copy and past too.
As far as you putting the new card in I think all you have to do is put the SD card in your HD2 and then boot it up. I think it will be like the first time you booted because WP7 uses the SD card for it's internal memory so it will have to format your new card with RAID and place what info it has to place on it. Atleast that is what I have read, I do not use WP7.
T-Macgnolia said:
Ywe drag and drop will work with photos, videos, documents, and etc. Or you can use copy and past too.
Click to expand...
Click to collapse
It won't. There is no real file explorer for WP7 and I don't believe the filesystem is readable outside of WP7.
I believe you will also need to reflash WP7 to have the card work effectively in the OS.
Donketdaz said:
only thing is my sd card is 2gig so will need to buy a bigger one when i got some cash, when i get a bigger one can i just use the pc, drag and drop the files on the card to the pc and then back onto the bigger card, or is all the needed files saved on the phone?
cheers
Click to expand...
Click to collapse
Check this thread...
Gustopher said:
It won't. There is no real file explorer for WP7 and I don't believe the filesystem is readable outside of WP7.
I believe you will also need to reflash WP7 to have the card work effectively in the OS.
Click to expand...
Click to collapse
You may be right, but I thought that you could still use drag and drop or copy and paste if you use the little USB mass storage hack for WP7. But I have never used WP7 on my HD2 so what do I know.
T-Macgnolia said:
You may be right, but I thought that you could still use drag and drop or copy and paste if you use the little USB mass storage hack for WP7. But I have never used WP7 on my HD2 so what do I know.
Click to expand...
Click to collapse
You can to some degree, but it's not as simple as good old WM and WP7 will most likely rename all of the files to add further complication. For a noob, best advice is to expect a hard reset
Well after a day at work, last night i was loving the win 7 on my phone, now i hate it....
Got so many issues with it,
1. Randomly reboots itself every 10 mins or so everytime, all day long and when it does it goes into a sort of safe mode with none of my settings saved, themes etc, and i have to reboot 2+ times to get my settings back, then it goes again after 10mins
2. when screen is locked for a few mins, when i go to unlock it and activate screen nothing happens, then the phone reboots.
3. During all these problems, every other time all the apps stop working, dont load up, reset fixes, not always.
4. Battery dies within an hour os so from full
Used [LEO_70]BOYPPC-SHIFTPDA-HD2_WP7_V4_(13.Apr) rom
any others anyone can cecommend or maybe even Android?
Also how do i install a new Rom, do i just run in on the 5th option of Magldr or do i need to delete it off first then install the new one? cheers
Donketdaz said:
Well after a day at work, last night i was loving the win 7 on my phone, now i hate it....
Got so many issues with it,
1. Randomly reboots itself every 10 mins or so everytime, all day long and when it does it goes into a sort of safe mode with none of my settings saved, themes etc, and i have to reboot 2+ times to get my settings back, then it goes again after 10mins
2. when screen is locked for a few mins, when i go to unlock it and activate screen nothing happens, then the phone reboots.
3. During all these problems, every other time all the apps stop working, dont load up, reset fixes, not always.
4. Battery dies within an hour os so from full
Used [LEO_70]BOYPPC-SHIFTPDA-HD2_WP7_V4_(13.Apr) rom
any others anyone can cecommend or maybe even Android?
Also how do i install a new Rom, do i just run in on the 5th option of Magldr or do i need to delete it off first then install the new one? cheers
Click to expand...
Click to collapse
Your issue most likely isn't WP7 - which is normally quite stable - but an incompatible SD card. I'd suggest you bring forward your plans to get a bigger card - have a read around (there are several threads) to see which flavours of card are more likely to work well - and prepare to re-flash.
You should note that the selection of a suitable SD card does not seem to be an exact science - there is evidence to suggest that almost identical cards may have varying levels of success.
So the bad news is you are facing expense; the good news is that your experience of WP7 isn't representative.

[Q] Focus Bricked During Mango Update

Hey guys,
I was updating my Focus earlier today. It went through the process fine until the last restart step of the last update(there were 2 or 3 in total), when it seemed to just hang on the Samsung loading screen. I left it for about 10-15 minutes, but I had to go catch a bus so I had to unplug the phone and go.
Bad choice on my part. Reading online after the fact informed me the Focus could hang for a while on the Samsung loading screen at that step of the update. And now, since I interrupted the update process, its been bricked for me. Whenever I turn it on, it just stays on the Samsung loading screen. It will not be recognized by Zune, or my computer at all. I can get it to go to the hard reset screen, but nothing seems to come of that (I let it go for intervals of 15 minutes, as a few sites advised, to 45, with nothing occuring).
I'm trying leaving it on the Samsung focus screen for a few hours. If that fails, I'll leave it on overnight in the hard reset download mode. I dont have much hope though, and I'm wondering if any of you guys know anything I could try to fix it.
Thanks a bunch.
I'm pretty sure you can get to download mode and flash one of the original focus roms. Just head over to the Focus development section and reflash the rom. Make sure you flash the right one in regard to rev version. The thread will give you all the directions you need.
Figured i'd include the link just to make it a little easier. I hate bricking phones haha. Good Luck
http://forum.xda-developers.com/showthread.php?t=1131022
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
neibl said:
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
Click to expand...
Click to collapse
The low storage issue from adding a mSD card would have been resolved with a simple HARD RESET.
Right now you need a backup of your phone, made before the flashing with Omnia bits. Someone else had this issue, read here. This is also for the specific thread you opened here.
*noob*
My phone froze during the update for 7.5... Zune gave me an error code but wasn't able to write it down. The phone froze on the left arrow and the red "do not remove" symbol for about 30 mins before i unplugged it and turned it off. When i turned on the phone it stayed on the samsung logo and did nothing. i did a hard reset i still got the same thing. Then i took out the memory card and reset, still the same stuck on samsung. Then i called samsung and the walked me through a reset/reformat By pulling out the sim card then Holding down the camera/volume/power at the same time until it vibrates then after just hold down the camera and volume down, click the windows icon to reformat, still stuck on the Samsung logo!!!!
I'm going to try this flash thing... We will see how it goes i'm a noob
Interesting Samsung gave you that advice.
First thing you should have done is connect it with Zune started and it should have continued the process as long as there wasn't a fatal error.
Flashing UCJK2 should work in your case (assuming you have 1.3 hardware).
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
neibl said:
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
Click to expand...
Click to collapse
As I said and the per the info in the thread above, you need to restore from backup. Most likely flashing any rom is not working.
If you tinkered by flashing unknown bits and without taking precautionary measures, don't blame others.
I was not blaming anyone, the only reason i started flashing was because a microsd card ruined the phone down to 15 mb and no matter what method i used to reset the phone it would not leave that state, i tried for month before resorting to drastic flashes.
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
neibl said:
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
Click to expand...
Click to collapse
Zune creates backups of stages before the last update. If you're on Mango, you should have a NoDo backup in Zune. There is no way you can restore without Zune. You can check by going in Zune (when phone connected), Phone (near Marketplace/Social - top left), then "Settings", then "Update". Now Zune should tell you you have a Restore. Good luck!

Categories

Resources