Related
hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,
http://forum.xda-developers.com/showthread.php?t=2087567
blastman said:
hi all,
So, I've been a bit of a idiot.
In a nut shell I was trying to manually remove the flash count and followed the wrong tut.
I did dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732 and now when i try to boot the note I dont get the Samsung logo splash screen, I get a screen full of static.
I can access the recovery partition, I can also access in download mode with odin.
If I try to flash the stock rom, it completes ok but doesn't auto restart and stays on the odin mode screen.
I do get E:\ unable to mount /efs when i wipe the cache's.
I have a 2nd note 10.1 (both n8010) so I'm hoping I can fix/copy/image from the 2nd working device.
Any ideas on how to fix? or is it now an expensive paper weight?
I have flashed the stock firmware and rom from samsung-mobile but no joy.
thanks,
Click to expand...
Click to collapse
You are in a tough situation my friend
I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)
Scorpion_Ibm said:
I think as long as the recovery and odin work there is a chance...
can you give me the link to that tutorial .. I think i may help
Or do you remember where that sector was??
Anyways you may try to backup both devices EFS (backup that of the non working device in case you need it for anything) .... (But i think the EFSPro wont work) (you may do that using EFSpro or i think it may be done through the shell by "dd if=dev/block/mmcblk0p? of=/sdcard/efs.img" where "?" is the number of EFS partition you can know that from shell command mount "i think its mmcblk0p3") .... then restore the EFS of the working device to the non-working one (EFS pro or using "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p?" "i think its mmcblk0p3")
I hope this would succeed although i red that it contains MAC address data which may prevent both devices connecting to same network
(N8010 has no connection to cellular networks so i think no problem)
Click to expand...
Click to collapse
this?
http://forum.xda-developers.com/showthread.php?p=37465299
jaydubbbbs said:
this?
http://forum.xda-developers.com/showthread.php?p=37465299
Click to expand...
Click to collapse
But before all these go to shell and try "dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img" and "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
if these commands succeed you would have a backup of old efs before changing any thing (keep it in a safe place)
Look you may try just backing up and then restoring the same EFS of the device
Try this first: use the tar command to copy the files of EFS "tar -cvf /sdcard/EFS.tar /dev/block/mmcblk0p3"
then do " mke2fs /dev/block/mmcblk0p3" the last thing is to restore the tar with "tar -xvzf /sdcard/EFS.tar -C /dev/block/mmcblk0p3"
I prefer you try what i said first as it's shorter and makes nearly the same thing except that it takes all files not just the nv_data.bin
You can then try that tutorial in the link i think it works and you can get the that file nv_data.bin from your other device or from the non-functioning one if you can extract it from the tar backup in the first step
Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks
blastman said:
Cheers for the replies guys.
I'll find the tut I followed and post a link.
I'll also look into the link and suggestions you've mentioned.
My main issue seems to be that I can't get a adb connection to the device as it won't boot.
Even with cwm 6.1 installed, I still can't connect. Bear in mind, I've flashed back to stock but not been able to boot it to put it into usb debugging mode. does this mean I'll never be able to get a shell open?
I have managed to create a efs.img from the working device but have no way to push to the broken one.
Any suggestions?
Thanks
Click to expand...
Click to collapse
You say that adb wont work even from CWM??
Try this and see if it works http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html
yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.
sadly that link is no good.
I'm able to connect to the working device on the same cwm recovery version, using the same cable, so setup and PC are ok.
I dont know if the roms are the same (maybe not) but I'll flash the broken one with a custom 'pre rooted' rom in case it helps.
blastman said:
yep, even when booted into cwm recovery i still can;t connect to adb
just downloading a custom rom now to see if it's the stock rom causing the issue.
although I am able to access adb in cmw recovery from the other working device, even with USB debugging turned off.
Click to expand...
Click to collapse
Ok try another rom as i think roms have diferences in adb !!
if not working also and If you know you can safely flash a new recovery .. try TWRP it has an inbuilt shell .. the keyboard is not that good but you can try it better than nothing
ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,
blastman said:
ok so....
I've flashed an different custom rom via cwm install from ext_sdcard. After a reboot I now have the samsung logo back!!!!
It's hung on the samsung logo for a wile now, 5 minutes or so, but I'll let it sit there for a good 30 minutes to be sure.
I'll see what happens from this rom flash, but failing this I'll stick TRWP on and have a go with the inbuilt shell. even if i can mount ext sd I should be able to restore the block i over wrote.
getting closer!!!
thanks so far,
Click to expand...
Click to collapse
Good to hear .. i hope it finishes the problem .. but in case it fails before flashing TWRP try from adb .. adb kill-server then adb start-server and adb usb and see if it works
will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.
blastman said:
will do, thanks.
I've just noticed that the command i ran I outputted to mmcblk0 and your commands refer to mmcblk0p3.
Am i right in guessing the the 0 part lists the disk and the px part is referring to the partition on that disk (so to speak)?
so my original command which broke it basically wiped the internal storage? this would explain a lot about failed connections as well.
Click to expand...
Click to collapse
Did the device work or did you manage to get adb connection??
Anyways ... from what i read during searching is that if=/dev/zero and bs=1 count=1 seek=3145732 parts of your command writes zeros only to one byte, one time after seeking 3145732 blocks of the storage which seems to be in EFS partition which says cant mount ... So the commands i wrote are to take a backup of whatever files in there then format the drive and restore the files back to it ... after formating using mke2fs reboot the device before restore and see if it shows the cant mount message again
arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again
how about doing a dd if=efs.img of=/dev/block/mmcblk0p3??
I got a efs.img from efs pro on the working device..
blastman said:
arh ok, that makes sense.
I've managed to tar the efs files form the working device.
I then opened the shell in twrp and did a mke2fs /dev/block/mmcblk0p3 which completed ok.
But when i try to tar -xvzf EFS.tar -C /dev/block/mmcblk0p3 (from the external sd dir, it tells me that the mmcblk0p3 isn;t a directory.
any ideas?
thanks again
Click to expand...
Click to collapse
try remove -C from the command it's for directory my mistake
and you can also try dd with (if=/"path of extsd"/EFS.img) but try the tar first .... after that see if it tells you cant't mount EFS by opening mount and select EFS and see if it becomes with an 'x' then going to the upper right corner of the screen and pressing the icon beside back and home and see if it shows cant mount EFS
sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?
blastman said:
sorry, before you replied i went and did a dd if=efs.img of=/dev/block/mmcblk0p3
I then flashed the stock ROM and BOOM!! im in!!
YEAH BABY!!!
only issue now is that the boot loader isn't quite right.
1 - it doesn't show the 'Samsung Galaxy Note 10.1" splash screen
2 - instead of above I get a screen showing the last thing i was doing, ie, download mode, but with static across it.
any ideas on how to correct this?
Click to expand...
Click to collapse
Can you answer some questions??
what do you mean by you are in?? .. can you get to android or not yet?? ... what do you mean with getting download mode with static ??
would you try going to recovery and clear cache and dalvik cache to try??
sorry, by I'm in I mean that I can now boot to Android.
when i say download mode with static, image the download screen but fuzzy and punctuated with white nose.
I've done a cache format and a reset to factory but I still get the same issue.
Also, I'm still unable to get an adb connection to the device.
I have noticed that the serial number has now changed to the same as the working device but thats expected as we copied the efs contents from one to the other.
thanks for all your help. you saved my bacon
I went to use my Nexus 5 (D821) earlier today but it wouldn't turn on. Holding power didn't seem to work, so I assumed the battery was flat and left it charging for a couple of hours. Now it gets stuck at the first black and white "google" logo forever. The device is unlocked and rooted, but was working fine, and nothing was changed leading up to the issue.
I'm able to access the bootloader and fastboot still, but nothing seems to work.
Attempting to flash a partition (fastboot flash recovery twrp.img):
FAILED (remote: flash write failure)
Attempting to erase a partition (fastboot erase userdata):
FAILED (remote: failed to erase partition)
I can boot TWRP by running fastboot boot twrp.img, but attempting to mount any partitions results in errors such as:
E: Unable to find partition size for /system
E: Unable to mount /system
Also, attempting to install a zip shows that internal storage is 0MB in size.
At this stage, I suspect the flash memory has died a horrible death, and I'm trying to work out how to set the tampered and unlocked flags back to false to I can return it under warranty, however this is proving difficult too. If I run 'fastboot oem lock', it appears to succeed (the bootloader even changes to 'LOCK STATE - locked'), but as soon as I reboot the device, it reverts back to unlocked, and the padlock shows up again.
I've even tried manually via:
echo -ne "\x00" | dd obs=1 count=1 seek=16400 of=/dev/block/platform/msm_sdcc.1/by-name/misc
echo -ne "\x00" | dd obs=1 count=1 seek=16404 of=/dev/block/platform/msm_sdcc.1/by-name/misc
but these don't seem to have any effect on the flags.
So now I'm out of ideas, and just hoping I can set these flags back before sending the device for warranty. Any ideas?
There's nothing you can do about it now. Just send it back. I doubt they'll blame flash memory failure on unlocking the bootloader
Sent from my Nexus 5 using Tapatalk
I was helping a guy yestreday, he had a some problem like you. When you turn on the phone, the flashchip shuts off for some reasone. I was looking for the mmc or mmcblk device in the /dev then /dev/block after I booted a twrp like you, but I could not find any device called mmcblk or mmc, even the partitions was missing like mmcblk0p1 etc...
cat /proc/partitions just give me an empty screen, that it didnt find any storage device.
rootSU said:
There's nothing you can do about it now. Just send it back. I doubt they'll blame flash memory failure on unlocking the bootloader
Click to expand...
Click to collapse
I'm just a little worried they'll refuse to honour the warranty without even bothering to check the hardware. Aren't they within their right to do this given the warranty terms? Sounds like I don't have any choice!
bitdomo said:
I was helping a guy yestreday, he had a some problem like you. When you turn on the phone, the flashchip shuts off for some reasone. I was looking for the mmc or mmcblk device in the /dev then /dev/block after I booted a twrp like you, but I could not find any device called mmcblk or mmc, even the partitions was missing like mmcblk0p1 etc...
cat /proc/partitions just give me an empty screen, that it didnt find any storage device.
Click to expand...
Click to collapse
I'm seeing a bunch of partitions listed when I run 'cat /proc/partitions', so I guess my issue might be a little different.
What I'm confused about though, is if the NAND flash is truely dead, how does the bootloader run? Isn't this stored on the same NAND flash chip? Also, aren't the lock state and tamper flags on the same chip? If so, how are these still accessible, but not writeable? I'm guessing it's not a complete failure, but only a partial one... Thoughts?
It surely isn't fully dead. It could be a corrupt partition or bunch of partitions being the issue. But the bootloader also isn't fully functional as you cannot relock it.
You definitely need to reset tamper flag for RMA, but for warranty, don't they have to prove that the hardware fault was caused by the unlocked bootloader? I know Samsung refuse warranty on modification but I don't think Google do. It is a developer phone after all.
That said, you've no choice as I can see. I'm not aware of anyone having warranty rejected or approved with an unlocked bootloader yet
sir_earl said:
I'm seeing a bunch of partitions listed when I run 'cat /proc/partitions', so I guess my issue might be a little different.
What I'm confused about though, is if the NAND flash is truely dead, how does the bootloader run? Isn't this stored on the same NAND flash chip? Also, aren't the lock state and tamper flags on the same chip? If so, how are these still accessible, but not writeable? I'm guessing it's not a complete failure, but only a partial one... Thoughts?
Click to expand...
Click to collapse
Can you post the outpot for the cat /proc/partitions command?
rootSU said:
I know Samsung refuse warranty on modification but I don't think Google do. It is a developer phone after all.
Click to expand...
Click to collapse
I'm not sure if the process is different here in New Zealand. I was under the impression LG deals with warranty issues here, and Google isn't involved?
bitdomo said:
Can you post the outpot for the cat /proc/partitions command?
Click to expand...
Click to collapse
I'll have to take a photo, as I can't find any way to run adb or save the log off. Give me a minute!
sir_earl said:
I'll have to take a photo, as I can't find any way to run adb or save the log off. Give me a minute!
Click to expand...
Click to collapse
you can do the whole thing with adb from your pc.
you need the naked usb drivers for that, and if you running windows 8 or 8.1 you have to turn off driver signiture enforcement inorder to isntall the drivers.
and then with adb shell command you can use your cmd window on the pc as a terminal window on your phone
bitdomo said:
you can do the whole thing with adb from your pc.
you need the naked usb drivers for that, and if you running windows 8 or 8.1 you have to turn off driver signiture enforcement inorder to isntall the drivers.
and then with adb shell command you can use your cmd window on the pc as a terminal window on your phone
Click to expand...
Click to collapse
adb was working with the Nexus when the rom was booted, but can't seem to find the device when running TWRP or fastboot (not sure if the server can run there?) Will the naked usb drivers resolve this issue?
Regardless, I've attached the photo with the partitions.
sir_earl said:
I'm not sure if the process is different here in New Zealand. I was under the impression LG deals with warranty issues here, and Google isn't involved?
Click to expand...
Click to collapse
google are only involved in that all this is done on behalf of them. They commission the phone. But the mandate is that it's a developer phone
rootSU said:
google are only involved in that all this is done on behalf of them. They commission the phone. But the mandate is that it's a developer phone
Click to expand...
Click to collapse
That's somewhat comforting. We shall see how it goes! Not looking forward to being without a decent phone for however long the warranty process takes though!
sir_earl said:
That's somewhat comforting. We shall see how it goes! Not looking forward to being without a decent phone for however long the warranty process takes though!
Click to expand...
Click to collapse
Please do let us know how you get on. It will be interesting to confirm how the unlocked bootloader goes down.
sir_earl said:
adb was working with the Nexus when the rom was booted, but can't seem to find the device when running TWRP or fastboot (not sure if the server can run there?) Will the naked usb drivers resolve this issue?
Regardless, I've attached the photo with the partitions.
Click to expand...
Click to collapse
Yes naked drivers will help you, but keep in mind that fi you are running windows 8 or 8.1 you have to turn of driver signiture enforcement.
Could you mount the system partition?
$ mount -o rw /dev/block/mmcblk0p25 /system
$ cd /system
and try to make folder like
$ mkdir asd
and then remove it
$ rm -rf asd
if that works we can write the flash chip, so it must be some kind of partition corruption.
bitdomo said:
Yes naked drivers will help you, but keep in mind that fi you are running windows 8 or 8.1 you have to turn of driver signiture enforcement.
Could you mount the system partition?
$ mount -o rw /dev/block/mmcblk0p25 /system
$ cd /system
and try to make folder like
$ mkdir asd
and then remove it
$ rm -rf asd
if that works we can write the flash chip, so it must be some kind of partition corruption.
Click to expand...
Click to collapse
I'm able to use adb now, so that's a start.
Trying to mount with the command you gave gives:
mount -o rw /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
sir_earl said:
I'm able to use adb now, so that's a start.
Trying to mount with the command you gave gives:
mount -o rw /dev/block/mmcblk0p25 /system
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
Click to expand...
Click to collapse
for me this command works.
I use twrp 2.6.3.4
bitdomo said:
for me this command works.
I use twrp 2.6.3.4
Click to expand...
Click to collapse
Running same twrp here, so I guess it's failing because it can't mount the partition due to some kind of corruption.
rootSU said:
Please do let us know how you get on. It will be interesting to confirm how the unlocked bootloader goes down.
Click to expand...
Click to collapse
Will do. I'm curious though, if random corruptions like this can occur, isn't it possible that the bootloader could appear unlocked if it's reading a corrupt piece of memory? If that's the case, they can't just assume the user has unlocked the bootloader in cases where the flash chip fails, correct? Granted, this isn't the case here, but it must have some impact!
sir_earl said:
Running same twrp here, so I guess it's failing because it can't mount the partition due to some kind of corruption.
Click to expand...
Click to collapse
I don't know what else you could do. You can try to lock and reset tamper flag by mmcblk0p15 and not with ...../by-name/misc, if it works probably you could not unlock your bl again.
Try to lock bl and reset tamperflag (adb shell):
echo -ne "\x00" | dd obs=1 count=1 seek=16400 of=/dev/block/mmcblk0p15
echo -ne "\x00" | dd obs=1 count=1 seek=16404 of=/dev/block/mmcblk0p15
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
sir_earl said:
Will do. I'm curious though, if random corruptions like this can occur, isn't it possible that the bootloader could appear unlocked if it's reading a corrupt piece of memory? If that's the case, they can't just assume the user has unlocked the bootloader in cases where the flash chip fails, correct? Granted, this isn't the case here, but it must have some impact!
Click to expand...
Click to collapse
bl lock state and tamper flag stored at the misc partition, so bl can read it but ti seems it fails to write it, i don't know the reasone why, but it seems tha path to the partitions by-name is missing
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
kataik95 said:
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
Click to expand...
Click to collapse
I think your Stuck with the bootloader..
The issue about im feeling lucky thing... I think you have malware on your device... Never heard of or seen nothing like that
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
moonbutt74 said:
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
Click to expand...
Click to collapse
Thanks man i havent tried it yet but i hope it will help
Sent from my SM-G900F using XDA Free mobile app
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
FGM 11 said:
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
Click to expand...
Click to collapse
I tried everything but nothing helped. And now i have the same efs problem like you. I hope that somebody can help us
This worked for the galaxy tab 3 10.1
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
partitions
moonbutt74 said:
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
Click to expand...
Click to collapse
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Instructions Matter
kataik95 said:
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Click to expand...
Click to collapse
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
moonbutt74 said:
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
Click to expand...
Click to collapse
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
kataik95 said:
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
Click to expand...
Click to collapse
Sure, no problem. Hope everything works out. :good:
m
moonbutt74 said:
Sure, no problem. Hope everything works out. :good:
m
Click to expand...
Click to collapse
Imagine after 2 services where the could't fix I took to a 3rd. They could fix it so it works its on 4.0.4 in some kind of factory mode (strange). I can not quit from this mode and odin not works as well. In the recovery it says efs is invaild. What is that fw?
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
EDIT: Finally, I managed to restore my phone. To save you from reading the whole thread, which is full with creative ideas to unbrick the phone you can jump to the last post. There I described my final solution and ruled out, what probably my mistake with the MiFlash Tool was.
Muenzi said:
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
Click to expand...
Click to collapse
Did you do anything before you noticed your partitions are fried?
jjgvv said:
Did you do anything before you noticed your partitions are fried?
Click to expand...
Click to collapse
Yes I installed OrangeFox as a recovery. From there on, everything get messed up.
If nescessary to know, the BL is unlocked of course. I backuped all data from the phone. So I do not need a safe way to get them back. I am happy when the phone can operate a reliable OS again.
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
jjgvv said:
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
Click to expand...
Click to collapse
Thank you for your help. Can you tell me please to which partition this has to be flashed? And what will be the outout I can send you (probably a log file?).
So lets say commands instructions like
fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
would be really cool to avoid confussion and mistakes.
Anyway, it is 3 am here and I have to get up in around 4 hours. So I will leave and take a nap. Maybe I can ask you to wait for my reply? And again, thank you so much for your help.
Best regards
Stephan
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Muenzi said:
And what will be the outout I can send you (probably a log file?).
Click to expand...
Click to collapse
I need What happens in the cmd window like:
Code:
Desktop-XCRXAJB > C:\platform tools >
fastboot flash system system-roar-arm64-aonly-vanilla.img
Reported max download size = 2580192068 bytes （ 2.7 GB）
sending 'system' （2070713691 bytes）
OKAY （1576 secs）
writing 'system' （2070713691 bytes）
FAILED （remote : failed to mount 'system' : system partition layout is 'null'）
jjgvv said:
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
Thats the outout:
Code:
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (786328 KB)...
OKAY [ 21.029s]
writing 'system' 1/3...
FAILED (remote: Partition not found)
finished. total time: 21.031s
So, I have to go now. See you in a couple of hours.
adb shell
parted /dev/block/mmcblk0
print
see you soon
jjgvv said:
adb shell
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Muenzi said:
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Click to expand...
Click to collapse
recovery
jjgvv said:
recovery
Click to expand...
Click to collapse
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Muenzi said:
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Click to expand...
Click to collapse
oh so probably Orangefox fried your other partitions
jjgvv said:
oh so probably Orangefox fried your other partitions
Click to expand...
Click to collapse
What happens when flash TWRP
jjgvv said:
What happens when flash TWRP
Click to expand...
Click to collapse
I already did. The problem persists. To clarify, all the last steps were already performed with TWRP as recovery. But the problem occurred first under TWRP.
Is there any chance to recreate the partition table?
maybe but complicated
Hi you may try boot from sd card
[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
I'm a mechanical engineer, not an IT guy. I can fix machines, perhaps, but not bricked phones. So try anything at your own extreme risk. This is NOT a step by step guide. DEVICE: QMobile Z8, same as Wikio Ridge 4G, (MSM8916). Running Android...
forum.xda-developers.com
jjgvv said:
maybe but complicated
Click to expand...
Click to collapse
Okay if you have any idea, let me know.
or this https://forum.xda-developers.com/t/...dor-partition-for-pt-gsi-rom-mi3-mi4.3878995/
this is create vendor but should be possible to create all