Develop Bugs

ADB driver

Hi guys.
I have a question..
I want to get s-off but do i need ADB driver to do it ? If yes. Can you show me how to install ADB .
THANKS

Yes, you need two "types" of drivers to ensure there are no potential driver problems:
- Download HTC Sync, Install it and Uninstall it after that. We just need the drivers.
- Hacked HBoot Drivers. Guide Here

I had followed exactly what you said but while doing it, it just said :
Acquiring root (method 1)...
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors ( If any):-
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
Press (almost) any key to exit.
What wrong with that ?
I got HBOOT 1.01.001

I have seen a few members get that, but have no idea what it implies. You might want to ask the Alpharev X team themselves:
http://webchat.freenode.net/?channels=alpharevx

[Q] alpharev x issue - mtd: not writing bad block at 0x00020000

So a few of us wildfire users are trying to use Alpharev X to get S-off and are met with the following frustrating error:
Acquiring root (method 1)...
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press (almost) any key to exit.
This was pasted from another post, I'm sure the error I get is 0x00020000 rather than 0x00040000, but either way the issue is bad NAND and alpharev team are aware of this. My question is how many other users are experiencing this and has anyone had any success with getting past this? I dont think its very high on their to do list, but I'm sure if enough people are experiencing this they will take it more seriously.
I'm on a Telstra branded Wildfire (A3335) with HBoot 1.01.0002, so I wonder if its specific to this model or is it completely random (and simply bad luck)?
I've done a downgrade using the downgrade guide at http://forum.xda-developers.com/showthread.php?t=1132028
This got me HBoot 1.01.0001, but the problem persisted. It must have taken me 20 attempts to actually get this guide to work and I think the reason for this was also because of the bad NAND. during step 1 (gaining temp root) it would complain about not being able to write to the flash (sorry don’t have any exact error messages). The fact that it eventually worked makes me wonder if continuously running Alpharev X (and rebooting phone after every fail) would eventually work..
Would be good to hear suggestions and please reply if you are also getting this error or have managed to find a work around.

have you solved this issue yet ?? i got same problem but there is no way to solve it so far !

I have an HTC Evo 4g and I tried to root it using the Revolutionary tool and I got the same error message. My phone was upgraded to gingerbread OTA without my permission. Has there been a fix yet?

I am encountering the same problem and it's quite annoying
Tried both unrevoked and revolutionary methods without any success. Unrevoked comes back with: "Error: failed to get root. Is your firmware too new?" whilst revolutionary comes back with below:
C:\revolutionary-0.4pre4>revolutionary.exe runas administrator
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: HTC Wildfire (buzz-1.01.0001, Android: 2.2.1, ROM version: 2.
22.405.1)
This is a beta release and requires a beta release key.
Enter beta key [ serial: <###SERIAL HERE###> ]: ##KEY HERE##
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
Press (almost) any key to exit.
In order to get revolutionary to work, I also ended up downgrading my hboot to 1.01.0001 from 1.01.0002.
In case this helps, my phone is on the three network in the UK. Looking forward to a solution to this issue since quite a lot of people seem to be encountering it.

never root??...
Desire(A8181) Hboot 1.02.0001, firm 2.3.3 stock. Have a 100% same problem. NO root, no s-off.... i Killed my brain. Nothing helpe, absolute.
From Russia, sory for my english)

I have the same problem with Wildfire bought in Poland. :/
but there is also an official way to unlock bootloader.
has sb tried (with bad block issue) unlock bootloader via HTCdev?

maskim said:
I have the same problem with Wildfire bought in Poland. :/
but there is also an official way to unlock bootloader.
has sb tried (with bad block issue) unlock bootloader via HTCdev?
Click to expand...
Click to collapse
I don't think you will have any problems unlocking via HTCDev. I also think that there is a thread regarding this somewhere in the q&a section forum.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5

needs help with these error messages with the 2.3.3 rooting process .......

Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00060000
Press (almost) any key to exit.
CAM SOMEONE HELP ME WITH THIS ERROR ? I'VE FOLLOWED THE TUTORIAL TP THE LETTER AND STILL END UP SHORT ... E-MAIL ME AT [email protected]. THANKS ALOT

are you in usb debugging mode? are you in charge only mode? did you uninstall htc sync, but reinstall the drivers?

yes I did all of that .....

Code:
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre3 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PC36100 (supersonic-2.16.0001, Android: 2.3.3, ROM version: 4
.24.651.1)
This is a beta release and requires a beta release key.
Please visit: http://revolutionary.io for more information.
Enter beta key [ serial: ********** ]: *************
Beta key accepted - thank you for participating!
Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00060000
Press (almost) any key to exit.
Any Ideas?

@ ww3 i GET THE SAME THING, ONLY i HAVE AN evo 4G

PC36100 is a evo 4g as well

Anyone ? seems like i had bad blocks.

I'm having problems on my EVO..I'm running the latest MIUI Rom 1.8.26...I've done full wipe & all that stuff, I've done all the proper steps...But everytime i click on something i get "The process android.process.acore has stopped unexpectedly. Please try again."

ShowTimeGraham said:
I'm having problems on my EVO..I'm running the latest MIUI Rom 1.8.26...I've done full wipe & all that stuff, I've done all the proper steps...But everytime i click on something i get "The process android.process.acore has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
Redownload & reflash the rom. Be sure to wipe boot, system, data, cache, dalvik, sd-ext, and .android_secure. What recovery are you running?
And next time you may want to start your own thread or search a little further. This has nothing to do with the OP other than the fact that you're getting an error message.
Sent from my PC36100 using Tapatalk

[Q] Problem while trying to s-off, please help

Hi Everyone,
I just rooted my Htc Desire by using unrevoked and have superuser permissions in my app menu. Now before I would like to install a rom which I have never done before I believe I would need to turn the s-off. When I try to do that through revolutionary 0.4pre4 I am getting errors as below. I did install Htc drivers, restart my laptop & phone but still the same error keep coming up. I also downloaded the Hboot tool called alpharev but not sure what to do with it. Please guide me and I would really appreciate it.
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors (if any):-
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000

S-Off Instructions
The AlphaRev HBOOT tool (assuming you got it from here?) from what I saw on their site is an .iso file, which you have to burn the image to a CD, then follow the instructions for the link above. My gf got a USCC Desire, so using Unrevoked/AlphaRev's Revolutionary, I was able to S-OFF and then root all at once. Pretty easy.
I have not tried the method posted in this link. It's an explanation of what to do with the .iso file.

I'm assuming you used the AlphaRevX tool? If you didn't then do so. Also, did you read the FAQ on the main page with the AlphaRevX download links? If not then I suggest you do as you've likely not installed the Android drivers that are included in the FAQ page.

guptavar said:
mtd: not writing bad block at 0x00080000
Click to expand...
Click to collapse
This seems say all...Bad (damaged) block sectors in ur hboot internal partition..not good..ask in the revolutionary IRC channel http://webchat.freenode.net/?channels=revolutionary

s-off problem
hello, i am trying to s-off my desire with revolutionary but i get the error msg :
caroline failed, but had this to say: an err occured when writing partition
errors:
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
i tried revoked too and alpharev with no luck.
i updated with the official RUU to 2.3 and the 1.02 Hboot but still the same errors.
i read it might be hardware issue.
i actually want to use the stock rom but just want to use a script/prog to increase the internal memory.
any solution to s-off? or any script that needs no root to work?
thanx!

akoutsakas said:
hello, i am trying to s-off my desire with revolutionary but i get the error msg :
caroline failed, but had this to say: an err occured when writing partition
errors:
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00020000
i tried revoked too and alpharev with no luck.
i updated with the official RUU to 2.3 and the 1.02 Hboot but still the same errors.
i read it might be hardware issue.
i actually want to use the stock rom but just want to use a script/prog to increase the internal memory.
any solution to s-off? or any script that needs no root to work?
thanx!
Click to expand...
Click to collapse
Write down all you have in bootloader.

guptavar said:
Hi Everyone,
I just rooted my Htc Desire by using unrevoked and have superuser permissions in my app menu. Now before I would like to install a rom which I have never done before I believe I would need to turn the s-off. When I try to do that through revolutionary 0.4pre4 I am getting errors as below. I did install Htc drivers, restart my laptop & phone but still the same error keep coming up. I also downloaded the Hboot tool called alpharev but not sure what to do with it. Please guide me and I would really appreciate it.
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partition.
Errors (if any):-
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x00080000
Click to expand...
Click to collapse
Hi, you don't need to be s-off to flash a rom. You can just install it from clockworkmod recovery (which will have been installed during unrevoked rooting process).
Sent from my HTC Desire using xda app-developers app

bad block problem by revolutionary ?is there way to avoid writing in bad block ?

Have problem
im trying to S-OFF & Recovery by Revolutionary
and it always give me
Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while writing the partit
ion.
Errors (if any):-
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00040000
Press (almost) any key to exit.
Click to expand...
Click to collapse
and my device Info. is
(bravo-1.02.0001, Android: 2.3.3, ROM version: 3.14.405.1)
and as shown in RootWiki
my device is officially supported
Revolutionary currently supports the following Android phones and HBOOT versions:
HTC Desire (bravo) 0.93.0001, 1.02.0001
Click to expand...
Click to collapse
im just asking is there way to avoid writing in bad sector ??
i contact with revolutionary (IRC)
and they told me your device is defective and i must get a new one

Ask in revolutionary irc channel.
SwiftKeyed from Oxygen with Transparent XDA App

I have EXACTLY the same problem
mtd: not writing bad block at 0x00040000
with desire with HTC's "official" gingerbread.
Can somebody give us any advice - is there any other way to write a different rom/S-OFF?
help

GreenToad said:
I have EXACTLY the same problem
mtd: not writing bad block at 0x00040000
with desire with HTC's "official" gingerbread.
Can somebody give us any advice - is there any other way to write a different rom/S-OFF?
help
Click to expand...
Click to collapse
go to htc care center and tell them i have internal memory problem and some apps goes away and brick, they should replace ur mother board with new one
thats what hapeend with me ,,