Hello. I'm new to all this. I've searched several forums for an answer to my issue, but unfortunately I haven't been able to get to a final resolution.
What's wrong?
When I boot into ClockworkMod (2.5.0.7) Recovery, I get the below:
E:Can't find MISC:
E:Can't mount cache:recovery/command
E:Can't find MISC:
E:Can't mount cache:recovery/log
E:Can't find MISC:
Click to expand...
Click to collapse
When I try to backup the current ROM, I get this:
Backing up boot...
Error while dumping boot image!
E:Can't mount cache:recovery/log
E:Can't find MISC:
Click to expand...
Click to collapse
When I try to flash LeeDr0iD 2.3d, I get:
-Writing boot.img
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/LeeDr0iD.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
So I thought this might be because the .zip file is corrupted or something, so I went on and downloaded and flashed the latest CyanogenMod (checked the MD5 to make sure), but it gave me the same error.
What I did to my device?
I rooted using the unrevoked method. It was pretty straight forward, just installed the Android USB drivers and ran the reflash_package.exe... At the end I checked the root access by adb shell, then su, and I got the ever-so-famous #. I noticed there was an "update.zip" in the root of the SDcard after rooting the phone, but I didn't run it.
What I gathered from my search
When I was searching I read about SPrecovery, I'm guessing it's another recovery...thingi, other than CMrecovery, but I never found a .zip file for it [maybe someone can point me to it].
I also read something about a file PC36IMG.zip, and that people have fixed this error I'm getting using that file. From what I gathered, I think that file was used in the HBOOT downgrading process (from 0.8 to 0.7-something). I downloaded this file but I didn't copy it to my SDcard because I read something I'm not supposed to "apply" it when I enter HBOOT on my phone.
I have yet to use AlphaRex 1.8 to S-OFF the NAND security, but I currently don't have a blank CD to burn the alpharev image. [Question: can I just run the "fastboot flash hboot bravo_alphaspl.img" command on Windows 7, without having to boot into the Linux livecd? I already downloaded and installed the Android SDK tools =/].
My device information
HTC Desire GSM. Froyo (Android 2.2) out of the box, now running software: 2.29.405.5
And this is what appears in HBOOT:
Bravo PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Click to expand...
Click to collapse
PS: I wouldn't blame you if you hit the back button on your browser after being shocked by this long post...wait, you wouldn't be reading this if you already navigated away from the thread...ah well =/.
As you have a PVT4 Desire you need to use AmonRa instead of CWM, read the PVT4 thread in General
Use amon-ra recovery. I had the same error as you on my pv4 desire.
Sent from my HTC Desire using Tapatalk
Ok, so I'm trying to flash the Amon-Ra recovery but I get the below error:
sending 'recovery' (3936 KB)... OKAY [ 0.938s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.404s
Click to expand...
Click to collapse
I'm guessing this is because I do not have S-OFF yet (and I can't get S-OFF right now since I do not have a blank CD to burn the Linux livecd). So, I can just unroot the device, then root it again but point unrevoked to the Amon-Ra recovery instead of the CMrecovery, right?
Question about unrooting: Download the official RUU. Connect the phone to HTC Sync. Run the official RUU. That's it?
EDIT: Do I have to unroot then root again? Or is it possible to just run unrevoked on the already-rooted device but point it to the Amon-Ra recovery instead?
You need to be rooted to S-OFF, just run unrEVOked again and choose a custom recovery
EddyOS, thank you, and you as well drSTRIFE. I finally flashed my first custom ROM.
To whom it may concern, 'what did I do':
I tried running unrevoked but I kept getting the "Error: failed to get root. Is your firmware too new?", so I factory reset the device and gave it another try. Successfully flashed Amon-Ra. I tried flashing CyanogenMod and it was flashed successfully, but the splash screen kept looping. I only wiped the cache before, so now I wiped ALL userdata, and reflashed CyanogenMod. Now it works. Unfortunately though, I did not backup my original ROM, but I have the official RUU, so I guess that's enough if something goes wrong.
Thanks in advance for taking the time to read this!
Phone in Question: Sprint HTC Evo 4G (Original, not LTE)
Where I have been
-----
Phone came to me with S-OFF, but no one could tell me how exactly it was done. All I know for sure is that was NOT done with Revolutionary. The phone was hung at the white HTC screen. Thinking this was a simple flash-gone-wrong, I entered HBOOT and found it to be functional. Entering recovery also resulted at a hang at the white HTC screen though.
I was able to regain Recovery functionality by installing ClockWorkMod Recovery via HBOOT PC36IMG.zip load. I then used CWM to try and install CM7.2. I received this error:
assert failed: write_raw_image("/tmp/boot.img","boot")
Assuming I had some sort of compatibility problem (possible issue mentioned somewhere in the forums here) I upgraded the HBOOT to 2.15.0001, the Radio to 2.15.00.08.08, WiMax to 26023, PRI to 2.15 and NVRAM to 2.15. I encountered te same error.
Then on a whim I tried to flash CM6.1.2. Success! The phone booted and appeared to be functional. I thought my problems were over.
Since I am planning to give this phone to a layperson, I downloaded and installed:
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
No problems were reported during the installation. Upon rebooting though, the phone got stuck again at the white HTC screen. Thinking it was maybe just due to the first boot, I left it there overnight... It was still stuck at the white HTC screen in the morning. Upon further inspection, I found that I am also now S-ON.
Realizing I didn't have much to lose, I took it all the way. I applied this:
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed
Again, no problems whatsoever during installation. But, yet again, here I am, stuck at that cursed white HTC screen. And now a new symptom. If I leave the USB connected to my computer during bootup, it eventually cuts to a screen with a circle composed of two green arrows around a green arrow pointing down to a small phone picture. After a few more seconds, it blacks out and gives me 5 viberations and the cursed blinking green light. HBOOT still seems to work perfectly though.
What I have tried
-----
* Everything above. All procedures were followed correctly for the above activities (Caches wiped, etc).
* Various combinations of various Radio/HBOOT versions, old to new in succession. No differences experienced from any version. All are current now.
* Formatted /data, /system, and various caches. RUU 234563 reinstalled, no change.
* HBOOT USB Access - No ENG mode available, so I couldn't perform any testing on the NAND. Couldn't find any information on the task or rtask number to execute to accomplish anything useful. This interface is poorly documented and I don't want to poke around here anymore without expert guidance.
* Booting with every possible combination of power connected, data connected, and Micro SD installed or not.
* Various combinations of PC36IMG and RUU flashing. Never encountered any problems via these methods. They all still brought me back to the white HTC screen.
Where I am now
-----
HBOOT screen follows:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Regular boot leads me to be stuck at the white HTC screen.
Attempting to enter recovery takes me to the white HTC screen, then the Green Arrow circle screen, then waits at the Red Triangle exclamation mark screen. I assume this is standard recovery behavior. (Never actually went here on stock before.)
Micro SD access seems to work correctly from HBOOT, though acted flaky earlier when accessed from CWM Recovery.
Where I was thinking of going
-----
* Downgrading all the way to an engineering HBOOT and testing the NAND. Bad blocks maybe? Only problem there is I can't figure out how to check my hardware version using only HBOOT.
I could also spend hours faking my way through swapping this ESN onto one of my lines so I could get it exchanged. Seems like a huge PITA I would like to avoid.
I am proficient with Linux (though I use Windows 7) and command lines don't bother me. Suggestions?
Thanks again!
That's what I call a well written post. Excellent description. I'm sure one of these guru's can help you out, but the guy to look up is Captain Throwback. He is the master at recovering these phones. Just PM him this same thing
I imagine a lot of Evo veterans will read this and have a knee jerk reaction "why not try Amon Ra instead of CWM?"
Not that this is definitely your problem, but it was the first thing that jumped out at me.
If you have red triangle, you probably need to reinstall your recovery anyway, so see if you get better results with Amon Ra this time?
Not a big fan of all the later variants: just go with 2.3 . Tried and true.
Sent from my PC36100 using XDA
Nice thoroughly documented post
I would say, at this point, to unlock your bootloader using HTCDev, and then reinstall a custom recovery (Amon_RA-based recoveries are the best choice). If that goes successfully, I would flash the latest stock rooted ROM (mine) and see if it works. If so, you're good to go. If not, then we'll have to do some additional troubleshooting.
It seems like the bootloader flashes didn't complete successfully for some reason (even without an error message). Could be bad blocks, but it's difficult to tell at this point.
You won't be able to downgrade your bootloader with the version you're on (and it's not really necessary), but without first checking the eraseblock size, that's not a good idea anyway.
Ok. I unlocked and flashed the recommended recovery (Aman_RA 2.3) via PC36IMG.zip. No problems.
I downloaded this file:
5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip
I then booted into Recovery. Seems to work fine. Upon trying to choose the zip from sdcard, I received the following error:
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Here is my updated HBOOT Status:
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
taylorinnov said:
Ok. I unlocked and flashed the recommended recovery (Aman_RA 2.3) via PC36IMG.zip. No problems.
I downloaded this file:
5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip
I then booted into Recovery. Seems to work fine. Upon trying to choose the zip from sdcard, I received the following error:
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Here is my updated HBOOT Status:
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Click to expand...
Click to collapse
Try booting into fastboot, and applying the SD card fix from here. Then, boot back into recovery and see if the SD card will mount.
EDIT - The captain beat me to it. Never mind.
You've tried booting with your existing micro SD card and without it, but have you tried a *different* card? Have you (backed up all your data and) reformatted the existing SD card?
Instead of bad blocks in internal ram, maybe you just have issues with your external storage?
Sent from my PC36100 using XDA
I have already ruled out SD Card problems through the use of multiple cards and verifying MD5 sums of the file on the card itself, not just the downloaded file on my C Drive. I just now tried another SD Card just in case. No change.
I followed the SD Card Fix instructions. RA Recovery is now able to mount the SD Card. However, upon attempting to flash the zip file, I receive this (line-by-line accurate):
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
Install : 5.07.651.1_Supersonic_Stock_Rooted_CPT
B.zip ?
Press Power to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip
(Status 7)
Installation aborted.
taylorinnov said:
I have already ruled out SD Card problems through the use of multiple cards and verifying MD5 sums of the file on the card itself, not just the downloaded file on my C Drive. I just now tried another SD Card just in case. No change.
I followed the SD Card Fix instructions. RA Recovery is now able to mount the SD Card. However, upon attempting to flash the zip file, I receive this (line-by-line accurate):
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
Install : 5.07.651.1_Supersonic_Stock_Rooted_CPT
B.zip ?
Press Power to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That sounds like a bad download. Did you verify the md5?
If not that, it almost seems like you might have bad blocks on the boot partition, which there might not be much we can do about.
Maybe try downloading an older ROM (2.3.3 or previous) that has a smaller boot.img, and see how that works. It's also possible that your misc partition got messed up somewhere along in this process, so once you can get a ROM flashed, we should probably flash that back to the ENG version.
But if you can confirm you got a good download of my ROM, try instead flashing MikG v3.11. That's a good one to use because of the Wireless ADB, just in case there are USB issues when we get the ROM on there. That one is updated to Android 2.3.5, so it might not work. If I have to find you an older one, I will.
I pulled the SD Card and connected it to my computer. MD5 sum of the file on the SD card checks out.
I tried to flash this file:
MikG-v3.11-signed.zip
Same error as before. I took your suggestion and tried to flash the same firmware that had worked before:
update-cm-6.1.2-Supersonic-signed.zip
It worked... At least it wrote without any errors.
Upon rebooting, the white HTC screen comes up but after about 15 seconds the screen goes black and the phone vibrates 5 times. Then the green light starts flashing.
Ok... So I checked the boot.img file sizes. All the files that failed had sizes over 2.4MB. All the ones that worked were smaller. So I thought CM7.2 should work. I tried flashing it and this happened:
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/cm-7.2.0-supersonic.zip
(Status 7)
E:Can't finish MISC:
(No space left on device)
That last error repeats every 5 seconds or so as long as I remain in RA Recovery.
Couldn't find MISC partition listed under the wipe menu, so I did a wipe all and a wipe /BOOT. This made no difference.... Except...
After rebooting, this is my new HBOOT status:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
So I tried flashing one more time. No change. I rebooted again and guess what? My HBOOT status changed to S-ON!!
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Obviously I need to unlock it again... I apparently have discovered how to get an Evo back to factory locked status... By accident. Besides that, what should I do next?
taylorinnov said:
I pulled the SD Card and connected it to my computer. MD5 sum of the file on the SD card checks out.
I tried to flash this file:
MikG-v3.11-signed.zip
Same error as before. I took your suggestion and tried to flash the same firmware that had worked before:
update-cm-6.1.2-Supersonic-signed.zip
It worked... At least it wrote without any errors.
Upon rebooting, the white HTC screen comes up but after about 15 seconds the screen goes black and the phone vibrates 5 times. Then the green light starts flashing.
Ok... So I checked the boot.img file sizes. All the files that failed had sizes over 2.4MB. All the ones that worked were smaller. So I thought CM7.2 should work. I tried flashing it and this happened:
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/cm-7.2.0-supersonic.zip
(Status 7)
E:Can't finish MISC:
(No space left on device)
That last error repeats every 5 seconds or so as long as I remain in RA Recovery.
Couldn't find MISC partition listed under the wipe menu, so I did a wipe all and a wipe /BOOT. This made no difference.... Except...
After rebooting, this is my new HBOOT status:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
So I tried flashing one more time. No change. I rebooted again and guess what? My HBOOT status changed to S-ON!!
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Obviously I need to unlock it again... I apparently have discovered how to get an Evo back to factory locked status... By accident. Besides that, what should I do next?
Click to expand...
Click to collapse
Your problem is definitely your misc partition. It got messed up somehow, and is causing your bootloader to falsely report your NAND security status.
When you get it unlocked again, we'll need to update the misc partition through recovery.
EDIT: What you'll need to do is download the flash_image binary & mtd-end.img from this post, and follow the instructions there under "STEP 2~FLASHING MTD PARTITION TO ENABLE DOWNGRADE:" In recovery, in the "Mounts" section, you'll have to mount /data and /sdcard (/system couldn't hurt either). Then you can connect to your computer and run those commands from wherever you have adb.
Hopefully once that is done, your partitions should be normalized and the bootloader should read everything correctly.
It took 3 tries to get HBOOT to accept the unlock code. Finally got the HBOOT unlocked.
HBOOT now reads:
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
SD Card access was broken again. Same procedure as before fixed it though.
Entered RA Recovery.
Mounted /system, /data, and /sdcard successfully.
Attched USB cable.
Attempted first command and received the following error:
C:\Android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
taylorinnov said:
I pulled the SD Card and connected it to my computer. MD5 sum of the file on the SD card checks out.
I tried to flash this file:
MikG-v3.11-signed.zip
Same error as before. I took your suggestion and tried to flash the same firmware that had worked before:
update-cm-6.1.2-Supersonic-signed.zip
It worked... At least it wrote without any errors.
Upon rebooting, the white HTC screen comes up but after about 15 seconds the screen goes black and the phone vibrates 5 times. Then the green light starts flashing.
Ok... So I checked the boot.img file sizes. All the files that failed had sizes over 2.4MB. All the ones that worked were smaller. So I thought CM7.2 should work. I tried flashing it and this happened:
assert failed: write_raw_image("/tmp/boot.img",
"boot")
E:Error in /sdcard/cm-7.2.0-supersonic.zip
(Status 7)
E:Can't finish MISC:
(No space left on device)
That last error repeats every 5 seconds or so as long as I remain in RA Recovery.
Couldn't find MISC partition listed under the wipe menu, so I did a wipe all and a wipe /BOOT. This made no difference.... Except...
After rebooting, this is my new HBOOT status:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
So I tried flashing one more time. No change. I rebooted again and guess what? My HBOOT status changed to S-ON!!
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Obviously I need to unlock it again... I apparently have discovered how to get an Evo back to factory locked status... By accident. Besides that, what should I do next?
Click to expand...
Click to collapse
Well if u think u wouldn't have any problems try going to the htcdev website and root it that way. Correct me if I'm wrong but try that. Best of luck to you.
Sent from my PC36100 using xda premium
taylorinnov said:
It took 3 tries to get HBOOT to accept the unlock code. Finally got the HBOOT unlocked.
HBOOT now reads:
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
SD Card access was broken again. Same procedure as before fixed it though.
Entered RA Recovery.
Mounted /system, /data, and /sdcard successfully.
Attched USB cable.
Attempted first command and received the following error:
C:\Android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Um, ok HBOOT is unlocked, but now you are S-ON? Seems like that will definitely be an obstacle...
Sent from my PC36100 using XDA
taylorinnov said:
It took 3 tries to get HBOOT to accept the unlock code. Finally got the HBOOT unlocked.
HBOOT now reads:
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
SD Card access was broken again. Same procedure as before fixed it though.
Entered RA Recovery.
Mounted /system, /data, and /sdcard successfully.
Attched USB cable.
Attempted first command and received the following error:
C:\Android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
You're going to have to reflash a ROM on there first. You need a ROM that has wireless adb capability, but it has to be one with a smaller boot.img, i.e. Android 2.3.3 or older. I'll see what I can find. We're going to gave to get the phone to boot up to proceed, at this point.
I'll see what I can find.
EDIT: See if MikG v3.00 will work. Make sure you fully wipe in recovery before flashing (everything except SD card). If you can get it booted up, then we definitely have a chance.
Well, after attempting many versions of MikG's I came to realize that the main problem there is that his ROMs mess around with the MISC partition somehow. After unlocking the phone 3 more times, I tried CyanogenMod 7.0.... No dice.
Finally got CyanoGenMod 6.12 loaded and booted successfully. I confirmed USB Debugging is enabled. Also, it appears that the phone has lost its wireless and bluetooth MAC addresses.
I did a little recon for my own curiosity:
cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
Looks like the old partition scheme.
I successfully overwrote the MISC partition using ADB and mtd-eng.img as instructed and rebooted. Here is the HBOOT status immediately after the procedure:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Unlock and try to flash? Or is there something else we should do since 6.1.2 seems to be fully functional?
taylorinnov said:
Well, after attempting many versions of MikG's I came to realize that the main problem there is that his ROMs mess around with the MISC partition somehow. After unlocking the phone 3 more times, I tried CyanogenMod 7.0.... No dice.
Finally got CyanoGenMod 6.12 loaded and booted successfully. I confirmed USB Debugging is enabled. Also, it appears that the phone has lost its wireless and bluetooth MAC addresses.
I did a little recon for my own curiosity:
cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
Looks like the old partition scheme.
I successfully overwrote the MISC partition using ADB and mtd-eng.img as instructed and rebooted. Here is the HBOOT status immediately after the procedure:
*** LOCKED (OOW) ***
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224-16ab
RADIO-2.15.00.12.19
DEC 21 2011,12:50:32
Unlock and try to flash? Or is there something else we should do since 6.1.2 seems to be fully functional?
Click to expand...
Click to collapse
No need to unlock now - you're S-OFF.
Mik's ROMs don't do anything to the misc partition. There was an issue with your device (possibly NV corruption). At this point, I would downgrade to the 4.54 Gingerbread ROM, and re-root with Revolutionary. If I'm right, everything should work fine after that.
What procedure should I use for that? I would usually search for something, but I don't want to leave anything to chance here.
EDIT: Spelling errors corrected.
taylorinnov said:
What procedure should I use for that? I would usually search for something, but I don't want to leave anything to chance here.
EDIT: Spelling errors corrected.
Click to expand...
Click to collapse
First, check and see if you have wireless & bluetooth addresses now. If you do, then I think we're safe to proceed. Flashing the mtd-eng file should normalize the misc and other partitions so that they're recognized correctly by the bootloader (thus why your device now shows S-OFF, as it technically always was).
I think unrooting, and then re-rooting via Revolutionary should prevent this from happening in the future (this is speculation, but it has some basis in fact). from the "How to unroot Revolutionary" link in my signature, download the 2.15.00.11.19 recovery-flashable radio, unrevoked s-on zip, and the PC36IMG file for the 4.54 Gingerbread update (rename that to PC36IMG, place on the root of the SD card).
First, flash the radio zip in recovery (you'll need to reboot the device once to complete this process - make sure you don't pull the battery during this process!). Once it drops you back into recovery, you can flash the S-ON zip. When complete, power off, and then hold volume down while powering back on to get to the bootloader. The PC36IMG should should, and choose yes to update. The device will reboot once during the process after the bootloader downgrades, and the digital watermark should be gone. The update should continue after it re-reads the zip, and finish flashing. If it doesn't, post back and let us know. When complete, choose "Yes" to reboot. You should be back to stock. Confirm everything works, and then you can follow the procedure at revolutionary.io to unlock/root the device (if you're so inclined).
The WiFi MAC is there, but the Bluetooth MAC is 0'ed out (only the manufacturer component is present):
43:29:B0:00:00:00
Just to confirm, I have downloaded these files:
CM-EVO_Radio-2.15.00.12.19-Only
PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_ 2.15.00.0808_NV_2.15_release_220182_signed
(Radio in that last one is older than first?)
And I didn't see any reference to S-ON in your signature, so I don't have that file yet.