Hi,
i've got the windows-boot-freeze issue on my wifes phone. Problem is, there are some important files stored in the main flash. as it is possible to gain access to the flash partitions via the bootloader, i think there should be a way or even a tool to access the files stored within. My problem is, i cant find such a tool / way
Maybe some of u guys can help me out
If the phone is CID unlocked you can use mtty to make a dump of the User Area to an SD card with the command: r2sd (something i can't recall now)
its a locked G4 device
Related
Hello guys,
OTA update failed on my hero and I can't do anything right now. I understood from other topics that it's possible to use goldenimage card formatted on one android to use it on another. I don't have GC right now and I'd like to 4 question:
1. Did anybody try to use goldencard on hboot 007?
2. Did anybody try to boot GC (which was created on another phone), on hero?
3. What SD Cards did you use [Stock SanDisk[2GB] or others [Names please]?
4. If second question is true, there is a way to create an image for goldenCard and by thus it'll help to newbies like me to survive first flash. Might anybody who uses linux or winhex may help?
Available SD rippers: WinHEX [Windows] and Linux [HexDump].
Thanks in advance,
MrBora
Download this file: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
Run it. Once you see the ROM update utility GUI, search c:\users (windows 7) or c:\documents and settings (other versions) for a file called rom.zip.
Rename this file HEROIMG.zip and get it onto your SD card.
I think it's HEROIMG.zip. It might be HEROIMAGE.zip. I'm doing this from memory but I'm pretty sure it's HEROIMG.zip.
Power on the Hero holding the VOLUME DOWN button. It should scan the file and then ask you if you want to update. Say yes. This will restore you back to factory and should be able to go from there.
I tried that and I got incorrect CID
If i'm doing it through Windows i'm getting hero 131 customer ID error
thx
Thats because you need to keep trying the goldcard method..Ihad to make the goldcard 3 or 4 times before it worked,used the standard card that same with the Hero (sandisk)
guys it worked with KingSton 2GB image. I succesfully installed stable image, but i can't now to use fastboot for rooting. Write failed. Is there a way to downgrade hboot? no need. with flashapp it works like a charm.
in any case i'll create an image for goldcard
Here are some questions about Android 4.3 and upper.
A pair of questions about unrooting/locking/unlocking/booting.
1) What are the benefits of rooting other than being able to a) set custom cpufrequency policies, b) being able to update your phone (to custom new ROMs like cyanogenmod) when your OEM has decided to stop supporting it, c) full filesystem access, d) tuning sysctl parameters?
I don't like the fact the rooting totally breaks Android's security model.
2) Do I understand correctly that a locked phone is the phone in which you cannot overwrite/replace/customize vmlinuz? or there are even stricter limitations?
3) Do I understand correctly that in order to change e.g. /etc files you don't really need a custom ROM, you can boot into TWRP and replace/edit/remove the needed files?
4) Why does unlock wipe all your data?
5) If the phone is locked, how bootloader/firmware understands that our bootloader is untempered? Does the bootloader have a digital signature? I have this question because let's imagine that I 1) unlock 2) change vmlinuz (allow superuser) 3) lock?
6) How does "oem lock" verifies that system data is genuine? Or it simply wipes everything clean? Does Android has some (RO) partition which always contains a genuine virgin ROM you cannot meddle with?
7) If I do "unlock" on my Nexus device, without changing anything or installing any 3d party bootloader (like TWRP), will I be able to update to new official ROMs via OTA updates?
8) Why every "lock" manual says that I need to upload a genuine official ROM - what if I've changed it and made it "rooted"?
Storage.
Why does Android has so many partitions?
What method is used to break the internal storage into partitions? Is it some kind of partition table (MS-DOS, GPT) or it's hardware based?
Thank you for answers.
Lovely. 4 years and zero answers.
Soooo... Does flashmode or fastboot let you read the files? AFAIK whenever I have flashed a rom and selected format data, it selects a file called "userdata.sin". So I guess that the /data directory is being flashed over, without the ability to read the files.
However, is there a way to *just* flash the data/system/gesture.key(yup, you know it. Forgotten pattern and phone doesn't recognize username and password, tried multiple times)?
Another, more device specific question: The phone with me now is a 4.3 Xperia T. Whenever I connect it with my computer without unlocking the lockscreen, it doesn't allow access to the internal storage. Is that functionality something that can be easily bypassed, or is it a more "hardcoded" basic functionality that blocks even through flashmode/fastboot?
Hello,
I am new to xda, but with what I would say a good understanding of computers in general, and good knowledge of c programming (if that matters)
I am structuring a guide for myself to be as foolproof as possible when attempting flashing my new phone. Please fill in any voids, comment, or answer questions if you can. This should prove useful to other users as well as it's not so model-specific.
1) It appears that the custom recovery of choice in most situations and for the time being is TWRP (correct?).
2) If I can get a backup of EVERY partition on my stock phone (as it came from the factory) using TWRP, could I conceivably restore ALL of them and be in a factory default setting? Excluding stuff like eFuse and similar mechanisms.
3) If the phone supports fastboot, unlocked bootloader and there is a compatible TWRP for it, would it be possible to boot the TWRP recovery through fastboot (without flashing that particular partition to phone), open a shell and take backups of all partitions on the phone? That should give us a file for each partition.
4) If one accomplishes step 3 successfully, in what scenarios would he/she NOT be able to bring the phone back to life after software bricking?
Minor questions:
a) "To have root" on a phone, is basically the same as having a root account on a BOOTED OS partition (like the admin accoun on a booted windows machine, or a root account on a linux machine)? If that's the case, booting a different partition (for example the recovery partition) could also give you root priviledges without affecting the booted partition, correct?
b) Why do some custom ROMs require a certain version of the stock/OEM rom to be installed PRIOR to flashing, since they are going to replace those partitions anyway?
c) How is Xiaomi's Anti Roll Back (ARB) feature implemented, if one restores all partitions to stock from step (3) ? There must be some other places of storing of information on the phone, besides internal memory, correct?
Hi,
has someone experience with making backup of user data partition? (dd, adb pull mmcblk0 or something else.. read-only mode) I need backup whole disk (include empty space). I need to do some deleted data recovery, therefore i can't use normal data backup.
Bootloader is not unlocked, phone is not rooted I need "not destructive" root, because traditional unlocking wipe all user data ...) I have access to settings (USB debugging etc ...).
In past there exists on some phones temp-root (exploit) and with ADB was possible create raw image.
I find out there is also temp-unlock https://www.youtube.com/watch?v=7L1v7KtSg78 (ttool pro utility)
Maybe this is the solution way? (in next step install TWRP and then make backup)