So I read the tutorial on how to remove the MTD mod. I cant seem to get it to uninstall though. I tried flashing a new recovery image through terminal emulator and then doing a factory reset/wipe. Here are the steps I did to attempt to get rid of the MTD mod, please let me know where I went wrong here, thanks.
Flashed a new recovery via terminal emulator
Rebooted phone into recovery
Performed a nandroid backup of current ROM
Performed factory reset/wipe
Rebooted recovery
Nandroid restore of ROM
When this didn't work I attempted this:
Rebooted into recovery
Modified mtdpartmap.txt file with MTD 0
Ran the boot patcher
Factory reset/wipe
Nandroid restore
Both methods did not remove the MTD resizing I did. What/where did I go wrong?
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
PcFish said:
All I do is run the boot patcher then reboot.
Wouldn't nandroid restore just return it to whatever it was when you backed it up?
Click to expand...
Click to collapse
Nandroid restore only restores the ROM itself though doesn't it which wouldnt impact the recovery image and boot flasher?
Ok, so I did the nandroid restore and then I ran the custom boot patcher with my mtdpartmap.txt set to MTD 0 and rebooted...looks like im stuck at the start up splash screen...what is going on???
EDIT: Figured it out:
Formatted system, data, and cache
Resized mtdpartmap.txt to "mtd 0"
Flashed boot patcher
Advanced nandroid restore of system, data, and cache
reboot
ROM booted right up and I am back to stock partition sizings.
Related
Hello,Guys im not able to install GGL Roms....im followed exact steps but still not able to install GGL Rom phone is rebooting and it's just booting into stock 2.2.2 any way to fix it im on 2ndinti
Is your defy with green lens? are you trying this with multi boot? do you have the 5+ version bootmenu and recovery.
GGL roms are based on ginger bread kernel, once restoring the system we need to restore boot/devtree for gb kernel installations, it is to be done through customer recovery restore. You should be able to boot into GGL rom once you do this.
If it is still taking you to stock 2.2.2 means, probably you are trying in multi boot and it will not work the ROMs with different kernels. For you to boot into virtual system, you should go to boot menu and select 2ndboot option.
premaca said:
Is your defy with green lens? are you trying this with multi boot? do you have the 5+ version bootmenu and recovery.
GGL roms are based on ginger bread kernel, once restoring the system we need to restore boot/devtree for gb kernel installations, it is to be done through customer recovery restore. You should be able to boot into GGL rom once you do this.
If it is still taking you to stock 2.2.2 means, probably you are trying in multi boot and it will not work the ROMs with different kernels. For you to boot into virtual system, you should go to boot menu and select 2ndboot option.
Click to expand...
Click to collapse
Yes,My Defy with Green Lens..im on stock 2.2 im not trying to multiboot...and jst i want to use the GGL Rom and followed the instructions and my boot it is 2ndinit and not cwm
you have CWM installed right, for you to restore nandroid backup?
If you have this, just go to custom/latest recovery and restore system+data,boot,devtree and recovery from the nandroid of GGL rom, after this youshould be able to boot into GGL, what am I missing here?
This is my Boot Menu imo it's not cwm
L7iharsha said:
This is my Boot Menu imo it's not cwm
Click to expand...
Click to collapse
The option that you selected is 'Recovery' only right, which I couldnt read it properly, that is CWM mode.
If you go there, you will find number of other options like install from update.zip, install from zip, backup and restore etc.
You should select backup and restore, and then Restore options, system+data by selecting GGL ROM directory after that Advance Restore and then boot&devtree restore.
Before this I assume you have put GGL nandroid directory inside sdcard/clockworkmod/backup.
premaca said:
The option that you selected is 'Recovery' only right, which I couldnt read it properly, that is CWM mode.
If you go there, you will find number of other options like install from update.zip, install from zip, backup and restore etc.
You should select backup and restore, and then Restore options, system+data by selecting GGL ROM directory after that Advance Restore and then boot&devtree restore.
Before this I assume you have put GGL nandroid directory inside sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Still it's not booting...
L7iharsha said:
Still it's not booting...
Click to expand...
Click to collapse
put the nandroid folder in sdcard/clockworkmod/backup/, if you access your SD card you should find GGLRom folder inside that, and if you further open the GGLRom folder you should see immediately boot.img, devtree.img, system.ext3.tar etc. (You can use any file explorer, preferably root-explorer or total-commander) Once you ensure these things, then you are set to install.
Restart your phone and when BlueLED lights, immediately press Vol-down, this would take you to boot-menu. Since the screenshot tells that you are at 1.0.5 bootmenu version, you should atleast have 5.0.3.1 and up recovery installed. Select 'Recovery' inside boot-menu, this would take you to recovery mode, you can select 'Stable' or 'Custom recovery' anything is Okay. ( incase you installed and use multi-boot, then stable recovery is for your main-rom, and custom/latest recovery is for virtual-rom)
Do factory data/reset, then go to Advanced and wipe Dalvik Cache. Then comeback and select Backup and Restore. Select Restore with the nandroid folder of GGLRom, restore system+data. Go to Advanced Restore, select using nandroid folder of GGLRom, restore boot, devtree and recovery(if there).
Just precautionary, you can wipe cache data/factory reset, and Advanced wipe Dalvik cache. Reboot Now. Wait for few minutes, since dalvik cache is wiped, it may take 3-5min for complete bootup.
Your defy should now start with GGL Rom if all the steps are done correctly. This is the procedure for any nandroid ROM installations.
Thanks For Guiding Me Fixed it
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
I did nothing but boot into recovery and this is all that happens when trying to recover my cwm backups. The version of CWM should not have changed and I've flashed these files before. I accidentally started another backup and shut the phone off while it was plugged in through usb (debugging might have been enabled but I don't use adb commands or have a shell).
I can restore my rom but I want to restore my backup.
How can I know the version of the backups and see if they are different from the cwm recovery version? Also in the past I have flashed and backup through rom manager, but would my rom manager boot into cwm recovery load a different cwm recovery (it shouldn't)?
I also tried this...reload the rom but restore each partition except for system, but it fails on data too then.
At a loss here. I love my backup. I was just a system camera apk away from perfection
Please help
Solution: 5 hours of playing around and the solution is that you need to make sure the cwm version is always the same...through rom manager.
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
How old are those nandroids? Did you do them with the 2.8.6.x betas? Some people have had trouble restoring nandroids from the betas in 2.8.6.1.
You might try reflashing your rom, or flashing a full stock firmware package.
leadCactus said:
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
Click to expand...
Click to collapse
I have created a guide to install xposed, its in the themes and apps section, called screen off animation.
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
To get back to a functional ROM I would try to install a ROM which matches the firmware that you're on, perform a full wipe of data, android secure, cache and dalvic. You can use the file manager within twrp, also make sure your running the latest beta version of twrp.
You haven't bricked your device it will be recoverable..
Backup your nandroid, wipe everything (full internal storage data, cache, EVERYTHING). If that doesnt work, go to advanced wipe-> check everything and then click on repair as ext4
I have a problem with my TWRP backups created for 32.3.A.2.33 version. When I restore them, the phone restarts once and in the next boot int goes into recovery directly.
I have flashed:
E6853_32.3.A.2.33_1299-1511_R3D.ftf
Boot and recovery from:
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
And works perfectly, backups creates correctly from recovery, but when I try to recover them doesn't work.
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
I have the same problem.
srg84 said:
The problem seems to be in system partition , data partition recover with no problems.
Any suggestions?
Click to expand...
Click to collapse
Is dm-verity turned off in kernel? If not this is the reason why. You need to backup system image instead of backup files from system partition like usually in TWRP.
Can you try to make backup and restore with this recovery?
flash with "fastboot flash recovery lineage_twrp_recovery.img"
To boot into recovery power off phone, wait 5-7 sec then press power+vol_down until it vibrate.
Select "System Image" to system partition backup.
I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.
Enter fastboot, and boot twrp from adb then try again to flash it
Destinyg133 said:
Enter fastboot, and boot twrp from adb then try again to flash it
Click to expand...
Click to collapse
I already did that. But the result was the same.
Rahul Choudhury said:
I already did that. But the result was the same.
Click to expand...
Click to collapse
Try this:
Go into twrp, wipe, advance wipe, select system filesystem only and the option to repair/resize file system and repair it...
can u factory reset it? Using stock recovery
luck2ang said:
can u factory reset it? Using stock recovery
Click to expand...
Click to collapse
I flashed the fastboot rom. It is working fine now
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
i am in the exact situation please someone help me.i tried to reboot twrp with pc as well the same thing happens. please tell me how you did it
---------- Post added at 02:15 PM ---------- Previous post was at 02:02 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i cant find orange fox img file everytime i end up with zip file which can be flash in twrp. plz can you help me asap
---------- Post added at 02:27 PM ---------- Previous post was at 02:15 PM ----------
YasuHamed said:
seems like /data partition encryption / decryption issue!
fastboot rom reset everything! so you are fine now!
if you ever stuck in such situation again!
boot in to ORANGE FOX recovery 8.3 (NOT From recovery parititon!) - load it as FASTBOOT BOOT recoveryORANGFOX.img and let it boot .. goto partition, and change format DATA , YES and do it, if it doesn't allow (OR IF IT DOES ALLOW) the next step is to select the DATA partition again and change the file system from ext4 to xFAT, it will give error, NOW again change the FILESYSTEM of DATA to ext4, you will see that even after error the DATA partiton was set as xFAT and now back to EXT4. do the SAME with /SYSTEM (if necessary)
power off the device from recovery
boot recover again (fastboot boot recovery orangeFOx.img ) and FLASH the custom ROM you wanted to!
you will be fine!
Click to expand...
Click to collapse
i backed up my pixel experience rom in twrp then installed liquid remix. but i did not like it so i went into twrp wiped the phone, not inernal and all, but everything we wipe before installing rom, then i went into restore and restored my backup and reboot after that im stuck in bootloop and everytime i try to go into twrp the 1st twrp bootscreen shows up then goes back into bootloop. please help me i would be really greatful
Rahul Choudhury said:
I was on pixel experience rom and wanted to try out other pie based roms on my device. So i backed up all the partitions from twrp recovery and went on with flashing arrow os. But when i wanted to revert back to pixel experience by restoring the previously made backup, it showed that system partition mount was failed during the restore process. So i tried booting into twrp again but the device just bootloops. I tried entering recovery mode by using volume up and power combo. But twrp starts bootlooping after the logo appears on the screen. I also tried flashing redwolf twrp but it also fails to boot. Any help would be appreciated.
Click to expand...
Click to collapse
I experienced that too.. i think some ROM does something to vendor partition, example:
1. You backup data,system,boot etc...lets say u do that on "A" rom..
2. then u install "B" rom, and u like not satisfied on that..
3. Then u wipe everything and restore your "A" backup..
if you do that like what i said.. you will ended with bootloop or just stuck on mi screen..
I found a workaround ..
You just need to re-flash the "A" rom (clean install), then wipe everything again , and restore your backup..
? Sorry for my english btw
In my 16GB model, when I did a recovery through TWRP, I had a bootloop problem.
However, 'OrangeFox Recovery' does not cause this issue.
And, SD card with 'exFAT' format is recognized as normal.
I strongly recommend.
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3900471