Database Develop

[Q] Samsung Galaxy Pop

I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.

deep143in said:
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
Click to expand...
Click to collapse
No replies??

deep143in said:
No replies??
Click to expand...
Click to collapse
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.

kirakun said:
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
Click to expand...
Click to collapse
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.

deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
that will ruin your phone
and for the message just need to wipe data from recovery

deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
My bad i was not aware of this different version. Yes do try what dheeraj has said.
I think that entering recovery should be same for u, just switch off phone, press home button and power button simultaneously and hopefully you will enter recovery.
Navigate using volume button and do a wipe data and cache. Doing so you will lose any app and everything from your phone, so do a backup before.

dheeraj (dhlalit11) said:
that will ruin your phone
and for the message just need to wipe data from recovery
Click to expand...
Click to collapse
I have already tried to wipe from recovery twice but still face the same error. Everything resets to factory defaults except this error which pops up at every restart..

reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care

dheeraj (dhlalit11) said:
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
Click to expand...
Click to collapse
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.

deep143in said:
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
Click to expand...
Click to collapse
In case if you don't mind I would like to know how my phone will get ruined if I use the system.rfs from the original firmware file downloaded by Kies?
Secondly, is there a particular version of ODIN I need to use for this handset? I have tried 1.85, 3.07 and 4.38 versions.
Actually I do not have any other files than the I559DDEH31_HOME.tar.md5 required by ODIN.
I would prefer to go to Samsung service centre only when I am left with no option or if the handset fails to do its regular tasks.
Anyways, thanks for your suggestion.

you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs

dheeraj (dhlalit11) said:
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
Click to expand...
Click to collapse
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?

deep143in said:
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
Click to expand...
Click to collapse
Alternatively I can also do when the phone is in download mode..
What do u think?

well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root

dheeraj (dhlalit11) said:
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
Click to expand...
Click to collapse
I used a linux machine to mount the system.rfs. Extracted phone.apk and installed the app using root explorer.
Finally the problem com.android.phone has been resolved..
Thanks for your help.

deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
the upgrade is available in India but only at the official samsung repair center.
u will have to visit 'em get it upgraded

HOW to back up EFS here in S5830

hi guys i am looking here for thread that will give tutorial on how are we going to back up the said EFS which is the very important file of the phone where IMEI resides, suddenly after searching for so many days still haven't found an answer. I already tried using EFS Pro 1.9.2 and it prompts that the said directory isn't there.. i checked it out on the root of my phone and found that EFS folder isn't there.. now my question is there any apps or tool that will backup our efs so that if incase we accidentally mess with our phone, it will be easy for us to revert back to the time when the phone is functioning well..

The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
mkdir /efs
mount /dev/block/stl5 /efs
Click to expand...
Click to collapse
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)

dev0xteam said:
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
Click to expand...
Click to collapse
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe

mizukage said:
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
Click to expand...
Click to collapse
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2

(Frank) said:
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
do u have any better idea on how are we going to save our efs partition so that we can revert back if we messed with our phone?flashing is risky especially for noobs..

[Q] Failed to mount /sdcard problem

Hello everybody, I'm new to this forum, but I'm reading it for about 8 months now. I have a problem with my Samsung Galaxy S I9000. After flashing with Odin3 v1.83(with 512.pit file, bootloader, PDA, PHONE and CSC), and I got a green "PASS!" on it, and after phone rebooted in Recovery Mode, I've got following error while Copying media files:
E:Failed to mount /sdcard (Invalid Argument)
After that, I tried flashing bunch of different ROM's but I always get the same error. Phone can go into Download mode, Recovery mode with no problem, I can also normally turn on phone and in a beggining I get a lot of "Force Close" pop-ups, but after that my phone works okay, I can go into settings and there I can see that there is no memory, so that means that my phone doesn't even sees my 8GB external micro sd card. When I try to open Camera, I get this error:
Turn off usb storage before using camera.
I currentlly have i9000XWJVZ 2.3.6 ROM on it, with CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS(Clockwork Recovery v3.0.0.5). When I'm in Recovery mode and access my phone via ADB, and try to manually mount sdcard, this is what I get:
~ # mount sdcard
mount sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: I/O error
I've also tried partitioning my external 8GB micro SD card with linux(I found a video on youtube: "Samsung i9000 mmcblk0p2 error recovery"), and then tried to flash ROM on it, but I get the same error.
Can somebody please help me, I'm getting really desperate.
All ideas are welcome, Thanks.

Hi there! I have a similar problem. After updating from Android 2.3.4 Build MCGv7.6 ( I9000XXJVK) I keep on getting CWM. I can also return to download mode and use Odin with success - with as only result a changed CMW version at max. Returning to CWM 3.0.0.5 and stock rom Froyo doesn't result in a applied rom. When i try to mount /emmc and /sd-ext it simply states Error mounting /emmc! Even though I didn't format it! When I look in AROMA explorer in CWM from Semaphore_JB_2.9.12, I can see that both /emmc and /sdcard have ----- as permissions instead of rxwrx or something alike. If permissions are the problem here, Fix Permissions doesn't appear to have an effect on these two folders. Is there another way to restore these permissions?
Thanks guys for your time! :good:

@ficko flash dbdata.rfs as PDA in odin.
Sent from my GT-I9000 using Tapatalk 2

knuckles1978 said:
@ficko flash dbdata.rfs as PDA in odin.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I've tried that, but with no luck.. always the same error.

Check my signature:laugh:

EwOkie said:
Check my signature:laugh:
Click to expand...
Click to collapse
Can't see sigs, I'm using tapatalk.
Sent from my GT-I9000 using Tapatalk 2

EwOkie said:
Check my signature:laugh:
Click to expand...
Click to collapse
Your tutorial was the first thing I tried, it fixed the wipe error, but the main error (E:Failed to mount /sdcard) stayed.

Possible solution is to Format your SD card by using SDFormatter (Windows)
01. Download "SDFormatter" from the link above
02. Install "SDFormatter"
03. Enable "USB Debugging Mode" from Developer Options in settings.
04. Connect your tablet to PC (USB).
05. Then, tap the "USB Strage Mode" to connect to PC.
06. Backup data on INTERNAL_SD card.
07. Run "SDFormatter".
08. Specify the drive letter of INTERNAL_SD in SDFormatter and click "(Option)" button.
09. "FORMAT TYPE" select "FULL OVERWRITE" and set "FORMAT SIZE ADJUSMENT" to "ON" and click "OK"
10. Now click "FORMAT" and wait for the procedure to complete. (Can take approximately 1 hour 40 minutes)
11. After format is completed you can recopy the backup files back onto the INTERNAL_SD
Let me know if that works
If not hopefully someone else can give more info

EwOkie said:
Possible solution is to Format your SD card by using SDFormatter(Windows)
01. Download "SDFormatter" from the link above
02. Install "SDFormatter"
03. Enable "USB Debugging Mode" from Developer Options in settings.
04. Connect your tablet to PC (USB).
05. Then, tap the "USB Strage Mode" to connect to PC.
06. Backup data on INTERNAL_SD card.
07. Run "SDFormatter".
08. Specify the drive letter of INTERNAL_SD in SDFormatter and click "(Option)" button.
09. "FORMAT TYPE" select "FULL OVERWRITE" and set "FORMAT SIZE ADJUSMENT" to "ON" and click "OK"
10. Now click "FORMAT" and wait for the procedure to complete. (Can take approximately 1 hour 40 minutes)
11. After format is completed you can recopy the backup files back onto the INTERNAL_SD
Let me know if that works
If not hopefully someone else can give more info
Click to expand...
Click to collapse
This worked!
It took me about an hour, and after it was finished, I was able to flash ROM without any errors. Thank you so much for this, you saved my phone.

No problem glad it worked out for you:good:

Ficko2210 said:
This worked!
It took me about an hour, and after it was finished, I was able to flash ROM without any errors. Thank you so much for this, you saved my phone.
Click to expand...
Click to collapse
EwOkie said:
No problem glad it worked out for you:good:
Click to expand...
Click to collapse
I got the same problem but my phone alway boot loop. How can I enable USB Debugging mode to format internal SD

zaniku1 said:
I got the same problem but my phone alway boot loop. How can I enable USB Debugging mode to format internal SD
Click to expand...
Click to collapse
Explain your issue please

EwOkie said:
Explain your issue please
Click to expand...
Click to collapse
Thanks for your response
Here is my problem
1. Phone got boot loop (Never pass splash Galaxy S).
2. Try to flash a new rom via ODIN (several version JPA, JW4 , JVU..) then got error as below
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. Please use UI
menu for format and reboot actions
Media files copy failed.
--Wipping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wip failed.
--Applying Multi-csc...
Installing Multi-csc
Can't access to '/system/csc/TMB/system/'.
Successfully applied multi-CSC.
3. After reboot phone still boot loop.

Refer to My signature at bottom HOW TO GUIDE it show steps on what you need to do....
dbdata and PIT File is all there.....just follow instructions and it will set you free!

EwOkie said:
Refer to My signature at bottom HOW TO GUIDE it show steps on what you need to do....
dbdata and PIT File is all there.....just follow instructions and it will set you free!
Click to expand...
Click to collapse
Yep, seconded. dbdata.rfs and PIT file, that's what you need
Sent from my Nexus 7 using Tapatalk HD

After flash dbdata.rfs.tar, it still showed same error message.

zaniku1 said:
After flash dbdata.rfs.tar, it still showed same error message.
Click to expand...
Click to collapse
You could try changing the way you do it. I can't remember whether you should flash dbdata straight after the rom, or if you should let it fail to boot then go back into download mode and flash it.
I do remember though that it was a bit fussy with me like that, so try it both ways.
I also found that flashing your GB ROM twice, one after the other seemed to help sometimes too. (Just noticed that I've written a .txt file in my GB ROM folder on my PC reminding me to do this, so there must have been a reason for it - been a while since I've played with gingerbread so I can't remember why)
So there's a couple of things for you to try.
Sent from my Nexus 7 using Tapatalk HD

Flash the JVU Rom First with PIT and Root...
When Finished Root pull battery ....put battery back in after 30 seconds
Reset ODIN Flash dbdata ..Done
Hope this helps

knuckles1978 said:
You could try changing the way you do it. I can't remember whether you should flash dbdata straight after the rom, or if you should let it fail to boot then go back into download mode and flash it.
I do remember though that it was a bit fussy with me like that, so try it both ways.
I also found that flashing your GB ROM twice, one after the other seemed to help sometimes too. (Just noticed that I've written a .txt file in my GB ROM folder on my PC reminding me to do this, so there must have been a reason for it - been a while since I've played with gingerbread so I can't remember why)
So there's a couple of things for you to try.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
EwOkie said:
Flash the JVU Rom First with PIT and Root...
When Finished Root pull battery ....put battery back in after 30 seconds
Reset ODIN Flash dbdata ..Done
Hope this helps
Click to expand...
Click to collapse
Thanks both of you. I will try.
EwOkie - Should I use CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS for rooting phone or others?

CF Root is in the HOW TO GUIDE or HERE
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS is the correct one to use ...
Everythng you need is in there

Question | how to extract an android backup that i made before updating

hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!

doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works

mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s

doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.

where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh

doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then

mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery

doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.

mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)

doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"

mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day

Bricked Realme X2 Pro (Still have TWRP and Fastboot)

I was trying to flash the Ozip to restore the stock rom using TWRP and after that boom
damaged boot/recovery that msg
i still can go inside twrp and the fastboot mode
what i did notice is that the file folder name changed to system_root and it was just system bevor
is there any fix for it i am using the CN Version

(how-to unbrick your realme device) fastboot needed fix inside.
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.

System wiped/corrupted. Flash the chinese fastboot rom to fix it via fastboot

The real mistake is when your device brick with locked bootloader, all the other cases are solvable.

HTCDevil said:
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
Click to expand...
Click to collapse
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Sent from my RMX1931 using Tapatalk

natedogg20050 said:
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Click to expand...
Click to collapse
That's interesting, i thought it works only if you relock bootloader and then update fw

HTCDevil said:
That's interesting, i thought it works only if you relock bootloader and then update fw
Click to expand...
Click to collapse
Worked perfectly fine even on the old 0.8 firmware
Sent from my RMX1931 using Tapatalk

Can you make a small video please showing this steps? After that terminal thing I didn't understand anything

talalahmed said:
Can you make a small video please showing this steps? After that terminal thing I didn't understand anything
Click to expand...
Click to collapse
I will is your device broken
Sent from my RMX1931 using Tapatalk

What to do when 2 Folders one called system and one called system_root are missing? cant access data in MTP when in TWRP from PC to send the rom file.
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse

hack-os said:
What to do when 2 Folders one called system and one called system_root are missing? cant access data in MTP when in TWRP from PC to send the rom file.
Click to expand...
Click to collapse
Can you enter twrp?
Sent from my RMX1931 using Tapatalk

natedogg20050 said:
I will is your device broken
Click to expand...
Click to collapse
Thanks,I fixed it but not with your steps,it turns out using the Chinese twrp fixed everything for me

Solved.! (For me) CN
I unlocked the bootloader according to the guide [Guide] Guides for x2 Pro[Locking/unlocking bootloader, tweaks and more]. And flashed TWRP successfully. MY MAIN MISTAKE -> DIDN'T MAKE A BACKUP AT THIS POINT.
Then I flash canary debug magisk and open gapps micro (culprit for brick). Then tried to reboot but stuck in yellow Realme screen. Then went back to recovery tried "Facrory reset", "Format data", flash latest CN ozip, even fastboot flash and guide by natedogg20050 with no luck. But Lineage OS unofficial by karthick mostwanted worked with magisk 20.3. :good:
For one final time I tried to get back the stock(since Lineage is still in alpha ATM), after seeing this post by exadeci. Did a "format data" following fastboot flash with chinese images, SUCCESS...!!! :victory: And even updated with ozips from CN site worked.. Finger print works too.
Still in update process to latest .15 . Plan to install magisk.(hopefully canary debug).
Will update this after latest upgrade + magisk install.

don't worry we can
first reboot to recovery
then go to wipe
and wipe sytem,catche,davik catche and data
then download the stock os for realme software
download link(please select your mobile) in realme software website
and flash the recovery
wipe catche and data
and you are back to stock os
enjoy

natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse
after do that my phone boot only in TWRP but i can't see anything.
if I connect the phone to the computer it is empty and if I want to transfer something on it gives me an error.
can you help me ?
SOLVED: i formatted by TWRP.

When I type LS in terminal it gives a long list. There is a "system" and a "system_root".
When I try to open "system" with cd system command, it says, no such file or directory. When I enter "cd system_root" it goes into this Folder. But using "ls" command within this Folder it just shows nothing. Am I doing something wrong?
Any idea?
P.S. Yes I can enter fastboot, and TWRP is working.
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse

Sir Backe said:
When I type LS in terminal it gives a long list. There is a "system" and a "system_root".
When I try to open "system" with cd system command, it says, no such file or directory. When I enter "cd system_root" it goes into this Folder. But using "ls" command within this Folder it just shows nothing. Am I doing something wrong?
Any idea?
P.S. Yes I can enter fastboot, and TWRP is working.
Click to expand...
Click to collapse
did you figure it out ?

natedogg20050 said:
did you figure it out ?
Click to expand...
Click to collapse
Thanks for asking! Yes, I did, but in a different way. It was a long way, running from stuck in yellow realme boot logo to bootloops already on the white realme start logo. Finally I got back a running system, which I don't trust anymore now. My configuration is:
- unlocked bootloader
- TWRP 3.3.1.13
- Magisk canary debug 8ca5a048 (20405)
- Magis Manager 72f6770d (278)
- Andorid 10, C24
I was already at this point 2 days ago. Then Magisk Manager announced an update. Stupid as I am, I just klicked install, and arrived at the same point. Stuck in yellow boot logo, and the whole operation started from beginning. Now I am at the same point again as above, and Magisk Manager announces again an update for itself. But I don't trust it anymore, and I don't know what to do. Just leave it? Or making a nandroid backup first? But will it be sufficiant to backup boot partition, system image and data when the crash comes again? I don't know what to do.

HTCDevil said:
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
Click to expand...
Click to collapse
My Phone cannot boot and cannot go to recovery mode. What should I do? Please help:crying:

allan1998PH said:
My Phone cannot boot and cannot go to recovery mode. What should I do? Please help:crying:
Click to expand...
Click to collapse
If you have unlocked bootloader you could go in fastboot mode and flash twrp, then format data