Related
Hello everyone!
I have a galaxy s i9000b with 8gb.
was using the Christian rom a gingerbread 2.3.3.
of a sudden he started to restart on lopping and ended up entering the system after some time. until it stopped booting the system permanently.
this is a recurring problem found much information on google about it!
solves the problem most easily by using the stock rom tim.
in my case.
after much research I learned to use the adb basically and was following a tutorial
parted on then it should go to the directory / dev / block and find mmcblk0.
but he was not there!
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
though I see him there in the adb shell browsing the folder / etc
finally began to get discouraged with the problem and for not having found the mmcblk0 there in / dev / block.
I'm beginning to think that with the 8GB internal memory of my beloved GS I9000B actually damaged.
Can someone help me confirm this or help me somehow?
just pointing out that the system does not start, but I have access to recovery mode and download
I'm using the recovery is the CMW RECOVERY v2.5.1.0 SPEEDMOD ULFK
to have access to the cell by adb!
sorry for bad english!
re:
Very sorry to hear this . You can try to find some solutions in this thread:
http://forum.xda-developers.com/showthread.php?t=845708
There are some more topics here on xda, try anything, before a year, i had one i9000 int dead, and there is no solution , hope your problem can be solved.
At the end if nothing helps, now we have some sort of fix, and this can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=973687&page=3
look at Catanni post, this must work if anything else fail. This is vold file needed for this.
Good luck.
hey! tanks man!
thanks for the reply! I'll read all these topics and then I see that fstab!
then write here what happened!
Thank you so!
bispoom said:
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
Click to expand...
Click to collapse
your command that you used above is incorrect.
To transfer from phone to computer use "pull"
To transfer from computer to phone use "push"
re: read this please
It is very important, before u start flashing and work with abd, to do backup your /efs folder if u dont have already. If your phone really have dead internal sd then is almost impossible to recover your imei if /efs folder become corrupted. This is covered by this thread:
http://forum.xda-developers.com/showthread.php?t=859914
After that you can try to flash some older firmwares, try with repartition, try to manually set up partitions, and u have full procedure in first link on my previous post.
You can try this command from adb:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
this command will mount your internal sd in windows, and then u can try to partition in windows
In second link, is procedure how to change internal and external sd, this is last that u can try (that mean that your internal sd is really dead). Attached fold.fstab will make your external sd to work like internal (this is not tested by myself, but a lot of people have succsess with this).
Bye and good luck, and please tell us how progress work.
hi!
result of command:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
is here
cannot create /sys/devices/platform/s3c-usbgadget/gadget/lun1/file: directory no
nexistent
to access the folder dev / block there is no a mmcblk0
and not one or the other as mmcblk0p1 or p2
and inside the folder / sys/devices/platform/s3c-usbgadget/gadget / folder does not exist lun1 / ...
sorry for bad English, and tanks for the help
re:
If mmcblk do not exist, best u can do is to try to flash with repartition in odin. If this does not help, always can try this
http://forum.xda-developers.com/show...=973687&page=3
Wish u best
broken link
hi!
man tanks for the help but this link
http://forum.xda-developers.com/show...=973687&page=3
is broken!!!
Please Help Me :crying:
Make Backup System Partition EFS and ModemFS and upload
Your device MUST be GT-I8190 ONLY! and NOT-I8190N GT or GT-I8190L.
Here's a dd Command To Enter In Terminal Emulator
Code:
[B][FONT=Courier New]dd if =/dev/block/mmcblk0p11 of=/sdcard/efs.img
dd if =/dev/block/mmcblk0p12 of=/sdcard/modemfs.img[/FONT][/B]
After Successful, Navigate to your internal sd card, download it and paste the link here.
I Want to Try to Fix Issues Baseband Version: XXXX
Thank You :angel:
faisalxp said:
Please Help Me :crying:
Make Backup System Partition EFS and ModemFS and upload
Your device MUST be GT-I8190 ONLY! and NOT-I8190N GT or GT-I8190L.
Here's a dd Command To Enter In Terminal Emulator
Code:
[B][FONT=Courier New]dd if =/dev/block/mmcblk0p11 of=/sdcard/efs.img
dd if =/dev/block/mmcblk0p12 of=/sdcard/modemfs.img[/FONT][/B]
After Successful, Navigate to your internal sd card, download it and paste the link here.
I Want to Try to Fix Issues Baseband Version: XXXX
Thank You :angel:
Click to expand...
Click to collapse
Double post, and none of them in the right section..
This has nothing to do with development, right?
Ok, no one is gonna give you a copy of their /EFS partition.
If you wonder why you can read here.
Sorry I couldn't be of more help.
We just need a legit fully working modemfs.img and flash it via dd command.
Code:
dd if=/sdcard/modemfs.bin of=/dev/block/mmcblk0p12
Benzonat0r said:
We just need a legit fully working modemfs.img and flash it via dd command.
Code:
dd if=/sdcard/modemfs.bin of=/dev/block/mmcblk0p12
Click to expand...
Click to collapse
Thanks Man... I thought Code That Can Only File Extract. IMG, I Think It Can not Extract File. BIN...I Want To Try It.
Btw What is Your opinion about Post Me The Last To Threads http://forum.xda-developers.com/showthread.php?t=2151288 :victory:
When you flash modem.bin file the image will be extracted to your /modemfs partition.
I have the same problem, I have flashed a working modemfs, but I it still does not work, I think that I also need an EFS file
evolution_x said:
I have the same problem, I have flashed a working modemfs, but I it still does not work, I think that I also need an EFS file
Click to expand...
Click to collapse
here backup from the modemfs>(mmcblk0p12) and efs>(mmcblk0p11)
http://dl.dropbox.com/u/2632841/mmcblk0p11.img
http://dl.dropbox.com/u/2632841/mmcblk0p12.img
thanks ! I have flashed the modem_fs from someone else, but I did not have the efs too, so it did not work. Now I don't have the phone, I sent my phone to a service company, they told me that there are 50% chances they can repair it and i takes 2-3 days. And in case they can repair it, it will cost me $40
I will save your files to try them in case they cannot repair it.
evolution_x said:
thanks ! I have flashed the modem_fs from someone else, but I did not have the efs too, so it did not work. Now I don't have the phone, I sent my phone to a service company, they told me that there are 50% chances they can repair it and i takes 2-3 days. And in case they can repair it, it will cost me $40
I will save your files to try them in case they cannot repair it.
Click to expand...
Click to collapse
just look on the website> http://forum.xda-developers.com/showthread.php?t=2165508
if you have the exactly the same problem you will help further the things that I've already posted here, for me it worked. I've also just thought it needed a new cell phone yesterday folded
my cell phone was dead until yesterday
First, sorry for my English.
Someone would have these files:
dd if =/dev/block/mmcblk0p11 of=/sdcard/efs.img
dd if =/dev/block/mmcblk0p12 of=/sdcard/modemfs.img
for samasung I8190L??
thank you very much
Trying to recover S3 mini. When received, would not boot (hung on initial Samsung logo). Powered up in download mode. Loaded "I8190XXAMC1_I8190OJVAMC1_HOME.tar.md5" with Oden. Now boots (takes about 3 minutes) but device information is displayed on the main screen (attachment.
Can't connect with Kies.
Can't connect with S3 Mini Toolkit.
Can someone explain what state it is in and what to do next?
Your carrier and location?
Sent from my GT-I8190 using Tapatalk 4
Carrier and location
ppero196 said:
Your carrier and location?
Sent from my GT-I8190 using Tapatalk 4
Click to expand...
Click to collapse
Straight Talk, Atlanta
Try reflashing unbranded EU ROM
Sent from my GT-I8190 using Tapatalk 4
Where to find it
I'm a NOOB. Where do I find unbranded EU ROM?
Barry2013 said:
I'm a NOOB. Where do I find unbranded EU ROM?
Click to expand...
Click to collapse
Here:
http://www.sammobile.com/firmwares/2/
You could also try to install a custom ROM and recovery. I recomend enox revange.
http://forum.xda-developers.com/showthread.php?t=2146129
Barry2013 said:
Trying to recover S3 mini. When received, would not boot (hung on initial Samsung logo). Powered up in download mode. Loaded "I8190XXAMC1_I8190OJVAMC1_HOME.tar.md5" with Oden. Now boots (takes about 3 minutes) but device information is displayed on the main screen (attachment.
Can't connect with Kies.
Can't connect with S3 Mini Toolkit.
Can someone explain what state it is in and what to do next?
Click to expand...
Click to collapse
you are in factory mode, did you lose also lockscreen and power menu??
you must be rooted:
with a root explorer go to efs/FactoryApp/factorymode, open factory mode file and change it to on then save, long press on the file and fix permission (tick all) save, reboot
Factory mode
samersh72 said:
you are in factory mode, did you lose also lockscreen and power menu??
you must be rooted:
with a root explorer go to efs/FactoryApp/factorymode, open factory mode file and change it to on then save, long press on the file and fix permission (tick all) save, reboot
Click to expand...
Click to collapse
Factory mode sounds right. No lockscreen, No power menu. Always reboots with USB debugging disabled.
Looks like the /efs folder is corrupted. Get "Failed to mout /efs" when booting in recovery mode.
Searched forums. Not clear what to do next.
i've got same situation "maybe"..
but my s3 mini can use normally but except charge the phone...
phone cant charging up battery, just icon appear but not up percentage of charge..
and usb not detected..
i dont know exactly the prob of mine..
maybe "i've rooted and install Rom and restore Stock Rom" and tried to change some icon in Stock Rom..
and its start the problem with when charging up to 99% suddenly drop down one by one percentage battery..
and send to samsung warranty, they send me back the phone since my phone is rooted "i assume", haha.. they didn't tell me y not repaired....
so solution :
install back Custom Rom, and restore back stock rom ( fortunately i've got backups )
and tried to charging and tried usb to pc, it works normally...
i thought port usb and charging damage and nearly want sent to shop to repair.. haha:laugh:
Barry2013 said:
Factory mode sounds right. No lockscreen, No power menu. Always reboots with USB debugging disabled.
Looks like the /efs folder is corrupted. Get "Failed to mout /efs" when booting in recovery mode.
Searched forums. Not clear what to do next.
Click to expand...
Click to collapse
mount efs partition before editing efs folder, type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p11
mount -w -t ext4 /dev/block/mmcblk0p11
reboot
samersh72 said:
mount efs partition before editing efs folder, type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p11
mount -w -t ext4 /dev/block/mmcblk0p11
reboot
Click to expand...
Click to collapse
I was spending way too much time on this, so sent it off to a repair shop. They have had it for 3 months and came to the conclusion the folder containing the ENS is corrupted and they don't know how to fix that. I think this is the /efs partition.
The last suggestion on this forum was to make and mount the efs partition from a terminal emulator. Can anyone tell me how to install a terminal emulator?
Barry2013 said:
I was spending way too much time on this, so sent it off to a repair shop. They have had it for 3 months and came to the conclusion the folder containing the ENS is corrupted and they don't know how to fix that. I think this is the /efs partition.
The last suggestion on this forum was to make and mount the efs partition from a terminal emulator. Can anyone tell me how to install a terminal emulator?
Click to expand...
Click to collapse
if you r on stock rom i think you must be rooted. and i think you need busybox. an emulator is for example THIS one from store.
vecaicl difcovered
i sufered from the same problem its the efs folder its corupted and i solve the problem with this prerooted stock rom http :// goo.gl/c9 Tmu
Hello,
I have posted on various threads that i can fix DRK (Device root key), but after large demand in PM for the fix i have decided to make a tutorial, since i don't have much time to help everyone, this tutorial is only tested on SM-N910C, could work on other variants of Exynos, perhaps snapdragon but NOT TESTED!!!!
So how is DRK broken? Usually when you flash roms and stuff you should have EFS backup as its most important thing while rooting samsung phones, but some people just dont do that, other people use boxes like z3x for unlocking and they wipe EFS, while unlocking phones the process sometimes changes IMEI number and leaves device root key wiped. These modifications sometimes make it hard to revert back to stock and i personally had problems with device suddenly rebooting etc... with this tutorial we will try to mitigate these problems.
PLEASE DO NOT PROCEED WITHOUT SHELL/ADB KNOWLEDGE IF YOU MESS SOMETHING UP YOU WILL LOOSE IMEI AND WILL HAVE A BRICK! You have been warned and i am not to be held liable!
First we need to make backup of your EFS, we will use TAR and shell which is most reliable way (Partition Backup is good too), with adb shell:
1. su
2. cd /efs
3. tar czf efsbackup.tgz *
4. mv efsbackup.tgz /data/media/0/
Now go to your internal memory in My Computer and there should be file called efsbackup.tgz copy it somewhere safe on your PC. This is your efs backup!
Now we need to take two files which we will reuse latter, you can extract them from efsbackup.tgz but this is easyer:
1. su
2. cd /efs
3. cp nv_data.bin /data/media/0/
4. cp nv_data.bin.md5 /data/media/0/
Now go to your internal memory and copy nv_data.bin and nv_data.bin.m5 to your desktop, we will need these files later. These files contain your imei!
Now we need to reboot to TWRP and format EFS partition via terminal (We are doing this to force radio to recreate the files we lost while flashing and make system more stable, no reboots etc..)
TWRP --> Advanced --> Terminal type these (These will also fix "Failed to mount /efs (Invalid Argument)) Don't missspell, if you get error no mount in fstab, that is ok!
1. mke2fs /dev/block/mmcblk0p3
2. mount -w -t ext4 /dev/block/mmcblk0p3
3. reboot
Now the system will be booting, once done when you dial *#06# you will see generic IMEI and it's not yours, don't freakout this is how its supposed to be. Radio also recovered your default values in FactoryApp folder which is nice. Now reboot phone twice!
Let's restore nv_data and restore imei, assuming you still have those files in your internal memory do this with ADB:
1. su
2. cd /efs
2. rm -rf /efs/nv_data.bin
3. rm -rf /efs/nv_data.bin.md5
4. mv /data/media/0/nv_data.bin* /efs/
5. chmod 700 /efs/nv_data.bin*
6. chown radio:radio nv_data.bin*
7. reboot
After phone reboots your factory IMEI is back and registering to network properly, now we have achieved stable device no random reboots and clean remade factory EFS!!!
DRK REPAIR PART!
Now lets go to the part of fixing DRK Device Root Key and dm-verity error! I have attached file called prov_data.zip, extract the prov_data folder to your internal memory (This is not a flashabe zip) And run these commands with your ADB Shell:
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
Device root key is now present in your device but not yet active/validated, in order to validate this, you need to flash your factory firmware with ODIN, go to factory recovery and wipe data/factory reset, and dm-verity error is now gone!
SERIAL NUMBER FIX PART
I have attached file called serial_no.zip (Not a flashable zip file), extract the file from it called serial_no open it with notepad or whatever text editor you use and replace XXXXXXXXXXX with your own serial number that is written behind your phone. Now copy serial_no file to your internal memory again and with adb we do this:
1. su
2. cd /efs
3. mv /data/media/0/serial_no /efs/FactoryApp/
4. chmod 700 /efs/FactoryApp/serial_no
Reboot and done, you have your serial number back *#06#!
FACTORY CSC FIX PART
Download the file called csc_repair.zip, inside you will see the file called mps_code.dat, open it with notepad or whatever text editor you use, type in your factory CSC instead of XXX in my file and save. If you cant find your factory CSC, go to Kies or SmartSwitch, initialize firmware, type in your serial number and device model it will show your factory CSC for reinstall, this is your CSC. Now copy mps_code.dat file to your internal memory and again we run ADB Shell:
1. su
2. cd /efs
3. mv /data/media/0/mps_code.dat /efs/imei/
4. chown root:root /efs/imei/mps_code.dat
5. chmod 755 /efs/imei/mps_code.dat
This is it, if you can follow these steps you can get clean factory remade EFS partition, with your own IMEI, Serial Number, CSC Code, DRK/dm-verity fixed. Flashing factory ODIN firmware after this will make your phone work as it should!
i have this issue on the n910t... I have full access and a working phone but it lags a lot... youtube videos stutter and when typing some words they keyboard, well all keyboards stutter too... this began to happen when my phone started showing me this message, you see the phone was unlocked by certfile with octoplus or z3x... then it lost signal but when i tried to wipe efs, the phone recovered its own imei and serial... So i unlocked it normally with z3x but had to downgrade the modem from EPE3 to DOK2 to unlock it.... then i restored the complete firmware to the latest version of android 6.0.1 and it showed me the DRK problem..
I'm going to try this tutorial and see it this stops all the stuttering every 8 seconds,..
SeerePetrova said:
i have this issue on the n910t... I have full access and a working phone but it lags a lot... youtube videos stutter and when typing some words they keyboard, well all keyboards stutter too... this began to happen when my phone started showing me this message, you see the phone was unlocked by certfile with octoplus or z3x... then it lost signal but when i tried to wipe efs, the phone recovered its own imei and serial... So i unlocked it normally with z3x but had to downgrade the modem from EPE3 to DOK2 to unlock it.... then i restored the complete firmware to the latest version of android 6.0.1 and it showed me the DRK problem..
I'm going to try this tutorial and see it this stops all the stuttering every 8 seconds,..
Click to expand...
Click to collapse
I am not sure if it will work on N910T variant, but you can try it. DRK error happened on your note because z3x wipes EFS and then writes new nv_data.bin, but by wiping it destroys your prov_data/dev_root folder which contains DRK. If you think your EFS partition created your problem, you can start from the start and format EFS to make it factory and then proceed.
Hey there!
I recently bought a used Note 4 910C. I was told by the shopkeeper that it has never been tempered with. But OTA update fails bcuz of DRK error. I guess someone did try something with it previously. I manged to update Marshmallow via ODIN.
yesterday I rooted it and followed your DRK REPAIR Part. flashed via ODIN for validation but the error still exists. I did not do the whole method from the beginning ( I backed up EFS and nv_bin). Plz tell me what did I do wrong.
Another thing that may be of some importance. The serial no was different form phone's back in just one letter in the middle. Instead of '5' it was showing 'S'. I wonder it can not be by mistake. there must be some messing up previously.
Anyway I followed ur method of SERIAL NO repair and managed to repair the serial no. The IMEI was already a match.
Plz help me what should I do for DRK repair.
Regards.
Usually when you restore prov_data folder properly, you need to go to twrp, format system, data and cache. Then with odin flash stock firmware with your own csc code (do csc repair if its not a match). After that phone should boot to stock recovery, then do format data/factory reset from stock recovery. It should say something like "verifiyng dm-verity" when you go to reboot. After system boots when you go to recovery again it wont show drk error anymore. Tested 100% on 910c variant.
magix01 said:
Usually when you restore prov_data folder properly, you need to go to twrp, format system, data and cache. Then with odin flash stock firmware with your own csc code (do csc repair if its not a match). After that phone should boot to stock recovery, then do format data/factory reset from stock recovery. It should say something like "verifiyng dm-verity" when you go to reboot. After system boots when you go to recovery again it wont show drk error anymore. Tested 100% on 910c variant.
Click to expand...
Click to collapse
So I'm doing the drk fix on my smg925p device and when doing the drk commands the prov_data folder doesn't move to the efs folder it stays in my internal memory and i did the restore and reset and i still get the drk error clearly a command or something is wrong
Use root explorer to move the folder then
magix01 said:
This is it, if you can follow these steps you can get clean factory remade EFS partition, with your own IMEI, Serial Number, CSC Code, DRK/dm-verity fixed. Flashing factory ODIN firmware after this will make your phone work as it should!
Click to expand...
Click to collapse
1. su
2. cd /efs
3. tar czf efsbackup.tgz *
4. mv efsbackup.tgz /data/media/0/
Testing........I was able to make a backup of efsbackup.tgz on a phone without any dm-verity damage. So the command works.
But on the phone that needs efs repair, when I run the command tar czf efsbackup.tgz * with Terminal Emulator
I get the error message tar: efsbackup.tgz: file is the archive; skipping
Any thoughts anyone?
Try with busybox installed and system root not systemless.
magix01 said:
Try with busybox installed and system root not systemless.
Click to expand...
Click to collapse
Thanks, that worked. The phone I'm working on is a SM-N910V and it does not have the files nv_data.bin or nv_data.bin.md5 inside the efs folder, any suggestions?
Can I send you my efs folder for repair?
I have two SM-N910V one is Okay. could I pull some files from the good one to help fix the damaged one?
+1 N910F have dont the nv_data's...my efs it's okay, i only wanna look
magix01 said:
Try with busybox installed and system root not systemless.
Click to expand...
Click to collapse
SM-N910V I decided to give this a try.
I used Root Browser to change the name of every file and folder inside the efs folder. I just added a 1 to the end of the names so I could revert back if needed.
I rebooted the phone, went back to check the efs folder and it had regenerated everything I needed to keep. And it didn't load the junk files. The phone runs like it's using AdAway on steroids.
What do you think about that. Why did it work.
http://forum.xda-developers.com/note-4-verizon/general/spyware-fix-fixed-lag-wi-fi-problems-t3433839
HI im having trouble doing the third command in DRK repair . it say that it cant be moved becuase the directory is not empty what should i do ?
I can confirm that it doesn't work with the Samsung Galaxy S6 Edge Sprint Model (SM-G925P)
bro i use your method to recover sn number and i get my serial number back but when i reboot its gone null again what can i do bro
Thank you! I use this method to restore the serial number and fix DRK on the phone Samsung SM-A310F Galaxy A3 (2016)
This method is full working on sm-n910g but still dm verification failed messages
Efs restore and phone working well
So thank u magix01
is it possible to use your files on my note edge n915fy ??
i have done everything but i can get back original emei. DRK everthing seem ok.serial number said no when i dial *#06# but i can see it on settings -status...
my phone can no register nto network
..please help.
doctor-cool said:
Thanks, that worked. The phone I'm working on is a SM-N910V and it does not have the files nv_data.bin or nv_data.bin.md5 inside the efs folder, any suggestions?
Can I send you my efs folder for repair?
I have two SM-N910V one is Okay. could I pull some files from the good one to help fix the damaged one?
Click to expand...
Click to collapse
Did you get any fix? I'm also missing these files in my N910T.
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day