Sorry if the post has already been mentioned in another forum before.
I have an O2 XDA Orbit and i'm looking to put Fracoons Artermis rom on it http://forum.xda-developers.com/show...o♦.
I'm pretty new to flashing phones and PDA's but i'm quite experienced with a PC so shouldnt need to much help!
I was wondering what steps I should ensure to take to make sure that I dont turn it into a brick, I could do with a complete guide! I've also been told that i'll need to run the Artermus USPL program after connecting the phone. But any help and advice would be a great help. Is there anyway to backup the phone in the state it is at present if or if it doesnt go wrong?
Thankyou for the help and sorry again i've this has already been asked by someone else! Will really appreciated it!
There is no assurance that the process will not make your device a brick. But it happens only on a rare case. Many 1000s of users have upgraded without problems however a few has got their devices a brick.
There is no point taking a backup as the new ROM will give you different files. Anyway, to make sure you don't end up with a bricked device:
-Charge your device fully
-Run USPL
-The process should complete successfully!
-Upgrade ROM.
-Never disconnect your Pocket PC or turn of your PC when the upgrade is going on.
-If your stuck anywhere, don't try to do anything stupid but come here and post.
-Your device should be fine
-Even if some devices get bricked during one of the upgrade process, there is still a high chance of bringing your device back to good working condition with the help of a Factory ROM and so don't worry and go ahead.
Regards,
Carty..
that's my biggest concern so far... my XDA II SHOULD be able to run WM5 but i'm very concerned that i could turn it into a brick... the reason for this is: the XDA is the only phone i have at the moment.
If it bricks, then i'm literally screwed... i have the HimaUpgrade File that does not need an ID, and as i'm pretty fluent with English, i see no problem in using an English ROM.
The Wiki is a good place to start... but i still don't know if i REALLY need active sync to be running or not, since i cannot understand what good that would do if the device is in Bootloader Mode anyway.
Reason for this is that sometimes i read "Active Sync should be on" and sometimes i read the complete opposite... it's freaking me out.
Device should be Synchronized always for the best choice. All un-official ROMs will require this. However, factory ROMs can be flashed directly from Bootloader mode.
That is why I said when you think you screwed the process of upgrading, mostly your device will be stuck at bootloader or you can access bootloader screen and only a factory rom can go from here.
PS: I wont guarantee if the above will be true on all conditions.
Regards,
Carty..
I flash all my ROMs in bootloader mode, including my own, so it's not restricted to the official ROMs. But you need a working ROM to get it back alive.
I'd recommend using a laptop for flashing or use a USV. If some guys cut your power your computer would crash right in the middle of the flashing process - won't happen on a laptop with a working battery.
This is what I want to know. How do I flash in bootloader mode?
okay, i did it this way: first of all you need a rom to flash your device with, but i guess that should be clear
To put your device into Bootloader Mode you have to press the On/Off Button, the Directional Pad AND the reset button (mostly at the lower left corner) simultaneously.
Release the Reset Button first after about a second, and then the other two Buttons.
Your Device should say "Serial" on its Screen... by that time you can put your Device in the Cradle or connect it via a USB Datacable to your PC.
Also: connect the Cable/Cradle directly to your PC, not to a hub as that could cause Problems during the Flashing Process.
Now you can start the Flash-Program, wait approximately 30 Minutes (if you are just flashing the ROM and nothing else) and follow the Instructions that came with your ROM WORD FOR WORD as these instructions are working for most people.
I'm not saying that flashing is without Problems though... when i flashed my XDA II with WM2005 yesterday, i was not able to send/receive Textmessages (SMS), so i had to reflash the device again with the last ROM released by O2, which sucks.
I have been waiting nearly two months for HTC to get on the ball and release the official version of Windows Mobile 6.5 so I could download it and see if it's worth using as my main phone OS. But they have been lazy and have yet to come out with it. So, I got impatient and began looking into the roms that were already available and how to flash my phone to get them to work. The first step I read that I needed to do was unlock my phone. However, I forgot what the text said at the top of the page (here's the link to the program I used, if that's helpful): http://forum.ppcgeeks.com/showthread.php?t=36062. So I proceeded to use the Diamond Unlocker (as that should have been a huge tip-off to me then, but this was my first ever unlocking experience, so I had no idea what I was doing) Now, my HTC Touch Pro 2 from Verizon won't even turn on. It won't go into a bootloader screen, absolutely nothing happens when I press power button, the reset button, or a combination of any of the buttons on the device.
However, when I plug the phone into my computer, a device does pop up: Qualcomm CDMA Technologies MSM. I can't get anything more than that, though. No software drivers will install, it does try very hard to find some though.
Any help, advice, tips, tricks, random guesses, would be greatly appreciated. Thanks for all your help.
Welcome aboard
try to reflash another ROM
have a deep read here
http://forum.xda-developers.com/showthread.php?t=550540
Good luck,
Buttons don't respond.
I can't get my phone to turn on or even go into bootloader mode. So, without that, I don't understand how I can flash a new ROM onto my phone.
And hello to you as well.
I did read that link, but none of the button codes worked, and my phone isn't responding to the Hard-SPL that I started when my phone was connected. It says that it cannot find the device and I need to resync it. But I start Windows Mobile Device Center and it can't find my phone either.
However, an interesting new development is that my phone, every now and again, starts charging when connected to my computer. The light turns orange, and my computer picks it up. But it does this for a bit, and then it changes back to nothing.
If you can't access the bootloader using any of the methods detailed here, then I hate to say it, but your device is probably bricked. It's really difficult if at all possible to recover when the SPL (AKA bootloader) is severely damaged or completely destroyed. There were some tools a while back to help recover from nuked SPLs, but AFAIK they aren't compatible with the TP2, and you have to be security unlocked, which I can pretty much guarantee you aren't.
Your best bet would be to take it back to the store and play dumb, saying that it "just stopped working" in the hopes that they'll give you a new one, but there are no guarantees it'll work. Best of luck
That's what I need to know
Thanks for the information. I just needed to know what to do. I can't access the bootloader or anything even similar to it, so I am just going to get it replaced and then be much more careful in the future.
Hi everyone,
I've been reading these boards for a while now, and THINK I know howto flash my phone now. (HTC Desire GSM)
However, I've bricked a phone before (HTC Magic) and I'm not looking forward on doing so again, so I'm taking caution ;-)
I've tried to follow this how-to:
HTC_Desire_GSM:_Full_Update_Guide
(Cannot post the URL, but it's easy to find)
But I get stuck at step 2 already! It says to use the 'unrevoked method' to root my device, which looks pretty simple, but just doesn't work for me.
If I boot in HBOOT, my PC doesn't recognize my phone in any way, also my phone doesn't display 'USB PLUG' or whatever it is that's supposed to appear.
If I connect my phone while it's turned on it DOES get recognized, but when running the unrevoked software it gives me an error after comfirming I want to run the program.
Also, I cannot install the custom USB driver, Windows just tells me the driver is already up2date.
Wonder what I'm doing wrong here..
Also, nearly every single tutorial tells me to make a NANDROID backup before I do anything. But I need to flash a custom recovery before I'm able to do so right?
Any advise or answer is greatly appreciated!
Regards,
Sjakie
Why does everyone get confused on the 'HBOOT USB' bit??
If you read the instructions you'll see that seeing HBOOT USB on the screen as an option is ONLY FOR THE EVO 4G - everyone else will see it AFTER they connect the phone to the PC
Other than that it's a driver issue so go to the unrEVOked website and follow their guide
"Also, nearly every single tutorial tells me to make a NANDROID backup before I do anything. But I need to flash a custom recovery before I'm able to do so right?"
Yep.... nandroid is part of the CW/AmonRA recovery. Essential if you ever want to roll back to a stock setup.
Hi XDA, this is my first post here
I Have 1 problem with my GNex GSM-version.
I bought it used, but now when i start it, it gets stuck at "Google" logo, with a lock below.
All the guides i found, require my phone to be started, and go into USB-debuging etc.
I dont want any custom rom or something else that is custom. I just want to have a functioning phone, with stock-rom.
This is the first time my phone is connected to this computer.
I use both windows 7 and OSX Lion, so feel free to hit me with whatever guide or instructions that you have available.
SweBania said:
Hi XDA, this is my first post here
I Have 1 problem with my GNex GSM-version.
I bought it used, but now when i start it, it gets stuck at "Google" logo, with a lock below.
All the guides i found, require my phone to be started, and go into USB-debuging etc.
I dont want any custom rom or something else that is custom. I just want to have a functioning phone, with stock-rom.
This is the first time my phone is connected to this computer.
I use both windows 7 and OSX Lion, so feel free to hit me with whatever guide or instructions that you have available.
Click to expand...
Click to collapse
Here, and next time read stickies
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.
I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/
Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
Have you tried selecting the option of hardbrick on the tool?