Related
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
Awesome if you do manage to find it please post it
crunchyHTC said:
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
Click to expand...
Click to collapse
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
crunchyHTC said:
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
Click to expand...
Click to collapse
Weird, didnt work for me. Dit you manually flashed the boot.img extracted from the nandroid backup?
Yup. So i took the backup from my sd card and put the backup onto my computer. Then I used clockworkmod recovery to restore the backup, and then used fastboot on the computer to manually flash boot.img through usb.
Hope that helps
Cannot restore with the procedure.
I have been trying to restore stock rom but I'm unable to do it.
I flashed boot.img using command prompt.
Restored it via Clockworkmod recovery but after restoring when i reboot the phone, it again takes me to recovery mode.
What should I do?
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
NicOsol said:
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
Click to expand...
Click to collapse
No..I have not changed anything.
I even tried formatting it in ext3 using Touch recovery and then tried to back up..but it didn't work.
It just keeps on taking me to recovery mode when I reboot.
Why don't you guys get s-off? I'll post a link when I'm on my PC on how to do it. That way, you won't have to flash the boot.img each Time you install a new rom...
Sent from my HTC Incredible S using XDA
tpbklake said:
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Click to expand...
Click to collapse
Hello, I tried with "fastboot flash boot boot.img" took the boot.img from the backup and then I did a restore but it always goes into recovery mode, what else can I do?
I remember reading somewhere (dont remember exactly where) that you can make a nandroid backup before rooting or flashing a custom recovery.
This was done by booting into fastboot mode and running the custom recovery, not flashing, just running it. This would preserve the stock recovery as a custom recovery is not flashed, but would still allow you to make a backup of the stock rom without root and without a custom recovery.
Is this a possible method for making a nandroid backup of the stock rom? Which would allow you to return to stock after rooting and installing custom roms?
fastboot boot recovery CWM.img (or whatever you have called the recovery image) will boot into CWM but not flash it and you can then make a nandroid
EddyOS said:
fastboot boot recovery CWM.img (or whatever you have called the recovery image) will boot into CWM but not flash it and you can then make a nandroid
Click to expand...
Click to collapse
One more question, even if you have a nandroid of the stock rom, wouldnt your device still show up as tampered and unlocked? Is there a way to remove that AFTER returning to the stock rom..?
EddyOS said:
fastboot boot recovery CWM.img (or whatever you have called the recovery image) will boot into CWM but not flash it and you can then make a nandroid
Click to expand...
Click to collapse
Hi, you again
That didn't work for me with CWM, but it didn't work after I flashed it either. It just failed to back anything up.
I didn't try it with TRWP though, in theory you're correct.
twrp 2.6 flashed different rom stocktwrp restore files wont show up in restore.
Can anyone make a rom with my backup that i can install back on threw sideload or install?
i have the boot.img and recovery.img backed up from that restore.
I just came to know that unlocking my xiaomi device will erase its data !!!!
Is this true??????
this thread says this only!!! -> https://twrp.me/xiaomi/xiaomiredmi4x.html
:crying::crying:
KCstark said:
I just came to know that unlocking my xiaomi device will erase its data !!!!
Is this true??????
this thread says this only!!! -> https://twrp.me/xiaomi/xiaomiredmi4x.html
:crying::crying:
Click to expand...
Click to collapse
Unlocking bootloader always erases Data Partition. First check that yours one is unlocked or not, not most devices are come locked. Unlocking will take time as Xiaomi gives you permission to unlock by their own software.
Make a backup, get all your data off then root it. I'm not entirely sure if you can unlock without erasing, but you should never be in a position where you can't afford to reinstall your applications.
This is why it is always best to get twrp on your phone asap so you can back up it.
No, unlocking bootloader doesn't wipes data but you must backup everything just in case anything goes wrong.
it is always recommended to backup everything when flashing ROM, kernel, mod, zip, flashing rom via fastboot method and recovery. in short you should backup everything in all this cases.
shohabmsk said:
Unlocking bootloader always erases Data Partition. First check that yours one is unlocked or not, not most devices are come locked. Unlocking will take time as Xiaomi gives you permission to unlock by their own software.
Click to expand...
Click to collapse
Actually I know most part and have already done getting permission but this was just a quick question as that's my sister's device and she won't accept its data being erased still thanks for your quick answer...
And by the way that device's bootloader is locked I have checked it.
.....:good:
metelhammer said:
No, unlocking bootloader doesn't wipes data but you must backup everything just in case anything goes wrong.
it is always recommended to backup everything when flashing ROM, kernel, mod, zip, flashing rom via fastboot method and recovery. in short you should backup everything in all this cases.
Click to expand...
Click to collapse
Have u done it your self if yes did u lose any of your data. Plz let me know......
KCstark said:
Have u done it your self if yes did u lose any of your data. Plz let me know......
Click to expand...
Click to collapse
Yes i have flashed recovery and roms i always do backup important thing and i take screenshot of installed apps before making any changes and save them to pc or to cloud storage.
there was issue i had was when i flashed TWRP 3.2.1.0 via adb i do not why but it asked me for password i didn't know to password so i had to wipe everything including internal storage and data.
latest twrp is must which is TWRP 3.2.1.0 in order to flash Oreo based ROM.
i was using TWRP 3.0.2-0 before and i had no issue with this recovery i has flashed several nougat roms on this recovery even have upgraded and downgraded from miui9 to miui 8 everything worked perfectly.
i don't know why but i wasn't able to flash any marshmallow based or nougat based roms on TWRP 3.2.1.0 recovery.
yes i did lose data when upgrading from TWRP 3.0.2-0 to TWRP 3.2.1.0 but i had done backup so no issues.
i would highly recommend you to do backup if you are making any changes in your device.
metelhammer said:
Yes i have flashed recovery and roms i always do backup important thing and i take screenshot of installed apps before making any changes and save them to pc or to cloud storage.
there was issue i had was when i flashed TWRP 3.2.1.0 via adb i do not why but it asked me for password i didn't know to password so i had to wipe everything including internal storage and data.
latest twrp is must which is TWRP 3.2.1.0 in order to flash Oreo based ROM.
i was using TWRP 3.0.2-0 before and i had no issue with this recovery i has flashed several nougat roms on this recovery even have upgraded and downgraded from miui9 to miui 8 everything worked perfectly.
i don't know why but i wasn't able to flash any marshmallow based or nougat based roms on TWRP 3.2.1.0 recovery.
yes i did lose data when upgrading from TWRP 3.0.2-0 to TWRP 3.2.1.0 but i had done backup so no issues.
i would highly recommend you to do backup if you are making any changes in your device.
Click to expand...
Click to collapse
Thanks bro
you need to install stock rom after unlocking
Unlocking Xiaomi Redmi4x santoni bootloader doesn't delete the data partition, but after unlocking the bootloader your phone won't boot, you need to install the same stock rom it was on phone previously.
Download MIUI Stock ROMs (if you didn't make OTA update from MIUI, check Older versions and download the correct ROM)
You can copy the ROM image to phone before unlocking or if you have already unlocked and stuck in boot, you can copy the ROM to an USB flash drive.
You need ADB installed on your PC.
Download the TWRP for Xiaomi Redmi 4X image.
If you want to restore the existing state of your phone, you need to make a backup of the data partition.
Press Volume Down + Power until phone gets in FASTBOOT.
Connect phone to PC with USB cable.
From PC command prompt type the command: fastboot.exe boot twrp-3.2.1-0-santoni.img
TWRP will start on your phone, you can backup all of the partitions, but you need only the data partition to restore.
Now Install the stock rom (you can select USB OTG if ROM is on USB drive), then RESTORE the backed up DATA partition only.
After I unlocked the bootloader, and before flashing anything, I did a full complete backup using TWRP. After that, I installed a custom ROM. Now I would like to restore back the stock ROM using TWRP. If I would like to install a custom ROM sometime down the road, is it necessary to flash the copy-partition again?
I tried doing the same thing as you and when I tried to restore de TWRP backup it failed completely, the phone was not bootable. I had to restore it with Lenovo/Motorola Rescue Assitant.
I have flashed numerous custom ROMs and for safety, I always flash the copy-partition first. Never had an issue.