[Q] Request help Yuweng please - General Questions and Answers

Hi Yuweng! How are you?
I am writing here, since no new members can post questions in the restricted area only to devs (still do not understand why this).
I tried to install this mod to my phone a few days ago, but no luck. After installation, at first, it seemed that everything happened as expected, but after a few moments of much slowness in the system, my phone went into boot loop. I tried to do as you had described in their responses, removed the SD card and started the phone, but nothing happened. I then tried clearing the caches, dalvik, factory reset, and nothing. Reinstalled, then the entire ROM and have not tried anything else after that day, but now I wonder why so many people could and I could not? Certainly did something wrong and after having gone through a similar problem a few weeks ago, when I thought I would never again recover my first Android, behold, I got following the forums, including XDA, thanks to God, put my phone working again. So I thought, if I could bring back to my cell operation twice why I can not try this new solution to the problem of unreasonable internal memory size of our phones? Could you please answer me where I went wrong step?
I believe ive done everything right, since the procedure is quite simple (I could carry my recovery and now I'm working CWMR ), but I do not know if I should delete the content of the SD card completely, redoing all the partitions, and then reattach it backed up the entire contents, since I have many applications installed directly on the SD card? That would be correct? Or is it unnecessary? Or wrong? How should I proceed with the content on my SD card? What about the scripts contained in the folder Scriptz, should I remove any of them or it's not necessary? I used the command to check if I have swap support and unfortunately I have not found that. The swap script can disrupt the functioning of my phone since it does not support it? Some other script may have caused the problem I had, depending on the support capabilities of my phone? How should the preparation of my SD card, when I already have content applications installed on it? My SD card is a 4GB class 4, this may have been the problem? Sorry for my almost total ignorance in the Android world, but I am willing to learn much about it, but while I'm getting, I'll be bound to annoy the wiser on the subject ... I thank you.

hey complete your 10 post by posting in drfrent thread ask them question and do whatever you want to then go to dev thread of the rom and post you problem there you will find a better ans you might get your rom working

Related

Changing SD Cards

Hi, i looked in other forums but couldn't find the answer to this. If I got a new SD card, what is the process to change cards?
I formatted the new one and copied all the stuff from the old one to the new one. Booted, blank screen/wouldn't boot.
Do I need to format, Download a ROM to it, flash it, then boot or what?
Thanks in advance.
I think you would have to partition it and then put whatever rom and reflash everything
A blank screen..? The hell, that's weird. From my knowledge, it should still work with a bunch of FC's and Errors. And no you don't have to reflash everything like KingSkeme recommended, but you may have to since your device is acting a bit weird.
But yeah, first of all you need to format it. Second, you need to search this yourself. I find it bullcrap that people like you can't find this info yourself.
Here, I spent about 2 minutes of my life for you.
http://wiki.cyanogenmod.com/index.php/Apps2SD#Upgrading_SD_.2F_Moving_data_to_new_SD
If you can't follow those steps, then you shouldn't have rooted your phone.
P.s depending on which Rom you use, I believe CM automatically does the ext/swaps for your SD card.
If not, oh I found more information with my friend google
http://www.mattidroid.net/2009/10/g1-rebuild-new-sd-card-and-cyanogen_09.html
TheUnlockr is your friend.
How to switch to a different SD card
EDIT: Sorry, double post.

[Q] Unable to locate internal sdcard error

Hello All,
I wanted to post this to the Android Development section but since I have fewer than 10 posts I am forbidden from doing so.
Intermittently I will notice some apps do not load images or act as they normally should, and upon opening Solid Explorer to do some investigation I receive an error message (Cannnot browse to "/mnt/sdcard". An unknown error occured.). I find I am unable to access the internal sdcard through Solid Explorer, and when navigating using Root Explorer it only displays an empty folder.
This seems to happen at least once a day, and restarting my phone usually fixes it at least for a few hours. Sometimes ending all applications through task manager & clearing RAM memory through RAM manager will allow me to normally browse my internal sdcard using Solid Explorer for about a minute or so, and then become unaccessable again. Phone reboots seem to be the only fix, albeit a temporary one that only lasts a few hours.
I am unable to save screenshots when this occurs, unable to save pictures, some apps do not function properly -- all which makes sense if the phone is really unable to access the internal sdcard. I have performed numerous wipes (full wipe, cache, dalvik) & reinstalled newer nightly SynergyROMs but I have been unable to fix the issue. Searching these forums has not brought me any relevant information which pertains to the same issue I am having.
I appreciate any help or insight you guys can provide, thanks for taking a look.
Quick Background:
32GB Samsung Galaxy S3 on Verizon network
No external microsd card
Unlocked & Rooted
Running SynergyROM Nightly (r73)
CWM-based Recovery v6.0.1.0
Why would you think to post this in Android Development? This is a question, and thus belongs in Q/A (where it is posted). Android Development is for people who actually developed something, like a ROM, Kernel, etc.
I don't know what kind of advice to give you though, besides try formatting in advanced options of CWM, a reprovision (*2767*3855# ) on stock (back up everything first, to somewhere other than internal SD as it will be wiped) or maybe a 32GB PIT, with a PIT being the least likely solution.
I second this question!!
Kenshingtx said:
Hello All,
I wanted to post this to the Android Development section but since I have fewer than 10 posts I am forbidden from doing so.
Intermittently I will notice some apps do not load images or act as they normally should, and upon opening Solid Explorer to do some investigation I receive an error message (Cannnot browse to "/mnt/sdcard". An unknown error occured.). I find I am unable to access the internal sdcard through Solid Explorer, and when navigating using Root Explorer it only displays an empty folder.
This seems to happen at least once a day, and restarting my phone usually fixes it at least for a few hours. Sometimes ending all applications through task manager & clearing RAM memory through RAM manager will allow me to normally browse my internal sdcard using Solid Explorer for about a minute or so, and then become unaccessable again. Phone reboots seem to be the only fix, albeit a temporary one that only lasts a few hours.
I am unable to save screenshots when this occurs, unable to save pictures, some apps do not function properly -- all which makes sense if the phone is really unable to access the internal sdcard. I have performed numerous wipes (full wipe, cache, dalvik) & reinstalled newer nightly SynergyROMs but I have been unable to fix the issue. Searching these forums has not brought me any relevant information which pertains to the same issue I am having.
I appreciate any help or insight you guys can provide, thanks for taking a look.
Quick Background:
32GB Samsung Galaxy S3 on Verizon network
No external microsd card
Unlocked & Rooted
Running SynergyROM Nightly (r73)
CWM-based Recovery v6.0.1.0
Click to expand...
Click to collapse
I logged in today because I am having the exact same problem. Same ROM as well, Synergy r73. I've tried formatting the SDCard, tried a complete reformat of the phone. But nothing seems to help.
Also, to clarify, it isn't restricted to the external SD card (which mounts to /mnt/etxSDcard folder). It's the entire /mnt directory that hangs. I'm able to go into options and mount and unmount the external card fine. But as soon as I try and access /mnt using any app (andExplorer, Wifi File Explorer, even a simple 'ls' in terminal) the phone hangs, stops responding to button presses, and eventually reboots itself.
Also, I've found my timing matches Kenshingtx's as well. If I reboot the phone, I can access external storage, and the entire /mnt folder for that matter, just fine, and it stays this way for about an hour or so.
Any further ideas are greatly appreciated.
btw, I think he mentioned posting the Android dev because there is a thread specifically dedicated to this ROM with numerous questions and answers in it. (Albeit hard to follow since it's over 800 pages) I already searched in there and found no mention of this issue.
The SD card problem sounds like something that used to happen with the old modems.
Go to about phone and check your baseband. If it doesn't end in G7 or HD then you have an older radio that had this issue.
Here's a link to where you can get what you need that explains everything better then I could.
MasterPoppy said:
The SD card problem sounds like something that used to happen with the old modems.
Go to about phone and check your baseband. If it doesn't end in G7 or HD then you have an older radio that had this issue.
Click to expand...
Click to collapse
My phone has the G7 modem in it.
Thanks for everyone's input so far. My baseband ends in F2 so I'll try updating my modem and see what that does (even though nerfage seems to be having the same problem with the G7 modem). And you're right, I wanted to post in the synergyROM development thread thinking the problem might've been specific to that ROM.
I'll also look into reprovisioning on stock rom per Zalithian's suggestion to wipe the internal sd card, and see if that helps.
@nerfage - I dunno what the problem is then, could be ROM specific. If you figure out what's wrong post how you fixed it here. You may also want to try flashing the HD rom. Might fix it, might not.
@Kenshingtx - Not sure if the wipe would help so make sure that's an absolutely final thing, googling around is always useful. Hopefully the flash thing does the trick though.
MasterPoppy said:
@nerfage - I dunno what the problem is then, could be ROM specific. If you figure out what's wrong post how you fixed it here. You may also want to try flashing the HD rom. Might fix it, might not.
@Kenshingtx - Not sure if the wipe would help so make sure that's an absolutely final thing, googling around is always useful. Hopefully the flash thing does the trick though.
Click to expand...
Click to collapse
Flashed the latest modem ending in HD, and tested my phone over the weekend. Still having the same issue where the internalsd becomes unavailable. Wondering if the hardware in our devices are faulty..?
nerfage said:
My phone has the G7 modem in it.
Click to expand...
Click to collapse
My phone appears to be fixed. I backed up all the files on my mnt/sdcard, performed full/cache/dalvik wipes, formatted internal memory through recovery, flashed the rom again (decided to try Beans ROM this past week) and I haven't had the same issue come back. It looks like the cause of the problem was something on my internalsd, try formatting it (after backing up any files you need) to see if it'll fix the problem for you too. Good luck.
Note: the fix does not appear to be related to the ROM, i was having the same issue on the Beans ROM as well until I formatted the internal memory

[Q] Trying to root my Inspire 4g

I am asking this again here, as my previous thread seemed to be hijacked by someone elses question!
I recently decided to root my inspire as i am no longer using it as a phone, so i thought that it would be interesting to do and fun to play around with all of the options available (i recently did the same thing on my Nook Tablet, and that was the single best decision i have made a while!). I started out researching the manual techniques to do it, but i didn't really like the high risk factor there (i really dont want to brick my phone) so i tried Ace Hack Kit. Of course, it has to download the phone from 2.3.5 to be able to work. During this process, it has me hold volume up and power twice, and every time i do that, it flashes up really quick something about holding volume up and volume down and power, but then it skips past that. Anyway, here is where my problem comes in: It says that it should reboot in to hboot, which it does, but that hboot should run a test, then prompt me to continue by pressing volume up, and then should reboot, flashing twice, and that should be the end of it. THe problem is, it does boot in to hboot, but it is just a standard hboot screen asking to recover, load bootloader, etc. When i reboot from there it just boots in to the phone as normal. I have tried 3 different SD cards, all of which work and are recognized by my PC, my other phone and my Nook tablet. I have also inserted a working sim card, just to be sure that wasnt the issue, and i still cant make it work. Does anyone have any experience with his issue, or any idea what i might be doing wrong?
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
marsdta said:
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
Click to expand...
Click to collapse
OK, as i have stated, i have tried a new SD card (2, actually, with the same results.) as far as an output screen, there is none. Ace Hack Kit goes through the whole downgrade process, my phone gets in to hboot, but it is just a standard hboot screen, and it doesn't downgrade. When my phone restarts, it restarts like i just did a factory reset.
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
marsdta said:
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
Click to expand...
Click to collapse
by changing the of the boot img do you mean downgrading it? That is what i am trying to do. The kit is supposed to do it automatically. If that is not what you mean, please explain!
As to the output, copy thing, no, there is none of that. I have followed the instructions about 20 times. After starting the downgrade process, the phone restarts and comes up with a red triangle. At that point i am supposed to hold volume up and power, and it goes and reboots and i do the same thing again. At this point, i am told that the phone will boot into hboot and check the boot image. When it is done, i am supposed to hit volume up to confirm, and then the phone will reboot, this time in to the down graded image. That is where my problem comes in. Instead of checking the boot image, it just goes to a standard hboot screen. There are no error messages or warnings, and i have followed the instructions to the letter.
As far as the cards are concerned, the maker of the kit suggested a 2 or 4gb Sandisk series 4 or 6 SDHC card, so i bought 2 of the series 6 4gb, along with the 2 others that i already have. I also have 2 series 4 4gb and 2 series 4 2gb Sandisk cards, as well as an 8gb and 2 4gb PNY cards. All of the cards recognize in my phone and PC, and the older cards also recognize in my Nook (and were used to root and load custom roms on several other devices), i have not loaded the new cards in to any other devices besides my laptop and the phone for fear of corrupting it. So i find it difficult to believe that the cards could be the problem.
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
marsdta said:
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
Click to expand...
Click to collapse
I appreciate the attempt to help (the reason why i didn't post a direct copy paste was simply as i was in no position at the time to take one, not any reluctance to ultimately do so...) In my recent attempt to provide you with a full copy paste of the process, i was able to figure out what i was doing wrong. For anyone who may have the same or similar issue: format the SD card while it is in the phone from your PC right before starting the process. Thats all it took. Even for a card that was brand new and untouched, or formatted before putting it in the phone, i couldn't get it to work, but it worked doing it that way, and i am now happily rooted and ready to install CM9!
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
pazzo02 said:
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
Click to expand...
Click to collapse
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
glevitan said:
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
Click to expand...
Click to collapse
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
pazzo02 said:
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
Click to expand...
Click to collapse
As far as I am concerned the boot partition can not be restored by formatting. SDCARD should always be dismounted properly.

[Q] Unable to install or update "root" apps

Hi,
I have had my phone now for a week, and am a complete noob to Android.
All my other phones were windows based, and I am used to changing phones firmware etc. I am OK with a lot of the terminology, only, not with Android based products.
Now for my problem:
When I try to install an app, I am getting the "insufficient storage available".
It appears (to me, anyway), that it's only when I try to install, or update an app, that required a rooted phone to install/run, (ie. busybox, root checker, titanium backup, etc.) OR an update to one of the apps that came as "standard" with the phone (ie. ROM based).
All other apps appear to install fine.
I have Googled the error and found loads of people with this problem, and some have had it fixed by the methods below. I have tried them, but I still have the problem (as do MANY others it seems).
Does anyone know of a sure-fire way of getting the functionality back ?
I have a couple of copies of LuckyPatcher.apk, but I can't run or install either of them.
I have tried loading the <whatever>.apk file on the phone, then running it, I just get the "out of memory" error.
I have tried to just copy the <whatever>.apk into \system\apps, but it wont copy - I just get a "copy failed" message.
I have checked in \data\app for .odex files - there are none.
I have manually been through the Manage Apps details and cleared out the caches.
I have re-booted MANY times.
I did have Titanium Backup, but I have uninstalled it for now, as the pro key wont install, nor will any of the other "pro" keys I have purchased.
I hope I have presented enough information to start someones grey matter to tick over some rational fault finding techniques.
Please. Can someone help me ?
Regards,
Paul
-------------------------------------------------
Android 4.1.1
Samsung Galaxy Note 2 (16Gb)
32Gb MicroSD (unused)
Phone is Rooted
Hi,
I think your Internal Storage is empty.
You could move apps from Internal Storage to the internal storage.
Hope it helps
Daniel120201 said:
Hi,
I think your Internal Storage is empty.
You could move apps from Internal Storage to the internal storage.
Hope it helps
Click to expand...
Click to collapse
I don't think so, I have got 8.89Gb free.
Regards,
Paul
Do a backup and reinstall the rom
what is your android phone model..?
is depend on phone internal memory...
Hi,
I've fixed it now.
All the questions that have been asked are answered in my first post. I thought I would try and be helpful by including everything I could find about my phone and problem. I had scoured this (an other) forums, and read the questions people asked, as well as the answers they gave, hence the amount of information I gave originally.
Asking questions that have already been answered is of little use to me, and others in the same predicament, although I realise that it increases your post count.
Regards,
Paul

[Completed] Get Data Back after DataDeleted+FactoryReset+NewStockROM+Root

The question:
Is it actually possible recovering your data on an android device after flashing it with a Stock ROM?
The reason:
The whole story is about to be told, and you know that you don't have to read it.
I went through a few days of hell (and apparently it's a waste of time) in learning how to get back my photos.
1. Lenovo Vibe P1 (16GB internal memory) with 64GB SD card, no root.
A lot of space and a lot of photos. "Job" Gallery, Personal Gallery, "Fun" Gallery.
I decided to keep my photos organized and moved my "Job" Gallery to my SD card, as well as all other files, that I wouldn't miss much if they would get lost, as it often happens with SD cards, I believe.
"Job" Gallery is what I sometimes have to show to people by actually giving them my phone.
In order to keep my Personal Gallery away from anyone I simply moved it into an internal memory Folder with a "." in it's name (Hidden or System Folder is what Android calls them).
2. Personal photos lost.
One of the popular "Cleaning\Boosting" Apps or Android itself (not sure by now) decides to give me an advice to wipe my "Photos Cache", which is what I did, sadly.
It turned out that it deleted my personal photos from the Hidden Folder.
3. Failed Recovery.
Downloading "Data Recovery" apps did not help much since most of them wanted a Rooted device.
And those that could work without Root some why just wouldn't locate anything from my Hidden Folder.
4. Failed Rooting = dead SDcard.
I already knew about how hard it is to root my device, not to mention that going Android6.0 made it even harder, so I never wanted to take that risk.
Now I sort of a had to try, since most of the data I really cared about was lost.
Downloading rooting apps and trying them out somehow killed my SDcard.
5. Failed SDcard Recovery = dead CardReader, dying HardDrive.
While using some Data Recovery software on my PC with SDcard plugged via CardReader, something apparently went wrong and my HardDrive started having one of those dying sounds.
It still worked though, so I could spend some time browsing the recovered SDcard data.
Sadly, those files where unreadable, probably because the recovery software was trial, so it made all of them "Unreadable Before You Pay", hard to tell by now.
I decided to try another Recovery Tool, ignoring the HardDrive issue for now, but my CardReader or the SDcard or both appeared to be dead.
6. Bricking the Vibe.
After spending some time doing backups of my dying HardDrive data, I returned to Rooting my smartphone, but by "manual" methods this time.
Trying all of those scary weird methods while actually learning all the stuff about "flashing" led me into bricking my device.
7. Failed Rooted Recovery.
Somehow, by following few guides, I finally managed to do everything correct (I hope).
I mean, unlocking bootloader by fastboot, gaining temporary root by ADB, flashing TWRP recovery and Stock ROM by QFIL, installing SuperSU, and actually rooting the device.
Right after, I downloaded a bunch of recovery apps to try again, but all of the photos and pictures, found by scanning, were useless.
Even those results before rooting were much better.
8. Failed RAW Recovery.
Surfing different forums, led me to a guide about using PC recovery tools on an Android RAW image.
While surfing, I have already tried about five PC-Android recovery tools and they didn't help much, but I decided to try it anyway.
By using BusyBox, Cygwin, NetCat, ADB, VhdxTool, I made a RAW image of my internal memory partition, converted it into a VHD and mounted it for scanning.
After using about 25-30 recovery tools I did not find any of those desired lost photos.
Scanning results on jpegs are pretty much the same for each tool.
Thank you for reading if you decided to do so anyway.
I also found others who did try to recover their precious data, like I did (after flashing and going through all the problems with rooting and getting a RAW file).
It seems like they all failed as well, so the question is - is it actually possible?
I know it's much easier with an HDD, since I know that those mansions usually keep ghosts for years, while Android totally exhausted and after all, killed me.
I really need help with this, since I see no more ways to try. If you have any advice, please share.
P.S. I'm sorry for my english, not native.
XDA Visitor said:
The question:
Is it actually possible recovering your data on an android device after flashing it with a Stock ROM?
The reason:
The whole story is about to be told, and you know that you don't have to read it.
I went through a few days of hell (and apparently it's a waste of time) in learning how to get back my photos.
1. Lenovo Vibe P1 (16GB internal memory) with 64GB SD card, no root.
A lot of space and a lot of photos. "Job" Gallery, Personal Gallery, "Fun" Gallery.
I decided to keep my photos organized and moved my "Job" Gallery to my SD card, as well as all other files, that I wouldn't miss much if they would get lost, as it often happens with SD cards, I believe.
"Job" Gallery is what I sometimes have to show to people by actually giving them my phone.
In order to keep my Personal Gallery away from anyone I simply moved it into an internal memory Folder with a "." in it's name (Hidden or System Folder is what Android calls them).
2. Personal photos lost.
One of the popular "Cleaning\Boosting" Apps or Android itself (not sure by now) decides to give me an advice to wipe my "Photos Cache", which is what I did, sadly.
It turned out that it deleted my personal photos from the Hidden Folder.
3. Failed Recovery.
Downloading "Data Recovery" apps did not help much since most of them wanted a Rooted device.
And those that could work without Root some why just wouldn't locate anything from my Hidden Folder.
4. Failed Rooting = dead SDcard.
I already knew about how hard it is to root my device, not to mention that going Android6.0 made it even harder, so I never wanted to take that risk.
Now I sort of a had to try, since most of the data I really cared about was lost.
Downloading rooting apps and trying them out somehow killed my SDcard.
5. Failed SDcard Recovery = dead CardReader, dying HardDrive.
While using some Data Recovery software on my PC with SDcard plugged via CardReader, something apparently went wrong and my HardDrive started having one of those dying sounds.
It still worked though, so I could spend some time browsing the recovered SDcard data.
Sadly, those files where unreadable, probably because the recovery software was trial, so it made all of them "Unreadable Before You Pay", hard to tell by now.
I decided to try another Recovery Tool, ignoring the HardDrive issue for now, but my CardReader or the SDcard or both appeared to be dead.
6. Bricking the Vibe.
After spending some time doing backups of my dying HardDrive data, I returned to Rooting my smartphone, but by "manual" methods this time.
Trying all of those scary weird methods while actually learning all the stuff about "flashing" led me into bricking my device.
7. Failed Rooted Recovery.
Somehow, by following few guides, I finally managed to do everything correct (I hope).
I mean, unlocking bootloader by fastboot, gaining temporary root by ADB, flashing TWRP recovery and Stock ROM by QFIL, installing SuperSU, and actually rooting the device.
Right after, I downloaded a bunch of recovery apps to try again, but all of the photos and pictures, found by scanning, were useless.
Even those results before rooting were much better.
8. Failed RAW Recovery.
Surfing different forums, led me to a guide about using PC recovery tools on an Android RAW image.
While surfing, I have already tried about five PC-Android recovery tools and they didn't help much, but I decided to try it anyway.
By using BusyBox, Cygwin, NetCat, ADB, VhdxTool, I made a RAW image of my internal memory partition, converted it into a VHD and mounted it for scanning.
After using about 25-30 recovery tools I did not find any of those desired lost photos.
Scanning results on jpegs are pretty much the same for each tool.
Thank you for reading if you decided to do so anyway.
I also found others who did try to recover their precious data, like I did (after flashing and going through all the problems with rooting and getting a RAW file).
It seems like they all failed as well, so the question is - is it actually possible?
I know it's much easier with an HDD, since I know that those mansions usually keep ghosts for years, while Android totally exhausted and after all, killed me.
I really need help with this, since I see no more ways to try. If you have any advice, please share.
P.S. I'm sorry for my english, not native.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please have a look at the P1 homepage:
http://forum.xda-developers.com/vibe-p1
If you create an XDA account, you can ask your question to the experts here:
http://forum.xda-developers.com/vibe-p1/help
Good luck and welcome to XDA!

Categories

Resources