I cannot for the life of me get my phone to update the ROM, even the one from T-mo it will start the ROM update, and get to the point where it says "this process can take up to 10 minutes" then the screen goes to the multi colors, and it says it fails, and I have to take the battery out, and restart the phone. Luckily it comes back to life.
What am I doing wrong? The phone has been CID unlocked as well.
Thanks.
Nevermind...................figured it out.........APPARENTLY it is because I was using Vista, switched to an XP system and VIOLA!
Related
Hello,
I received an XDA Mini II and am having a few issues. Firstly the person who had it 'attempted' installing Windows Mobile 6 that is available on torrent and ran the file 'EnterBL' and it went into boot loader (and goes into it nearly always). However now I have it was able to 'hard reboot' it and get the normal screen to come up and it seems to have reset it since it is taking me through all the welcome stuff.
But it goes to install all the programs and then reboots back into bootloader and cycles through all of that again.
What would be the best option. I am happy putting Windows Mobile 2003 back on but what files do I need to do this? is it possible to put WM6 (from torrent) on it with what comes in that torrent?
I am sorry if this is in the wrong section.
Thank you for any help...
UPDATE: I managed to get back into the phone by removing the battery before it did the 'customising' and then when it booted it came up okay. However when ever I reboot it it goes back into 'Serial' bootloader mode and then I have to do the setup all over again.
How can I stop this?
MattJ1989 said:
Hello,
I received an XDA Mini II and am having a few issues. Firstly the person who had it 'attempted' installing Windows Mobile 6 that is available on torrent and ran the file 'EnterBL' and it went into boot loader (and goes into it nearly always). However now I have it was able to 'hard reboot' it and get the normal screen to come up and it seems to have reset it since it is taking me through all the welcome stuff.
But it goes to install all the programs and then reboots back into bootloader and cycles through all of that again.
What would be the best option. I am happy putting Windows Mobile 2003 back on but what files do I need to do this? is it possible to put WM6 (from torrent) on it with what comes in that torrent?
I am sorry if this is in the wrong section.
Thank you for any help...
UPDATE: I managed to get back into the phone by removing the battery before it did the 'customising' and then when it booted it came up okay. However when ever I reboot it it goes back into 'Serial' bootloader mode and then I have to do the setup all over again.
How can I stop this?
Click to expand...
Click to collapse
Its a bad flash,extended rom has got corrupted,download the official carrier's rom from its official website for the make & model of your phone and reflash it.It'll srart working to default status.After that if you wish you can upgrade to any wm6 latest rom by following the correct unlocking and upgrading method as per your device.
Secondly,don't download Roms from Torrents,as they usually are corrupt or virus infected.Always get Roms from here from xda-developers forum or from the official carrier's website.
Good luck
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
So xda, here's the situation.
I'm on stock 2.1 update 1, build number 2.27.651.6. I know you can't root that, which is why I downloaded the RUU that installs 2.27.651.5 back on my phone. Right now, I have a MacBook Pro running Windows 7 under BootCamp. Whenever I run the RUU, plug my phone in, and start it up, it just hangs on that "Verifying information on your Android phone, please wait..." gray box screen the entire time, I see no progress. I just wiped my phone completely hoping it will show up as a new device now, and I also removed all the device drivers installed. I'm about to try the RUU and plugging in the phone fresh one last time, but I need your take on what the problem is. The phone is showing up fine under devices.
Basically, when running this RUU, I have the phone on charge only, on, screen timeout off, and just sitting there plugged in. Once I get this RUU to run and install the new firmware, I'm golden. I just need someone to identify the problem of why it's not getting past the verifying info on my android phone.
Help would be EXTREMELY appreciated, to the point where I'd be willing to pay something like $5 via PayPal for your time if you solve the issue.
Thanks XDA, I'm fully confident if somebody here wants to do this they could solve it in a matter of minutes, and hopefully someone will be as kind to help me out here.
You might try booting into fastboot and trying to run the RUU.
Fastboot: while holding the volume up button press the power button.
Okay, I did that, it says FASTBOOT USB in a red box, do I just leave it now and run the RUU? Or do I need to select any options?
Can you 'adb devices' on the Win7 machine?
if you can, just let it set there - mine took at least 15 minutes to verify or error.
If it errors don'u unplug or mess with the phone, let it sit there. Then restart the RUU and it should work the second time.
I can in fact abd on here, the process works up to the point where I need superuser and it doesn't appear as it's .6 build. I'm going to try running it in FASTBOOT and see what goes on, I just wish something on the phone changed so I knew it was working.
Trashing the RUU, redownloading, and fastboot all solved the problem. Now, it's currently running the RUU. In a second when the RUU finishes I will post the results and retry the adb process, and let you all know. For now, what's the best official 2.1 ROM? I know Regaw has one, and I'm also wondering how his toolbox works.
Alright here's the deal, it's been stuck in the RUU on "Rebooting Android Phone" for more than 10 minutes now, however the bar is still animated and its still working. It just won't reboot for whatever reason. On the phone is htc with a full green bar underneath.
Same problem on my Hero with 2.1-update1 , build number 3.32.405.1CL191507 relase-keys.
Is any way to get this rooted ?
daweed3003 said:
Same problem on my Hero with 2.1-update1 , build number 3.32.405.1CL191507 relase-keys.
Is any way to get this rooted ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=747598
Worked on my new Hero just fine. You can root it,then unroot it if you need to have any warrenty work done on it.You do have to do all the back ups you normally do if you switch to another rom though.
I'm not running any custom roms yet cause I haven't decided on which one to use,but my Sprint CDMA hero rooted easily with this method. Now if the developers will just come out with a 1 click method of installing one of their customs roms.....One can only wish
Mac
Yup, one click root works perfect on .6 builds.... done 2 myself
Thanks "Mac11700" It works
Hello,
I ran update on my HTC one m7 sprint and the phone now is not booting up.
It starts after I hold both volume up and power (any other combination does not start the phone at all), htc logo comes up and then the (see attached image) sync logo pops up. Waits for a few seconds and shuts down.
I have not modified the phone since buying it, no rooting, no custom ROMs etc. Clean ESN, my contract is over and I thought I would update the phone before selling it, I ran the update this morning, it downloaded the update, restarted the phone and competed the update. After update is done it shut down and since then this problems started.
Appreciate any help,
thanks in advance
I have an AT&T Note 3. I was rooted using the KINGO app, but returned my phone to stock several weeks ago and the rom shows official and the knox count is 0. I am running the stock AT&T Note 3 Android 4.3
The other day, an official AT&T android update was pushed to my phone. The update bricked my phone and now I am unsure if I can even recover what was on my phone...or at the very least get it running again. For now, I am without a phone.
When I can get the phone to power up, the phone attempts to "Recovery Booting" (this is displayed in blue letters in the top left corner with the galaxy Note 3 Logo in the middle). It tries to install this AT&T update following the recovery wording when powering it on normally and when using Volume UP/Home/Power . The update progresses towards 100% then "completes" sometimes, but then the screen goes black and the phone does not start back up. I have to remove the battery for a period of time and replace to get the phone to do anything
I can get the phone to go into download mode (Volume down/Home/power), but my phone did not have USB debugging turned on the last time I was able to access the options, so it is not recognized by kies/odin, etc!
Even though their update caused the problem, AT&T wont help me (over the phone or at the store) as my phone is over a year old...their solution is to buy a new phone and plan as they say they can't do anything to fix the phone.
ANY HELP WOULD BE GREATLY APPRECIATED!
Can you get into recovery?..if so try to factory reset then maby you will be able to power up get to developer options and turn on debug so you can use odin...other option..I have heard of some doing this..go to Bestbuy Samsung counter..ask them if they have the odin tool. If they do they may be able to get you up and running.
FIREKAT V11/S5-V1
Don't worry bro.
Just follow this post to put your phone back to stock and get it rooted again. My phone used to brick and I went through it.
Follow the steps carefully, and you'll get your phone back.
http://forum.xda-developers.com/showthread.php?t=2559715