Hey, I have a huge problem... (I couldn't find the answer anywhere)
I inserted the phone lock password (WM6.5) too many times wrong and it locked forever (ROM bug?). When I gave the right pass it did nothing. So I decided to flash WP7 or Android to my Leo but... I need to backup my data from internal memory before. Is there any way to dump phone internal memory via bootloader mode or any way to mount it to Linux. Or even to do "dd" on Linux to export the whole memory to a file.
No.
The only method i've come across to dump the nand uses psdwrite, and that not only requires winmo to be working, but only gives you the rom as it was out of the box, no data.
Perhaps there are hardware solutions to dump the nand, along the lines of jtag, but I've never seen reference to anything like it.
yes, the only way is via jtag. Even so, a jtag dump will contain only binary data, in the exact way they were physically stored on the nand memory chip.
You need to "compile" them to a more useful form but i don't know of some way to do that.
Older phones simply allowed active sync connection even if still locked by passwords. Those were easier times
OK, I don't need any more answers because I have installed WP7. Anyway this thread will be useful in the future so if you know something about accessing internal memory of Leo via bootloader then please write
Related
I used to play with roms on my Wizard alot, ive had my HD2 since release and thinking about toying with some roms. I've done some searching and cant see to find any previous posts about this
On the wizard you could use a program such as mtty and run the r2sd all command with a blank sd card of the same capacity as the device's rom and it would dump the entire rom contents into the SD card.
Does this also work on the HD2 or is there a similar command to do the same?
I found it to be a good way to do an image of the device as it currently existed, so i could trial a rom, if i didnt like it id put that SD card back in and dump it back to the phone in bootloader mode.
This type of ROM dump would get everything, the rom and user writable flash space, in essence it was like a ghost image of your PC's hd. you wouldnt have to deal with backup software which at times seems to not get everything.
Hello,
Go here...http://forum.xda-developers.com/showthread.php?t=623356
and here...http://forum.xda-developers.com/showthread.php?t=644781
and maybe here...http://forum.xda-developers.com/showthread.php?t=575579
To help you out in future, also use this...http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
Hope this all helps. Happy reading.
WB
Has anyone been able to backup an activated WP7 Rom. Since the WP7 Rom password which is tied directly to the sd card used when the phone is initially turned on prevents easily swapping stuff around, I like to backup my existing WP7 Rom. Then I can flash a Nandroid Gingerbread Rom and then be able to return flash to my stored activate WP7 Rom/SD card whenever I'd like. Sounds good anyway.
hooutoo said:
Has anyone been able to backup an activated WP7 Rom. Since the WP7 Rom password which is tied directly to the sd card used when the phone is initially turned on prevents easily swapping stuff around, I like to backup my existing WP7 Rom. Then I can flash a Nandroid Gingerbread Rom and then be able to return flash to my stored activate WP7 Rom/SD card whenever I'd like. Sounds good anyway.
Click to expand...
Click to collapse
You mean a program like Nandroid?
And no. That's not possible at the current moment.
That's too bad, what we need is a version of ClockworkMod that works with WP7.
This would be a great tool if someone brought it out.
Have my HD2 now running wp7,activated and not bad at all, loads of apps missing
that I would normally have in my android build.
Wanting to flash back to android but would also like to backup this activated wp7
and then can swap and change as new stuff comes out.
Any mods willing to take this on.
George
maybe by reg'?
hooutoo said:
Has anyone been able to backup an activated WP7 Rom. Since the WP7 Rom password which is tied directly to the sd card used when the phone is initially turned on prevents easily swapping stuff around, I like to backup my existing WP7 Rom. Then I can flash a Nandroid Gingerbread Rom and then be able to return flash to my stored activate WP7 Rom/SD card whenever I'd like. Sounds good anyway.
Click to expand...
Click to collapse
I am positive there could be a way through Regedit.
I carry a 16gb sd and i noticed it showed a little reserved partition of around 20% in the zune software(which allows its tweaking). The tweak ability was gone after reinstalling windows and zune.. and that made me loss the partition and an extra unused 2gb.
Now the main thing is, i reg edited the phone for portable usb capabilities - viewing its content, moving, creating and pasting stuff around. To regain my full gb's, i wud 've copied all contents to pc and formatted it but then realized it contained all call history and EVERY settings made to the phone(on sd) which the reg editing i did didnt give full access to than only the media folders.
Unless ADVANCED reged' is made to make visible all primary phone settings(for easy pc backup) then . . . . . . . . . yeah....'no cant do'
But this is xda. and i hope someone could figure this out
When I try to turn my phone on, it will not get passed the ROM loading screen (Energy blue logo). This is because the internal memory is full.
I really need to get into the file system to delete a file (and fix the problem) or copy certain stuff out - it has pictures of my fiance on to say the least, and I really want them.
But, as Windows won't boot I can't do this in the traditional way. Obviously I can still get into bootloader - so is there a way I can access the file system? A bit of software I can run on my laptop that can somehow access the file system through bootloader mode? All I need to do is identify a c.1mb file and delete it...
The background to all this is the phone was displaying messages about 'memory nearly full' - but it had done this before and just stopped, so I left it again. Except, at some point signal reception dropped and stayed at 0. So I rebooted, and got stuck at the loading screen - which is where we've been for the last few days now.
I really hope someone can help. If you can, I'll buy you a few beers.
Thanks,
David
Phone was running WM6.5 with HSPL (3 I'm fairly sure)
How in the hell did you manage to fill your internal memory up, why not just use a SD card for storage?
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
I think I took too many photos! Though I'm not exactly sure tbh... Some bug in the ROM kept changing the save dir from SD card to internal, but I did keep an eye on the space, perhaps just a few too many photos in one night...
Anyway ActiveSync isn't working (for me at least) in bootloader mode - don't I need to have Windows Mobile loaded?
Should activesync work in bootloader mode?
TheATHEiST said:
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
Click to expand...
Click to collapse
doesnt work. you cant access the live file system from anywhere except within running wm.
You can dump off the rom partition into .raw files, but when you rebuilt it (in a ktchen) you would still only end up with the original rom as it was out of the box, no user data.
@OP, you could possibly go into bootloader, confirm 2.08.hspl, flash magldr, and then boot from an sd android, though i suspect you still wouldn't see the winmo files. (I assume there are now android builds that can be booted to and run from sd without the need for haret/winmo? i'm a nand man meself so unsure. )
It's what i'd try if it really was that critical, otherwise I'd weep for a little while, kick myself and write 'backup' post-its all over my office, then hard reset and move on.
Thanks for the advice - I will definitely try your suggestion before 'moving on', losing a whole bunch of contacts will also be a real pain.
Do you know of any threads/links explaining magldr and how it will help?
Is there no other way to access any part of the internal memory and just delete 1 file?
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Thanks
Bear in mind WP7 and winmo are two very different OSes.
WP7 has been out btw.
Once you flash the device, with MAGLDR, android or WP7, the internal storage is wiped so it makes no sense to flash it if you still want what is in it.
davenash said:
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
Click to expand...
Click to collapse
any type of flashing (nandroid, wp7 or wm) will destroy whats on there already, thus defeating the object.
There are more than two options in magldr, one of which is 'boot sd ad' for boot sd card android.
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Click to expand...
Click to collapse
its probably not an issue of the file system type, android (linux) can access fat partitions no problem. Its probably more to do with whether the sd builds can mount the internal rom or not.
Im no linux head at all, still fumbling in the dark though, so i could be wrong.
I have a Touch Pro 2 but this applies to any Windows Mobile Phone.
I have searched but surprised to find there seems to be no application which can be installed on a Windows phone which at boot, recursively makes a raw back up of the file system to the SD Card.
This backup could then be written back to the NAND storage memory so that the phone would be in the exact state it was before testing a ROM without having to use various backup programs to get every little thing back the way it was. I.e literally a clone of the phone system memory to the SD card and back.
Please let me know if this is simple impossible and as such I am wasting my time looking
Thanks.
bump
The problem is solved, the solution is as followed:
Problem
- The device is unable to mount every partition, this includes:
/efs
/persdata
/system
/data
/cache
Solution
Flash the stock firmware following this instruction to Repartition the device:
https://www.sammobile.com/forum/showthread.php?t=30800
The credit goes to member greenman of sammobile forum as the link above.
Thank you very much for everyone who took the time and effort to read the thread and answer my question. I appreciate it a lot.
HI there, i think you should try and grab an image for 935F from sammobile and restore with ODIN? This should restore the device into clean state. Not sure if you tried, ie to boot into download mode, and flash via odin?
**Edit, oops, i see you already tried Odin. Hope someone can assist you..
Edit. As far I have learned so far. Every root method etc will decrypt ur sd card. If you format it will be encrypted again. Because the files get reinstalled with the config. Wich can hurt allot. As I stated before try to get the first backup from efs and ur bootloader twrp makes. After make a new one and make sure they are on ur pc. I think u will need 2 freshly flash stock rom with repartition. Since it will relocate the sd card and reformats it. But im not truely sure. If I were you wait for some senior members to confirm.
I had this issue before kinda same as yours. No os etc. But I always make backups of efs and bootloader and everything else every change I make.
So I bassicly made a fresh flash. Downloaded latest stock firmware from sammobile and converted the 4 files into 1 huge file wich I putted in ap. And putted the normal once in bl and csc etc. Then Putted in hidden image for the repartion and checked reset efs.
The flash took 15 minuts and the bootup about 30 with 3 reboots.
But pls dont try this yourself. I Program whit icepicket multi flashdevice as daily job and write the coding for eepromx chips. Thats the heart of most prints with hidden coding. And controls all hardware. This method worked out for me. But like I said I rather should wait for someone to confirm this.
removed
chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
Well I didnt lose efs yet using odin with re partition and efs reset. And if you already need to pay. Yes efs is an unique file.
removed
chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
chaopac said:
After some more reading, I think my last resort is to perform a "Full Firmware" flash, with options such as NAND erase, PIT file flash and EFS clear.
However, I am not entirely sure what they will do, and if in my device situation they will help fix the issue or make it worse. Information I've found so far on the net are quite vague.
So I guess I will wait until someone who is familiar with this so called "Flash Full Firmware" process to point me in the right direction to move forward. Until then, I will keep searching.
Thank you for your input. I appreciate your time.
Click to expand...
Click to collapse
Edit I have typed this and readed it back. There are allot of grammar corrections to make. But I had a shift of 9 hours and due a traffic jam I also had to drive 4 hours. Also im dutch and my keyboard trys to correct stuf to Dutch. Hope you will understand what I wrote. Im just to tired now to correct it haha.
Repartion is ussualy used when you change from a multi csc to a single csc with the open pit file from the csc file. It hold how your mobile provider app instaltion etc etc.
Efs clear will bassicly wipe the cache of that part. It hold the previous versions of your mobile provider allowed things and system apl version. Also the history of previous settings. When you set up the mobile first time with a sim and add your google account there is an option restore previous backup and seetings of accounts amd system app versions of last reset. Wich always be turned on after factory reset. If you tick clear efs in odin it will wipe that. The unique codes in the efs part are not wipeable easily. Only when you really start messing arround with fully system root acces.
When a print is flashed the mainbord it is done with a flash device. In this case the one I have is used by big corporations. Every print has an hardcode. With unique codes.
To acces these or flash a new one you need sich device. Then u also need the right method. From 5 pins to uart usb in this case. Them u need the right port nuber and flash time etc etc etc. Also corporations use those special devices since we can connect different cables mini usb rs245 and so on. Wich give use another layer of protection for people who try to steal our hard code.
To ecplain lets say I made a print and the flash will be on a mini usb. Lets say the cable has 3 wires to the mini usb amd the mino usb has 5 connectors we can connect to. This gives us the oppertunity to lets say we put wire 1 and 2 on connector 3 and wire 3 on connector 1. We have allot of options. Since we can also program eich wire will transfer the data. We even can put resistors on them as a safery check.
That is one of the reasons why its damn hard to read the coding and unlock a new bootloader or efs file to root stuf. It takes allot of time to get it done. And im not sure if great programmers like chainfire do it this way. But it takes them allot of effort and time to deliver us the great rooted software.
The issue is resolved. The solution is updated at the post #1.
Thank you for everyone who read the thread and participated in.