yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] android.gt:
Thank you Sir! Sorry for wasting your time. I did look through the thread, though I was looking for"drop box". I appreciate your quick response. Definitely a donation coming your way.
[AT&T Samsung Galaxy Note II] z28tovette:
You don't see many developers helping outside their dev. thread.

Kudos to manelscout4life.

sent by,note 2 using liquidsmooth.
[AT&T Samsung Galaxy Note II] android.gt:
Sure wish I could post directly on the thread but I can't. Haven't seen anyone else list this as a bug but in the notification drawer single messages and gmail notifications only show the top half of the message unless you pull down. Not a big deal but just my contribution to helping with the Dev. Of the sleekest ROM out there.
[AT&T Samsung Galaxy Note II] ManelScout4Life:
Once you pull down once it should show up pulled down unless its very long or you have many notifications
[Nexus 4 Q&A, Help & Troubleshooting] iBowToAndroid:
How hard would it be to create a script that runs on boot that formats /system if su is detected?

And could it be made into a flashable zip to be used on any phone?

Very happy to throw a nice donation your way if it can be done.

Thank you.
[Nexus 4 Q&A, Help & Troubleshooting] abnormalreply:
It's not hard at all, but why would you want to do this?
[Nexus 4 Q&A, Help & Troubleshooting] iBowToAndroid:
Ha. I spose that sounds a little suspicious. It's a long story, but basically I just want a script that I can run on a few of my devices so I can test out a few things, mainly via recovery and adb, really just making sure I can recover if something like that happens. Yeah I could wipe from recovery but I'd rather simulate the real thing, or if I have stock recovery, etc. I know a tiny bit about init but not enough to know how to write the script so I just figured it would be easier and quicker for someone to do it who actually has experience. I also realized that there's no need for a zip since I can just copy the script to any device I need. Basically "if /system/bin/su or /system/xbin/su exists, then format /system" - something like that, although I know the formatting is different. Yes I understand what I'm doing and the risks and have the restoration tools ready lol :P
[Nexus 4 Q&A, Help & Troubleshooting] fenstre:
I'm surprised you're able to test recovery/ADB scripts on your devices but don't know how to write the script you're describing.
[Verizon Samsung Galaxy S III] umirin94:
Just flashed synergy release 373 and also flashed the new modem and rpm from the latest leak. Wifi seemed to work in the beginning but after I put the phone into recovery and flash anything wifi breaks.

So far ive wiped my phone and reinstalled then reflashed emoji keyboard and the original Samsung boot logo and wifi does not work!

Toggle in notifications stays lit and if I try to turn it on in settings it goes to on and straight to off.
[Verizon Samsung Galaxy S III] corbn89:
Boot loader unlocked? Just asking because that's was the cause of a lot of Wi-Fi issues before. I'm also running synergy but experiencing no Wi-Fi troubles
[Verizon Samsung Galaxy S III] umirin94:
Yup bootloader has always been unlocked. Im not really concerned with using wifi cause I have unlimited but I just want to turn it off because it seems to be on in notification toggles
[Verizon Samsung Galaxy S III] umirin94:
Bump would really like help
[Verizon Samsung Galaxy S III] corbn89:
It must be something you're flashing after you've flashed synergy that is breaking Wi-Fi. You'll need to start over and flash things one at a time a check what is causing the problem. The rom itself didn't cause Wi-Fi problems. Something that obvious would've been reported by testers immediately
[Verizon Samsung Galaxy S III] umirin94:
The only two things I am flashing are:

4.2 emoji keyboard

Original samsung boot logo

Ive flashed both of those on previous builds and different roms and ive never experienced loss of wifi.
[Verizon Samsung Galaxy S III] corbn89:
Just pull one of them out and see if Wi-Fi works. If it doesn't, put it back and pull the other one instead.

Taking out the logo in /data/local only takes a second. The keyboard not so much.

You need to find out what's causing problems before you can determine why.

Unless something was made for a specific Rom, you can never know when it will break something.
[Verizon Samsung Galaxy S III] umirin94:
could you tell me exactly how to pull out the boot animation* sorry if i got that confused.

i actually just flashed the stock verizon animation to see if it was the samsung one and wifi is still broken.

i do remember after flashing only the boot animation the first time around (must have forgotten about the keyboard) wifi did not work after a reboot.

now the wifi toggle looks different:
[Verizon Samsung Galaxy S III] LeonardoNero:
I have this exact issue upon reboot. I checked the logs and apparently for some reason, upon reboot /data/misc/wifi/wpa_supplicant.conf has the incorrect permissions set. Manually setting to 775 or 755 should immediately restore the ability to turn on wifi.
[Verizon Samsung Galaxy S III] corbn89:
Hmm my permissions on that file are 660 and I'm fine. Should be worth a shot though.

In order to pull a custom boot ani out, go to /data/local and remove the bootanimation.zip

That should revert you back to the stock synergy animation. Just paste it back in there and make sure permissions are 755 to re-enable it.
[Verizon Samsung Galaxy S III] umirin94:
I tried changing the permissions with es explorer and I tried rom toolbox both successfully changed the permissions but wifi still did not work. If I look back on the permissions of that file it is reset back
[Galaxy Note 10.1 General] Dookiestan:
I have found a LOT of the flimsy silicon covers and even more of the folding covers. I have one of each. I like the silicon case because it does protect well but it is super flimsy. I would like a hard backed case to stiffen it up and for another reason. I use a car mount and it presses through the case and back and puts pressure on the back of the tablet which shows up on the screen as, to replicate it you can lightly press on the screen and see what it does. I am worried this may cause issues.

I am thinking of finding a 1/8" sheet of plastic and gluing it to the inside.
[HTC Amaze 4G] jdh2000:
I've been running Energy_2.27.2012.Stock.Kernel.Amaze on my TMo Amaze 4g almost since I acquired it about 22 months ago. It's rooted and hboot is set with S-on. I still have the TMo account app on it, and lately it's been reminding me to reboot every so often. Odd, since I've always done it like I would a PC, etc. I remember the first notice a couple of months ago, restarted and ultimately had to go through recovery to bring everything back. I've ignored the posts from TMo since then, but I restarted the phone last week as a regular practice and it never came up. I went to recovery, but the message I get is this: unable to mount \internal_sd_card. No recovery sequence I tried has worked. Everything on my external sd is backed up. If anyone can give me something to work with, I would really appreciate it.

I'm relegated to my old HTC HD2 running AOKP/Tytung ICS 4.0.4. I wish it was 4G.
[HTC Amaze 4G] daorderdillon:
Which recovery ye using
[HTC Amaze 4G] jdh2000:
I've tried 3: 4ext, TWRP, and CWM. I'm using CWM at the moment, but was on 4ext when this debacle took place. Thanks for asking!

More information:

When booting into recovery, the initial information that's returned is:

CWM Recovery v5.5.0.4 Xboarders Ruby Source

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

When attempting to mount the /internal_sdcard, the return message is:

Error mounting /internal_sdcard!

All other functions like wiping *whatever*, backup and restore, install zip from sdcard, will fail.
[HTC Amaze 4G] jauhien:
Format it..
[HTC Amaze 4G] jdh2000:
Tried to, but can't...because it's not mountable. I've run Ruby Superwipe as well, only to get the same results regarding inaccessibility to the same directories mentioned earlier. If you know another way, please, let me know.
[HTC Amaze 4G] jdh2000:
Just a heads-up, daorderdillon: I switched to the latest TWRP because what I read about it looked promising. It didn't work, but it sure looks good!

:silly:
[HTC Amaze 4G] jauhien:
Try mounting and formatting with help of TWRP..
[HTC Amaze 4G] jussisolja:
Have the same issue. Something happened while installing a custom ROM wia CWM. I'm on a Galaxy Note GT-N7100...any help would be appreciated! I'd love to go back to the stock ROM but flashing with Odin seems to work but then the phone says that "something went wrong with the update process"...and CWM & TWRP & Stock recovery all say the same thing: Can't mount internal or external SD's...what could it be?
[HTC Amaze 4G] jdh2000:
You might notice the message just before yours :). I switched back to the latest TWRP and tried that. Everything regarding formatting and wiping I've read about and attempted...with no luck at all. As they say, been there, done that, bought the t-shirt. What about a heavy magnet?
[HTC Amaze 4G] jdh2000:
NEW INFORMATION!!! I really hope this helps you help me.

I got to fooling around with adb.exe contained in Hasoon 2000's latest All-in-one kit (v5.1), and with my languishing HTC Amaze 4G connected and booted into recovery, I started a shell session. Low and behold, I ran a /ls -a -l command and I saw this:

See attached JPEG...

I was leery at first, so I changed directories to the sdcard (the external one), and saw my files there. Sooo, this must be the root directory, or the infamous INTERNAL_SDCARD. If ANYONE has a suggestion on what I can do from here to restore this phone, give me a shout.

I'm currently running TWRP v.2.3.3.0 for recovery. I like it...
[HTC Amaze 4G] zandgreen:
Ok, man, seems I've been out of a similar "merde" just now. After having tapped by mistake onto the "factory reset" in the bootloader I could no longer mount my internal_sdcard (4ext would say "error mounting internal_sdcard"). I thought that I had corrupted partition table. So I decided to check fstab. The internal sdcard on my device was supposed to be mounted through

/dev/block/mmcblk0p36

Then I've checked it with the fdisk:

fdisk -l /dev/block/mmcblk0p36

Disk mmcblk0p36: 10.4 GB, 10468982784 bytes
4 heads, 16 sectors/track, 319488 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

It could see the disk but could not mount it:

mount mmcblk0p36
mount: mounting /dev/block/mmcblk0p36 on /internal_sdcard failed: Invalid argument

Next you can either try to format and partition the disk manually or use "format sdcard" function from a recovery.

Finally I was able to mount and use the internal sdcard.
[HTC Amaze 4G] jdh2000:
This is outstanding. One issue I came across was finding the actual volume name that I needed to mount. The /dev/block directory shows this:

/dev/block # ←[6nls -l

ls -l

brw------- 1 root root 7, 0 Jan 2 00:00 loop0

brw------- 1 root root 7, 1 Jan 2 00:00 loop1

brw------- 1 root root 7, 2 Jan 2 00:00 loop2

brw------- 1 root root 7, 3 Jan 2 00:00 loop3

brw------- 1 root root 7, 4 Jan 2 00:00 loop4

brw------- 1 root root 7, 5 Jan 2 00:00 loop5

brw------- 1 root root 7, 6 Jan 2 00:00 loop6

brw------- 1 root root 7, 7 Jan 2 00:00 loop7

brw------- 1 root root 179, 0 Jan 2 00:00 mmcblk0

brw------- 1 root root 179, 1 Jan 2 00:00 mmcblk0p1

brw------- 1 root root 179, 10 Jan 2 00:00 mmcblk0p10

brw------- 1 root root 179, 11 Jan 2 00:00 mmcblk0p11

brw------- 1 root root 179, 12 Jan 2 00:00 mmcblk0p12

brw------- 1 root root 179, 13 Jan 2 00:00 mmcblk0p13

brw------- 1 root root 179, 14 Jan 2 00:00 mmcblk0p14

brw------- 1 root root 179, 15 Jan 2 00:00 mmcblk0p15

brw------- 1 root root 179, 16 Jan 2 00:00 mmcblk0p16

brw------- 1 root root 179, 17 Jan 2 00:00 mmcblk0p17

brw------- 1 root root 179, 18 Jan 2 00:00 mmcblk0p18

brw------- 1 root root 179, 19 Jan 2 00:00 mmcblk0p19

brw------- 1 root root 179, 2 Jan 2 00:00 mmcblk0p2

brw------- 1 root root 179, 20 Jan 2 00:00 mmcblk0p20

brw------- 1 root root 179, 21 Jan 2 00:00 mmcblk0p21

brw------- 1 root root 179, 22 Jan 2 00:00 mmcblk0p22

brw------- 1 root root 179, 23 Jan 2 00:00 mmcblk0p23

brw------- 1 root root 179, 24 Jan 2 00:00 mmcblk0p24

brw------- 1 root root 179, 25 Jan 2 00:00 mmcblk0p25

brw------- 1 root root 179, 26 Jan 2 00:00 mmcblk0p26

brw------- 1 root root 179, 3 Jan 2 00:00 mmcblk0p3

brw------- 1 root root 179, 4 Jan 2 00:00 mmcblk0p4

brw------- 1 root root 179, 5 Jan 2 00:00 mmcblk0p5

brw------- 1 root root 179, 6 Jan 2 00:00 mmcblk0p6

brw------- 1 root root 179, 7 Jan 2 00:00 mmcblk0p7

brw------- 1 root root 179, 8 Jan 2 00:00 mmcblk0p8

brw------- 1 root root 179, 9 Jan 2 00:00 mmcblk0p9

brw------- 1 root root 179, 64 Jan 2 00:00 mmcblk1

brw------- 1 root root 179, 65 Jan 2 00:00 mmcblk1p1

drwxr-xr-x 4 root root 80 Jan 2 00:00 platform

However, catting fstab gave me the actual volume name: mmcblk1p1

What the heck are the rest of those volumes listed?

AND, I haven't taken the steps to correct the mounting issue, yet, but you will know the outcome.

Again, OUTSTANDING reply. I will keep you, and everyone up to date.
[HTC Amaze 4G] zandgreen:
cat /proc/emmc

Good luck ;)
[HTC Amaze 4G] broker32:
Having the same problem as you are. I flashed the PAC MAN ROM'S newest version, everything worked fine, shut it off and to my surprise, this happened in the morning, it's super weird.
[HTC Amaze 4G] jdh2000:
Have you been able to re-flash, or recover? If you did, let me know how you did it.

I'm still soft-bricked, and I can't get the internal memory partition to format. I'm sill exploring solutions available from the adb shell. It's allowed me to really brush up on my linux/unix commands; however, I don't think I'm close to any recovery...yet.

If I get a break, you'll know it. I plan to document the whole thing right here.
[HTC Amaze 4G] broker32:
I tried mounting system, cache, internal/external cards, flashing the latest ruu.. everything and it's next to impossible, hell even USB won't work.

Much obliged.
[HTC Amaze 4G] jdh2000:
Can you "see" the directory tree when using adb shell? Or, can you get to your recovery so you can initiate a shell session?

That's one of the promising developments I've encountered since I posted this plea for help. If I can use the command-line to format I think I'll be able to flash another image and get back to square one.

At this point, reassigning rights (CHMOD) has NOT worked for some reason, but I'm continuing to try this one directory at a time. I hope to hear about your own success.
[HTC Amaze 4G] zandgreen:
jdh2000:

assuming that

you have your internal sdcard backed up

you can boot into a recovery

you can access the root using 'adb shell'

the mounting point of your internal sdcard is /dev/block/mmcblk1p1

what is the result of

dd if=/dev/zero of /dev/block/mmcblk1p1

run from 'adb shell'? (This is supposed to overwrite your partition with null bytes, thus formatting it).

P.S. it's not quite clear whether you have tried formatting the internal card from the 4ext recovery (Wipe/Format - format sdcard) or not.
[HTC Amaze 4G] jdh2000:
I'll answer the P.S. question first:

I had 4ext recovery on from the beginning of this issue. I used the Wipe/Format feature within that recovery and was NOT successful. The key directories were not mountable. It is the same with TWRP (v2.3.3.0): those directories are not mountable. As you know, if I can't mount them, then I can't format them/wipe them. When I'm in the adb shell, I CAN see them, cd to them, ls to them. They contain nothing.

Now for the results of the copy/conversion command dd:

----------------------------------------------------------------------------------------

~ # ←[6ndd if=/dev/zero of /dev/block/mmcblk1p1

dd if=/dev/zero of /dev/block/mmcblk1p1

BusyBox v1.20.1-cm7 bionic (2012-05-28 03:56 +0200) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]

[seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

if=FILE Read from FILE instead of stdin

of=FILE Write to FILE instead of stdout

bs=N Read and write N bytes at a time

ibs=N Read N bytes at a time

obs=N Write N bytes at a time

count=N Copy only N input blocks

skip=N Skip N input blocks

seek=N Skip N output blocks

conv=notrunc Don't truncate output file

conv=noerror Continue after read errors

conv=sync Pad blocks with zeros

conv=fsync Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),

MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

----------------------------------------------------------------------------------------

Does it matter that BusyBox is utilized when the command dd is used? It appears as if BusyBox is in control of the logic.

Thanks for your continued inquiries. Hope to hear back soon.
[HTC Amaze 4G] jdh2000:
Oops!

I overlooked part of your requirements: you asked whether "the mounting point of your internal sdcard is /dev/block/mmcblk1p1"

How would I tell?
[HTC Amaze 4G] jdh2000:
OK OK OK

Check this: I looked at your command format and the original output after executing the original command. You missed the "=" after the "of" logic request. I changed it to "dd if=/dev/zero of=/dev/block/mmcblk1p1", and this is what I got...

------------------------------------------------------------------------------------

~ # ←[6ndd if=/dev/zero of=/dev/block/mmcblk1p1

dd if=/dev/zero of=/dev/block/mmcblk1p1

dd: writing '/dev/block/mmcblk1p1': No space left on device

848025+0 records in

848024+0 records out

434188288 bytes (414.1MB) copied, 6.870026 seconds, 60.3MB/s

~ # ←[6n

------------------------------------------------------------------------------------

Now I will try to format. Hold on...

:(

No go.
[HTC Amaze 4G] zandgreen:
It can be found by

cat /etc/fstab

from 'adb shell' while you are in recovery.

Or another way to check it is:

fdisk -l /dev/block/*

this will show partition of every volume. Can you post its output here?
[HTC Amaze 4G] zandgreen:
I guess it was your external sdcard :rolleyes:

I was sure your had checked your fstab and that's why I suggested "mmcblk1p1".
[HTC Amaze 4G] jdh2000:
My external sd card was removed, unless you're talking about sd_int, and sd_ext...

You're right, I did check fstab. I'll put the question another way; when I start adb shell, I'm always at root: "/", but you asked if I began my session at mmcblk1p1, I think, and I don't think I am. I have to drill down to /dev/block to get there. :eek:

I will post what you've asked for later tonight. Probably around 10 PM PST, or UTC -8.
[HTC Amaze 4G] jdh2000:
Yes, absolutely.:good:
[HTC Amaze 4G] jdh2000:
zandgreen - Here is a snapshot of the latest log after booting into recovery. It's contents seem a little larger after running the dd command last night. This is in TWRP recovery.
[HTC Amaze 4G] zandgreen:
Ok, could you also post your fstab? Thanks.
[HTC Amaze 4G] ravike14:
seeing this thread everyday so i did some research follow this it worked for one of my friends :) http://xdaforums.com/showpost.php?p=27844248&postcount=6 you have to have 4ext recovery for this.. cheers :good:
[HTC Amaze 4G] jdh2000:
Yes, absolutely. I'll put it up later tonight.
[HTC Amaze 4G] jdh2000:
I appreciate the input. Earlier in this post zandgreen suggested that I do the same thing. Unfortunately it didn't work.:p
[HTC Amaze 4G] jdh2000:
Here is the result:

~ # ←[6ncat /etc/fstab

cat /etc/fstab

/cache ext4 rw

/data ext4 rw

/sdcard vfat rw

/system ext4 rw

/devlog ext4 rw

/emmc vfat rw
[HTC Amaze 4G] Keylogger_0:
Run this command. Should fix your internal sd card. Make sure your phone is connected and is in recovery, and make sure adb is accessible.

adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36

In this, the case IS important. Make sure it's -F, not -f, and -L and not -l, and such.

Didn't see that someone included a link to my post.

However, I don't see why you couldn't load a RUU. That should fix any and all of your corrupted partitions.
[HTC Amaze 4G] ravike14:
I put the link post Sorry for not asking your permission for that... :)

Sent from my HTC Amaze 4G

Juopunutbear S-OFF

Super CID

bootloader unlocked

Powered by Faux Kernel V027

HBOOT : 1.93.2222

hit the thanks button if i've helped you :good:
[HTC Amaze 4G] Keylogger_0:
You don't need permission to refer posts :P It's fine.
[HTC Amaze 4G] jdh2000:
I tried to load a RUU. It gets so far, then fails on the signature confirmation. This was with a stock Gingerbread TMo RUU. Here's the file name: PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed.zip. And I relocked the bootloader before attempting to flash. Any ideas???
[HTC Amaze 4G] Keylogger_0:
that's a fairly old RUU. Use this latest ruu: http://d-h.st/3VD

Also make sure to rename it to PH85IMG and follow the usual RUU flashing instructions.
[HTC Amaze 4G] opticalmouse:
Does anyone sucssed to recover the internal SD after flashing an stock RUU to Amaze 4G???

EDIT: I did... For those that want to do just flash and stock ICS rom to your Amaze and then flash recovery (4EXT in my option) and then you can proceed as normal install from zip...
[HTC Amaze 4G] kodunmit:
Internal memory not mounted

I ran into almost similar situation when i flashed Jb on my Amaze. Luckily for me when i connect it to my PC, the PC recognised the internal memory as not formated and when i formatted through the PC it worked and I could reflash the phone
[HTC Amaze 4G] Sirocco.ukr.lviv:
IT WORKS!!!! the same happenned to me 1 hour ago. thank you for your post. plugged in to PC - formatted my disk. now I can flash my rom. God Bless You!!!!:victory: Now I flashed Viper Amaze and in Aroma Installer checked Full Wipe otption. It helps me too.
[HTC Amaze 4G] jazzyoneman:
htc desire vc can't mount sdcard

Same probllem after flashing new rom, cwm and twrp unable to mount sdcard, it can't be formatted, may be any bad block partition in sdcard, so anybody can solve this problem
[HTC Amaze 4G] kiskisboki:
same here

Hi! I know its a bit old post, but I went through the same issues but unfortunately I can't format it from my pc. Did you just use ext4 recovery - toggle usb storage and it connected to the pc? did you use windows? maybe linux? I read a ton about this but nothing works yet
[HTC Amaze 4G] pijo1971:
Hello, I've the same problem (GT-N7100), I'm not be able to mount neither internal SD nor external SD.

I've run the above command, and this is my result

some one could help me to recover my phone?
[HTC Amaze 4G] ravike14:
Flash a RUU?
[HTC Amaze 4G] pijo1971:
Hello,

I don't know if with "Flash a RUU" you intend download a stock rom and flash it via odin, but in this case I've already tried and the log of odin is:

Odin isn't able to write.

Thank you.

Luigi
[HTC Amaze 4G] ravike14:
since when HTC have Odin? :S i think you're in the wrong forum..
[HTC Amaze 4G] pijo1971:
OPS... I'm sorry. I've read only the title post, and I've not checked where were the forum.

I'll move to GT-N7100 formun. Thank you the same.

Kind regards,

Luigi
[HTC Amaze 4G] punkboyinsf:
Yes, flashing RUU fixed it for me

Had this error show up earlier tonight.. I used your link, locked bootloader with Toolkit, Flashed the ruu and got my internal storage back (minus the data, luckily I have a month old backup, so not all is lost).. Ironic that I was performing a backup when it failed to come back from the reboot afterwards..

Thanks for the advice and the link!
[HTC Amaze 4G] NooBOnTheBlock:
Okay it looks like your system is wiped and you have some things on your sd card still...if you had 4ext installed then its the only recovery that can fix you...try reinstalling it and then flashing a rom? If your data is not precious and is expendible then you should be able to format in 4ext and repartition in 4ext