Develop Bugs

O2 XDA Orbit - Upgrading/Backup/Flashing

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.

[Q] My Defy really is Dead!

Ok my phone is DEAD! Yes I have have read alot of posts and used my mate "Google" but they are all saying or pointing to the threads saying flash with the .sdf files with RSD which I have done Infact i've tried most .sdf images. I work in ICT so I know to do research first before posting but I'm not getting anywhere. I just hope i'm being a numpty and missed something.
I have an unbranded UK one original version 2.21 and I had successfully flashed with the available roms on here and others by following the steps, but last night I flashed it with PAYS rom and it was fine but then it all went pear shaped when I tried to flash it back to the original 2.21 rom via RSD Lite but it's just a black screen and when plugged in I get a charge light. The Battery is fully charged.
I can not enter Bootloader and when I enter system recovery it does not respond when pressing the bottom right hand corner.
RSD does see the phone connected and it runs through the process of flashing it but then it goes to re-boot and nothing. RSD says it's finished, it does not go through the process of re-booting the phone.
In RSD on the phone properties this is all I get:-
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e600209036f60010000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: a9e56c008df05759e72a50cf0e4ce907eea6c0de
Please, please somebody help me!

Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App

chaihg said:
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Hi,
I have tried flashing the 2.51.sbf even tho it has the problems with downgrading. It does the same as the the other 5 or 6 i've tried.
Thanks for your suggestion tho.

I'm no expert, but is this where the touch all four corners going clockwise starting is upper left comes in?
Thought I read something about doing that when touching the single corner didn't work to get into recovery.
I could have misremembered (don't even know if it was in this forum), but it couldn't be that hard to try and it doesn't sound like you have much to lose.
maybe search four corners or something to figure out more.

Maybe time for factory repair

ABC_Universal said:
Maybe time for factory repair
Click to expand...
Click to collapse
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!

In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.

it_ferret said:
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
Click to expand...
Click to collapse
Did you send it away?. You sounded like a bright guy we could have solved this together though . Ultimate thing you could have done was to flash one of the leaked original UK froyo sbf. If you still have not sent it then do this. BTW what is the bootloader version when you put it on vol up+ power ?

Have the same problem
The phone is briked. Only RSD is working but wathever sbf I flash, at the end i get the same black screen. I can not do anything. Please could someone help us?
If someone send their phone to service, please share the result.
The only sbf file that start the phone is
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF.sbf
but is working hard, the market is not working, everything i want to download is say that is downloading and nothing hapends.
Could someone tell me how to go back to original software?
The recovery mode is not working, when the android face is showing, i tap all corners and all display area but nothing hapend.

For recovery mode, you should click both vol up and vol down simultaneously. They changed the recovery button function with the new bootloader.

it_ferret said:
Ok my phone is DEAD! .....
Please, please somebody help me!
Click to expand...
Click to collapse
I had the same problem, but with luck i had read this thread :
http://forum.xda-developers.com/showthread.php?t=940647&highlight=market
and i succeded to restore my "brick" into one working phone.
Try it.
Many thanks to : adlx.xda

Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
Umm... I just bricked mine (HK version 2.51.0) as well.
I used ClockWorkMod Recovery for Defy to install 3.4.2 131-003 Orange Deblur. When the recovery finished, I found a tiny yellow line "E: can't open /cache/recovery/command" on the bottom of screen. Not sure if it was there before the recovery. When rebooted the phone showed the M logo for a minute, turned black for a second, and showed the M back again in loop.
Then I installed RSDlite 4.8 to flash the sbf directly. RSDlite finished and showed a "Pass". The phone was turned off automatically but couldn't be turned on again. The battery was fully charged before I started the update so it's not likely the battery charge problem.

Weudel said:
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
Click to expand...
Click to collapse
I did post in the thread.

Heys guys thanks for all the comments, but last night it came alive.
I used 3 different computers and in the end the last pc I used was a WIN 7 x64 machine and it managed to complete the .sbf install which was a 34.4 version then i applied my previously nand backup to 34.4.4 US T-Mobile version which is Jboogie3 rom.
Keep up the good work guys and gals. This is an excellent community to be in.

ABC_Universal said:
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
I tried this install but that aswell failed.
Click to expand...
Click to collapse

im a newbie at this and did pays flash but had probs couldnt dial out ect ect so went to recovery but could not get bottom left hand screen work so after half day of trying i clicked both bottom -vol and top+ vol and restart button on top and it worked!!! but thought id give the rom one last go so did factory reboot flashed cash ect restarted signed into blur and now works great pleased i stuck with it...cheers pays

[Q] Unsuccessful Root of Desire HD. Please Help, Newbie Here.

Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)

I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA

dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.

benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.

same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?

hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"

Installing standard ROM or rooting does not work

A couple of years ago i asked this forum to help me install the unbranded version of the ROM from HTC for my Desire. I created the goldcard, installed the ROM as instructed and everything worked fine. I was happy for 2 years.
Fast forward, my phone fell a couple of weeks back and now when the screen turns off the power button fails to turn it back on. The buttons at the bottom of the phone do illuminate when I press the power button, but the screen does not turn on. Even receiving a call or an alarm ringing does not turn the screen on. The only solution so far has been to remove the battery and reboot the phone: this solution works, but not on every occasion.
I have tried to reset it back to factory settings, but that has not helped. I have tried to install the ROM from scratch (I want to confirm if this is a software problem), but every time I try to install it I get the following error:
ERROR [131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
The interesting thing is that the ROM is the one I used 2 years ago and, while I generated a new goldcard, I checked and can confirm that the old goldcard and the new goldcard are identical.
I have then tried rooting the phone using SuperOneClick, Unlock Root and Unrevoked - so as to try installing another ROM instead -, but all of them have failed. It seems that they all try to install some drivers and fail.
I have exhausted all my ideas on what to do.
Any ideas on how to save this phone? I really like my Desire and I do not want to buy a new one right now.
Thanks in advance for your help and support.

I think you are being a little optimistic about it being a software fault. The fact the issue developed after being dropped points to it being hardware (Proximity Sensor possibly).
I wouldn't be screwing around with roms/rooting at all.

Any ideas how to fix it?

Sorry no, the PS being at fault is just a guess as being a logical thing to start with. If you aren't comfortable in dismantling the phone and looking for obvious damage then you'd be best to consult a technician.

Ok, then let's edit the question slightly:
1. Can somebdy help root the device?
2. Can somebody help me understand why the old ROM is failing to install?

[Q] Please help :(

Ok i'll start at the beginning. i've had a HTC One X since launch i've never bothered with the Custom roms before but i had some time on my hands today and thought i would give it a go. and everything went wrong.
i downloaded a called "One X All-in-one kit v2.2" and followed the instructions. i managed to get my bootloader unlocked with out much bother and then i decided to install a custom rom. so i loaded up Clockwork Mod Recovery and downloaded CleanROM 5.1 and put it on the phones memory.
I made a mistake at this point. using the tool i flashed the kernel from the Zip file before flashed the Rom or even made a backup!!!!. Now no matter what i do my phone will turn on and just sit at the "HTC Quietly Brilliant" screen, if i turn the phone off it just turns back on and site at that screen.
i have tried re-following the steps and it is still exactly the same. Do any of you guys have any solutions to this or have i wrecked my phone?
Any help will be gratefully taken as i don't have the cash to throw down for a new phone!!
Thanks,
Matt

First of all you need to clarify which version of HTC One you have, currently you are posting on international version forum ( tegra3 ), and im pretty sure that CleanRom was made only for Snapdragon S4 version ( was it this topic ?). Also check if you are able to boot into bootloader ( power down your phone by holding power button for ~~15 sec, press power while holding volume down button ).

MatPease said:
Ok i'll start at the beginning. i've had a HTC One X since launch i've never bothered with the Custom roms before but i had some time on my hands today and thought i would give it a go. and everything went wrong.
i downloaded a called "One X All-in-one kit v2.2" and followed the instructions. i managed to get my bootloader unlocked with out much bother and then i decided to install a custom rom. so i loaded up Clockwork Mod Recovery and downloaded CleanROM 5.1 and put it on the phones memory.
I made a mistake at this point. using the tool i flashed the kernel from the Zip file before flashed the Rom or even made a backup!!!!. Now no matter what i do my phone will turn on and just sit at the "HTC Quietly Brilliant" screen, if i turn the phone off it just turns back on and site at that screen.
i have tried re-following the steps and it is still exactly the same. Do any of you guys have any solutions to this or have i wrecked my phone?
Any help will be gratefully taken as i don't have the cash to throw down for a new phone!!
Thanks,
Matt
Click to expand...
Click to collapse
Just a few questions that'll help us help you:
1. If you boot into the bootloader (power and volume down when powering on) What is the first word on the second line of text?
2. On the third line it should give you the HBOOT, could you give us the version number please?
3. Lastly could you please link the ROM you have flashed.
At the moment it seems to be able to be recovered so you can stop worrying

What Rom you're flashing and what hboot you have?
Sent from my HTC One X (sorry for my English)

Thanks all for your help!! I've gotten my phone back to stock and it's now working thanks to this thread (http://forum.xda-developers.com/showthread.php?t=1859714) and i've made a back up so i can now start playing again without worrying. going to give cm10 a go and see if i can get that working. thanks again all
Matt