Database Users

[Q] borked internal sd card on Atrix

Hi all,
I posted this in the Atrix Q&A but it doesn't seem to have had many hits, thought I'd try my luck here (here is the original thread: http://forum.xda-developers.com/showthread.php?t=1594675) ...basically my Atrix emmc internal memory card is borked and I am trying to find a way to restore it other than SBFing to factory (which is risky and a hassle...).
rickywyatt kindly told me to execute these commands in an adb shell and to post the results:
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
well my results are as follows:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #​
anyone know what I need to do next? If anyone can interpret the output for me I'd be so grateful.
Thanks,
Mark

I'd say flashing an sbf is alot easier then that haha.
Sent from my MB860 using XDA

If i where you i'd try to leave it as if was new and take it to motorola service, they change it to a new one. If you did unlocked the bootload (i guess you did) i think that there was a way to hidde the unlocked at boot.
GL with that!

[System, Boot & Recovery Dump][8-27-13] SGH-T599 (4.1.2) JZO54K.T599UVAMB5

I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
CWM
Instructions and discussion available here
Click to expand...
Click to collapse
CWM Flashable Recovery
Both have been tested by me
Stock Recovery
CWM 6.0.3.6 by Unjustified Dev
Click to expand...
Click to collapse
DOWNLOAD:
System.img (/dev/block/mmcblk0p22)
Boot.img (/dev/block/mmcblk0p20)
Recovery.img (/dev/block/mmcblk0p21)
Modem.img - T599UVAMB5 (/dev/block/mmcblk0p12)
modem.bin (/dev/block/mmcblk0p16)
param.lfs (/dev/block/mmcblk0p19)
Preload.img (/dev/block/mmcblk0p24)
efs.img (/dev/block/mmcblk0p11)
Click to expand...
Click to collapse

Hmmm... can you explain me what is that? Thx

Feyerabend said:
Hmmm... can you explain me what is that? Thx
Click to expand...
Click to collapse
It is for development purposes. It is basically the stock firmware minus the kernel and recovery.

goldfingerfif said:
I uploaded the system tar its almost 1GB I cannot pull the Kernel though.
I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
If someone can assist with getting the kernel without root I would be forever grateful. If it is unpossible then please let me know as well as I cannot find a root method that works.
Click to expand...
Click to collapse
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?

tys0n said:
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?
Click to expand...
Click to collapse
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.

goldfingerfif said:
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.
Click to expand...
Click to collapse
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin

tys0n said:
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin
Click to expand...
Click to collapse
Yes just like that minus the need to unpack it because it is just a tarball so 7zip or whatever should open it fine. I am at work but I believe my home computer has either a linux vm installed or Cygwin with dsixda’s kitchen.
I should be able to manually or through dsixda’s kitchen add supersu and su convert to a odin img and flash.
If it successfully roots so I can at least get a rooted shell so I can dd if=/dev/block/….. of=/sdcard/…img to get a recovery.img and boot.img then carefully cook up a TWRP or CWM recovery to flash then make a “custom” or modified stock rom to flash with insecured kernel.

Anything new on how this is going?

thecasual01 said:
Anything new on how this is going?
Click to expand...
Click to collapse
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.

goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.

goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
I think it will be fine to flash system.img only as long as you don't use any pit and repartition. Factory reset first to prevent bootloops.
tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
Are you saying you used a boot.img from s3 mini?

tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190

goldfingerfif said:
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190
Click to expand...
Click to collapse
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.

tamil.soljahz said:
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.
Click to expand...
Click to collapse
The site you linked doesn't mention the SGH-T599 just the GT-8190 and the GT-i9300, did you send the right link?

According to http://www.gsmchoice.com/en/catalogue/samsung/galaxyexhibit/ it's built on same board. ST-Ericsson U8420.
It' same for i8190, some sites say U8500 others say U8420.

The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.

marksalot said:
The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.
Click to expand...
Click to collapse
Cool
So, first guy who "dd" will be hero of the day
If partition layout is the same as i8190 it should look like this.
Code:
GT-I8190 PARTITION LAYOUT
Official Name * Fs * Mount point * Known as * Contents
/efs * ext4 * /dev/block/mmcblk0p11 * Efs folder *Device IMEI,mac address etc
/modemfs * ext4 * /dev/block/mmcblk0p12 * Radio *
/SdCcard * vfat * /dev/block/mmcblk1 /dev/block/mmcblk1p1 * Internal sd * Your stuff
/boot * emmc * /dev/block/mmcblk0p20 * kernel/zimage * Drivers etc
/recovery * emmc * /dev/block/mmcblk0p21 * Recovery partion * ??????
/system * ext4 * /dev/block/mmcblk0p22 * System folder * The operation system
/cache * ext4 * /dev/block/mmcblk0p23 * Cache partition * Update.zips csc,samsung and carriers customizations
/preload * ext4 * /dev/block/mmcblk0p24 * Hidden partition * Media files,apks etc from Samsung/carriers
/.lfs * j4fs * /dev/block/mmcblk0p19 * param.lfs ## * splash screen,charging animation download mode pngs, etc
/data * ext4 * /dev/block/mmcblk0p25 length=-16384 * data folder * Your download apps, current device and use, settings
/temp * ? * /dev/block/mmcblk0p5 * nedded to load *
* * * psccd and CSPSA *
* * * when reset is *
* * * triggered *
* * * *
* * * *
* *
* * * *
I guess boot, recovery, and param is most wanted

Here is the content of /proc/partitions
Code:
major minor #blocks name
7 0 5229 loop0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 737280 mmcblk0p23
179 24 102400 mmcblk0p24
179 25 1535983 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
254 0 5229 dm-0
Here is the output of busybox df -h
I have a 16GB SD Card, apparently Maverick (GPS map app I installed) creates it's own partition.
Code:
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 402.1M 112.0K 401.9M 0% /dev
tmpfs 402.1M 0 402.1M 0% /mnt/asec
tmpfs 402.1M 0 402.1M 0% /mnt/obb
tmpfs 402.1M 0 402.1M 0% /dev/shm
/dev/block/mmcblk0p22
1.2G 965.4M 215.7M 82% /system
/dev/block/mmcblk0p12
15.7M 4.3M 11.4M 28% /modemfs
/dev/block/mmcblk0p23
708.7M 12.0M 696.7M 2% /cache
/dev/block/mmcblk0p11
15.7M 4.5M 11.2M 29% /efs
/dev/block/mmcblk0p24
98.4M 11.6M 86.8M 12% /preload
/dev/block/mmcblk0p25
1.4G 1.3G 173.7M 88% /data
df: /mnt/.lfs: Function not implemented
/dev/fuse 1.3G 1.3G 73.7M 95% /storage/sdcard0
/dev/block/dm-0 5.0M 2.9M 2.1M 57% /mnt/asec/com.codesector.maverick.full-1
/dev/block/vold/179:97
14.9G 10.1G 4.8G 68% /storage/extSdCard

cat /proc/partitions gives me in I8190.
Code:
major minor #blocks name
7 0 16664 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 2111 loop3
7 4 2111 loop4
7 5 2111 loop5
7 6 2111 loop6
7 7 17703 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 13473792 mmcblk1p1
179 98 2075648 mmcblk1p2
254 0 16663 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
254 4 2110 dm-4
254 5 2110 dm-5
254 6 2110 dm-6
254 7 17703 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 26019 loop9
254 9 26019 dm-9
Looks like it matches pretty well

So, I used the Online Nandroid app, it detects the T599 as "codinatmo" and doesn't have a patch available.
Manually chose the "Samsung Galaxy S III mini GT-l8190" patch and installed.
Was able to back up boot.img and recovery.img, both 16MB.

I9505 - Cannot create loop device, action not permitted

Hi, I am trying to put kali linux on my Galaxy S4 I9505, using Complete Linux Installer.
However, I came across an error I couldn't fix, not even after searching every XDA thread about it.
My Galaxy S4 I9505 runs Android 4.3 and was rooted using this method: w|w|w.w0lfdroid.c|o|m/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
(Please remove the "|", I have no idea how else I can give detailed information, If I am not even allowed to post my root method. And I don't want to spam the forums for 10 posts..)
Rootchecker says my phone is rooted and I able to run root explorer etc.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
So I downloaded the kali linux image via the Complete Linux Installer app (kalilinux.ext4.img), put it on my sdcard and then pressed the "start linux" button.
As soon as the script tries to create a loop device, I get the following error:
Code:
Creating loop device.. mknod: /dev/block/loop255: Operation not permitted
FAILED
Error: Unable to create loop device!
When I checked in /dev/block, I couldn't find a file called "loop255" however I could find files like "loop0".
When I tried to set their permissions, I got the error that I was not allowed to modify it.
When trying to run
Code:
# busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system
I get the error:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
I am hoping someone could help me further. I am unsure if the problem lies at my root method (not full root or something? KNOX blocking it? Android 4.3 blocking it?), a wrong busybox location or something, or a kernel that doesn't support device looping. Or maybe the problem is something much simpler.

Hey, could anyone help me? Still looking for a solution or workaround.
I can give more info if needed.

GalaxyPhoner said:
Hi, I am trying to put kali linux on my Galaxy S4 I9505, using Complete Linux Installer.
However, I came across an error I couldn't fix, not even after searching every XDA thread about it.
My Galaxy S4 I9505 runs Android 4.3 and was rooted using this method: w|w|w.w0lfdroid.c|o|m/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
(Please remove the "|", I have no idea how else I can give detailed information, If I am not even allowed to post my root method. And I don't want to spam the forums for 10 posts..)
Rootchecker says my phone is rooted and I able to run root explorer etc.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
So I downloaded the kali linux image via the Complete Linux Installer app (kalilinux.ext4.img), put it on my sdcard and then pressed the "start linux" button.
As soon as the script tries to create a loop device, I get the following error:
Code:
Creating loop device.. mknod: /dev/block/loop255: Operation not permitted
FAILED
Error: Unable to create loop device!
When I checked in /dev/block, I couldn't find a file called "loop255" however I could find files like "loop0".
When I tried to set their permissions, I got the error that I was not allowed to modify it.
When trying to run
Code:
# busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system
I get the error:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
I am hoping someone could help me further. I am unsure if the problem lies at my root method (not full root or something? KNOX blocking it? Android 4.3 blocking it?), a wrong busybox location or something, or a kernel that doesn't support device looping. Or maybe the problem is something much simpler.
Click to expand...
Click to collapse
Hi.. I have found a way of getting through the loop255 creation, below is what i have done;
Installed Terminal IDE on my Samsung GT-19505 and connected to the phone through telnet from my PC.
Once connected change to Super User and go to the below dir', run the command and hit enter
[email protected]:/system/xbin #mknod -m a=rw /dev/block/loop255 b 7 255
This will create the loop255 device for you
To varify, go to the below directory and run;
[email protected]:/dev/block# ls
dm-0 loop7 mmcblk0p16 mmcblk0p24 mmcblk0p6 ram1 ram4
loop0 mmcblk0 mmcblk0p17 mmcblk0p25 mmcblk0p7 ram10 ram5
loop1 mmcblk0p1 mmcblk0p18 mmcblk0p26 mmcblk0p8 ram11 ram6
loop2 mmcblk0p10 mmcblk0p19 mmcblk0p27 mmcblk0p9 ram12 ram7
loop255 mmcblk0p11 mmcblk0p2 mmcblk0p28 mmcblk1 ram13 ram8
loop3 mmcblk0p12 mmcblk0p20 mmcblk0p29 mmcblk1p1 ram14 ram9
loop4 mmcblk0p13 mmcblk0p21 mmcblk0p3 param ram15 vold
loop5 mmcblk0p14 mmcblk0p22 mmcblk0p4 platform ram2 zram0
loop6 mmcblk0p15 mmcblk0p23 mmcblk0p5 ram0 ram3
You will see that the device has been created.
Now I have come to another road block;
127|[email protected]:/data/local # sh /data/data/com.zpwebsites.linuxonandroi>
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[35]: dirname: Permission denied
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Error: Unable to mount the loop device!
I have tried mounting the device manually to /data/local/mnt but still getting same error
Still searching for a solution

Same problem
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
dr_do_little_ said:
Hi.. I have found a way of getting through the loop255 creation, below is what i have done;
Installed Terminal IDE on my Samsung GT-19505 and connected to the phone through telnet from my PC.
Once connected change to Super User and go to the below dir', run the command and hit enter
[email protected]:/system/xbin #mknod -m a=rw /dev/block/loop255 b 7 255
This will create the loop255 device for you
To varify, go to the below directory and run;
[email protected]:/dev/block# ls
dm-0 loop7 mmcblk0p16 mmcblk0p24 mmcblk0p6 ram1 ram4
loop0 mmcblk0 mmcblk0p17 mmcblk0p25 mmcblk0p7 ram10 ram5
loop1 mmcblk0p1 mmcblk0p18 mmcblk0p26 mmcblk0p8 ram11 ram6
loop2 mmcblk0p10 mmcblk0p19 mmcblk0p27 mmcblk0p9 ram12 ram7
loop255 mmcblk0p11 mmcblk0p2 mmcblk0p28 mmcblk1 ram13 ram8
loop3 mmcblk0p12 mmcblk0p20 mmcblk0p29 mmcblk1p1 ram14 ram9
loop4 mmcblk0p13 mmcblk0p21 mmcblk0p3 param ram15 vold
loop5 mmcblk0p14 mmcblk0p22 mmcblk0p4 platform ram2 zram0
loop6 mmcblk0p15 mmcblk0p23 mmcblk0p5 ram0 ram3
You will see that the device has been created.
Now I have come to another road block;
127|[email protected]:/data/local # sh /data/data/com.zpwebsites.linuxonandroi>
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[35]: dirname: Permission denied
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Error: Unable to mount the loop device!
I have tried mounting the device manually to /data/local/mnt but still getting same error
Still searching for a solution
Click to expand...
Click to collapse
---------- Post added at 05:15 PM ---------- Previous post was at 04:43 PM ----------
Ok i'm trying to let it work, and reading the man page of mknod i tried:
mknod -m a=rwxrwxrwx /dev/block/loop255 b 7 255
to avoid the permission problem, in fact i works, BUT trying again to boot linux this error appears:
Error: unable to attach image to loop device!
Now i'm playing with the mount -o loop fedora.img /deb/block/loop255 to find the solution....
Any idea ?
flashback_pa said:
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
Click to expand...
Click to collapse

Something is changing, just used
losetup -r /dev/block/loop255 /fedora.img
but the mount command still fails.
By the way, Are you sure that the type ext4 is correct to mount the iso ? Maybe we should use iso9660 ?
flashback_pa said:
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
---------- Post added at 05:15 PM ---------- Previous post was at 04:43 PM ----------
Ok i'm trying to let it work, and reading the man page of mknod i tried:
mknod -m a=rwxrwxrwx /dev/block/loop255 b 7 255
to avoid the permission problem, in fact i works, BUT trying again to boot linux this error appears:
Error: unable to attach image to loop device!
Now i'm playing with the mount -o loop fedora.img /deb/block/loop255 to find the solution....
Any idea ?
Click to expand...
Click to collapse

Do not flash cm12 over 5.1 bootloader/finding the files for qhusb_bulk

THREAD IS NOW AT ->
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518

I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6

Casper34 said:
I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6
Click to expand...
Click to collapse
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks

opssemnik said:
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks
Click to expand...
Click to collapse
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6

Casper34 said:
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6
Click to expand...
Click to collapse
which you prefer, tho the output will be a bit big

opssemnik said:
which you prefer, tho the output will be a bit big
Click to expand...
Click to collapse
Check PMs
Sent from my Nexus 6

Casper34 said:
Check PMs
Sent from my Nexus 6
Click to expand...
Click to collapse
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform

So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?

I flashed back to stock other day after running it ..Should that have been affected
Sent from my Nexus 6 using Tapatalk

looking foward to unbricking it. Thanks a lot

opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6

My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Casper34 said:
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks, im preparing the QPST / Drivers zip, im also looking into the factory images

ccb1208 said:
My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Click to expand...
Click to collapse
yep, in that mode we need a program that acts as QPST (or QPST itself) a 2nd_loader.hex (new bootloader) and a APQ8974_image hex that matches ours nexus 6, once there we can send the basic stuff and get rsd mode / fastboot to work, then we just flash factory images

Your best bet would be to try the Moto X/G blankflash program. It uses an executable called qboot which is a USB loader. It may be possible to use the 8226 programmer to flash the bootloader image back to the device from bulk mode. I'd doubt it'd work, but worth checking out.

freebee269 said:
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?
Click to expand...
Click to collapse
Yes, you can go back to the 5.0.x system after updating to 5.1
I just flashed the ENTIRE 5.0.1 factory image, minus the bootloader.
You must obviously already be bootloader unlocked to do so.
No ill-effects whatsoever.
If you do go back to 5.0.x, make sure you flash the radio for it as well. There's a chance you'll not be able to receive calls if on LTE with 5.1's radio, as was the case for me. Only on 3g/4g did calls go through (I'm on TMO, btw)

I had the same calls issue on T-Mobile, I was on a 5.0.2 ROM and had flashed the 5.1 bootloader and radio and a friend said she called me but I didn't get a call. When she came over I had her call me again but got nothing, I could call her though. I booted to a 5.1 rom and had her call me and my phone rang.

Hey I have a fully working N6 running stock 5.1, what can I do to help?

opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
swimdude1120 said:
Hey I have a fully working N6 running stock 5.1, what can I do to help?
Click to expand...
Click to collapse
Run those commands if you are rooted and quote opssemnik, the one with the commands, so he can see them.
If you do, put the word SPOILER in brackets [] and then the output, the /SPOILER in the brackets []
Sent from my Nexus 6

broken partition table, please help - newbie

Hi, I recently decided to dust off my old nexus 10 and install a current version of android on it. With some guides I unlocked the bootloader, installed TWRP, installed AOSP Android 9.0 Pie and then when I wanted to install open gapps I got an not enough space error. After some searching I found a post with a repit file, which should automatically increase the size of my system partition. Unfortunatelly while this repit thing was running the display flickered for a second and the resize failed. (Stupid as I am I didnt make screenshot of the error :/) I think the screen flickering thing is a hardware problem, as it did this even without cutum recovery/rom from time to time. But i always thought it was only a problem with the the screen backlight, as it had no impact on any running software before. (I replaced the battery now to maybe fix this.) But my main problem now is, that TWRP cant mount any partitions. I think the partition table is broken.
fdisk -l doesnt output anything
fdisk -l /dev/block/mmcblk0
Code:
warning: GPT array CRC is invalid
Found valid GPT with protective MBR; using GPT
Disk mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 8192 49151 20.0M 0700 efs
2 49152 65535 8192K 0700 param
3 65536 98303 16.0M 0700 boot
4 98304 163711 31.9M 0700 recovery
5 163712 163839 65536 0700 metadata
6 163840 172031 4096K 0700 misc
7 172032 376831 100M 0700 cache
8 2301952 2826239 256M 0700
9 2891776 61063167 27.7G 0700 userdata
I think 8 should be the corrupted system partition. But isnt there also "data" missing?
Should I resize 8 to 376832 - 2891775 and fix the missing name?
ls /dev/block
Code:
loop0 loop5 mmcblk0boot1 ram11 ram2 ram7
loop1 loop6 platform ram12 ram3 ram8
loop2 loop7 ram0 ram13 ram4 ram9
loop3 mmcblk0 ram1 ram14 ram5 zram0
loop4 mmcblk0boot0 ram10 ram15 ram6
There mmcblk0p7, mmcblk0p8, etc. are missing. How can I fix this?
Can someone help me please? I dont want to break it even further :/

I think I solved it. I downloaded the factory image and ran flash-all. Now the stock rom is running again and I can try flashing a custom rom again.