So...I was trying to test a rom that ive been trying to port for a while now and with the help of a few here, I was able to find out how to pull a log from my evo while in recovery...or at least a partial log
While it didnt help me with figuring out why my rom wont install, it did raise other questions...I uploaded the last part, can anyone suggest what may be wrong?
At first glance, it looks like my internal ram has bad blocks on every partition...not sure how big some of these partitions are, or how serious this could be..
Code:
Formatting BOOT:...
Formatting CACHE:...
mtd: not erasing bad block at 0x039c0000
mtd: not erasing bad block at 0x039e0000
Formatting DATA:...
mtd: not erasing bad block at 0x10040000
mtd: not erasing bad block at 0x153a0000
mtd: not erasing bad block at 0x15520000
Formatting SYSTEM:...
mtd: not erasing bad block at 0x006e0000
mtd: not erasing bad block at 0x031a0000
mtd: not erasing bad block at 0x092a0000
Formatting BOOT:...
Formatting CACHE:...
mtd: not erasing bad block at 0x039c0000
mtd: not erasing bad block at 0x039e0000
Formatting DATA:...
mtd: not erasing bad block at 0x10040000
mtd: not erasing bad block at 0x153a0000
mtd: not erasing bad block at 0x15520000
Formatting SYSTEM:...
mtd: not erasing bad block at 0x006e0000
mtd: not erasing bad block at 0x031a0000
mtd: not erasing bad block at 0x092a0000
Formatting BOOT:...
Formatting CACHE:...
mtd: not erasing bad block at 0x039c0000
mtd: not erasing bad block at 0x039e0000
Formatting DATA:...
mtd: not erasing bad block at 0x10040000
mtd: not erasing bad block at 0x153a0000
mtd: not erasing bad block at 0x15520000
Formatting SYSTEM:...
mtd: not erasing bad block at 0x006e0000
mtd: not erasing bad block at 0x031a0000
mtd: not erasing bad block at 0x092a0000
Superwipe complete!
Related
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
Hi, I got the slide on taobao (chinese ebay)
It is with s-off, a strange froyo with "xda market" instead of google's and a custom recovery, 2.5.0.9 by nduoa.com
The recovery is in chinese, and I would like to get that in english...
I downloaded the clockworkmod update.zip, but I get error 2 while flashing from the recovery
I connected the phone via fastboot to flash the recovery.img, but I get this:
fastboot flash recovery recovery-clockwork-2.5.0.7-espresso.img
sending 'recovery' (2964 KB)... OKAY [ 0.683s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.687s
How I could change the recovery?
edit: i solved the problem, but i would like to add that rom manager did not allow to flash the recovery, as it saw newer version flashed
Tipika said:
Hi, I got the slide on taobao (chinese ebay)
It is with s-off, a strange froyo with "xda market" instead of google's and a custom recovery, 2.5.0.9 by nduoa.com
The recovery is in chinese, and I would like to get that in english...
I downloaded the clockworkmod update.zip, but I get error 2 while flashing from the recovery
I connected the phone via fastboot to flash the recovery.img, but I get this:
fastboot flash recovery recovery-clockwork-2.5.0.7-espresso.img
sending 'recovery' (2964 KB)... OKAY [ 0.683s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.687s
How I could change the recovery?
Click to expand...
Click to collapse
You could try flashing it from terminal emulator. I forgot the command though. Just search around. Try looking in the G1 forum for the Amon RA thread and there should be the commands to flash through recovery.
EDIT:
su
flash_image recovery /sdcard/recovery.img
the commands. Just change the name of the recovery to recovery.img (.img is the extension. make sure you don't make the file name recovery.img.img
yes! this time worked!
Thanks for the suggestion!
# su
# flash_image recovery recovery.img
flashing recovery from recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: successfully wrote block at b10c00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00000000
# reboot recovery
Click to expand...
Click to collapse
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
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
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 ,,