Database Info

Help please! phone won't boot

So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.

which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error

Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.

BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4

Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.

BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time

Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2

Rom Builder

Rom Builder​ Hi guys this is me a small utility for creating flashable zip custom firmware for recovery I think will help many​how to use​unzip the contents of a folder on your computer
connect your phone via usb and enable USB debug
run the program and press enter
Click OK on your phone
We are waiting for the completion
So almost all ready, we go on a memory card and look for the folder "ROM" and see there copy 4 files to your computer
almost finished
Now we take update.zip to move all the files
That's just what we've created custom firmware for recovery
Download RomBuilder​
Automaticaly Version​
thanks Symbuzzer ​
XDA:DevDB Information
[dev tools] Rom Builder, Tool/Utility for the Nokia X2
Contributors
y-bee4pda
Version Information
Status: Beta
Created 2015-08-01
Last Updated 2015-08-01

Thanks, will try on Monday.
I have 2 questions:
-Which partitions are created?
-Can we modify updater-binary vs without resigning?
Thanks again.
Sent from my NokiaX2DS using XDA Free mobile app

yes
symbuzzer said:
Thanks, will try on Monday.
I have 2 questions:
-Which partitions are created?
-Can we modify updater-binary vs without resigning?
Thanks again.
Sent from my NokiaX2DS using XDA Free mobile app
Click to expand...
Click to collapse
-partitions
recovery.img
boot.img
system.img
custom.img
You can easily modify the file update script in Notepad ++ and update binary can take on any of the other newer firmware example of CM

nice ,the recovery build also

@ybee4pda
I enhanced your code a bit and make it fully automatic. How can I send you new codes?
Sent from my NokiaX2DS using XDA Free mobile app

thanks
symbuzzer said:
@ybee4pda
I enhanced your code a bit and make it fully automatic. How can I send you new codes?
Sent from my NokiaX2DS using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, you can submit it here

y-bee4pda said:
Thank you, you can submit it here
Click to expand...
Click to collapse
Thanks
It can:
-back up boot, system and custom partitions as img file to sdcard (recovery partition not supported for now)
-move these 3 img files from sdcard to PC
-make flashable zip (update.zip)
-clean img files from sdcard and PC
Note: When you start build_Rom.bat again, it deletes update zip. So you should backup your update.zip for every process.
All credits to go this topics creator. I only modified a bit to automate process.

I have flash the update.zip with 2 partitrions inside and i get NokiaVariantManager has stopped message when boot up the phone...how can i fix it

kaotd99 said:
I have flash the update.zip with 2 partitrions inside and i get NokiaVariantManager has stopped message when boot up the phone...how can i fix it
Click to expand...
Click to collapse
it wipes 3 partitions. so you probably lost your custom partition. try to reflash it.

@y-bee4pda , thanks for your work. One thing, why the rom zip size is always 600mb+ ?

Nokia variant manager has stopped
symbuzzer said:
it wipes 3 partitions. so you probably lost your custom partition. try to reflash it.
Click to expand...
Click to collapse
Hi.I installed one Rom and I get this problem when I want restore my back up. I try any thing but I can't find any things for this.cm roms work correct ly but I want restored my stock Rom .please help.....:crying:

How to modify build.prop ?

I tried to modify the build.prop lines, I can save it successfully and I can see the build.prop content updated without problem. But after reboot my Mate 9, all my modifications were gone and restored to original. Are all those files under /system on Android N or Huawei require special tricks to modify? Because I also found that I am unable to add new file under /system directory, any new file created will be removed after reboot. Sorry for my dumb questions, I am new to Huawei and Android N... THANKS

Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app

Sammath said:
Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.

raychak said:
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.
Click to expand...
Click to collapse
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.

duraaraa said:
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.
Click to expand...
Click to collapse
so , without changing build.props how can you rebrand to others region FW?

OnimushaPooh said:
so , without changing build.props how can you rebrand to others region FW?
Click to expand...
Click to collapse
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.

duraaraa said:
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.
Click to expand...
Click to collapse
cool thanks, it quite complicate things, not simple as others huawei's phone.

OnimushaPooh said:
cool thanks, it quite complicate things, not simple as others huawei's phone.
Click to expand...
Click to collapse
They changed a lot when they went to Android N, unfortunately.

The real build.prop is under vendor, not system. Just for information.

Restore Onplus Switch Backup

hi!
i did a full Backup with Oneplus Switch on my old official ROM. When i open the folder on my computer it is structured like this:
.Preview
App
Data
OPLauncher
.nomedia
so after i unblocked bootloader, flashed rom and have rooted the phone i downlaoded the Oneplus Switch app from Appstore. When i open it, i can pretty much only scan a QR code with i dont have other possibilities.
Can you please tell me how i can restore my "Switch" backup.

Nobody here who can help me out?

mosc2k said:
Nobody here who can help me out?
Click to expand...
Click to collapse
Hey, You have to copy the op backup to the computer. Root your phone then copy the file op file to your internal storage. Download oneplus switch then open it and click backup/restore in the bottom left. If you've done the other steps correctly then the file should be there ready to restore.

Bxperiaz3 said:
Hey, You have to copy the op backup to the computer. Root your phone then copy the file op file to your internal storage. Download oneplus switch then open it and click backup/restore in the bottom left. If you've done the other steps correctly then the file should be there ready to restore.
Click to expand...
Click to collapse
Hey , well That's the problem he can't use the app since he can only send those days not receive any.

Mist3rShey2nIl said:
Hey , well That's the problem he can't use the app since he can only send those days not receive any.
Click to expand...
Click to collapse
What?

TWRP : SYSTEM partition not in backup list, how do i backup it?!

After unlocking phone & installing TWRP, i want to backup of course, but in the partition list, SYSTEM is not here! Never seen this before. Happens with any version of TWRP for the Realme 5 Pro. I may be missing something..? Let me know ASAP, thanks

Try Erase Partition Recovery and Flash TWRP again.
Command
fastboot erase recovery
fastboot flash recovery file-name-twrp.img
Click to expand...
Click to collapse

faisalxp said:
Try Erase Partition Recovery and Flash TWRP again.
Click to expand...
Click to collapse
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..

Yeah realme rename it to system_root

faisalxp said:
Yeah realme rename it to system_root
Click to expand...
Click to collapse
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:

GoJo ^^ said:
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
Click to expand...
Click to collapse
Have you previously tried to backup a System Image and try to open the backup file system_image.emmc.win with an Archive application like RAR or Zip ?
If so you will see that the System folder is inside the system_root folder so it can be concluded that System Image or system on twrp is the same as system_root or root. You can check attachment file.
I think the problem is with the twrp source or the developer, where the system image backup path leads to System_Root not /system_root/system.
If you only want to backup only the system partition you can use "dd" command on the TWRP terminal.
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..
Click to expand...
Click to collapse
When you tick and mount the system partition on twrp, you will be able to edit all files and folders in system_root. for more details diferent tick and untick system, you check the file attachment.
GoJo ^^ said:
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:
Click to expand...
Click to collapse
I try searching and not its not same for all device realme, one of the example : Realme X & XT using /system-root
I think it depends on the variant or type of device reality. bit the point its same System Image or system on twrp is the same as system_root or root

But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..

GoJo ^^ said:
But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..
Click to expand...
Click to collapse
Try this command on Terminal TWRP
Code:
dd if=/dev/block/by-name/system of=/sdcard/backup-system.img

anyone here facing backing up system image back up failed on fox and twrp ?