Develop Bugs

Downgrading from 2.2 to 2.1 fails, partition failure [[BRICKED !!]]

Hi,
Could anyone please help unbrick myphone !
I have a problem downgrading from 2.2 to 2.1 using the tool "Downgrade Utility" 2.3b on a European HTC Desire phone (unlocked).
Here is exactly what I did so far :
* Install HTC Sync -> "_HTC Legend_HTCSync.exe"
* Settings / Applications / Development / Enable USB debugging on phone
* Settings / Connection to PC / Default connection type : Charge only
* Settings / Connection to PC / Ask me : Disable
o Downloaded downgrade 2.3b
o Execute : win-down.bat
+ It says it will take a minute, but 10 minutes is more realistic.
# Select FASTBOOT on phone. The Phone loads PB99IMG.ZIP -> This is the 2.1 f/w with HBOOT 0.83
# Do you want to start update : Press volume up
# HBOOT 0.83 installed
# PB99DIAG.zip
# No image!
# PB99DIAG.nbh
# No image!
# Loading PB99IMG.ZIP
* Everything else updates ok *except* Radio_V2 - Fail-PU
* Partition update fail!
* Update fail!
* Do you want to reboot the device, volume up = yes
* Phone stays on the HTC logo
* Disconnect USB cable, pull out battery for 2 minutes and power on phone.
* I will hear 7/8 vibrates
* Phone stays with the HTC logo and does nothing.
When I power on the phone, there is one long vibrate and 7 shorter vibrates.
I don't know what else to try right now... I have gone back into the HBOOT and re-started the update which fails again on the Radio_V2 section.
How can I escape this endless cycle to fix it.
This worked once previously for me, and I went from 2.2 to 2.1 which worked flawlessly. For various reasons I decided to go back to 2.2, so this is the 2nd time that I would like to downgrade to 2.1 so that I can ultimately root it.
The phone has never been rooted successfully.
Note : I think I should of posted to "Desire General", my apology's.

I don't know the answer to your downgrade problem, but to root you don't need to downgrade anymore. Just use unrevoked.

Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.

By placing the SD card in a friends phone, we removed PB99IMG.zip and replaced this with a valid RUU and booted up using the new RUU, which fixed it.
However after running unrevoked 3.2.1 several times on the MAC, we could not root the phone.
It stalled on the "waiting for bootloader" message. I don't understand why some people have immediate success with unrevoked and others
have no luck whatsoever. Any suggestions, is there another method to root 2.2 ?

dazdaz said:
By placing the SD card in a friends phone, we removed PB99IMG.zip and replaced this with a valid RUU and booted up using the new RUU, which fixed it.
However after running unrevoked 3.2.1 several times on the MAC, we could not root the phone.
It stalled on the "waiting for bootloader" message. I don't understand why some people have immediate success with unrevoked and others
have no luck whatsoever. Any suggestions, is there another method to root 2.2 ?
Click to expand...
Click to collapse
dude i was having tons of problems in rooting but than i used the thread ... turkeys guide to root and while i was doing so i joined their IRC channel and asked for help .... the moderators were kind enough to establish remote access to my pc and do all the settings for me and helped me out in the whole process and my phone was rooted.. i suggest you do the same

dazdaz said:
By placing the SD card in a friends phone, we removed PB99IMG.zip and replaced this with a valid RUU and booted up using the new RUU, which fixed it.
However after running unrevoked 3.2.1 several times on the MAC, we could not root the phone.
It stalled on the "waiting for bootloader" message. I don't understand why some people have immediate success with unrevoked and others
have no luck whatsoever. Any suggestions, is there another method to root 2.2 ?
Click to expand...
Click to collapse
Use Windows...

Does adb work on a 64-bit VISTA included in other-shi??-DesireRoot

unrEVOked works fine in W7 x64 - I've done it numerous times with no issues

EddyOS said:
unrEVOked works fine in W7 x64 - I've done it numerous times with no issues
Click to expand...
Click to collapse
Out of curisoity, did you run unrevoked as administrator on W7 ?
That is about the only thing that i've not tried and I can't see why that would make a difference.

[Q] Help with unlocking bootloader

I've finally decided to unlock my bootloader. My Arc is sim-free, I've followed SE/XDA instructions to the letter yet when I check if the phone is connected for unlocking(can't remember the exact command, but blue light is on, command window opened in correct folder etc.)I get an error message along the lines of adbwin.dll is not present, I'm not at home just now and if required I'll post the exact messages. All sdk packs have been downloaded, installed and updated. I'm using windows7, 64 bit(x86) and no luck... The phone is rooted on .145, I think I read somewhere that to unlock the bootloader the phone should not be rooted so if this is definitely the reason then I'd be happy to use SEUS to update then proceed, but I'm not sure this is the cause. Before somebody posts a 'let me google that for you', I have tried various threads(obv xda, android soul, android forum, SE)with no success. I'm probably missing something really obvious or straightforward, and if so please feel free to point this out

Have a look at first post in this thread - you have to copy two files

Ahhh. Thanks
Sent from my LT15i

Desire (Virgin Mobile) potentially bricked, please help!

Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.

deolol said:
Hey there, I think I've bricked my device and naively thinking it would be pain-free and careless as it was in my DHD, it was an utter brain melter with it's little brother device and I've spent the past 2 days frantically trying to fix it, probably making it worse.
Here's the problem:
- USB responds on PC with notification, doesn't seem mounted
- Unable to access any form of recovery/bootloader
- Attempted VM RUU but at the end it has a 101: File read error, even though the file is intact.
- Attempted latest RUU amongst various others, with an image write error.
- Loaded fasboot via PC & flashed downgrade from http://alpharev.nl/ - although flasher said it was 'successful' the RUU mentions 2.0.x-something and fails again
- Now a black screen that doesn't even show 4 corner error.
So yeah, I'm so lost right now. Any help at all is appreciated, since it's so messed up might as well try experimental methods of recovering this. Thanks a lot.
Click to expand...
Click to collapse
Option A: Create a goldcard (you can use your DHD, or if you alread yahve one use that goldcard) and flash the latest WWE RUU (Link on my guide)
Option B: Less safe. Use the 2.3.3 RUU (Link on my guide)

[Q] How can i root a defy?

Hi Everyone!
I have been given a Defy MB525 with Froyo installed
Apparently O2 and Motoblur don't like each other 'cos I can't locate the phone or do anything else using "My Motoblur" as Motoblur wants Microsoft Explorer and I have Linux on my computer.
I want to manipulate files and basically get full access to my phone using a nice friendly Linux GUI, but apparently I need to root the bloody thing.
I know this question has been asked before. The thread below is an example.
http://http://forum.xda-developers.com/showthread.php?p=9456771
The thread mentions Z4root as an answer.. It doesn't exist anymore.
It then talks about adb and pushing files into the phone.
In the most part this worked
The bit that didn't was "adb push exploit.bin /data/local/tmp/exploit.bin"
It doesn't exist on the zip file attached..
It did however have "rageagainsthecage-arm5.bin" instead
I changed the name to exploit bin in the vain hope that it might be the one and continued the instructions.
It obviously wasn't the one as :
a) it wouldn't come out of the program and
b) I got the $ sign instead of the # sign, which meant I was not root.
This was confirmed when I did the next step in the instructions and got permission denied.
After a switch off and on again (the phone) I cannot even get get back into the phone using adb. It just comes up "error: device not found" even though Linux is showing it as a directory.
So! What next?
Yours in anticipation
Fitchie

I use this http://forum.xda-developers.com/showthread.php?t=1044765 and work very fine with froyo

You can look at the stickies at the top of the forum before posting, see "Defy all-in-one beginner's guide", understand that it probably refers to you and most likely contains the answers to any beginner questions you'd want to ask, open it, read it in case you're serious or just look for "rooting" word if you're not.
Well, you already missed the first part and posted the thread, but you could still do the rest.
Given that you're running Linux on your PC, I'm a bit puzzled - I'd think that the described above is expected from someone with unorthodox OS that is likely used to searching for various guides.

Using "SuperOneClick" is the best way to do Root on your Defy MB525.

I've done this. .. hope it'll help
http://forum.xda-developers.com/showthread.php?t=1551472

Z1C won't start - advice please

I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.

Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?

I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.

devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..

Oh my goodness......... It is pantomime season after all

Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.