Related
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, Im having an issue updating to the latest update for the captivate. I bought mine two weeks ago and its fine and dandy however i'd like the suppose semi gps fix. I installed all the samsung drivers and using Kies Mini. When i connect my phone in Kies mode it shows up how its supposed to tells me there an update (my phone shows JF6 and so does the kies program), but when i try to update it tells me update failed please remove battery and reboot phone then try again. I've tried that, i did have my phone rooted and lagfix installed however i made sure to remove both of those before i even started the update. I also removed the market place fix to see if that was the issue and it wasn't. Does anybody have any clue as to why it keeps failing?
Thank you!
edit: by the way on my phones screen it just says mtp application and with the usb plug picture and it says initializing under it.
skippyg said:
Hello, Im having an issue updating to the latest update for the captivate. I bought mine two weeks ago and its fine and dandy however i'd like the suppose semi gps fix. I installed all the samsung drivers and using Kies Mini. When i connect my phone in Kies mode it shows up how its supposed to tells me there an update (my phone shows JF6 and so does the kies program), but when i try to update it tells me update failed please remove battery and reboot phone then try again. I've tried that, i did have my phone rooted and lagfix installed however i made sure to remove both of those before i even started the update. I also removed the market place fix to see if that was the issue and it wasn't. Does anybody have any clue as to why it keeps failing?
Thank you!
edit: by the way on my phones screen it just says mtp application and with the usb plug picture and it says initializing under it.
Click to expand...
Click to collapse
Go to Settings > Applications > USB Settings > Ask on connection
Also Go to Applications > Development > Enable USB Debugging
That will get rid of your MTP screen. MTP is for syncing with Windows Media Player or something along those lines.
And finally, don't bother with this update. It DOES NOT fix the GPS like AT&T and Samsung have told us. It's a waste of your time.
Ok, If like me you should have your Mango update official through Zune and you haven't there's a way to force Zune to update your Windows Phone 7 Device.
This worked for me on my HD7.
What you need to do
1) Connect your Windows Phone to Zune.
2) Make sure your defiantly connected via USB.
3) Navigate to the settings and then to phone settings.
4)Click the update button. (Zune will now check for updates for your phone)
5) After a COUPLE of SECONDS when Zune still says "checking for update", quickly disconnect from your internet connection. Disconnect whilst Zune is still checking for updates.
6) You will either get a connection error, or you will get a message saying there is an update available for your device. If may take a few times of connecting and disconnecting but you will get the update available message.
7)After receiving the Update Available message, connect back to your internet and click update.
8) Complete the update process. This could take up too 50mins depending on your internet connection.
9) BOOOM. Hello MANGO! =)
One thing to add that I've been reading from folks; if you have 7008, 7390, or 7392, you will get OS upgrade 7403 1st, then it rolls into 7720.68..which is Mango...DO NOT DISCONNECT YOUR PHONE AFTER 7403!!!
Do this works if I'm in RTM 7720? I red somewhere that the oficial update have ICS, it's true?
well, i've tried this trick, but, it doesn't work......
and, i only got an error
it worked
Dude... It worked.... awesome... installing right now. tried first it showed update then in the middle it closed cause Zune was updating at the same time. So had to complete zune update first, then tried again and again and again... 6th try it showed again and now in the middle of update 7.5..
thanks mate
Works a treat - but what about firmware
Hey, just updated it and Mango is working a treat. However a few of the live tiles are broken now...most notably the music and video tile for Zune.
Do you know off hand if forcing also installs firmware? I'm on HTC HD7
Cheers!
Can someone who has tried this please tell me if it actually gives the carrier update or the general unlocked phone one?
Oww Yeah!! Thanks! Work!! :O
HTC HD7 in Brazil
Took 3 attempts, but it worked on that 3rd try...
Awesome...
Wow....its working fine for me.....but it took somuch time to get the update available message....i have tried more than 30times.....finally i got the update...
my mobile.................... network unlocked T-Mobile US version....using in Tata docomo network in INDIA....
Thanks for the idea....
cheers
Sweet ! Worked for me on the first try Thanks a lot !
For those who haven't completed this yet, keep trying, it will work, as for network branded im not all to sure. But im sure if there is an carrier update version available,. you will also get it via this method. I cant imagine you will install the unlocked version if you have carrier locked device.
If this method worked for you, please thank me by pressing the thanks button =)
aghhh!!!
DanielT3235 said:
For those who haven't completed this yet, keep trying, it will work, as for network branded im not all to sure. But im sure if there is an carrier update version available,. you will also get it via this method. I cant imagine you will install the unlocked version if you have carrier locked device.
If this method worked for you, please thank me by pressing the thanks button =)
Click to expand...
Click to collapse
I'll never buy a Mac again.
Having a complete and utter ***** of a time waiting for, then updating Parallels, then extending my virtual disk, etc., etc., just to install this update.
Update: Some time later, after extending the virtual disk (Parallels), re-installing a bunch of stuff, etc., etc., the update is downloading. All of this is to say that you can follow the forced update procedure using a Mac and Parallels. I probably could have done it using W7Phone Connector and the wireless toggle method, but I live the hard way.
[Just make sure your SIM card is actually IN the phone ... and] [C]lick "Yes" when Parallels asks you whether you'd like to continue the USB device settings in your virtual machine; i.e., when your phone automatically restarts, Parallels won't automatically assign its USB connection to your virtual machine unless you've already set it up to automatically assign the connection to XP/7.
Just tried this for my HTC Trophy I had the and it worked after 10 times...
Just to let you know... Patience is a must I noticed... I found it play up when I moved to different usb port that worked straight away
Worked perfectly for me first time..
Waited about a second before flicking off the wireless on my laptop.
Had to do it 4 times to update Zune and then get all WP7 updates but it was all pretty painless..
WP7 Mango on Telstra in Australia working nicely.. Haven't found anything that doesn't work so far!
Worked perfectly for me... Telstra HD7. Thanks for the tip!!
Holy Crap!
Worked first time for me too. On telstra HD7
Been trying this for my dad's HD7S, but I'm not getting either connection error nor update available. Just get phone is up to date (NoDo). Any suggestions?
I'll keep trying in the meantime.
Hi
I have a HD7 with software version 7.0(7032) i disconnect and all i get is the checking for updates and then get told my phone is up to date (current software 7.0(7032) I do not get any error, am i doing something wrong?
I have an HD7S, When I did this i was on 7390. It updated me to 7392??? Shoulnd't it have gone to 7403 1st, then Mango??? Do i need to rollback and try again???
Ok.
first off, Hii!! this is my first ever time writing on XDA.
Any way, i know this is not a new issue.. but my ATIV S is rebooting every 5 seconds after the 8.1 update via preview for developers.....
i did a lot of digging before writing here and found this thread : http://forum.xda-developers.com/showthread.php?t=2718023
I followed the instructions and flashed the GT-I8750_DXBMJ1_R_signed ROM along side the GT-I8750_VJALL3_P csc (this is the only combination that gave me some results.
After flashing, my phone did manage to boot up finally but with a twist. Trying to restart the phone sends me back to the boot loop forcing me to reflash everything again.
i tried the tip from the thread to download the preview for developers app and try to update the phone again (claiming it will resolve the issue) but as soon as the phone goes to reboot before the update the boot loop comes back and we're back to squire one.... so i'm kinda stuck.... is there any kind of FIX i can try to help me sad situation? :crying::crying::crying::crying:
I've had a lot of issues with my Ativ S as well.
Your rebooting issue seems recognizable, maybe this thread will help : https://social.msdn.microsoft.com/F...ime-after-wp-81-update?forum=winphoneosissues
Anyway, I'm on the latest Developer Preview update, my Firmware version is : 2424.14.9.3
It seems the phone is much more stable now, however i'm only using this phone for development, there is no sim card present anymore.
Switched to a new Nokia for my main device.
Advice : If you want a decent Windows Phone, buy a Nokia, not a Samsung or HTC.
Thank you for the reply!
i did some more digging and found that flashing the GDR2 FW 2424 actually helps. after that the is a need to update the phone to the official GDR3 update in the phone updater in settings. i am trying that as we speak and really hope it will work
BTW this ATIV S is my backup phone and not my daily driver (i use a Galaxy s4) i just wanna fix it up to use as my work phone. my trust in windows phone is gone for now XD
EDIT: OK, so i followed the thread and applied the instructions...
at first, i flashed the GDR2 official ROM with the instructed csc file and everything booted up well. at this point they say that if the phone is to be restarted the boot loop will come back (it did when i tested it)
afterwards, i installed the preview for developers app and started updating to the official GDR3 update as instructed. it finished up and booted up well. the next step was to update to 8.1... i did and at first it worked well but as soon as i disconnected the USB cable, the loop returned again. (if i connect the USB cable back it's booting up normally)
BTW i tried doing it all from scratch and noticed that in every step of the process, if i disconnect the cable the loop come's back and disappears as soon as i plug it back in... anyone has any idea what to do next?
I've been running NG3 rooted for 2 years w/ T-Mobile. Due to recent changes on the Tmobile network (they dropped 1900 and switched to b12 = 700a which the 870 can't acquire) I've been forced to move to ATT. When their SIM was loaded I could get 4gLTE so data and text worked, but couldn't make or receive any calls. The signal would drop entirely - no 4gLTE or bars.
I decided I'd try to reload the full NE4. The PC wouldn't recognize the phone via USB (new and old drivers tried). I tried 3 PC's same issue device unknown regardless of Samsung driver age. My wife has the same phone and same issue. Since USB wasn't being recognized (nor on my wifes 870) ODIN was out so I booted and tried loading via the SD card. Well I apparently bricked my phone attempting this. It won't boot beyond the SAMSUNG logo (thereabouts). I can't access the phone via USB. I can however use the bootloader (?) (v-up + pwer + home) and attempt to load from the SD card. I have several stock roms but I receive errors attempting to load these - " footer wrong" and " signature verification failure". I tried Downloading them again but md5 is good on them all
I'm not having fun... . Does anyone know how I can get my phone to load from the boot screen without these errors? I need to get my wife's 870 working too. Her phone can text but no calls (same scenario only I didn't mess here's up just yet). The boot screen on my phone still shows last up date NG3.
I 'm not concerned about being rooted or which version I land on anymore, I'd just to get it working again. Any help is much appreciated - thank you
for what it's worth talking to myself ... the USB cable I've been using for years and has always worked. Tried it on my wife's phone and didn't work but still thinking it's the PC unable to load the USB drivers. Bought 2 new phones. Tried the cable on the new phone - no drivers. Tried the new USB cable that came with the new phone and it worked fine. Used the new USB cable on my soft bricked phone and drivers loaded. I was able to use Odin to upload the OF3 revision to my G870 successfully. Now I'm looking for a way to root it.
any links please?
You can search for "wonder share mobile go" and find how to root with it.
OMG - That was amazing. It rebooted a few times but "SUCCESS". I can't believe all the steps we go through on XDA (and I love XDA) to root a phone but this was 1 click = done. The OF3 can easily be rooted with this software. I uninstalled it (cause I don't trust it) but the root remained and I'm rocking and fat happy.... AND the KNOX = 0
ON THE OTHER HAND - the software soft bricked my Moto G5 Plus. It's not all it's cracked up to be. I contacted the company and it really seemed to me the person responding couldn't read English. Their responses were incoherent and didn't approach the subject at all. Like they were from another country. Yeah.. one of those companies who rely on foreigners to handle their tech support. I'll never use that software again - not trust worthy and the techs are clueless
Thank you very much