Related
So I had rooted my Htc Evo 4g and I would try new ROM's maybe once a week or so... And than I flash a ROM and go to install some apps and I get a low memory warning. I used to have that problem with my Hero. I did the full wipe (everything 3x) and I was wondering why I would be low on memory after clearing everything? Is there something I'm missing, lol?!!
Are you using A2SD with an ext partition? And if so, are you wiping EXT as well? I know you said everything, just checking.
I have never had that problem, and I regularly have around 100 or so apps on my phone.
What roms are you trying? I have tried most roms on here, and almost all of them actually use LESS space then the stock rom, as they get rid of things you dont need.
Bad clusters?? Look at the recovery.log after a wipe
bkrodgers said:
Are you using A2SD with an ext partition? And if so, are you wiping EXT as well? I know you said everything, just checking.
Click to expand...
Click to collapse
Lol... Actually I've never wiped that but I don't use the A2SD or anything so it never crossed my mind...
gpz1100 said:
Bad clusters?? Look at the recovery.log after a wipe
Click to expand...
Click to collapse
What is and how do I check the recovery log? Sorry for the newb question, you'd think I'd know by now, lol!!!
By bad clusters I assume he means bad blocks. It sounds like parts of your memory have become damaged simply through normal use, its inevitable in all solid state memories. Supposedly some evos have been shipped with defects that cause lots of bad blocks. If your hardware version is 0003 or lower there's a chance yours was one.
Davidsr1127 said:
What is and how do I check the recovery log? Sorry for the newb question, you'd think I'd know by now, lol!!!
Click to expand...
Click to collapse
Recovery.log is generated at /tmp/recovery.log whenever you do something in recovery. In recovery, if you go to advanced and then select report error it will copy that file to /sdcard/clockworkmod/recovery.log.
I doubt you'll find anything about bad blocks in that file. I just generated one and looked through it and the only thing about blocks that it says is "successfully wrote to block 0", which is just one block out of thousands. Its mostly technical things like what version of recovery you have, what radio your using things like that. It wouldn't hurt to look through it though. Some of it wont make sense, some will. Just look through line by line, it'll take like 5 minutes.
Davidsr1127 said:
What is and how do I check the recovery log? Sorry for the newb question, you'd think I'd know by now, lol!!!
Click to expand...
Click to collapse
Yes, I did mean bad blocks, but had sectors and clusters on the mind
Type the following from a dos prompt in the folder containing adb
adb shell
df
Paste the results into a reply. This will show us just how much free space you have and where.
Got my Note 2 in today .. any ROM's known working with this hardware ? I'd read there might be issues with so many different versions of this device.
Thanks !
Sorry, but the i317 doesn't have any ROM. Not a single byte of it.
Perhaps you were asking about firmware?
garyd9 said:
Sorry, but the i317 doesn't have any ROM. Not a single byte of it.
Perhaps you were asking about firmware?
Click to expand...
Click to collapse
Interesting point. What are the firmwares stored in inside these modern devices? Are they not EEPROMs or some variant that are being flashed?
Non-volatile random-access memory.
All the memory in the device is one big pool similar to an SSD drive (even if its partitioned and mounted to appear otherwise.)
EEPROM would be WAY too slow (and wouldn't have the endurance.) Also, with EEPROM, you'd have to effectively erase and reformat all the device memory every time you got a new email message, logged a phone call, etc. (No random access with EEPROM.)
Yeah, I'm old.
Understanding the firmware... imagine shoving an SSD drive into a machine and making 2 partitions. The first you call "C" and install windows on. Then you create another partition ("D") to use as a data drive. You hack windows so that all writes are redirected to D. Now only mount the C drive as ro and mount D as rw.
This is easier with linux... first logical contains /usr, /etc, /home. /home contains mount points for the second logical that's mounted rw. Any time the firmware changes, the first drive is remounted as rw, changes made, and remounted as ro again.
ohRonaldo said:
Interesting point. What are the firmwares stored in inside these modern devices? Are they not EEPROMs or some variant that are being flashed?
Click to expand...
Click to collapse
I think his point of the question is that ROM usually would be a new aftermarket offing, say CM10 etc. And the Firmware refers to the Sammy official stock load or image (TAR?) that is flashed in ODIN or perhaps Keis.
I don't think that was a discussion on hardware.
ZedZardoz said:
I think his point of the question is that ROM usually would be a new aftermarket offing, say CM10 etc. And the Firmware refers to the Sammy official stock load or image (TAR?) that is flashed in ODIN or perhaps Keis.
Click to expand...
Click to collapse
How are they different? Either mount as /system and perform the same function. They are both firmware.
ROM means "read only memory." If it was actually ROM, it couldn't be modified.
If it'd help, I'd be happy to recompile CM10 for the i9300 and wrap it up in an ODIN compatible tarball.
garyd9 said:
How are they different? Either mount as /system and perform the same function. They are both firmware.
ROM means "read only memory." If it was actually ROM, it couldn't be modified.
If it'd help, I'd be happy to recompile CM10 for the i9300 and wrap it up in an ODIN compatible tarball.
Click to expand...
Click to collapse
Agreed. Just bits programmed to a memory.
garyd9 said:
Sorry, but the i317 doesn't have any ROM. Not a single byte of it.
Perhaps you were asking about firmware?
Click to expand...
Click to collapse
Now that I re-read your post, I see that it was a discussion of hardware. But aren't you just quibbling on symatics?
Off-topic> Is there a way to dump the TAR off my new phone prior to root? I guess some day the official firmware will become available.
ZedZardoz said:
Is there a way to dump the TAR off my knew phone prior to root? I guess some day the official firmware will become available.
Click to expand...
Click to collapse
Not all at once. The stock kernel and stock recovery images are already extracted. What I'd suggest is this:
After you get your phone, use ODIN to install the root kernel referenced in this post: http://forum.xda-developers.com/showpost.php?p=33846420&postcount=163
Then adb shell into the phone, but when you do the dd thing, instead of pulling the recovery partition, you can pull the system partition. The commandline would be:
dd if=/dev/block/mmcblk0p13 of=system.img bs=4096
That will result in a huge (but completely stock) system partition image. That, combined with the recovery.img and boot.img (kernel) we already have can be used to get a system completely stock.
PS: I hope the community gets you a Note2 soon!
Click to expand...
Click to collapse
Why? I just sold an international note2 and am using an AT&T note2. If the community were to try to donate one to me, I'd tell them to take their money and donate it to some children that need food, clothes, etc.
garyd9 said:
Not all at once. The stock kernel and stock recovery images are already extracted. What I'd suggest is this:
After you get your phone, use ODIN to install the root kernel referenced in this post: http://forum.xda-developers.com/showpost.php?p=33846420&postcount=163
Then adb shell into the phone, but when you do the dd thing, instead of pulling the recovery partition, you can pull the system partition. The commandline would be:
dd if=/dev/block/mmcblk0p13 of=system.img bs=4096
That will result in a huge (but completely stock) system partition image. That, combined with the recovery.img and boot.img (kernel) we already have can be used to get a system completely stock.
Why? I just sold an international note2 and am using an AT&T note2. If the community were to try to donate one to me, I'd tell them to take their money and donate it to some children that need food, clothes, etc.
Click to expand...
Click to collapse
Thanks for the response.
Sorry the PS was ment for another thread... Damn all this time waiting on my delivery and too much thread watching / posting.
It *is* a variant of EEPROM. It is also a type of "non-volatile RAM" which is also a form of erasable ROM. It's much further from RAM than it is from EEPROM. RAM needs constant power to refresh it to prevent data loss and reading it is destructive, it degrades the contents and requires recharging time before being accessed again.
I thought I'd try to point it out in question form. The guy asked an innocent question using older but correct terminology -- I completely understand being in that position because I'm an old man, a traveling man, trying to figure this new stuff out too.
ohRonaldo said:
It *is* a variant of EEPROM. It is also a type of "non-volatile RAM" which is also a form of erasable ROM. It's much further from RAM than it is from EEPROM. RAM needs constant power to refresh it to prevent data loss and reading it is destructive, it degrades the contents and requires recharging time before being accessed again.
I thought I'd try to point it out in question form. The guy asked an innocent question using older but correct terminology -- I completely understand being in that position because I'm an old man, a traveling man, trying to figure this new stuff out too.
Click to expand...
Click to collapse
First, please stop referencing your age in every single post. We get it. You're old. You might actually be surprised to learn that quite a few other people here are old as well.
As for EEPROM or not, I actually still use EEPROM with some of my ham radio gear, and NVRAM is nothing like it in general use. In order to rewrite any portion of EEPROM, the entire chip has to be erased. (I made reference to that above.) Same issue with EPROM (but for a slightly different reason.) I agree it might be similar electrically, but from a usage point of view, "ROM" is nothing like "NVRAM."
Oh, and I'm old too. How old? Let's just say that I wrote my first computer programs, I was terrified of dropping the deck and getting the cards out of order.
Take care
Gary
That's why you draw a line across the top of the deck, Gary. HI HI
73
ohRonaldo said:
That's why you draw a line across the top of the deck, Gary. HI HI
Click to expand...
Click to collapse
yep. okay, I'll kill stop harassing everyone.
dit dit
Hello,
New XDA poster, here... I've watched the intro video, and I've read the forum rules.
I'm not completely new to custom roms; I've previously flashed CM images on 2 other occasions, (on this same device, and 1 other.)
My question is: if I've lost my maguro's IMEI number (presumably by wiping /factory via CWM,) how screwed am I? I do not have a backup of /factory.
Here's how I got myself into this mess:
(Started from CM-10.1.2 or CM-10.1.3, can't remember.)
1. Updated recovery to clockwork-6.0.4.3-maguro
2. Factory reset (from inside recovery)
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
4. Installed "cm-10.2-20131030-NIGHTLY-maguro.zip"
5. Installed "gapps-jb-20130813-signed.zip"
6. Rebooted
Everything worked peachy, except now my mobile service is permanently unavailable. Confirmed that I now have a generic IMEI number under Settings -> About phone -> Status.
This was a Play Store purchase; I am the original owner.
</ryan>
I have the same issue.
Did the /factory wipe on my phone from cwm. Among other wipes from the mounts menu.
Installed cm-10.2 ... Nightly
Here are the problems which I am facing.
1. The network signal indicator is blank & the phone reports emergency calls only. On my Vodafone's sim. ( also on tata DoCoMo & Idea sim cards).
2. Although the network signal indicator is blank 2g gsm mobile data is still working I.e. I can access websites, sync my phone with Google etc. Its just the call functionality is not working.
3. Tried another SIM from BSNL ( a local service provider in India). This sim works fine all the functionality ie call, sms , data is working on the BSNL sim.
If anyone has any suggestion how to fix this issue please help.
Sent from my Galaxy Nexus
I haven't done this with the Gnex, but this did happen with the i9000 and i9100 back then when moving from CM6 > CM7 and formatting from RFS over to EXT2 partitions destroyed my EFS folder. What I ended up doing was using Odin to flash back to stock from bootloader: the TAR images. I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
OK let me try ODIN flashing.
Using the method & files from the following post
http://forum.xda-developers.com/showthread.php?t=2065470
Sent from my Galaxy Nexus
alpha-niner64 said:
I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
Click to expand...
Click to collapse
Of course I'm willing to try anything that stands some chance of success, but I wonder: how could flashing Google's stock takju image-- that is the same for everybody-- restore an IMEI number that is different for everybody?
Solution...
Well kinda.
The issue is with Generic IMEI 004999010640000 most network providers have blocked this IMEI no. on their network, which is why the network registration fails & thus we get no network.
Their is a file nv_data.bin in 2 places on the device one is in /factory/nv_data.bin & the other is in /data/radio/nv_data.bin
The file in /data/radio/nv_data.bin determines the phones imei no. & the one in /factory/nv_data.bin is the backup.
In case the phone gets wiped or factory reset the system copies the file from /factory/nv_data.bin to /data/radio/nv_data.bin in order to determine the handsets IMEI no.
When you & I wiped the /factory/ in CWM it removed this backup file, thus on installation of any subsequent roms the phone was getting a generic imei resulting in network error.
If you have a NANDROID backup of the phone in an earlier state when the network was working correctly then restore from that backup & your network should be fine. I did & it restored my network.
Also if you are successful in getting your network & IMEI back I suggest backing up /data/radio/nv_data.bin & /data/radio/nv_data.bin.md5 to your PC because since the nandroid backup does not restore these files in /factory/ I am guessing any future wipe / rom upgrades will reset the radio to generic IMEI.
If you dont have a nandroid backup of a earlier good state of your phone I have no idea how to recreate the files.
in case you need it You can find your handsets IMEI no. in at the back of the phone below the battery.
The following links may help
http://forum.xda-developers.com/showthread.php?t=1570342
http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
ryanvbissell said:
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Click to expand...
Click to collapse
Update...
@ryanvbissell any nandroid backup (no matter how old or whichever rom ) will do even if it is not CM.
You may try the procedure on the link above, but from what I have read Galaxy Nexus NV_data uses salted md5 checksums so that method might not work.
Also if you have the nv_data.bin & nv_data.bin.md5 files you can push it into /factory so that whenever you flash a new rom or do a factory wipe the system picks up these files from /factory & restores correct IMEI data.
You will need ADB & Samsung USB Drivers(only on windows) for this procedure to work, Please Google how to installing ADB
& If you are on windows installing Samsung USB Drivers for Galaxy Nexus. drivers for Galaxy Nexus™ (Verizon) Android Smartphone, work for the GSM variant as well.
On MAC you don't need the USB drivers, just install ADB.
Here is how
1. From CWM recovery -> mounts and storage -> mount /factory.
2. From your PC -> adb push nv_data.bin /factory
3. From your PC -> adb push nv_data.bin.md5 /factory
4. From Your PC -> adb shell
5. From Your PC -> # cd factory/
6. From Your PC -> /factory # chmod 700 nv_data.bin
7. From Your PC -> /factory # chmod 700 nv_data.bin.md5
8. From Your PC -> /factory # chown radio.radio nv_data.bin
9. From Your PC -> /factory # chown radio.radio nv_data.bin.md5
10. From Your PC -> exit
After this install a new ROM or do a factory wipe & your IMEI should be back & networks should work.
now any future wipe / rom upgrades will NOT reset the radio to generic IMEI.
I have done the same on my phone with successful results.
ryanvbissell said:
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
Click to expand...
Click to collapse
I did the exact same thing, felt the exact same way, and on the same day too. And I had also purged all my backups at one point and decided to start over when this happened. Freaky.
@gaurav1984 - That was my solution as well. Luckily, it turned out I had an old lingering backup I made months ago on a network drive from the last time I backed up my desktop to reinstall Windows. Completely forgot about it until just a little while ago, and found out that a regular data backup (at least with TWRP) includes /data/radio, so it contained a good set of nv_data.bin and nv_data.bin.md5. I wound up doing exactly what you did but also pushed them to /data/radio/ and set the same permissions/ownerships there -- more of a spray-and-pray tactic since I hadn't seen your post at the time. Crossed my fingers, rebooted, and it worked! What a nerve-racking 24 hours.
Needless to say, those files are now backed up in several locations. Having /factory in the format list seems odd... should have to go out of your way to format something that important.
From what I found before I discovered my old backup, you'd have to buy a $200 magic box (which I think would just end up being an overpriced UART cable for this particular phone) and possibly some software to do an "IMEI Repair." I found some cheaper options from SRS Services through SamMobile (~$15US UART cable from China plus ~$35US to run a repair once), but it wasn't 100% clear if it could fix a formatted /factory partition with no backup whatsoever. I'm guessing it could since it requires a UART cable and the demo videos showed assigning an IMEI. Rebuilding these files is probably hard to come by since the same process can be used to clone another IMEI or change your IMEI to something other than what it's supposed to be, which is illegal in some countries.
mrbo said:
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
---------- Post added 3rd November 2013 at 12:14 AM ---------- Previous post was 2nd November 2013 at 11:51 PM ----------
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
Misery loves company.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.[/QUOTE]
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
ryanvbissell said:
rburrow said:
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
Click to expand...
Click to collapse
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
Click to expand...
Click to collapse
Hah. I finally decided to order a Nexus 5 like an hour or two before I managed to wipe all the nv_data files simultaneously. My friend told me that I had a tiny tablet now when I figured out what I had done.
cardboardhome said:
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
Click to expand...
Click to collapse
If you really don't have a backup anywhere, I think your only solution is to send it in somewhere to have the IMEI repaired (either someone that says they can fix it, or to Samsung). Unfortunately it's more than likely going to cost money. The cheapest potential solution I could find was from SRS Services / SamMobile, where you have to buy a UART cable and pay to do an IMEI repair using their software. I have never used them so I have no idea how all that works out.
I searched quite a bit (albeit only for a like a day) for a free DIY way to regenerate or create a new nv_data.bin file, but I just couldn't find anything. The only thing I didn't try was an OMAP flash because I couldn't install the driver that came with the zip in Windows 8.1 64-bit, but I was already giving up at that point so I didn't go any further.
@ryan
I was just wondering about the ODIN method as posted on post no. 2 & 3.
When you flash your phone using ODIN it wipes the whole internal memory & recreates the partitions.
Thus we can assume all files gets wiped including those in the /factory.
So I was thinking if Odin recreates the whole filesystem as new maybe there might be some file or script or program .... In there which recreates the IMEI files as well.
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Sent from my Galaxy Nexus using xda app-developers app
gaurav1984 said:
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Click to expand...
Click to collapse
Good point. I originally passed up on the Odin angle because on a page that listed versions of Odin for specific phones, there was no suggested version for the i9250. But you have a good point; I really have nothing to lose. So I will try it, but it may take me a few days before I have time.
Meanwhile, I took my GN to a local 'CPR' cellphone repair shop, and explained my predicament. Their tech just shook his head sadly and said 'Only Samsung has the proprietary software to fix this.' I found that surprising because I think I've seen references online to some $200+ kit called SPT ("Samsung Phone Tools") which I thought was geared towards professional phone repair businesses. Oh well.
Sent from my ANDROID TOUCH... sigh.
</ryan>
IMEI
Odin flashing doesn't work
struggled today
dkkerry said:
Odin flashing doesn't work
Click to expand...
Click to collapse
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
pvkiniyan95 said:
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
Click to expand...
Click to collapse
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
file too big
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Utkarsh-ezzo said:
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
Click to expand...
Click to collapse
pvkiniyan95 said:
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Click to expand...
Click to collapse
ya i can understand that,
i think we domt have efs partition on gnex its located at /factory , so if you could share the file from /factory it would be great for me,
nv_data.bin, nv_data.bin.md5 , .nv_data.bak and .nv_data.bak.md5
these files from /factory would help me out..
you will need to use root browser or root explorer or adb shell....
Sent from my Galaxy Nexus using Tapatalk
hi guys, I am having trouble with my MI Max having 32GB internal memory.
From it's behaviour for last few days I have inferred it's system partition is the culprit.
On stock miui rom, it gives msg that encryption unsuccessful and I need to factory reset it. But even after doing factory reset it shows the same msg.
Its with locked boot loader but referring one thread I could install twrp latest version on it by replacing recovery image in stock rom and flashing with mi flash tool in edl mode.
So with two I tried installing few vision rooms like miui eu ROM, RR and crdroid based on Oreo. All the rooms while flashing fine error E1001, saying system image not updated and flashing failed.
I even tried repairing file system, fixing file system, Channing file system to fat, exfat, ext2, ext3, ext4 and f2fs several times (from advanced wipe menu) but things are not improving. Even tried formatting data partition as it's suggested at few places.
I am out of ideas after spending few days trying to fix it by flashing several times.
So please if some one can assist in resolving the issue, I would really appreciate.
Thank you in advance.
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Zasnizas said:
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Click to expand...
Click to collapse
Have already done it several times by now. Didn't make any difference.
harpy.eagle said:
Have already done it several times by now. Didn't make any difference.
Click to expand...
Click to collapse
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Zola III said:
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Click to expand...
Click to collapse
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
harpy.eagle said:
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
Click to expand...
Click to collapse
It's still ain't bricked so you can do this relatively easy. When it's bricked EDL programmer for used NAND chip used is needed.
So take a deep breath, see the exact size & type of the partition, delate it, create a new one exactly the same (type, size & name).
https://s10629.pcdn.co/wp-content/pictures/2010/01/captured_Image1.png51.png
https://helpdeskgeek.com/wp-content/pictures/2010/01/captured_Image1.png111.png
The tool I gave you URL is very good documented and with plenty examples & user guides available all which can be found on the site, it uses graphics GUI so it's as easy as it can be. So if you are inexperienced read/watch first how it's done. After you are done flash what you want in TWRP.
Best regards.
What I meant to ask is, how to access partitions of mobile on PC? I have used partitioning app on windows but never for android device. Anyway, as u have clued, I shall try accessing partitions with mobile connected in edl mode.
Hello, there is my problem with OP9 Pro – phone was stuck with some bug and only way to fix it was Wipe Data. Now it's ok, but I do really need to restore photos and videos. Phone is NOT rooted.
After reading tons of information I'm not sure that it's possible to get data back. As I understand I need to follow next steps:
1. Unlock bootloader without wiping data again in order not to lose old structure.
2. Root device, or at least temporary root it.
3. Use some tools to search and restore photos.
But now I'm not sure that everything would be fine. Even the first step is not 100% guarantee that it's possible to avoid data wiping.
So, If there are someone who understand this better, could you please advice me what should I do? Should I waste tons of time or it's muck more likely impossible to do?
Thanks!
mrGenry said:
Hello, there is my problem with OP9 Pro – phone was stuck with some bug and only way to fix it was Wipe Data. Now it's ok, but I do really need to restore photos and videos. Phone is NOT rooted.
After reading tons of information I'm not sure that it's possible to get data back. As I understand I need to follow next steps:
1. Unlock bootloader without wiping data again in order not to lose old structure.
2. Root device, or at least temporary root it.
3. Use some tools to search and restore photos.
But now I'm not sure that everything would be fine. Even the first step is not 100% guarantee that it's possible to avoid data wiping.
So, If there are someone who understand this better, could you please advice me what should I do? Should I waste tons of time or it's muck more likely impossible to do?
Thanks!
Click to expand...
Click to collapse
If you are not bootloader unlocked right now. All hope is lost since unlocking will force a wipe of data that can't be stopped.
MrSteelX said:
If you are not bootloader unlocked right now. All hope is lost since unlocking will force a wipe of data that can't be stopped.
Click to expand...
Click to collapse
I just wiped phone and restored some latest backup (which did not contain media ofc). I was reading about scenario, when we can backup current system, patch it somehow, unlock bootloader and keep old data somehow in place. But it looks so unstable for me.
The folder structure was destroyed when the data was deleted. Although the files still exist -if- they haven't been overwritten, they would be completely juxtaposed. A vast sea of files that could only be sorted by size and file type. No associated time stamps, exif data, original file names and no way to restore it. Let that sink in for a moment.
Just recovering a flash card with a 100 images on it and then trying to sort them is a major headache unless you have a photographic memory. The files names are gone. The recovered images will have a new assigned number generated that is unrelated to the file's original name. Now imagine trying to do that with a 100gb jigsaw puzzle from hell.
Always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
blackhawk said:
The folder structure was destroyed when the data was deleted. Although the files still exist -if- they haven't been overwritten, they would be completely juxtaposed. A vast sea of files that could only be sorted by size and file type. No associated time stamps, exif data, original file names and no way to restore it. Let that sink in for a moment.
Just recovering a flash card with a 100 images on it and then trying to sort them is a major headache unless you have a photographic memory. The files names are gone. The recovered images will have a new assigned number generated that is unrelated to the file's original name. Now imagine trying to do that with a 100gb jigsaw puzzle from hell.
Always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Click to expand...
Click to collapse
Yeah, thanks! Really, there is nothing critical, just default amount of family photos and videos (phone is my father's, I'm just investigating possibility of recovering).
And tons of different information is all across the web. Also, latest Android 12 is pretty new and I guess lots of articles are not suite for that phone.
So, I guess it's too overwhelmed even to try root phone and search files. Maybe, data value is lower that possibility to turn phone into a brick.
mrGenry said:
Yeah, thanks! Really, there is nothing critical, just default amount of family photos and videos (phone is my father's, I'm just investigating possibility of recovering).
And tons of different information is all across the web. Also, latest Android 12 is pretty new and I guess lots of articles are not suite for that phone.
So, I guess it's too overwhelmed even to try root phone and search files. Maybe, data value is lower that possibility to turn phone into a brick.
Click to expand...
Click to collapse
If you want the best possible outcome take it to a data recovery specialist. That's all they do.
Don't use any apps like FoneDoctor, they will find stuff but encrypt the drive $o only that app can unencrypt it.
blackhawk said:
If you want the best possible outcome take it to a data recovery specialist. That's all they do.
Don't use any apps like FoneDoctor, they will find stuff but encrypt the drive $o only that app can unencrypt it.
Click to expand...
Click to collapse
Thanks! A bit upset, but Im great to get useful information.
mrGenry said:
Thanks! A bit upset, but Im great to get useful information.
Click to expand...
Click to collapse
Losing critical data is never pretty.
I've lost a database with decades of data on it. The only way to help prevent this is redundant backups.
Perhaps your father had backup them up deliberately or by happenstance to a PC or other device.