Related
Hi
I'm using CM9 on SGS i9000 and after so many messages of low space, I found that /dev/block/mtdblock6 was almost full with 100 mb used even after deleting every single folder but lost+found:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 189444 32 189412 0% /dev
/dev/block/mtdblock2 256000 240312 15688 94% /system
/dev/block/mtdblock3 17920 2336 15584 13% /cache
/dev/block/mmcblk0p2 1935192 276228 1658964 14% /data
/dev/block/mtdblock6 176128 111872 64256 64% /datadata
/dev/block/mmcblk0p1 5913120 3036544 2876576 51% /sdcard
~ # cd /datadata
/datadata # ls
lost+found
/datadata # rm -R lost\+found/
rm: can't remove 'lost+found': Directory not empty
I've tried formatting from CWM but that folder is still there and it complains of being non empty but (a ls on it shows nothing)
¿How could I recover that phantom used space so my apps doesn't complain?
Thanks in advance
Found it!
Flashing a new image (stock one), then reflashing CM fixed it, it appears that the problem was just with the FS and not with the flash memory.
It's a pitty than CWM format option did not fixed it :/
But at least it works
Hi,
Glad you fix your issue, can I barrow your thread? The issue is not exactly the same (at least I think) but the title fit so well with the problem and it is in the good category/section.
I have 60mb of unused/unusable/missing space in /datadata.
If I compare the result of command DU vs DF I got a difference of 59M for what is supposed to be the space “used”.
Command: du -sch /datadata
Result: 104.1M /datadata
Command: df /datadata
Result:
Filesystem Size Used Free Blksize
/datadata 172M 163M 8M 4096
The application DiskUsage give me a mysterious “System Data” of 62Mb.
Lost+Found folder is empty but I cannot delete it. Thought I don’t think it’s the issue... Lost+Found folder was showing up with DiskUsage when I got corruption on my emmc. So the situation is different.
I manage to put e2fsck in bin, but my adb don’t connect in download mode… and when the system is up it is impossible to umount “/dev/block/mtdblock6 /datadata yaffs2 rw,relatime 0 0” and neither it is to scan it with e2fsck.
I would like to find a rapid fix for that in case it would re-occur in the future. If we don’t find one I will probably Reset Data/Factory and wipe everything before flashing the rom again and restore with Titanium…
Searching for this issue always lead to either LOST.DIR LOST+FOUND or format, but everybody seems to have that issue on sdcard which is easier to move data,format then move data back…
Is there somebody else have this issue on /datadata? Do you think it may be fix by e2fsck? If yes then how can I run it? Do you have any idea on how to fix that?
Thanks you,
Model : GT-i9000M
Rom : CM9 nighties
Kernel : CM9 stock or Semaphore
Others :
- Restoring with Titanium backup if necessary (did not since a while)
- Using Wendigogo Datafix http://forum.xda-developers.com/showthread.php?p=26375859
EDIT: Welcome to this forum. At least now your first 2 post have an reply
That goes way over my skill.
Can somebody adapt this to our i9000?
http://forum.xda-developers.com/showthread.php?p=17752957
The e2fsck I have is coming from that zip. I can try to adapt in the script all /dev reference to our phone. But even with that, I think there a part that need to be compiled no? I don't know anything about these binary that are used for CW....
Edit : let me guess, YAFFS file system cannot be fix by e2fsck?! Anyway, if that could not help for my specific issue maybe it can be useful for other situations...
Envoyé depuis mon GT-I9000 avec Tapatalk
Silentbob999 said:
That goes way over my skill.
Can somebody adapt this to our i9000?
http://forum.xda-developers.com/showthread.php?p=17752957
The e2fsck I have is coming from that zip. I can try to adapt in the script all /dev reference to our phone. But even with that, I think there a part that need to be compiled no? I don't know anything about these binary that are used for CW....
Edit : let me guess, YAFFS file system cannot be fix by e2fsck?! Anyway, if that could not help for my specific issue maybe it can be useful for other situations...
Envoyé depuis mon GT-I9000 avec Tapatalk
Click to expand...
Click to collapse
I was not able to find on Linux any repairing tool, that's why I finally used a full image restore and repartition to have the FS recreated and usable again... CWM, CM9 and TitaniumBackup did the rest...
is that ok for you if I try to get support by using your thread or you prefer that I create a new one for my problem ?
For recap: I try to understand why /datadata is always full while CM9 is suppose to clean cache in there automatically. I think this is coming from that mysterious "System Data" that now taking 64.1Mo on my /datadata partition. That seems to correspond with the difference between result given by DU and DF command.
Code:
DF (153220) - DU (91836) = 61384 (59.9Mo)
Code:
***************************
* DU result *
***************************
Result of Data usage
Total : 172.5M (176656)
Data/data : 80.5M (82420)
Datadata : 89.7M (91836)
Libs Total : 41.2M (42144)
Libs in /Data/data : 38.2M (39080)
Libs in /Datadata : 0 (0)
Cache Total : 69.6M (71247)
Cache in /Data/data : 35.9M (36784)
Cache in /Datadata : 33.7M (34467)
Databases Total : 30.9M (31657)
Databases in /Data/data : 5.4M (5544)
Databases in /Datadata : 25.5M (26137)
Free space in /datadata : 83164
***************************
* DF result *
***************************
Filesystem Size Used Free Blksize
/datadata 172M 149M 22M 4096
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock6 176128 153220 22908 87% /datadata
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock6 172.0M 149.6M 22.4M 87% /datadata
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/block/mtdblock6 172 150 22 87% /datadata
***************************
*** TYPES ***
***************************
1206 - app_appcache
3969 - app_databases
23432 - files
31681 - databases
39080 - lib
71251 - cache
***************************
*** Cache ***
*** TOP 20 ***
***************************
44 /datadata/com.smartandroidapps.audiowidget/cache
61 /datadata/com.google.android.youtube/cache
72 /data/data/ca.lapresse.android.lapressemobile/cache
72 /data/data/com.aurorasoftworks.quadrant.ui.standard/cache
96 /datadata/com.mikersmicros.fm_li/cache
112 /data/data/com.mobilityflow.torrent/cache
152 /data/data/com.pelmorex.WeatherEyeAndroid/cache
1617 /datadata/com.eolwral.osmonitor/cache
3106 /datadata/com.estrongs.android.pop/cache
4692 /data/data/com.artelplus.howtotie/cache
4692 /data/data/com.et.easy.download/cache
4704 /data/data/com.koushikdutta.rommanager/cache
4724 /data/data/os.tools.scriptmanager/cache
5139 /datadata/com.android.vending/cache
5713 /datadata/ccc71.bmw/cache
5713 /datadata/com.aor.droidedit/cache
5724 /data/data/com.unit.convert/cache
5760 /data/data/ds.cpuoverlay/cache
5972 /data/data/com.android.email/cache
12532 /datadata/com.quoord.tapatalkpro.activity/cache
***************************
*** Database ***
*** TOP 10 ***
***************************
615 /datadata/com.android.providers.telephony/databases
634 /datadata/com.google.android.apps.plus/databases
823 /datadata/com.google.android.apps.docs/databases
1168 /datadata/com.android.providers.contacts/databases
1379 /datadata/dk.tacit.android.foldersync.full/databases
1532 /datadata/com.dropbox.android/databases
3354 /datadata/com.kiragames.unblockmefree/databases
4315 /datadata/com.android.email/databases
5520 /data/data/ca.lapresse.android.lapressemobile/databases
6404 /datadata/com.android.providers.media/databases
***************************
***************************
Silentbob999 said:
is that ok for you if I try to get support by using your thread or you prefer that I create a new one for my problem ?
For recap: I try to understand why /datadata is always full while CM9 is suppose to clean cache in there automatically. I think this is coming from that mysterious "System Data" that now taking 64.1Mo on my /datadata partition. That seems to correspond with the difference between result given by DU and DF command.
Code:
DF (153220) - DU (91836) = 61384 (59.9Mo)
[/CODE]
Click to expand...
Click to collapse
From my understanding /datadata should not be always full, and even if cache is supposed to be cleaned automatically, system will complain if under some MB theresold.
If DU + DF != Total then you may have the same problem I had (reported at dmesg as corruption or failing NAND) which was marking blocks as bad /unusable thus consuming the available disk space.
lost+found
thatś the problem
lost+found directory
i try to see inside with ls -l command
there was plenty hidden files
it was for me quite difficult to dellete all
at last i managed to clean nearly everything
now i have just lost+found directory with aparently no files
but imposible to delete directory
my whole sd card is 3 gb and was fully occupied by this lost+found
if possible the best solution should be to format this sd card....but i don t know how...
thanks
I'm trying to increase the size of internal storage (/data) on my TL at the expense of emulated external storage (/storage/sdcard0). I found that FTF files contain partition-image.sin, which describes all 15 partitions on the phone. Using the partition modification guide for 2011 Xperias, I made the necessary adjustments in the partition image and userdata .sins, compiled the FTF, and flashed it. However, the result was only a decrease in size of external storage while internal storage was still measured at 1.97GB despite fdisk -l showing the new partition table. Is there another place that controls partition sizes? Or is it possible only with unlocked bootloaders? Is there anything similar to Samsung's PIT configs?
I don't want to use Link2SD because the phone has sufficient onboard memory, and turning off emulated external storage isn't an option either because I want to use the physical SD card only for photos, music, and nandroid backups.
Hello,
some months ago I make a modified partition table with some command line programs
Finally I've got a unique internal memory of 7,36 GB at least. IT'S TRUE! IT'S POSSIBLE! (with locked bootloader, stock kernel, rooted phone e CWM installed).
Unfortunately, I make this in a lot of time and I don't rember the right order of the command.
There are the steps that I make certainly:
1 Restore the swap between internal and external memory (if you do it). ITA: ripristinare lo swap tra la sdcard falsa e la sdcard (se è stato fatto...)
2 Rooting. ITA: rootare il telefono
3 Installing CWM. ITA:installare cwm
4 Mount /system/ in RW. ITA:montare /system in scrittura (ad esempio con es file explorer (abilita root explorer, clicca su root explorer e poi ci sono le opzioni di montaggio di /system))
5 Copy the partition commands (parted, mk2fs, resize2fs and similar (I can't post the link, search it)) in /system/bin/. ITA: trasferire in /system/bin (o /sbin ??) comandi partizionamento
6 Mount /system/ in RO. ITA: montare /system in sola lettura
7 Reboot in CWM. ITA: riavviare il telefono in recovery (spegni, accendi tenendo premuto vol. giu)
8 With ADB do this. ITA: avere in una cartella i comandi adb e aprire il prompt dei comandi in quella cartella e dare i seguenti comandi
9 Erase the false SDcard partition. ITA: cancellare partizione sdcard falsa
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
Now we need to extend the partition 14 from these blocks: 1621 > 7818
and to extend the related filesystem.
Someone know how to extend partition and filesystem from command line?
Note:
Unforunately the command 'parted' doesn't support ext4 filesystem. So we can't do that with this command.
The command resize2fs seems doesn't work, infact when I execute that command it says always 'command not found'.
If somethings go wrong, you need to restore your phone with Sony Update Service. It's very very very simple.
you look into the repartion method we used on the xoom,
it finds when the partitions start and end and then patches it to somewhere else to make the partitions bigger:
the patch is here: https://github.com/Schischu/xoom-ElementalX/commit/859d63b5cd9bd12ed778192234b0a1f5242df94b
the thread full of info is here: http://forum.xda-developers.com/showthread.php?t=2506997
teidus said:
Hello,
some months ago I make a modified partition table with some command line programs like these
Finally I've got a unique internal memory of 7,36 GB at least. IT'S TRUE! IT'S POSSIBLE! (with locked bootloader and stock kernel).
Unfortunately, I make this in a lot of time and I don't rember the right order of the command.
There are the steps that I make certainly:
1 Restore the swap between internal and external memory (if you do it). ITA: ripristinare lo swap tra la sdcard falsa e la sdcard (se è stato fatto...)
2 Rooting. ITA: rootare il telefono
3 Installing CWM. ITA:installare cwm
4 Mount /system in RW. ITA:montare /system in scrittura (ad esempio con es file explorer (abilita root explorer, clicca su root explorer e poi ci sono le opzioni di montaggio di /system))
5 Copy the partition commands (parted, mk2fs, resize2fs and similar (I can't post the link, search it)) in /system/bin/. ITA: trasferire in /system/bin (o /sbin ??) comandi partizionamento
6 Mouynt /system in RO. ITA: montare /system in sola lettura
7 Reboot in CWM. ITA: riavviare il telefono in recovery (spegni, accendi tenendo premuto vol. giu)
8 With ADB do this. ITA: avere in una cartella i comandi adb e aprire il prompt dei comandi in quella cartella e dare i seguenti comandi
9 Erase the false SDcard partition. ITA: cancellare partizione sdcard falsa
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
Now we need to extend the partition 14 from these blocks: 1621 > 7818
and to extend the related filesystem.
Someone know how to extend partition and filesystem from command line?
Note:
Unforunately the command 'parted' doesn't support ext4 filesystem. So we can't do that with this command.
The command resize2fs seems doesn't work, infact when I execute that command it says always 'command not found'.
Click to expand...
Click to collapse
So I've searched all over the place before and I can't find parted and other disk utilities for Android. Can you share the link?
It would be awesome if your method works.
matt4321 said:
you look into the repartion method we used on the xoom,
it finds when the partitions start and end and then patches it to somewhere else to make the partitions bigger:
the patch is here: https://github.com/Schischu/xoom-ElementalX/commit/859d63b5cd9bd12ed778192234b0a1f5242df94b
the thread full of info is here: http://forum.xda-developers.com/showthread.php?t=2506997
Click to expand...
Click to collapse
I never see these threads.
It's an hardest work to apply this solution to Xperia... Do you think it's possible?
teidus said:
I never see these threads.
It's an hardest work to apply this solution to Xperia... Do you think it's possible?
Click to expand...
Click to collapse
I think it can be ported. It's in the kernel and not specific to any board/manufacturer
Sent from my LT30p using Tapatalk
Finally I do it! This is the result: (image in some time)
Here is the solution to unifing the two internal memory of the sony Xperia V and (?) related phones. Tested on Xperia V (LT25i) running Android 4.1.2
You need:
1 Rooted phone (link in some time)
2 CWM installed on phone (link in some time)
3 ADB installed on pc
4 Some partitioning commands files (link in some time)
5 4.1Swap.zip
Here is the solution:
1 Copy the partition commands in /external_sd/
2 Reboot in CWM (turn off, wait one minute, turn on while pressing a lot of time volume down button)
3 With ADB do this:
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
rm 14
mkpartfs logical ext2 1621 7818
name 14 UserData
quit
chmod 777 /external_sd/tune2fs
chmod 777 /external_sd/e2fsck
cd external_sd
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
The first boot will require some minutes. Wait! (Now you have an internal memory of 5,68 GB)
Apply this zip through CWM
4.1Swap.zip (link in some time) (This will swap the internal memory with the external memory.) (Thanks to tangjun269)
In CWM wipe cache and Dalvik Cache.
Done!
If somethings goes wrong, simply download and install Sony Update Service and make a restore.
teidus said:
Finally I do it! This is the result: (image in some time)
Here is the solution to unifing the two internal memory of the sony Xperia V and (?) related phones. Tested on Xperia V (LT25i) running Android 4.1.2
You need:
1 Rooted phone (link in some time)
2 CWM installed on phone (link in some time)
3 ADB installed on pc
4 Some partitioning commands files (link in some time)
5 4.1Swap.zip
Here is the solution:
1 Copy the partition commands in /external_sd/
2 Reboot in CWM (turn off, wait one minute, turn on while pressing a lot of time volume down button)
3 With ADB do this:
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
rm 14
mkpartfs logical ext2 1621 7818
name 14 UserData
quit
chmod 777 /external_sd/tune2fs
chmod 777 /external_sd/e2fsck
cd external_sd
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
The first boot will require some minutes. Wait! (Now you have an internal memory of 5,68 GB)
Apply this zip through CWM
4.1Swap.zip (link in some time) (This will swap the internal memory with the external memory.) (Thanks to tangjun269)
In CWM wipe cache and Dalvik Cache.
Done!
If somethings goes wrong, simply download and install Sony Update Service and make a restore.
Click to expand...
Click to collapse
Awesome! I found some issues with the current versions of recovery, which require a couple of additional steps (including using 2 different recoveries), but overall this works. I'll put this into a more comprehensive guide applicable to all models regardless of their storage capacity.
I would be glad to get rid of this nons-sense internal SD, or make it a lot smaller. All my apps are system apps, I don'r want to bother with maintaining two (or three) different places. I am reading here, but this certainly is far beyond me, resp. I am scared.
peter-k said:
I would be glad to get rid of this nons-sense internal SD, or make it a lot smaller. All my apps are system apps, I don'r want to bother with maintaining two (or three) different places. I am reading here, but this certainly is far beyond me, resp. I am scared.
Click to expand...
Click to collapse
I've created a thorough guide on how to resize the partitions. I did not test it with removal of the emulated SD card altogether but if you aren't afraid to experiment, please do try and let me know if it works.
Hey bsines, I think is usefull to include in the tutorial the swap of the internal memory with the external sd.
It's only a simple zip.
What do you think?
Search 4.1Swap.zip in the forum.
lost acces to internal sd
ok i have an issue, have a zte nx406e that is a version of zte nubia z5s mini, and its only for my country and this phone hasnt an offical dev. i made a mistake triying to format external sd to expand internal whit link2sd, i errase the sdcard0 wich is the internal. for (pics,vids etc) an i cant remount it. idk how to do this plz i need help.
PD sorry for my bad english. it is self learned.
Hi everyone, I have a weird problem. Suddenly my phone turn of and when I turn on every app I have (included system apps) starts to FC and can't use any app.
I have TWRP but when I try to perform a factory reset the recovery dies and the only way to restart is perform a hard reset. Can't install any rom, any backup and when I do a wipe cache or dalvik or system has no effect on the system. Can't install anything via ADB or fastboot. Can't install a new recovery. Can't install nothing, is like the /data partition is read only.
Sorry for my poor english, hope understand me. Cheers.
Pongo el problema en castellano, tal vez alguien entienda mejor.
El telefono se me apago de repende, cuando lo volvi a encender todas las aplicaciones empezaron a tirar FC y no lo pude usar mas. No puedo hacer un factory reset desde recovery porque se reinicia y queda trabado en el recovery, haciendo wipe system, cache y dalvik no hace ningun efecto, no puedo instalar ninguna rom ni actualizacion ni backup ni nada. Intente volverlo de fabrica con los scripts que hay en la pagina y ninguno hace ningun efecto en absoluto, tampoco puedo instalar un recovery distinto, porque a pesar de que me dice que esta todo bien cuando reinicio sigue con el recovery que tenia. Intente montar /data desde recovery y me dice que la memoria es solo lectura.
Alguien tiene idea de lo que pueda ser?
Desde ya muchas gracias. Saludos.
Mmm I'll say dead nand but try e2fsck from adb.
fburgos said:
Mmm I'll say dead nand but try e2fsck from adb.
Click to expand...
Click to collapse
What is dead nand? Can you help me a little bit with e2fsck? I have read a couple of thing about it but I dont know exactly what to do-
Thanks.
Im not really shure how it goes, on this device I don´t own the device yet.... remember you could end in a worst brick.
Basically you setup correct adb and drivers on your computer, connect the phone, start adb and enter some commands.
adb devices <---- to check if device is recognize by the pc
adb shell <---- start command line for the phone
cat proc/partitions <-----this shows all the partitions in a format mmcblk0p##
umount /system
umount /data
e2fsck -fv dev/block/mmcblk0p## <--- I personally did this for all ## i had in my phone this ## is the number of the partition, data and system are commonly the biggest partitions
fburgos said:
Im not really shure how it goes, on this device I don´t own the device yet.... remember you could end in a worst brick.
Basically you setup correct adb and drivers on your computer, connect the phone, start adb and enter some commands.
adb devices <---- to check if device is recognize by the pc
adb shell <---- start command line for the phone
cat proc/partitions <-----this shows all the partitions in a format mmcblk0p##
umount /system
umount /data
e2fsck -fv dev/block/mmcblk0p## <--- I personally did this for all ## i had in my phone this ## is the number of the partition, data and system are commonly the biggest partitions
Click to expand...
Click to collapse
Thanks for your time man. I have use these commands and nothing, errors everywhere and nothing happens, Just 2 blocks are formatted and the phone stills in the same conditions.
Thanks.
That's bad news, I think its a bad nand, or wrong permissions as you said,
Can you upload the output for
cat proc/mounts
fburgos said:
That's bad news, I think its a bad nand, or wrong permissions as you said,
Can you upload the output for
cat proc/mounts
Click to expand...
Click to collapse
Hi, I have the same issues with my phone.... here the output. Hope someone can help!
~ # ←[6ncat proc/mounts
cat proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=428000k,nr_inodes=107000,mode=
755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=428000k,nr_inodes=107000 0 0
/dev/block/mmcblk0p38 /data f2fs ro,seclabel,relatime,background_gc=off,user_xat
tr,inline_xattr,acl,errors=continue,active_logs=6 0 0
/dev/block/mmcblk0p38 /sdcard f2fs ro,seclabel,relatime,background_gc=off,user_x
attr,inline_xattr,acl,errors=continue,active_logs=6 0 0
/dev/block/mmcblk0p35 /cache ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk1p1 /sdcard1 vfat rw,relatime,fmask=0000,dmask=0000,allow_utime
=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Can someone help me with full image backup of partitions eMMC?
I can try unbrick my rp2 with full backup mmcblk0 on sd card due my phone don't enter in fastboot anymore, only i see Qualcomm HS-USB QDLoader 9008 when connecting usb
I also tried buying unbrick files from this site
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
but they are scammers!! they only sent me an empty folder on google drive
------Update-------
(Razer Phone 2 don't have mmcblk0)
Now i have other Razer Phone 2, i have full backup now of partitions sda, sdb, sdc, sde, sdf...
but i have new problem, how i merge theses partitions "cutted" to my flashdrive?
theses partitions have same header looking in hex viewer comparing with gpt_both files
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also i used EDL Generator to create xml files if someone have prog_firehore
looking systeminfo_a or _b in txt, you see name of firehose used i think
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
oh jeez
does the phone boot at all? like can you even get it into fastboot? or is it just stuck on the splash image? did you unlock the boot loader?
Jordan5900 said:
does the phone boot at all? like can you even get it into fastboot? or is it just stuck on the splash image? did you unlock the boot loader?
Click to expand...
Click to collapse
bootloader is unlocked but don't boot more, only show Qualcomm HS-USB QDLoader 9008 when connect usb on PC
FellpeSoares said:
bootloader is unlocked but don't boot more, only show Qualcomm HS-USB QDLoader 9008 when connect usb on PC
Click to expand...
Click to collapse
Okay yeah I've been here before,
Follow this post
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/amp/
Before you try doing everything try just getting the drivers and using CMD to boot into bootloader or try system, once it's in bootloader, if all your files are gone, get ur factory ROM and reflash EVERYTHING MANUALLY. Like to into the flash all.bat and do every flash command it shows in that order - I had the trouble that the phone doesn't keep android-info.txt on it so reflashing everything manually will bypass using the flash all.bat and it failing.
Jordan5900 said:
Okay yeah I've been here before,
Follow this post
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/amp/
Before you try doing everything try just getting the drivers and using CMD to boot into bootloader or try system, once it's in bootloader, if all your files are gone, get ur factory ROM and reflash EVERYTHING MANUALLY. Like to into the flash all.bat and do every flash command it shows in that order - I had the trouble that the phone doesn't keep android-info.txt on it so reflashing everything manually will bypass using the flash all.bat and it failing.
Click to expand...
Click to collapse
thanks for helping, but this don't work because razer phone 2 don't use TOT files, these files are for LG
FellpeSoares said:
¿Alguien puede ayudarme con la copia de seguridad de imagen completa de las particiones eMMC?
Puedo intentar desbloquear mi rp2 con copia de seguridad completa mmcblk0 en la tarjeta sd debido a que mi teléfono ya no ingresa en fastboot, solo veo Qualcomm HS-USB QDLoader 9008 al conectar el usb
También intenté comprar archivos sin ladrillos de este sitio.
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
pero son estafadores !! solo me enviaron una carpeta vacía en google drive
------Actualizar-------
(Razer Phone 2 no tiene mmcblk0)
Ahora tengo otro Razer Phone 2, ahora tengo una copia de seguridad completa de las particiones sda, sdb, sdc, sde, sdf ...
pero tengo un nuevo problema, ¿cómo fusiono estas particiones "cortadas" en mi unidad flash?
Estas particiones tienen el mismo encabezado que se ve en el visor hexadecimal en comparación con los archivos gpt_both
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
También utilicé EDL Generator para crear archivos xml si alguien tiene prog_firehore
mirando systeminfo_a o _b en txt, ves el nombre de la manguera de incendios utilizada, creo
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
Click to expand...
Click to collapse
¿Podría resolverse el problema? Tengo un error algo similar
FellpeSoares said:
Can someone help me with full image backup of partitions eMMC?
I can try unbrick my rp2 with full backup mmcblk0 on sd card due my phone don't enter in fastboot anymore, only i see Qualcomm HS-USB QDLoader 9008 when connecting usb
I also tried buying unbrick files from this site
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
but they are scammers!! they only sent me an empty folder on google drive
------Update-------
(Razer Phone 2 don't have mmcblk0)
Now i have other Razer Phone 2, i have full backup now of partitions sda, sdb, sdc, sde, sdf...
but i have new problem, how i merge theses partitions "cutted" to my flashdrive?
theses partitions have same header looking in hex viewer comparing with gpt_both files
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
Also i used EDL Generator to create xml files if someone have prog_firehore
looking systeminfo_a or _b in txt, you see name of firehose used i think
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
Click to expand...
Click to collapse
so the soc for rp2 is sdm 845. i saw the firehose img in text that you saw but it just makes no sense for 8998 to be in system img when 8998 is the wrong chipset...RAZER enjoys playing games or something...ive been talking with and edl firehose exploiter and may be making progress
ATACELITE said:
so the soc for rp2 is sdm 845. i saw the firehose img in text that you saw but it just makes no sense for 8998 to be in system img when 8998 is the wrong chipset...RAZER enjoys playing games or something...ive been talking with and edl firehose exploiter and may be making progress
Click to expand...
Click to collapse
Any update on the progress?
After the official end of Razer support, I think it's more difficult to get these files now, dev's must be the only one who can have at hand in this moment.
Details of compatible Firehose that we need
HWID: 0008B0E101400003
MSM_ID: 0008B0E1
OEM_ID: 0140
MODEL_ID: 0003
CPU: SDM845
PK_HASH: 074DDB00C617690187503D8C795F497005C760965F8F48A7A8955271E4BF826B
Code:
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
Issuer: C = US, ST = CA, L = San Francisco, OU = Razer MBU, O = Razer, CN = Razer Attestation CA
Validity
Not Before: Mar 5 02:12:06 2019 GMT
Not After : Feb 28 02:12:06 2039 GMT
Subject: C = US, CN = Razer Subsystem Signing User, L = San Francisco, O = Razer, ST = California, OU = 01 0000000000000000 SW_ID, OU = 02 6000000001400003 HW_ID, OU = 04 0140 OEM_ID, OU = 05 00000228 SW_SIZE, OU = 06 0003 MODEL_ID, OU = 07 0001 SHA256, OU = 03 0000000000000000 DEBUG, OU = 13 0001 IN_USE_SOC_HW_VERSION
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:a6:82:5a:af:ba:3e:b3:8b:e0:25:13:e9:02:cd:
1b:a4:d9:e0:78:a6:89:09:2d:8e:84:4c:b7:52:18:
a9:fa:a1:c9:6f:6e:92:8c:30:88:a0:89:99:45:dd:
b3:1c:23:45:17:82:db:c7:1e:c7:45:f4:1f:12:ce:
bd:5e:50:b2:75:18:cb:07:c5:23:9d:14:ba:04:95:
b2:b9:3c:1f:32:60:3f:0f:f5:7c:d6:de:43:69:10:
9c:9f:55:9c:b4:35:ea:e9:b8:d7:5e:e1:f8:1c:05:
f2:97:d2:06:1b:b0:14:37:9d:de:a8:b3:14:0c:f8:
42:cc:c9:ec:42:c2:ec:c8:41:fb:12:67:2c:8b:5c:
cd:ca:a9:ea:db:30:89:4c:56:f7:b4:73:0c:46:7a:
30:0a:e5:9d:33:b6:3d:04:c4:41:87:9c:41:58:2d:
f8:e6:66:a6:52:a5:01:35:9a:92:dc:51:a1:28:e8:
e7:a5:11:ca:ec:a8:1f:0c:cb:58:bb:f9:61:59:46:
0d:92:05:cb:ce:2d:1e:7b:dc:08:93:f1:61:f5:ad:
72:20:a9:db:86:6d:0b:75:63:6c:04:54:a5:5e:89:
91:13:b9:23:da:ad:55:0e:4f:15:08:0c:19:39:56:
25:c2:94:6e:97:4f:b4:fa:10:b4:32:25:ea:40:6f:
d8:47
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
keyid:CA:43:84:0F:CD:A4:7B:D8:06:12:D2:BF:89:31:6B:93:35:00:DC:F2
X509v3 Basic Constraints:
CA:FALSE, pathlen:0
X509v3 Key Usage:
Digital Signature
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
06:46:11:a4:82:07:1e:d7:d0:67:eb:16:89:08:04:48:82:a8:
91:3d:9d:5e:32:60:f2:ba:11:c7:d1:6b:99:a1:40:ee:41:ad:
e4:e5:95:06:8e:86:59:a5:ad:bd:63:e0:30:9c:d2:f8:75:57:
b3:1d:86:a7:eb:a7:e1:a9:6f:da:70:74:0d:82:ed:7a:ec:1a:
ae:83:d4:0f:25:b6:ba:ae:ac:e0:9a:94:4c:25:6d:38:6e:61:
8d:59:15:73:24:a7:d4:34:2f:41:ae:51:38:d0:46:cd:90:63:
44:9c:d7:c3:64:7b:44:3e:7c:cb:c9:0d:c0:d4:d7:4a:95:fd:
d9:1b:8b:50:a9:38:bf:cf:a7:b2:8f:b6:9e:83:e3:2e:a0:02:
f2:57:60:cd:9e:ab:27:2c:c6:00:f1:dd:c9:2f:9a:bb:fe:4f:
9d:10:66:be:d1:61:d1:77:71:37:a6:de:e1:1f:55:14:0a:16:
2f:54:f3:a5:6b:0e:10:2c:2e:18:28:d0:e7:d2:19:fb:0c:7b:
61:5b:96:7b:48:7e:36:7a:1c:4c:36:07:9d:40:27:7a:ce:05:
9f:23:88:47:69:14:d6:1b:e9:3d:72:1c:91:ed:ab:45:e3:10:
22:a2:8a:67:db:dc:61:02:32:74:58:49:de:0e:ad:87:e9:62:
59:72:13:95
FellpeSoares said:
After the official end of Razer support, I think it's more difficult to get these files now, dev's must be the only one who can have at hand in this moment.
Details of compatible Firehose that we need
HWID: 0008B0E101400003
MSM_ID: 0008B0E1
OEM_ID: 0140
MODEL_ID: 0003
CPU: SDM845
PK_HASH: 074DDB00C617690187503D8C795F497005C760965F8F48A7A8955271E4BF826B
Code:
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
Issuer: C = US, ST = CA, L = San Francisco, OU = Razer MBU, O = Razer, CN = Razer Attestation CA
Validity
Not Before: Mar 5 02:12:06 2019 GMT
Not After : Feb 28 02:12:06 2039 GMT
Subject: C = US, CN = Razer Subsystem Signing User, L = San Francisco, O = Razer, ST = California, OU = 01 0000000000000000 SW_ID, OU = 02 6000000001400003 HW_ID, OU = 04 0140 OEM_ID, OU = 05 00000228 SW_SIZE, OU = 06 0003 MODEL_ID, OU = 07 0001 SHA256, OU = 03 0000000000000000 DEBUG, OU = 13 0001 IN_USE_SOC_HW_VERSION
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:a6:82:5a:af:ba:3e:b3:8b:e0:25:13:e9:02:cd:
1b:a4:d9:e0:78:a6:89:09:2d:8e:84:4c:b7:52:18:
a9:fa:a1:c9:6f:6e:92:8c:30:88:a0:89:99:45:dd:
b3:1c:23:45:17:82:db:c7:1e:c7:45:f4:1f:12:ce:
bd:5e:50:b2:75:18:cb:07:c5:23:9d:14:ba:04:95:
b2:b9:3c:1f:32:60:3f:0f:f5:7c:d6:de:43:69:10:
9c:9f:55:9c:b4:35:ea:e9:b8:d7:5e:e1:f8:1c:05:
f2:97:d2:06:1b:b0:14:37:9d:de:a8:b3:14:0c:f8:
42:cc:c9:ec:42:c2:ec:c8:41:fb:12:67:2c:8b:5c:
cd:ca:a9:ea:db:30:89:4c:56:f7:b4:73:0c:46:7a:
30:0a:e5:9d:33:b6:3d:04:c4:41:87:9c:41:58:2d:
f8:e6:66:a6:52:a5:01:35:9a:92:dc:51:a1:28:e8:
e7:a5:11:ca:ec:a8:1f:0c:cb:58:bb:f9:61:59:46:
0d:92:05:cb:ce:2d:1e:7b:dc:08:93:f1:61:f5:ad:
72:20:a9:db:86:6d:0b:75:63:6c:04:54:a5:5e:89:
91:13:b9:23:da:ad:55:0e:4f:15:08:0c:19:39:56:
25:c2:94:6e:97:4f:b4:fa:10:b4:32:25:ea:40:6f:
d8:47
Exponente: 65537 (0x10001)
Extensiones X509v3:
Identificador de clave de autoridad X509v3:
clave:CA:43:84:0F:CD:A4:7B:D8:06:12:D2:BF:89:31:6B:93:35:00:DC:F2
Restricciones básicas de X509v3:
CA: FALSO, ruta: 0
Uso de la clave X509v3:
Firma digital
Algoritmo de firma: rsassaPss
Algoritmo hash: sha256
Algoritmo de máscara: mgf1 con sha256
Sal Longitud: 0x20
Campo de tráiler: 0xBC (predeterminado)
06:46:11:a4:82:07:1e:d7:d0:67:eb:16:89:08:04:48:82:a8:
91:3d:9d:5e:32:60:f2:ba:11:c7:d1:6b:99:a1:40:ee:41:ad:
e4:e5:95:06:8e:86:59:a5:ad:bd:63:e0:30:9c:d2:f8:75:57:
b3:1d:86:a7:eb:a7:e1:a9:6f:da:70:74:0d:82:ed:7a:ec:1a:
ae:83:d4:0f:25:b6:ba:ae:ac:e0:9a:94:4c:25:6d:38:6e:61:
8d:59:15:73:24:a7:d4:34:2f:41:ae:51:38:d0:46:cd:90:63:
44:9c:d7:c3:64:7b:44:3e:7c:cb:c9:0d:c0:d4:d7:4a:95:fd:
d9:1b:8b:50:a9:38:bf:cf:a7:b2:8f:b6:9e:83:e3:2e:a0:02:
f2:57:60:cd:9e:ab:27:2c:c6:00:f1:dd:c9:2f:9a:bb:fe:4f:
9d:10:66:be:d1:61:d1:77:71:37:a6:de:e1:1f:55:14:0a:16:
2f:54:f3:a5:6b:0e:10:2c:2e:18:28:d0:e7:d2:19:fb:0c:7b:
61:5b:96:7b:48:7e:36:7a:1c:4c:36:07:9d:40:27:7a:ce:05:
9f:23:88:47:69:14:d6:1b:e9:3d:72:1c:91:ed:ab:45:e3:10:
22:a2:8a:67:db:dc:61:02:32:74:58:49:de:0e:ad:87:e9:62:
59:72:13:95[/CÓDIGO]
[/QUOTE]
How to load this code in the razer phone 2?
Click to expand...
Click to collapse
I DONT UNDERSTAND HOW DEEP YOU GUYS GET INTO THESE RZRS. WHENEVER I HAVE A PRBLEM I FLASHALL.BAT. AND IT REFRESHES THE PHONE THEN I RESTART WHATEVER IWAS TRYINA DO. HOWD YOU GET SO DEEP INTO THAT WHOLE OF BEING BRIICKED
itz_jordann said:
I DONT UNDERSTAND HOW DEEP YOU GUYS GET INTO THESE RZRS. WHENEVER I HAVE A PRBLEM I FLASHALL.BAT. AND IT REFRESHES THE PHONE THEN I RESTART WHATEVER IWAS TRYINA DO. HOWD YOU GET SO DEEP INTO THAT WHOLE OF BEING BRIICKED
Click to expand...
Click to collapse
yes I know, but it's all to have control of it
Cremosidad said:
yes I know, but it's all to have control of it
Click to expand...
Click to collapse
wow. man. is it cause of twrp? cause i always go the easy route n use magisk.
Cremosidad said:
yes I know, but it's all to have control of it
Click to expand...
Click to collapse
i feel like magisk is enough control itsself easy to get away bloatware and all the BS. and other simple ****. but it seems like yall are over here trina putta backdoor trojan into the pentagons servers or some **** lmao
I'm having trouble flashing android 10 Roms as system is automatically unmounting b4 flashing and an error as shown below pops up.
please help.....
it all started after flashing the new Pitch Black recovery.
but it works fine when I flash pie ROms.
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc1./by-name/system at /system: Invalid argument
unmount of /system failed; no such volume
Amigo intenta volver a la anterior ROM debe ser algún error en la ROM
∆D!n0 said:
I'm having trouble flashing android 10 Roms as system is automatically unmounting b4 flashing and an error as shown below pops up.
please help.....
it all started after flashing the new Pitch Black recovery.
but it works fine when I flash pie ROms.
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc1./by-name/system at /system: Invalid argument
unmount of /system failed; no such volume
Click to expand...
Click to collapse
Is your problem solved??
If not reply this message