Related
Ok, here's the deal.. I have the Skyrocket, and a couple days ago, I accidentally stepped on it and cracked the screen. It no longer showed any picture, so.... In a fit, i threw it at the wall and shattered the screen completely. The phone still powers on, and boots to CM10 (I can hear the sound when I press the power/lock button). I have CWMR installed as well. Apparently, I didn't have USB debugging enabled (altho i could have sworn I did!), and now I can't get at any of my files from my sdcard.
I tried adb and fastboot, neither even detects the phone as being there.
I have a replacement device coming in a few days (AT&T insurance, GREAT STUFF!), so I would really like to be able to get my stuff from this phone ASAP... Anyone know a way?
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
pitchblack5691 said:
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
Click to expand...
Click to collapse
No, fastboot doesn't work either, I tried that as well... I was trying to get into recovery, I found another thread here that was an HTC phone, I think, with a similar issue. It gave steps for navigating CWM. I couldn't get the partitions to mount.
I think you're right, that there is something more wrong with it than the screenm, because in the Windows device manager, I could see 2 extra drives that were both listed as Samsung something (it's the next morning now), both with a size of 0 bytes. The strange thing is that the phone would boot. Completely boot. I had a friend message me on Fcebook, and the notification went off on my phone at the same time it did my loaner. (both of which were signed into my Facebook)...
crashpsycho said:
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
Click to expand...
Click to collapse
Thanks for the tip, but this didn't work either.. I don't know what else I screwed up on this phone, but wow... lol
After searching for ages, I stumbled upon a solution for my tablet. Although all GTab ROMS work in the Zpad, I haven't been able to use the full 1GB RAM present in my Zpad.
So Finally today I stumbled upon a solution posted in slatedroid by Micky.
Instead of flashing the Viewsonic ROM to start with, we need to flash this ROM instead.
After you download the ROM from the link above, search for the TeamDRH CWM 5.5.0.4 and download. Extract the RAR file and replace the recovery.img in the folder with the TeamDRH CWM, cuz the one in the ROM is too old and doesn't support the latest ROMs.
[Note: If you want a larger system partition, follow this.
Open the file flash.cfg and find this no. 209715200 and replace it with this no.419430400
Now when you flash this ROM, you will get a system partition of 400MB.
If you use this method, you don't need to delete any system files after install from the ROM.]
Reboot the tab to CWM and wipe data/factory reset and wipe dalvik cache. Twice.
Shutdown and reboot to APX mode and connect to PC
NV Flash the ROM, let it boot and then shutdown.
Now to flash Jelly Bean.
Download Smoother Bean by nobe1976
Then boot the tablet to CWM
Again wipe data/factory reset and wipe dalvik cache. Twice just to be sure.
Flash the Smoother Bean zip file
Do not wipe data/factory reset or wipe dalvik cache this time.
Just reboot
Let it boot and run for a few minutes.
[Optional: Now install an app from play store to delete system apps and also a keyboard, Swipe or as such.
Open the system app remover and uninstall Gmail and AOSP Keyboard.
A few more apps can also be uninstalled, such as wallpapers, DSP Manager, Music FX, but not all.
Before deleting the AOKP Keyboard, you can copy it from the system folder if you want the stock keyboard. LatinIME.apk file.
(This does not apply if you modify the flash.cfg for larger system partition)
We need to uninstall these apps cuz after flashing with the above ROM, the system partition is only 209MB, so after flashing JB, we get around 5-6 MB free in the system partition. After uninstalling the apps, we get around 34 MB free.]
Hats off to nobe1976. He is able to develop a JB ROM that can be installed in a 200 MB system partition.
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
[After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Its a small request from us Zpad users.
(Note: From the help of all the users, I have been able to increase the system partitiom to 400MB)]
If anyone could help, I will be gratefull, we all will be very gratefull.
This is really pushing the limit.
Edit: Now you can use 1GB RAM present in your tablet and all the space available in the flash memory.
Note: This method can be used in all variants of the Zpad which has 1GB RAM and 16GB ROM.
Note: This tablet is sold by different names all over the world. The one I use is HCL AP10-A1
kank_fraud said:
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
Click to expand...
Click to collapse
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]su -c dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Click to expand...
Click to collapse
Though @rajeevvp is the best person on xda to give you solution that is more logical on this, I will tell you quick and dirty way to do this, which I have adopted.
1> download stock zpad rom if you don't have it already "ftp://112.5.164.225/tablePC/T2_nvflash_mp_3g(WCDMA)_20110824.rar"
2> unzip it, delete recovery.img from unzipped directory, copy part9.img from DRH nvflash which is used for prep 350M system partition to this directory, rename it to recovery.img
3> edit "android_fastboot_full_i_malata.cfg” change "size" of partition id 11 (which is a system partition)
Make sure you do not give any arbitrary size here; calculate it with the formula @rajeevvp posted here "http://forum.xda-developers.com/showpost.php?p=22138304&postcount=14"
4>now nvfalsh your tablet in apx mode with download.bat, now format /data /system /cache and flash whichever rom you want on top.
memory/partition config is supplied to kernel through CMDLINE parameter, so even if you nvflash tab with above procedure, its not necessary that default memory/partition sizes are maintained created by above prcoess, Team DRH boot.img has a blank CMDLINE. That is the reason
Above process will work on most of the ROM, which is using TeamDRH boot.img.
(more technical explaination stright from one of the posts of @rajeevvp "When the bootloader runs, it reads PT (partition 3) and constructs a command line telling the kernel what the partition layout is on the onboard NAND flash. Normally, the bootloader will pass this command line to the kernel as part of the boot-up process. However, if the bootloader sees that the boot.img already contains a default command line then that will take precedence")
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
Click to expand...
Click to collapse
glad to hear that it worked, BTW you will have to change /system size to minimum 350MB if you plan to use TeamDRH rom in future (hopefully with camera working)
I'll have a try later.Thanks So much.
Thank You all for the help.
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
It shows 419 MB in Titanium Backup
I am happy with it.
Its way better then before.
Thanks evryone
Problem solved
If anyone has formated or resized the internal memory resently, please try the maximum possible size for the system partition.
I tried 512MB but it didn't work. Maybe 490MB might work.
According to my knowledge, Android should support atleast upto 999MB for any partition.
Is it cuz of our tab or is it cuz of the architecture.
And if anyone knows, is it possible to create a larger internal partition.
As in 8GB or if possible the whole internal memory.
CWM doesn't allow more than 4GB internal space.
kank_fraud said:
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
Click to expand...
Click to collapse
Well this was expected result, /system partion resides on NAND flash chip (with is only 512MB) and not on SDcard.
Read this "http://raywaldo.com/2011/07/format-the-gtab/" and this "http://forum.xda-developers.com/showpost.php?p=15558724&postcount=12"
Also you need to bare in mind that other partitions also use 512MB nand flash as per explanation in above threads.
so if you take a close look at falsh.cfg file in nvflash directory you will understand that size allocation is sequential ("allocation_policy=sequential") and system partition (11) which is last to allocate the space, so you need to calculate it accordingly if you want to utilize all remaining space from NAND flash chip.
Well I cant open the page "http://raywaldo.com/2011/07/format-the-gtab/".
So according to this info I have hit the limit. I am already using 489MB of the 512MB flash. And as always, cuz of our storage manufactures, we get only 490MB in a 512MB chip.
What I wonder is why Malata and Viewsonic did not utilise the full NAND space available in the first place.
Is it used for something else.
I mean even the 350MB prep for Viewsonic GTab uses 350MB instead of 400MB.
It is so easy to to utilise and partition the NAND, then why not use the full available space.
What is the empty space used for!???
Or is it just a waste!!!
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
fanguru said:
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
Click to expand...
Click to collapse
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
rajeevvp said:
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo > /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
Click to expand...
Click to collapse
Well I am very sorry for such a late reply. :angel:
I missed your post as I was out of station.
After I came back there were already solutions posted by a couple of users. :victory:
Well today while updating my original post, I noticed ur first reply. :silly:
Well thank you for your reply.
And thanks to all the ppl who provided for the solutions to our ZPad.
I guess the problems are solved for now.
:highfive: :highfive: :highfive: :good:
kank_fraud said:
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
Click to expand...
Click to collapse
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
kank_fraud said:
I guess the problems are solved for now.
Click to expand...
Click to collapse
I'd still like the output of those commands--for my own edification.
fanguru said:
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
Click to expand...
Click to collapse
Well for Me it worked the first time itself.
Why don't u try giv it a few more couple of times. :laugh:
BTW, are you using the Malata Zpad or Viewsonic Gtab
If you are using Gtab, try TeamDRH method but modify the size of the partition.
If u are using Zpad, try again.
Clear cache and reset before installing.
Try previous older ROMs and gradually update to newer ones.
Reset and wipe before each update.
As I didn't get any problems, so I can't say whats wrong with your installation.
And very sorry for the late reply.
I have exams.
But my tablet is very stable after this.
Everything is running smooth, even HD games.
Goodluck :fingers-crossed::fingers-crossed::fingers-crossed:
rajeevvp said:
I'd still like the output of those commands--for my own edification.
Click to expand...
Click to collapse
I tried it in terminal emulator, but it says 'Operation not permitted'
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
same here.
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
Fixed commands. Try them again.
I seem to have everything running and it seems really fast, the only problem I have is that the home button (hardware and soft) does not work!
I've tried installing a different home app, tried home switcher and I get asked when the tablet boots as to which home app to use, but still the buttons don't work (back and recent apps work).
Any ideas???
This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
The Problem
Internal Memory doesn't mount as a drive like external memory does. External memory would allow you to use data recovery tools that scan for deleted files and return them to a usable state. These tools work because most operating systems don't go through and set all of those 1's and 0's to just 0's when you delete a file. Usually the operating system will just delete the reference pointer in the index that says that a file exists with such-and-such name and it's located at this position on the hard disk / memory location. There are destructive delete tools out there that will overwrite the spot of a deleted file multiple times to discourage recovery in just this manner. The issue is that data recovery tools need an actual mounted drive in order to dig deep and unearth those funny pictures of cats you so tragically deleted by accident. These newest batches of phones don't have external SDcards which are super easy to mount as drives. Internal memory mounts as MTP/PTP which is not treated as a mounted drive and cannot be scanned by these data recovery tools. But still there is a hope.....
The Process
My phone is the Samsung Galaxy s4 (GT-I9500) though I imagine this should work for ANY phone with Internal Memory. We will be using a Windows 7 machine to:
back up the entire internal memory partition to your computer as a single, massive .RAW file,
convert the .RAW file output to a VHD,
mount the VHD as a disk in Disk Manager,
scan the attached VHD volume for files that have been deleted and recover them,
The Requirements
A rooted Android phone, (try to root with a non-destructive method as this appears to protect those who must root from wiping the device data a second time),
BusyBox installed on your device,
Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install). Make sure to open Cygwin once to make sure that the /bin folder is created. Also, I made a folder at [c:\cygwin\samsung] to put the exported .RAW file,
Netcat (download the ZIP file and extract nc.exe to [c:\cygwin\bin]),
ADB - You can use minimal adb and fastboot which is 2MB only. Attached, find the link at the bottom of this post. (make sure adb.exe is in your path. Path is in System Properties -> Advances -> Environment Variables -> System variables -> Path and add to the end: ";C:\Program Files\Android\sdk\platform-tools" or where ever you placed your adb.exe),
USB Debugging enabled on your device,
VHD tool from the mighty M$. Put the VhdTool.exe file in [c:\cygwin\samsung],
Piriform Recuva or your favorite data recovery tool, (it appears Recuva only finds the more common file types like images, videos, etc. Those were the file types in which I was interested. If you are after more exotic file types perhaps you might share the software you used.)
A calm sense of peace and serenity that you will get your files back... :fingers-crossed:
The Work
*****Based on the number of people having trouble with this step it is now my recommendation that you choose to recover your entire memory block instead of just the data partition. In my phone's case that is mmcblk0. Please discover if yours is different.
[*]*****For identifying which block/partition you want to recover, install DiskInfo from Playstore. Open the app and click on Data (USERDATA) to see the partition name for yours. For our purpose here we are seeking to recover the userdata partition: /dev/block/mmcblk0p21
Turn on your phone
Connect the phone in ADB mode
Unlock the screen.
Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/system/bin/busybox]. It may be at [/system/xbin/busybox]):
*Remember to enter codes line-by-line. After you enter su, you have to grant permission on your mobile phone at the same time
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p21
Open another Cygwin terminal and enter:
Code:
adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p21.raw
[*]Depending on the size of partition it may take a while to backup.
We need to convert the .RAW file to a virtual hard drive. VhdTool.exe basically just puts a VHD footer on the end of the .RAW file. Open a Windows command prompt, go to [c:\cygwin\samsung], and type:
Code:
VhdTool.exe /convert mmcblk0p21.raw
Now we need to mount the VHD in Windows. Select the Start button-->right-click Computer-->select Manage.
Select Storage-->Disk Management.
In the menu select Action-->Attach VHD.
For Location enter [c:\cygwin\samsung\mmcblk0p21.raw] and select the OK button.
Right-click on the name (e.g. "Disk 1") to the left of the Unallocated space and select Initialize Disk.
Select the GPT (GUID Partition Table) radio button and select the OK button.
Right-click on the Unallocated space and select New Simple Volume...
In the Wizard select Next>, leave the default for the volume size, select Next>, select a drive letter (e.g. K), select Next>, MAKE SURE to select the 'Do not format this volume' radio button, select Next>, select Finish.
A box will pop up asking you to format the drive. You DO NOT want to format the drive at this time.
Right-click on the RAW space and select Format... MAKE SURE to change the File system to FAT32. Set the Allocation unit size dropdown to 'Default.' MAKE SURE that the Perform a quick format checkbox is CHECKED. You do not want to overwrite the entire new drive with all zeroes (0's) and destroy your data. Quick Format means that it will only attempt to destroy the index for the drive by establishing a new index. Without this box checked the Windows operating system will write zeroes (0's) across the entire volume, potentially destroying your data. Select the OK button.
A box will pop up saying that Formatting this volume will erase all data on it. That would be doubly true if you actually didn't check the 'Perform a quick format' checkbox. Double check that you actually did check the box and select the OK button. (Don't worry. This essentially leaves the volume in the exact same state that your phone's internal memory is living in right now: there is data on the drive...you just can't see it. It's coming back, I promise!)
Open the Piriform Recuva application. In the wizard select the 'Next >' button. Select the 'Other' radio button and select Next >. Select the 'In a specific location' radio button and enter: k:\ (assuming K is the drive letter you chose...) Select the Next > button. Select the Enable Deep Scan checkbox. This is the magical setting that finds files that have been deleted...but not really deleted. Select the Start button.
The application may take about an hour to do the 'Deep Scan.' It's time for more laps around the house! Once the application has returned its results you can choose which files to recover using the checkboxes. Select the 'Recover...' button and choose the location to which you wish to output your files.
?
Profit! :victory:
Good Luck :good:
help
M S T F said:
This is the same tutorial written by Wartickler at this link. Thanks for his efforts, his work is appreciated.
Here we bring minor changes to the tutorial for those of you who are facing problems accomplishing the procedures.
Good Luck :good:
Click to expand...
Click to collapse
You should add that the x86 version of Cygwin is needed, not the x64.
Do you also know that as of Android 4.3 this method doesn't work anymore?
yes
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.
Filoppi said:
it works with 4.4.x and 5.1.1, it probably also works with 4.3. it's just an adb command after all.
Click to expand...
Click to collapse
No its not that. As of Android 4.3 Google enabled Trim on our decives. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above methode and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?
try
Lennyz1988 said:
Do you also know that as of Android 4.3 this method doesn't work anymore?
Click to expand...
Click to collapse
Lennyz1988 said:
No its not that. As of Android 4.3 Google enabled Trim on our devices. That means when you delete a file its really gone. Not even a professional company can get it back.
I have tried the above method and I could not get any data back. Thats when I started reading about Google enabling Trim and found out its impossible to get it back.
Did you try it on Android 4.3+?
Click to expand...
Click to collapse
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.
Filoppi said:
I have tried on my previous Samsung galaxy s3 (i9300) and my one plus one, both 64gb, i got at least 20% of the pictures back (.png, .jpg, ...), possibly even 50% since i had no idea how many i had on the device, some zip, most of .pdf and .doc and some other random stuff.
In both cases i did not manually delete the files from the phone, instead, i screwed up the partitions by deleting some system file, so after restarting, the SDcard/used data partition was empty.
i noticed though that even if my phone only had 500mb of free space available, the .raw partitions i extracted with this method were mostly empty, they only had about 10% of the data, so i guess some happened when android restarted, maybe yeah, some kind of trimming.
i think its worth trying anyway. just remember to not open any program or copy any file in the memory, as it would lower the chances to get anything back.
Click to expand...
Click to collapse
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.
Lennyz1988 said:
Yes but that's something different I think. Then you never deleted the files, they were there but not accessible.
If you look for example in the last 10 pages of the main thread, then no one is able to recover anything. Because it's simple not possible anymore. That's just how Trim works.
Click to expand...
Click to collapse
I'm sorry for your loss.
Filoppi said:
I'm sorry for your loss.
Click to expand...
Click to collapse
What kind of response is that?
gonna try.
for those of u who want to know the blocks and partitions to recover the user data..
ls -l /dev/block/platform/*/by-name
after the adb shell will list them
127.0.0.1 5555 | pv -i 0.5 > mmcblk0p16.raw 0 B 0:00:02 [ 0 B/s]
i stuck at step 7 which is
0 B/s transfer rate
GoGopowerRanger said:
i stuck at step 7 which is
0 B/s transfer rate
Click to expand...
Click to collapse
That su is the most important part of command, if you miss it adb will not be able to transfer any data
M S T F said:
That su is the most important part of command, if you miss it adb will not be able to transfer any data
Click to expand...
Click to collapse
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.
Lennyz1988 said:
You should be honest with people. You should put in the op that it will only work on Android versions below 4.3. People are just getting false hope and wasting their time.
This method does NOT work anymore.
Click to expand...
Click to collapse
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.
M S T F said:
This is not my method nor I have, my self said that 100% you will get what you have deleted. I have only brought minor changes to the tutorial for the sake of successful transfer of data to the pc.
Now if you feel responsible for the feeling of people, definitely I will appreciate if you find another way.
Click to expand...
Click to collapse
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.
Lennyz1988 said:
That's the thing. You just copy paste a tutorial that does not work. Why would you do that? I can imagine that you did not know that it would not work anymore. But now you do know. What do you hope to achieve? Raising your thanks meter? You give people false hope and you waste their time.
And about me finding another way....There is not even a professional company that can do it. It's impossible at the moment.
Click to expand...
Click to collapse
I don't need thanks... why I should do.... it doesnt give me anything... I have got my own forum with its nice members.... if someone is in need of thanks, thats is you which is trying to show himself as a defender of others feeling, time, blah blah.......
I have recovered my file on a 4.4.2 android after a system crash which I had to reset the phone. if someone is in desperate need of something s/he will try anything and as far as I know trying this one doesn't harm anyone.
for you I have a recommendation, go and drink something cold and calm down!!!
Errr...
Awesome....the raw extraction worked on my S6 running Android 5.0.2. This time I tried it on a Mac and used Homebrew to install PV. Is there a way to get the entire image, even with the unused space?
Great
Thank you!
Worked on my sm-g900f
If you get nc/pv command not found , try this:
When you open cygwin terminal, start with this line: export PATH="/cygdrive/c/cygwin/bin";$PATH
The terminal should now know the location of them.
Same if you get that "adb: command not found" just type: export PATH=/cygdrive/c/XXXXX";$PATH
Just replace that XXXXX= to your location of adb.exe.
Hope it helps someone out of this ****
It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Edit: eventually I found that my problem like this guy http://forum.xda-developers.com/showthread.php?t=895628 was that the \data partition is read only but I can't fix it the way he did since he used advanced partitioning in clockworkmod recovery but I can't flash it or any other custom recoveries.
mostafa_0017 said:
It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Click to expand...
Click to collapse
Hmm...
First, tell her to quit using Facebook app, Facebook Messenger, WhatsApp and other social media and texting apps. I know she just HAS to keep up with all her friends and the latest gossip but her device can't handle all those system demanding apps, they are literal HELL on mid-low end devices. They all constantly run scanning for updates and notifications, CONSTANTLY. They are notorious for making devices act crazy, especially when you have more than one of them.
For Facebook, its best to bookmark the Facebook page in mobile browser then create a shortcut for that bookmark on her homescreen, then it has to be set so that it loads the desktop site for Facebook, then she can view her Facebook messages, if it isn't set to load desktop site it will request she install messenger but she won't need to if she uses the desktop site to view messages. Then she can set her Facebook notifications to go to her gmail account, then in gmail app she needs to make sure it is set to receive notifications for gmail, then when she gets messages or activity on Facebook she will get a gmail notification in her status bar letting her know to check Facebook, then she can open the bookmark to view it. That is just as convenient as having the two apps but without all the strain on the device, also takes less space on internal and has less junk running in the background eating mobile data and draining battery.
As for her texting apps such as WhatsApp, Kik, Snapchat, etc., she needs to pick 1 or at the most 2 of them and leave the others alone, her device will run much faster and smoother.
You can try booting to recovery and wipe cache partition(not factory reset).
As for fastboot and SP flashtool not working, do you have USB debugging enabled in developer options on the device?
well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I tried both to wipe cache partition and wipe data and yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it
mostafa_0017 said:
well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it
Click to expand...
Click to collapse
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?
Droidriven said:
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?
Click to expand...
Click to collapse
God no of course not I will till her to keep her apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:
mostafa_0017 said:
God no of course not I will till here to keep here apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:
Click to expand...
Click to collapse
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Besides, with some of the steps you've taken, you've probably created other issues than it started with. Whatever you do, don't format the device in SP flashtool, you'll probably lose IMEI if you do that.
Droidriven said:
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Click to expand...
Click to collapse
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD
actually I have grown very confident dealing with the phone that no matter what I do It wouldn't matter since it will come back just as always and now I didn't create any other issues since no matter what I hit a dead end the device revert back no matter what I do, Do you feel me I am starting to go insane I am pretty sure even If I tried to brick this device on purpose I won't be able to.
mostafa_0017 said:
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD
Click to expand...
Click to collapse
Your pic keeps directing me to the imgur app to view it, I'm not installing the app just to view it, why not just upload the pic as an attachment to your post and it will display in your post instead.
Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg
mostafa_0017 said:
Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg
Click to expand...
Click to collapse
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.
Droidriven said:
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.
Click to expand...
Click to collapse
Yeah thanks found it and it displayed this only one time when I was rebooting after doing various things and I never saw it again and yeah the grammar felt really strange when I googled its content I only found a couple of Spanish forums talking about this but couldn't get any information about the source of this message and that's why I thought about the logcat in the first place.
the same problem
hi i have the same probleme with my huawei y520 u22 i can do nothing just start up the phone i got the message and i can do nothing when i try to unistall any app the phone restart and go back to the same situation wipe cache and wipe data nothing change flashing 1000000000000000000 roms nothing change any one can tell me there the problem is
as i think the flash memory is the problem its blocked in write and read.
any solution plz
I read this and just think, what the hell... i can not understand why "/data" is write protected. Just some thoughts running through my head:
- phone is not rooted and completely stock, but factory reset not working!? in this case ask for warranty and send it back to seller!
- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
- if possible - make a "backup user data" with Android system recovery, you may restore it on working phone, later.
- if you have read-access to "/cache/recovery" look for file "last_log" and copy to sdcard. "/proc/emmc" and "/proc/partitions" are another useful files. keep this in case you have to manually create the scatter file.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
http://www.modaco.com/forums/topic/362724-official-code-request-to-unlock-the-bootloader-final-post
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
http://www.hardresetandroid.com/hard-reset/huawei-hr/huawei-ascend-y520-hard-reset-code-format-solution
- once you have unlocked the phone, do factory reset. phone should boot now. its hardly imaginable that "/system" is damaged because of never rooted the phone.
- if still not working, you should now be able to flash custom recovery, too. be careful, select tested binary for your special phone model only! flash in fastboot mode. avoid flashing with SP Flash Tool as long as you not absolute sure that scatter file is 100% correct (MTK Droid Tools may give you wrong scatter files for devices > 4 GB!)
- from custom recovery, you should able to root the phone via adb root method or install the "supersu.zip"
- once you have root, you can mount data partition read-write from adb shell (in recovery mode) and format or delete it. of course the custom recovery has a wipe data option, too.
- installing aroma file manager zip is another way to browse and modify everything in recovery mode. you can copy files from similar phone into "/system" folder, if phone still not working properly.
- don't restore a full backup from similar phone (especially NVRAM folder), this may clone IMEIs and WiFi MAC address.
- you can install a stock rom zip from custom recovery instead, and use my script bckp2cwm.zip to convert the user data backup into cwm format and restore "/data" folder only (converting script requires linux pc).
- delete suspicious apps from "/data/app" + "/data/dalvik-cache" + "/data/data" (every app has three entries with similar name). do it in recovery mode with aroma file manager, or on linux pc from backup file during converting (at this point where script is waiting for user input).
- search and read for "unbrick guides" on forum.xda-developers.com, as long as it is not a physical damage (Vol keys not working, emmc wearing out, etc) there must be a solution to get this phone working
- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
yeaah I don't think they would respond with any helpful answer and would probably tell me to send my phone to the nearest service center.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
That's what I settled for eventually and I already sent it to my sister and told her to visit any mobile repair shop that has boxes like miracle box and such.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
done that already but what I got in the end didn't help me to fix the phone note that I don't care about the phone's content sure I care about the IMEI but the phone is not affected by any write attempts so I am not so worried.
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
I searched online and in threads talking about custom roms and recoveries for this phone and not a single one of them mentioned anything about the bootloader being locked.
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
haven't tried that but will try it ASAP since I don't have the phone right now.
One last note the phone boots normally but as I described in my later posts I can't edit anything without it reverting back after restart like changing the wallpaper or uninstalling an app.
And anyway thank you for your respond.
did you try to get (temporary) root access?
aIecxs said:
did you try to get (temporary) root access?
Click to expand...
Click to collapse
Not sure of What you mean but I think I tried and failed you can tell me What you mean exactly and I will tell you If I tried .
Edit: Alright I googled it and turn out to be temporary root for locked bootloader devices no special procedure just the same procedure as in permanent root but will lose root as soon I reboot again I tried a lot of rooting methods including kingoroot and 360root.
Not sure, too.. installing kingoroot.apk and root the phone may give root access until reboot (can't remember if rooting requires a reboot)?
Brainstorming. Lets come from other side. When you intend to write a malware - how would you realize this setting?
one thing is remount /data partition read-only, but is this really enough? what happen if /data is not writeable anymore - apps should crash or give errors on write cycle, didnt they?
but you claim phone is changeable until reboot. so we need the possibility to let them write in some other memory without noting that it storage has changed.
another way is copying /data to any hidden storage, and restore it on each reboot, but this should be time consuming, didnt it? and where can this amount of data be stored? sdcard? cache partition?
besides this, guess the malware needs root access to modify /data. or is it imagineable to change it without root access? lets find a conception to understand whats going on
No reboot is fast and not time consuming and I am always working on the phone without the SD card and about apps sometimes uninstallation is complete and the app disappear to show again after reboot and sometimes the phone restart upon uninstallation of an app
I've spent the last couple days searching around to fix this problem, not only on XDA and Google, but in TWRP's Issues and code on GitHub; all to no avail. So here it is:
I have a device with a broken display. The only way I can initiate commands on it are with the power, volume, and home buttons, and with adb. I've installed TWRP on it, and I'm able to boot into it. I'm trying to back up everything on the device I can to a 32GB external SD card in the device's SD card slot. But when I keep getting the following result:
Code:
~ # twrp backup SDBOM
Setting backup options:
System
Data
Boot
Compression is on
Digest Generation is off
Updating partition details...
...done
* Total number of partitions to back up: 3
* Total size of all data: 7976MB
* Available space: 496MB
Not enough free space on storage.
Backup Failed
Done processing script file
The External SD Card has more than enough space for the backup (several times over, in fact), so clearly TWRP is attempting to save the backup to the device's internal storage. It seems, from testing I've done on an identical device with a working display, that twrp backup in the command line saves to the Storage last selected in the graphical version, but since my device's display is broken I can't select the External SD Card as the storage for the backup.
Since I have no display, I also can't do adb backup --twrp, since that requires confirmation on the screen.
Is there any way to select the storage for twrp backup fully through the terminal? For example, is there an environment variable I can set, or something I can pass twrp backup?
I figure this is an easy one to answer, and that it's something really, obviously, simple (so much so that I'll have to hang my head and never show my face here again!). But for the life of me, I can't find it.
Same thing here. In my case I have a working display but my kernel does not allow any touchscreen operations when in recovery so I can see TWRP but not input anything. So the command line is my only way to use TWRP but like you I cannot switch to creating backups to my external SD card.
It seems funny there is no solution to this since having touch screen problems with TWRP seems to be a common issue so how do all those folks with no touch recoveries do their backups?
check to which folder mount yours external SD
and set var "tw_storage_path" with "twrp set"
example "twrp set tw_storage_path /external_sd"
you can find this var in android_bootable_recovery/openrecoveryscript.cpp
also
you can change backup folder
example "twrp set tw_backups_folder /external_sd/all"
can find it in android_bootable_recovery/variables.h
OrBitRo said:
check to which folder mount yours external SD
and set var "tw_storage_path" with "twrp set"
example "twrp set tw_storage_path /external_sd"
you can find this var in android_bootable_recovery/openrecoveryscript.cpp
also
you can change backup folder
example "twrp set tw_backups_folder /external_sd/all"
can find it in android_bootable_recovery/variables.h
Click to expand...
Click to collapse
Hello and thank you very much for helping on this issue.
I gave up on this long ago but it is still of great interest to me since I am still using the same phone and TWRP backup would be welcome. But since so much time has passed since I unpacked the recovery, I am a bit rusty at it. I am an old programmer but my android knowledge is limited, still I did succeed to make the sdcard visible to the recovery (cant remember how but I think I changed its block name in recovery.fstab then for some other reason also had to un-repack) so I can handle such things if I am guided a bit.
So your help is very welcome and also reignited my interest to solve this issue. Problem is I cannot find the "android_bootable_recovery/openrecoveryscript.cpp" script in the unpacked recovery or the phone's file system. I am sure I am missing something silly but googling around did not help me either.
Could you possibly guide me into finding those scripts so I can edit the aforementioned variables?
Thank you very much for your attention and help.
Chris.
cfrantzol said:
(cant remember how but I think I changed its block name in recovery.fstab then for some other reason also had to un-repack) so I can handle such things if I am guided a bit.
Click to expand...
Click to collapse
Nice hack too!
cfrantzol said:
Problem is I cannot find the "android_bootable_recovery/openrecoveryscript.cpp" script in the unpacked recovery or the phone's file system. I am sure I am missing something silly but googling around did not help me either.
Could you possibly guide me into finding those scripts so I can edit the aforementioned variables?
Thank you very much for your attention and help.
Chris.
Click to expand...
Click to collapse
I find it (i have same problem like yours after 6 hours mess in adb and googling ) in sources of twrp on github github.com/omnirom/android_bootable_recovery
And also about factory reset (to whom it may concern) github.com/omnirom/android_bootable_recovery/issues/146
OrBitRo said:
Nice hack too!
I find it (i have same problem like yours after 6 hours mess in adb and googling ) in sources of twrp on github github.com/omnirom/android_bootable_recovery
And also about factory reset (to whom it may concern) github.com/omnirom/android_bootable_recovery/issues/146
Click to expand...
Click to collapse
Hi again.
Okay now I understand, I will download from there and check what I can come up with. I already feel that this will involve some compiling and I wonder how that is going to affect my custom TWRP (which I found at twrp builder). I will step into it and see.
Thanks a lot for your prompt help, I really appreciate.
cfrantzol said:
I already feel that this will involve some compiling and
Click to expand...
Click to collapse
Sorry if i misunderstand you but why compiling? You dont need it. You can change this vars from adb terminal. Boot device into TWRP connect USB to PC run adb shell and you can change vars in shell via commands like this: 'twrp set tw_storage_path /external_sd' and so on.
OrBitRo said:
Sorry if i misunderstand you but why compiling? You dont need it. You can change this vars from adb terminal. Boot device into TWRP connect USB to PC run adb shell and you can change vars in shell via commands like this: 'twrp set tw_storage_path /external_sd' and so on.
Click to expand...
Click to collapse
Oops, I thought I had to change the variable in the source files and then compile the recovery from scratch. This is now great news I will check it tonight.
Thank you again!
EDIT: For anyone who has the same problem I confirm that I checked it and the method above works fine! Kudos to you OrBitRo!