Develop Bugs

[Q] [HELP] Options following failed attempted root (stock)

Starting from a new stock Desire HD, I have attempted gaining root access using Visionary (r14). Temproot worked, but permroot apparently failed. My device rebooted, but didn't come back up - I get the phone-with-red-triangle screen.
If I pull the battery and then boot into the bootloader, using the Image CRC menu option I can see that my system partition has been modified (but all other partitions are unchanged):
<redacted>
Do I have any options available to me now, or am I screwed?
My phone is a stock Desire HD A9191 (stock HBOOT S-ON, stock recovery, stock radio S-ON):
Code:
Branded (Vodafone Australia)
<redacted>
Is there magic process that can be done to re-flash the faulty system partition?
Any help would be hugely appreciated. Sorry to make this my first post to the forums, but I'm well and truely stuck... hopefully not permanently, but I have that sinking feeling

What happens when on the red triangle screen, you HOLD the volume up, and then press power button? I think this will take you to stock recovery. Reboot if you have the option, or Wipe data & factory reset.
Sent from my Desire HD using XDA App

Thanks UpInTheAir.
At the red-triangle screen I press vol-up and power, and it displays the Android system recovery screen. It shows the options:
1 Reboot system now
2 Apply sdcard:update.zip
3 Wipe data/factory reset
4 Wipe cache partition
I've tried (3) and (4) and then rebooted, but it does not help - the phone continues to boot into the red-triangle screen.
It looks to me like the system partition was incorrectly modified / corrupted by visionary, and somehow flashing it back to a known-good condition seems like the only way forward...
Is it possible to use option (2) to flash a new rom if I package it up and put it on the SD card somehow? My phone is branded vodafone-australia, and they have not published any RUU update files yet. I gather that using a WWE rom update from HTC will not be possible?

Try DL think stock 1.32 RUU
Rename to PD98IMG.zip (not .zip.zip, do not extract)
Put PD98IMG.zip onto sdcard
HOLD volume down, and power on -> this will boot into Bootloader
Start update and follow the prompts
I hope this helps, but as always, please don't hold me responsible if anything goes pear-shaped.

Thanks again. Downloading now, and will update this post when I've tried it out. Cheers.

You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)

a33a said:
You'll need to make a Goldcard to flash this ROM (if your phone is branded).
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also for more help follow this thread http://forum.xda-developers.com/showthread.php?t=1035027 (follow the bit about flashing the PD98IMG.zip)
Click to expand...
Click to collapse
Won't the Gold Card be useless if the system partition is already corrupted?
This was to be done before using visionary?

Thanks a33a.
My phone doesn't boot (I can only get to the bootloader menu, or the red-triangle screen). I tried talking to it with ADB, but it says "device offline".
The instructions for making a gold-card appear to require you using adb to talk to the phone to get it to tell you some long id number... I don't think it's possible for me to do this.
Is there a work around or some other way?

Did the PD98IMG.zip work?

Did u update the HTC drivers for the usb before. The adb needs the latest drivers for Windows to communicate.
If u can't create a goldcard than u should try and borrow 1 from a friend that already rooted his dhd. It might work that way. If not than u have to bring it to HTC and have it reflash.

When you tried ADB;
1. Make sure your phone is in FASTBOOT USB (HOLD volume down + power on -> Bootloader)
2. Connect to PC
3. CMD (Command Prompt) cd\............android\android-sdk-windows\tools\ (or whewrever the adb.exe & fastboot.exe is)
4. Type fastboot devices
5. You should get pyour device serial number HT............
But as I said, if the partition is screwed up, it is pointless with the goldcard?........
Edit: Memory coming back......You only need the Gold Card if you flash a stock ROM and require OTA updates? Without this you can't get the updates. So not having it shouldn't stop the flash?

Unfortunately the PD98IMG.zip did not work.
As suspected, the bootloader found it, loaded it, checked it, then displayed:
Code:
CID incorrect!
Update Fail!
Press <POWER> to reboot.
I haven't tried creating the gold card yet. I'm not holding out much hope, because with the device not booting into the OS, I don't think you can get adb to connect.
When the phone was working, I was able to use ADB to install apps and run commands from the shell, so I'm pretty sure the USB drivers are OK (I've installed the latest HTC Sync, which included the usb drivers and adb.exe).
I don't know anyone with another Desire HD, let alone anyone who has created a gold card... maybe someone on here with one can zip up the files and send them to me?

Did you try through fastboot? Sorry I don't have one as wasn't carrier branded. I never had intention to keep the stock, so never bothered. I will keep an eye open for ideas though.
I suppose you would get the same if you rename it to update.zip & try flash through the recovery / update. My guess is yes, but doesn't hurt to try?
Sent from my Desire HD using XDA App

I'm just trying the fastboot method now (downloading and installing the SDK as I type).
I'll let you know how it goes.
Thanks for sticking around to help out.

If no good, look on the bright side. There will be no evidence on your phone about the attempted root, still s-on etc. With the system partition corrupt, you could send it back and claim ignorance, not sure what happened. I would think you would have a very goof chance of repair (htc flash) or replacement.
Well hope you have some luck first though.
Edit: meant s-on
Sent from my Desire HD using XDA App

Yeah, I was considering that -- all partitions except system are unmodified and stock, and both S-flags are S-ON. Using the bootloader to wipe cache and data, should erase any evidence that I was attempting to root the phone.
Fingers crossed they will replace / repair under warranty -- if it comes to that!

Okay, as per the earlier post, I've put the phone into FASTBOOT USB mode, and used the Android SDK fastboot.exe program, which gave me back a 12 digit number beginning with "HTxxxxxxxxxx".
However, the linked gold-card creation guide says to run "adb shell cat /sys/... " which does not work -- adb returns "error: device not found". Presumably this is because you can't talk to the phone when it's in the bootloader.
What should I do with the "HTxxxxxxxxxx" value? The goldcard guide doesn't mention it as far as I can tell...

That's your device serial number, meaning you can ay least talk with it via fastboot. Try substituting 'fastboot' instead of 'adb'. Your connected in Fastboot, ADB command is when your phone is powered up and connected in charge only, usb debugging enabled.
Sent from my Desire HD using XDA App

Okay, I've tried a couple more things:
Renaming PD98IMG.zip to update.zip and selecting "Apply sdcard:update.zip" from the recovery menu. This failed, displaying "E:Can't open /cache/recovery/command ---- invalid operation ----"
Then I tried issuing ADB commands using fastboot.exe, but fastboot doesn't support the shell parameter, so "fastboot shell cat /sys/...." doesn't work.

It does look like fastboot can be used to flash various parts of the device though... I wonder if this is worth looking into a bit more?
ie: fastboot's usage output says:
Code:
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
I tried "fastboot update update.zip" giving it the renamed PD98IMG.zip file, but it complained of:
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '....garbage characters...'
Does anyone know how and what to feed to fastboot to get to force-flash the system partition?
UPDATE: yeah I thought this might have been too easy... This link suggests that you can't flash a production device with fastboot unless you already have ENG S-OFF (which I don't).
http://wiki.cyanogenmod.com/index.php?title=Fastboot

[Q] poss brick? can boot CWM, but can't flash or fastboot

I've been fighting this for hours over the last couple of days....
I rooted my phone (ebay-purchased T-mobile G2) a few months ago with the Cyanogenmod guide (http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting), got Clockworkmod on using Rommanager and (almost) everything was good.
Recently, the entire phone crashed and seemed to get stuck in a boot loop. I booted into CWM recovery (v3.0.2.4). CWM gave me these errors every single time:
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to just reflash CM7 that I loaded onto the SD card via windows, always wiping data and cache first. The install would start, and then abort with "E:Error in /sdcard/update.zip" and "(Status 1)". Eventually one of the versions of CM6 started to actually install with the progress bar, but then would abort with "assert failed: write_raw_image" and "(Status 7)". Googling pointed to CWM possibly being the problem, saying updating to 3.0.2.5 would fix it. I haven't found a download for that, and because I'm stuck with boot loops, I can't get to Rommanager.
I tried using fastboot to flash the same version of CWM, but it comes up with "Failed (remote: not allowed)". Googling hints that installing stock ROM (PC10IMG?) would fix it, but I can't get that to flash or fastboot on.
I don't have a NAND backup, but I do have a CWM backup that I can't fully restore from because it always says "Error while formatting /system!". Haven't found a fix for that.
I am able to connect with ADB, but I've tried checking for the eMMC serial to see if I have a culprit chip (http://forum.xda-developers.com/showthread.php?t=1081243), and it doesn't return a value.
This thread OP is actually almost the exact same thing as I've been through except the last part about loading with hboot, which I can't get to work. And I've tried with the sd card mounted and unmounted.
I'm stumped, as most of the solutions are just "reflash ROM" or "reflash recovery" and I can't get either to work. At this point, I don't think I care if I end up rooted/customROM or stock. Any help is appreciated a hundred fold.
S-Off
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.0226_M
eMMC-boot

Hey,
Sorry, I have had the same exact problem. Spent a week+ working non stop, following every tutorial on the forums to try and fix it. I've had zero luck. good thing it was in warranty for me, I just sent it in and got a new one. just enjoying my non-rooted G2 now. I hope there is a fix for this somewhere, It has been happening quite a bit.

That's a bit discouraging. I wish I had the knowledge of the topic to even understand what the actual problem is, unless it's multiple smaller problems that I'm dealing with. It doesn't seem like a full-brick situation, but I guess it is.
Re: warranty - was it through HTC or the carrier? And how did you convince them to accept it? They usually say that rooting voids warranty, eh?

Tmobile told me rooting voids Htc 1 year warrenty but still have 129.
deductable through asurion for 5. a month.
I called Asurion to verify.
Sent from my HTC G2 using XDA Premium App

just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot

Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer

http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
Once you get in CWM you can format system, data, cache and restore from nandroid.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

killerbee12345 said:
just curious but why doesn't fastboot work? otherwise you could try to recover via fastboot:
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot reboot
Click to expand...
Click to collapse
"fastboot erase boot"
"Failed (remote: not allowed)"
Nipqer said:
Here is a thread about the error
Its most probably a hardware issue, so there's nothing you can do about it except return it.
Also, fastboot probably doesn't work cause you don't have eng hboot?
-Nipqer
Click to expand...
Click to collapse
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
onelikeseabass said:
http://forum.cyanogenmod.com/topic/20898-easy-way-to-flash-eng-hboot-new-80416-radio-and-cwm-3024/
That PC10IMG worked great for me. All you need is S-OFF.
Once you get eng hboot, use fastboot to flash the recovery.img from your last working nandroid backup. Might want to do 'fastboot erase recovery' just before 'fastboot flash recovery recovery.img' just to give a clean slate.
....
Click to expand...
Click to collapse
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?

tatsuha said:
"fastboot erase boot"
"Failed (remote: not allowed)"
starting to seem more and more like it's hardware. i don't have an Eng HBOOT, but I am S-OFF. Cyanogen wiki says that should be enough, but I'm still stuck, so maybe.
tried that PC10IMG.zip and it actually recognized it as soon as I got into HBOOT. but then I came up with the Partition Update Fail message.
Any tips on convincing HTC to warranty it anyway?
Click to expand...
Click to collapse
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!

onelikeseabass said:
This may be a shot in the dark, but have you tried reformatting your SD card? Back it up, format, and just put that PC10IMG.zip I linked earlier on it. Maybe it's a problem reading from the source that causes the write to fail.
HTC Vision (G2) - CM7 B100 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
Click to expand...
Click to collapse
Hadn't gotten a chance to do much during these last few days, but I finally sat down with the G2 again. I had already tried formatting, but it was a quick format, I'm fairly certain.
I tried with full reformats on both the SD cards I have (the 8GB Sandisk that came with the phone and an older 2GB Kingston). One recognized the PC10IMG, but had the same partition update fail. The other didn't even recognize the file.
If this ends up being unrecoverable, does anyone have any advice for a shot at the HTC warranty? or is there no chance that they would miss the fact that it's rooted? >_>

[Q] Desperately need help - stuck on splash screen

My S-Off, Alfarev Desire running the latest CM7 RC has been working very well for some time until recently I used it for navigating. It got very hot until it turned off. I thought it was nothing out of the ordinary (very hot and sunny over here, wasn't too surprised) until in the evening, after it had cooled off for several hours it simply refuses to get past the splash screen (the joker screen). I'd be happy to reflash and see if that's the problem, but I can only access fastboot and hboot: if I select recovery, it just gets stuck on the splash screen again. I've tried leaving it for a while, but turned it off after an hour as it was obviously going nowhere.
What should I do?
Thanks to all the gurus that may have some lifesaving advice.

Should be in the Q&A section.

@lucchini please explain to me why is there a Q&A (QUESTION AND ANSWER) section.

ooops, sorry about that - I'll see if I can get somebody to move it.
Anybody that actually has some advice?

look here mate http://www.youtube.com/watch?v=JmvCpR45LKA

Put it in the refrigator for a while (im not kidding), it helped numerous people with same issue.

You say that you can enter bootloader, so that means that you can flash RUU

Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.

Then find a good solid hammer and show that bitc* what she desirves

lucchini said:
Sadly, I tried that already to no avail. I also tried leaving it for a few days and then restarting, but nothing's changed.
Click to expand...
Click to collapse
Is your phone recognized in fastboot?
Try running:
fastboot devices

Did you rooted and s-offed your phone with revolutionary? If us, you have to flash bravo downgrader before you can apply ruu.
Or did you (also) get cid error when you wanted to apply ruu?
TouchPaled from Oxygen with Transparent XDA App

Thanks for all the replies.
update: It was indeed recognised in fastboot devices, so I followed jeremija8's suggestion and ran the RUU. Everything was going smooth until it got to the system files, when it said the partition didn't exist. It has since been stuck in the black HTC screen with a /!\ sign in each corner. As I understand it, it's still in fastboot, but I'm starting to feel a sense of impending doom now.
Any ideas?
Again, thanks to all.

SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.

lucchini said:
SOLVED: I finally figured it out - I had a damaged system partition. Managed to fix it by using fastboot from within Teppik74's downgrade tool [http://forum.xda-developers.com/showthread.php?t=768256] to erase everything, then ran the latest official WWE RUU which set everything to stock. Finally back in business.
A big thank you for everybody's suggestions, especially howdid's video - very entertaining.
Click to expand...
Click to collapse
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks

ridhavm said:
Have exactly the similar problem , stuck on Alpharev splash screen. Can you please explain what do you mean by erase everything or if you can give details of the steps you performed ?
Thanks
Click to expand...
Click to collapse
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck

EddieN said:
This is what I did last night when I was stuck on the alpharev logo (albeit with a CACHE error having no space, but this should erase the partitions so you can start from scratch again):
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/show....php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
Good luck
Click to expand...
Click to collapse
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.

Got it , Here is the Device Info:
SPL/hboot version: 0.93.0001.
Radio version: 5.11.05.27.
Main software version: 2.12.110.4.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
I had RCMIX v2.x installed on my desire

ridhavm said:
Thanks . Just to add some more information, when I took out the memory card earlier today, windows detected it as corrupt and asked to reformat it.
I have used Fastboot and followed these steps, but getting this message :
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
I believe I recently formatted my windows system and its missing drivers.
Is there any way to install the drivers without connecting phone ?
Thanks again for your help.
Click to expand...
Click to collapse
Now that you say it, it might be your SD card acting up. So try and reformat it and prep it according to this: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3.
I wouldnt recommend 512mb ext though, people usually recommend 1gb
After this you'll have to reflash the rom again and do a full wipe

Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.

ridhavm said:
Thanks, Tried reformatting SD card , was still stuck on boot loop.
Got Screwed up further now , Tried installing the official TMo RUU, it detected the phone in fast boot mode but aborted in the middle with error relating to verifying signature.
Now stuck with a Black bricked screen. No display , not able to get to FastBoot mode now.
Click to expand...
Click to collapse
Tried with a new recovery through ADB?
EDIT: Try this http://forum.xda-developers.com/showthread.php?t=831734

[Q] Desire Z - bricked?

Hi everyone!
Something is seriously messed up with my HTC Desire Z.
I downgraded my phone as described here:
http://forum.xda-developers.com/showthread.php?t=1178912
and rooted it like this:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I then installed ROM Manager, flashed clockworkmod recovery 3.0.0.5 and flashed Virtuous Unity ROM.
So I've got in Bootloader:
Vision PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
Radio-26.03.02.26_M
eMMC-boot
Everything worked without any problem - so far. After a few days (and no changes) the phone application of HTC crashed endlessly and I had to enter my PIN code (to unlock SIM) again and again. So I decided to flash a new ROM to fix this problem and this is where my real problems beginn. The ROM update to Cyanogenmod 7 failed.
First what I still can do:
- I can still enter the bootmanager and use fastboot from the computer.
- I can still access cwm recovery but only with errors.
- I can still flash some ROMs (like MIUI) via recovery without any errors, but it changes nothing.
Now what I can't do:
- I can't use adb, the device doesn't show up.
- CWM recovery shows the following errors at startup:
Can't mount /cache/recovery/command
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /chache/recovery/last_log
Can't open /cache/recovery/last_log
- I can't boot up my phone, it ends with the HTC screen (waited for a long time >20min).
- I can't flash a newer or older recovery using fastboot (tried a few):
sending 'recovery' (3624 KB)... OKAY [ 0.624s]
writing 'recovery'... FAILED (remote: image update error)
- I can't perform a RUU. After clicking through all the warnings and starting the update process RUU wants to restart the bootmanager at the beginning of the procedure. This ends with the HTC Screen and RUU brings a connection error after a minute or two. I tried different RUUs.
- I can't manually flash the PC10IMG.zip. The bootmanager brings the errors:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10DIAG.nbh]
No image or wrong image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
But it loads the PC10IMG.zip anyhow and brings the "parsing...[SD ZIP]" screen with possibility to start update now. After pressing volume up to start flashing ends with error "Fail-PU" at the first entry (Bootloader) and below it says "Partition update fail!". I tried different PC10IMG.zip's.
- I can't do a NANDroid restore in cwm. It says:
Erasing boot before restore...
Error while erasing boot image!
I also formatted the miniSDHC card, did wipes in cwm and performed a full wipe using SuperWipe from the forum here. I hope I didn't forget anything...
I really don't know what else I can do. I would be so thankful if anyone has an idea or solution for me! Thanks in advance!

Sounds like you have the bad emmc chip, in which case you'll have to get a replacement.
Here is more info on the error.
-Nipqer

Thx Nipqer for your quick answer and your hint!
So I will send it in. But what should I tell them what I've done? I know they find out anyway but what did you tell? You just wrote "my phone doesn't boot" or the full history?
Thanks for your advice!
greets

well can you flash stock rom possibly? Any chance you can get it going long enough to unroot?

I didn't send it back to HTC, as I bought it from a local importer.
Most people have had no issues with rooting, as its a hardware issue so it's HTC's responsibiltiy to replace it anyway.
-Nipqer

So you have a dead eMMC. Can you get the phone replaced? If so, before you send it in - would you like to be a guinea pig? You have the engineering hboot - do you know how to use fastboot?

Hi, thx for the answers!
well can you flash stock rom possibly? Any chance you can get it going long enough to unroot?
Click to expand...
Click to collapse
Using a RUU didn't work and flashing the PC10Diag.zip from the downgrade page (this should be stock) failed too. Is there another way?
I didn't send it back to HTC, as I bought it from a local importer.
Click to expand...
Click to collapse
So the local importer replaced the phone without sending it to HTC or the responsible service center first?
Can you get the phone replaced?
Click to expand...
Click to collapse
I hope so but I'm not sure, as it's easy for HTC or the service center to recognise that I bricked it by flashing/unrooting and there's no more warranty.
If so, before you send it in - would you like to be a guinea pig?
Click to expand...
Click to collapse
Here I'am!
You have the engineering hboot - do you know how to use fastboot?
Click to expand...
Click to collapse
Yes, but I'm no expert. If I'm in bootloader the command fastboot devices shows my phone, so little experimenting should be possible. What should I do?

remo.sp said:
I hope so but I'm not sure, as it's easy for HTC or the service center to recognise that I bricked it by flashing/unrooting and there's no more warranty.
Here I'am!
Yes, but I'm no expert. If I'm in bootloader the command fastboot devices shows my phone, so little experimenting should be possible. What should I do?
Click to expand...
Click to collapse
Disclaimer: Please be aware that following this procedure could permanently brick your phone; so if you don't fancy having a potential paperweight, you don't have to do this.
Could you run the following commands?
fastboot oem reinit_nand
fastboot oem rebootRUU
fastboot erase system
fastboot erase userdata
and tell me its' output?

Mhhh ok then I prefer to send it in first. Maybe I'm lucky and I get a replacement. But if not, I will definitely try these commands.
I'm in Switzerland and I have to send it to the responsible service center. What do you think should I tell them that I most likely get a replacement?

Basically same stuff here. DZ:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MIVROP-0425
RADIO-26.10.04.03_M
can get into fastboot. If i try to go to recovery, device shows htc boot screen, the boot screen with green pictogram, and then switches off, vibrating about six times in a row.
reinit_nand - Command error
rebootRUU - device gets stuck (previously it did load into that mode, but stopped after some time)
erase system - not allowed
erase userdata - same
erase cache - gets stuck (freezes)
As far as I get, bad emmc here? everything was fine till couple of days before - at first freezes and reboots, afterwards - stuck at boot forever.

sam_banshee said:
Basically same stuff here. DZ:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MIVROP-0425
RADIO-26.10.04.03_M
can get into fastboot. If i try to go to recovery, device shows htc boot screen, the boot screen with green pictogram, and then switches off, vibrating about six times in a row.
reinit_nand - Command error
rebootRUU - device gets stuck (previously it did load into that mode, but stopped after some time)
erase system - not allowed
erase userdata - same
erase cache - gets stuck (freezes)
As far as I get, bad emmc here? everything was fine till couple of days before - at first freezes and reboots, afterwards - stuck at boot forever.
Click to expand...
Click to collapse
Well there's your problem - your hboot is S-ON and it's not an engineering hboot. See if you can update it.

Unfortunately, all the methods to update hboot to ENG I located require working adb. Would appreciate if you point me to one with fastboot.
I did try flashing official RUU. If I use .exe process gets stuck at rebooting into update (rebootRUU). If I use PC10IMG.ZIP on SD card - update gets stuck at flashing boot - it saz "updating" and no changes for minutes, and nothing changed after reboot. Can't boot into recovery also.
As far as I understood from reading around, this is probably caused by corrupted emmc chip.

sam_banshee said:
Unfortunately, all the methods to update hboot to ENG I located require working adb. Would appreciate if you point me to one with fastboot.
I did try flashing official RUU. If I use .exe process gets stuck at rebooting into update (rebootRUU). If I use PC10IMG.ZIP on SD card - update gets stuck at flashing boot - it saz "updating" and no changes for minutes, and nothing changed after reboot. Can't boot into recovery also.
As far as I understood from reading around, this is probably caused by corrupted emmc chip.
Click to expand...
Click to collapse
Yes, it is caused by a corrupt eMMC. I'm just trying to see if there's a way out of it. I have a couple of ideas.
This is why I wish I was in physical possession of a bad eMMC phone then I could work and work at it.

This is why I wish I was in physical possession of a bad eMMC phone then I could work and work at it.
Click to expand...
Click to collapse
My phone (DZ with eng hboot and corrupt emmc) is now in repair. We'll see if they do it under warranty or how much I have to pay for it. If it's to much I maybe can send you the phone via airmail. But for now I just have to wait...

VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.10.04_03M
eMMC-boot
fastboot oem reinit_nand: ... INFO[ERR] Command error !!!
fastboot oem rebootRUU: ... OKAY [ 2.936s] -> reboot
fastboot erase system: erasing 'system'... -> stuck
fastboot erase userdata: erasing 'userdata'... -> stuck
---------- Post added at 12:20 PM ---------- Previous post was at 12:02 PM ----------
remo.sp said:
My phone (DZ with eng hboot and corrupt emmc) is now in repair. We'll see if they do it under warranty or how much I have to pay for it. If it's to much I maybe can send you the phone via airmail. But for now I just have to wait...
Click to expand...
Click to collapse
i'm also in switzerland, please keep me up to date.

Hey!
I've got my phone repaired under warranty conditions. They changed the motherboard. Just told them what happend (freeze, battery remove, no more booting).
CH related info: Bought phone by digitec and sent it to Arvato Teleservice.

Can't format /data & /cache

Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.

Leshy01 said:
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Click to expand...
Click to collapse
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?

cmlusco said:
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
Click to expand...
Click to collapse
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.

Leshy01 said:
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Click to expand...
Click to collapse
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.

cmlusco said:
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.

Leshy01 said:
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Click to expand...
Click to collapse
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc, and select fastboot from the hboot menu, so that it says fastboot plug in red at the top. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
fastboot devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.

cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.

tiny4579 said:
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
Click to expand...
Click to collapse
Thanks tiny, you do great work yourself. I like helping people and i love technical stuff. Knowledge is everything, and its good to pass it on.

cmlusco said:
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
adb devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
Click to expand...
Click to collapse
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?

Leshy01 said:
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Click to expand...
Click to collapse
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
I do not know of an irc channel, and i like to keep the conversation here so that the instructions and common issues and fixes can be seen and learned from by others.

cmlusco said:
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
Click to expand...
Click to collapse
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.

Leshy01 said:
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Click to expand...
Click to collapse
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?

cmlusco said:
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
Click to expand...
Click to collapse
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.

Leshy01 said:
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Click to expand...
Click to collapse
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.

cmlusco said:
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
Click to expand...
Click to collapse
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2

cmlusco said:
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Click to expand...
Click to collapse
Well... I'm sketchy on the exact terms here, but In CWM, I can mount the drives without getting any errors, but whenI try to format I get errors. I haven't actually "done" anything with those partition besides that.
However. I ran through ALL the steps you had me to. Flash the stock ROM w/ recovery, unlocked bootloader from HTC, pushed all the filies you had me through adb. After all that, I flashed CWM, then I flashed CM7, and then I booted up my device. As if my /data partition was not touched, all my apps were still there (titanium backup, my google accounts were still setup, app data and settings were untouched). So on a whim, I ran titanium backup, and uninstalled every single user app (since the android native uninstaller force closes). I ran it successfully, rebooted, and every other app was still there.
So it can READ the /data partition, but I have no abilities to MODIFY that partition. Through any recovery or formatting.
tiny4579 said:
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm willing to try anything because at this point nother else works, but I don't know where to start. And even if I find some documentation about other devices' partition table setup, I'm assuming the Incredible is different. Way I see it, I can't mess it up any more than it already is.
I'm hoping you guys have some sort of answer, but I'm looking around elsewhere, and I really appreciate everything you guys have contributed to this thread, and the community. Thanks!!!!!

Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?

megosu said:
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Click to expand...
Click to collapse
I don't think the mmc bug has anything to do with the Droid Incredible or even affects it. I thought the mmc bug led to a fully bricked phone.
This isn't really the thread for this but have you tried the full Odin Factory reset for your device which includes the /data partition? I think the method that uses a PIT file is the most thorough but most risky. I recommend posting any questions in your device's thread but I've had a few samsungs and am somewhat familiar with that process.