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] I need help, am going in circles with all the pages on xda-ddev and other sites

Right, basically I think I have pretty much messed up my phone, yeah yeah I know what your all thinking, seen this before.. you most likely have, I have read all the pages and tried to search for people with similar problems to me to save asking the same thing again, however I keep finding answer's that take me back to another problem on my phone.
anyway long story short, my phone wont get past bootloader. i can still get to recovery, but that does not help much as i get about 1 minute before it restarts if i plug it into my pc when in this mode, unless i format the system.
Phone spec:
Bravo PT3 SHIP S-On
Hboot-0.93.0001
Microp-051d
Touch Panel-Synt0101
Radio-5.17.05.08
Aug 10 2010, 17:52:18
Running ClockworkMod Recovery v2.5.0.1
am able to format Boot, System, Data and Cache.
However when i try format SDcard i get the message
"E: Can't Mount /dev/block/mmcblk (or /dev/block/mmcblk0p1)
(no such file or directory)
Error Mounting / SDcard/! "
I thought maybe trying to re-root my desire using unrevoked, if that would have been an option, with the latest Clockwork recovery, but it will not find my phone in fastboot. However after a few attempts of plugging in my phone ,AMDesire Recovery finds my phone and can get it to wipe the dalvic cache, sd:ext partition, create a partition, try to wipe sd:ext partition and it says "error : run 'wipe ext' via adb.
I thought at looking at the DeBricking page on here, but that seems a lot of code, and when trying to find the right downloads i to even enter all that code i have got myself a bit lost.
any help whatssoever, would be greatful,
also i apologise for this if it is in the wrong forum but as i am pretty much a new user, i am unable to post in many places.
Steve

I think you got a USB-BRICK problem.

op8867555 said:
I think you got a USB-BRICK problem.
Click to expand...
Click to collapse
This is very easy to solve i got it a lot of times
Here a link with the tutorial how to fix ithttp://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
Done in a few minutes
PS: wanted to quote not to press the thanks button anyway

adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
error: device not found..
my device drivers are android bootloader interface.
only just noticed with the adb tools that i don't need to install java SE and about 200 more apps being uploaded from adk server... but still, now i cant get past this bit!

Fastboot
Like what the other replies said, this is, most likely, a USB brick.
Try this command in fastboot mode: "fastboot oem enableqxdm 0"
Search in the forums to set up ADB/fastboot properly in your PC.

steve81uk said:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
error: device not found..
my device drivers are android bootloader interface.
only just noticed with the adb tools that i don't need to install java SE and about 200 more apps being uploaded from adk server... but still, now i cant get past this bit!
Click to expand...
Click to collapse
In order to install Android SDK you need JRE. You do not have to install all the software available in SDK you have only to download the tools.

steve81uk said:
"E: Can't Mount /dev/block/mmcblk (or /dev/block/mmcblk0p1)
(no such file or directory)
Error Mounting / SDcard/! "
Click to expand...
Click to collapse
This reads to me like you have a corrupt Ext...did you attempt to flash any alignment.zip before this happened?? Every time I try to flash an alignment, I also get this error message...hence I don't bother anymore...
My suggestion is to remove your SD and place in a card reader, then format your Ext using GParted. When you boot to recovery again, all should be sweet.
Just a thought.

dont use any EXT partition at this stage.. format ur sd card with single FAT32 partition and then try

Thanks to all of you trying to help me, I think i may need to mention that my phone does not seem to be able to read any sd card, not just the one i was using, tried my 16 gb, 8 gb, and 4gb. same message comes up.
going to try gparted later, and also have another go at creating gold card (what driver should be on set for this to work, Androidbootloader or MY HTC ? )
hopefully by the end of tonight i will have a working phone .
Once again thanks for everybody's help, I will click all the Thanks bit later
Steve

this is an usb brick, you should install android sdk, go into cmd
1. type in cd C:/android-sdk-windows/tools atleast if you have it there
go into hboot, press fastboot and connect your phone to your pc, it should say fastboot usb. then enter fastboot enable etc..(this enables the sd card read ability) after that go to the link i gave you, flash the update.zip and ur usb brick is gone,
easy as that

this sounds too simple and i still am having problems, do i not need a gold card?
Command prompt and typing in the commands you say, i continue to get an error message saying deice not found, seriously, i bet i am doing one thing wrong.. that's too simple to notice?!?!

i've never heard that you need a goldcard for a usb brick, it may sound dumb but have you installed htc sync? if so uninstall it and i you haven't install and uninstall for the drivers, usually a usb brick is solved in 4-5min, so maybe you missed out something, because when i had my first usb-brick i entered adb shell-.- you just have to type the command in once

just tried same on my notebook, no htc sync installed , Still Says error : device not found. am guessing i am pretty much screwed.

not got my hopes up too high just yet, but i think it's actually looking up a bit now, conected to phone, typed in the commands given, it can read sd card, installed update.zip. now i dunno if i should go back to backup, or try install everything again,
Thanks so much guys

How to recover my phone

I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.

You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.

Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.

I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.

Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.

mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.

mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.

Nexus Bricked

Hi guys, I have a very big problem. After a crean wipe and install of cm11, my phone started to reboot after maybe 10 seconds from the boot. I tryed to restore factory but the toolkit and odin fail on writing of system.img.Could anybody help me? Thanks so much

lo97 said:
Hi guys, I have a very big problem. After a crean wipe and install of cm11, my phone started to reboot after maybe 10 seconds from the boot. I tryed to restore factory but the toolkit and odin fail on writing of system.img.Could anybody help me? Thanks so much
Click to expand...
Click to collapse
Are you able to get to recovery via the power button and volume button method?

Stupendousman2012 said:
Are you able to get to recovery via the power button and volume button method?
Click to expand...
Click to collapse
Also, is device recognized w/adb?

Yes, I'm able to use the fastboot but it didn't seem to work bacause I'm on cwm and I tryed to flash twrp but It didn't work. Also I'm not able to flash stock because it fails at system writing. No adb, I have only 15-30 seconds befere the FC and the restart
EDIT: Maybe it's a permission error (only R/O) how fix it?

lo97 said:
Yes, I'm able to use the fastboot but it didn't seem to work bacause I'm on cwm and I tryed to flash twrp but It didn't work. Also I'm not able to flash stock because it fails at system writing. No adb, I have only 15-30 seconds befere the FC and the restart
EDIT: Maybe it's a permission error (only R/O) how fix it?
Click to expand...
Click to collapse
Reboot the phone into safe mode by holding power until the reboot menu appears, and then holding your finger on the beboot button until the reboot into safe mode dialogue appears.
When you are in safe mode, see if you are able to navigate around without the phone auto-restarting.
If so, see if you are able to copy the rom and GAPPS to the sdcard/download directory and try to flash again?
Not sure if this will work, but at least you can see if the hardware is failing in safe mode

Stupendousman2012 said:
Reboot the phone into safe mode by holding power until the reboot menu appears, and then holding your finger on the beboot button until the reboot into safe mode dialogue appears.
When you are in safe mode, see if you are able to navigate around without the phone auto-restarting.
If so, see if you are able to copy the rom and GAPPS to the sdcard/download directory and try to flash again?
Not sure if this will work, but at least you can see if the hardware is failing in safe mode
Click to expand...
Click to collapse
Safe mode works only if I presso volume down button because everything I do seems to don't change anything after it reboot = like not saving thing. And It reboots also in safe mode (bu i have like 1-2 minutes...unless i try to delete something or download because them cause a reboot...) (sorry for my english). Every whipes and flash doesn't work...no factory reset, no toolkit reset, no odin reset..they all failed or just don't change anything (I tryed odin download and I pass but after it rebooted like every-time before)

lo97 said:
Safe mode works only if I presso volume down button because everything I do seems to don't change anything after it reboot = like not saving thing. And It reboots also in safe mode (bu i have like 1-2 minutes...unless i try to delete something or download because them cause a reboot...) (sorry for my english). Every whipes and flash doesn't work...no factory reset, no toolkit reset, no odin reset..they all failed or just don't change anything (I tryed odin download and I pass but after it rebooted like every-time before)
Click to expand...
Click to collapse
Fastboot(bootloader) is recovery independent, recovery doesn't even need to be there. I'm pretty sure from what you've said that you've got some corrupted partition(s). I went through the same thing, couldn't flash anything with adb. This is what you gotta do after you've tried to adb pull as much data from your phone as you want to backup. Most people don't know about this for some reason, it's very easy and reliable.
->Bootloader(fastboot mode) --- hold down VOL_UP + VOL_DOWN + POWER until your phone vibrates. There's post information at the bottom and the start, poweroff, boot -recovery, -bootloader options to scroll through.
->Leave your phone in fastboot mode and connect it to your PC/remote terminal. You can look at it once we execute some fastboot commands. A blue bar appears at the bottom of the screen once you send it a fastboot command/signal.
->Open up a command prompt as administrator (su shell with *nix/mac) in the directory where your fastboot(.exe) binary is. Should be the same as where adb binary is -- Don't trust adb executable downloads that don't come with fastboot. Check for connectivity, a serial should print just like with adb after entering:
Code:
fastboot devices
-----NEXT STEPS WILL WIPE && FORMAT YOUR PHONE-----
->We are going to do a fastboot erasure. This is a complete wipe/format. It reconfigures block size, cylinders, etc (default unless specified) and can format all the specified "mmc" image blocks in /dev/block. The most likely place you're gonna see data corruption is in /data and /cache because those are always mounted Writable and pretty much all data writes occur their unless you're flashing a new rom, kernel, modding /system s***, etc. Then you will temporarily be writing to some other partition blocks. So let's do a userdata and cache fastboot format. This will completely erase /data and /cache (including sdcard, it won't take a second glance). I've never heard of this failing btw. It's the gold standard of debugging reliability, and unfortunately Odin is something to definitely avoid. Bury that one away in your suicidal desperation toolbox.
Code:
fastboot -w
Reflash your bootloader, unlock it, flash recovery TWRP, and flash a kernel boot.img that's super stable like FAUX Kern or Fancy. <---- Do all that in fastboot! ---- Check the Galaxy Nexus wiki page for these commands. I'd search "fastboot commands" in xda, there's some cool s*** fastboot can do.
Then you can boot recovery, adb push all sd stuff back over. Flash a new rom with adb sideload. Make sure to download trickster and either set Dynamic Fsync = OFF or set Fsync = ON to avoid data corruption system gangbangs. :good:

7175 said:
Fastboot(bootloader) is recovery independent, recovery doesn't even need to be there. I'm pretty sure from what you've said that you've got some corrupted partition(s). I went through the same thing, couldn't flash anything with adb. This is what you gotta do after you've tried to adb pull as much data from your phone as you want to backup. Most people don't know about this for some reason, it's very easy and reliable.
->Bootloader(fastboot mode) --- hold down VOL_UP + VOL_DOWN + POWER until your phone vibrates. There's post information at the bottom and the start, poweroff, boot -recovery, -bootloader options to scroll through.
->Leave your phone in fastboot mode and connect it to your PC/remote terminal. You can look at it once we execute some fastboot commands. A blue bar appears at the bottom of the screen once you send it a fastboot command/signal.
->Open up a command prompt as administrator (su shell with *nix/mac) in the directory where your fastboot(.exe) binary is. Should be the same as where adb binary is -- Don't trust adb executable downloads that don't come with fastboot. Check for connectivity, a serial should print just like with adb after entering:
Code:
fastboot devices
-----NEXT STEPS WILL WIPE && FORMAT YOUR PHONE-----
->We are going to do a fastboot erasure. This is a complete wipe/format. It reconfigures block size, cylinders, etc (default unless specified) and can format all the specified "mmc" image blocks in /dev/block. The most likely place you're gonna see data corruption is in /data and /cache because those are always mounted Writable and pretty much all data writes occur their unless you're flashing a new rom, kernel, modding /system s***, etc. Then you will temporarily be writing to some other partition blocks. So let's do a userdata and cache fastboot format. This will completely erase /data and /cache (including sdcard, it won't take a second glance). I've never heard of this failing btw. It's the gold standard of debugging reliability, and unfortunately Odin is something to definitely avoid. Bury that one away in your suicidal desperation toolbox.
Code:
fastboot -w
Reflash your bootloader, unlock it, flash recovery TWRP, and flash a kernel boot.img that's super stable like FAUX Kern or Fancy. <---- Do all that in fastboot! ---- Check the Galaxy Nexus wiki page for these commands. I'd search "fastboot commands" in xda, there's some cool s*** fastboot can do.
Then you can boot recovery, adb push all sd stuff back over. Flash a new rom with adb sideload. Make sure to download trickster and either set Dynamic Fsync = OFF or set Fsync = ON to avoid data corruption system gangbangs. :good:
Click to expand...
Click to collapse
It says that wase pass but didn't change anything. Also flash the recovery didn't change anything (I was on CMW and after flashing the TWRP, it opened CWL like always). I'm desperate .

lo97 said:
It says that wase pass but didn't change anything. Also flash the recovery didn't change anything (I was on CMW and after flashing the TWRP, it opened CWL like always). I'm desperate .
Click to expand...
Click to collapse
nothing is changed after flashing, it took long time to flash system then it failed...= fried emmc, need replacement.

samersh72 said:
nothing is changed after flashing, it took long time to flash system then it failed...= fried emmc, need replacement.
Click to expand...
Click to collapse
Also if it works normally for like a cuple of minutes?

lo97 said:
Also if it works normally for like a cuple of minutes?
Click to expand...
Click to collapse
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...

samersh72 said:
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...
Click to expand...
Click to collapse
Ok, thanks ... :'((

samersh72 said:
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...
Click to expand...
Click to collapse
Is this a pretty surefire way to tell if emmc is good or not?
I did a fastboot OEM lock and it seems to have locked ok (reloaded bootloader after command)

bpm2000 said:
Is this a pretty surefire way to tell if emmc is good or not?
I did a fastboot OEM lock and it seems to have locked ok (reloaded bootloader after command)
Click to expand...
Click to collapse
Are you able to adb push, adb sideload, fastboot flash anything over at this point? If you can you get into a recovery and use adb check for any files in data, system, cache that aren't deleted. Then run
Code:
adb shell
/sbin/busybox mount -w -o remount /system /system
/sbin/busybox mount -w -o remount /data /data
/sbin/busybox mount -w -o remount /cache /cache
find / -exec /sbin/busybox chattr -i '{}'\;
. This will make sure you don't have any immutable files; it makes all files mutable so rm -rf works and so installations can replace and delete them.

Soft Brick, couldn't flash anything, now can't mount anything

When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.

My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.