Related
Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard.
The N1 does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
NOTE:
This mod is experimental, and for advanced users only
Requirements (READ THEM CAREFULLY):
- A rooted and unlocked phone
- A FAST enough sdcard. This mod will work with any sdcard but I'd suggest at least a Class 4 card for performance reasons
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip over CWM of the ROM you wish to boot to. The flashable zip of the ROM is the same that is used for usual ROM installation. Also the zip should be using the latest update-binary format as is scripted in updater-script (e.g. the mount command takes 4 args, etc.)
Advanced Information regarding the process
- The mod requires a boot.img that is flashed by the zip. This is used for extracting the ramdisk, commenting out the mount mtd commands and using this ramdisk for chrooting into the ROM environment
- If no boot.img is existing, the ramdisk is picked up from /sdcard/ramdisk/
- The kernel used for booting all boot options is the one installed in the phone's boot mtd. This means that you need the respective kernel modules (e.g. WiFi) for this kernel, not the one that is bundled in the ROM that is multibooted. For example, if your main ROM is CM, pick the kernel modules from this one and push them to the multibooted ROM's /system/lib/modules/
Multiboot mod Installation
Download: N1_CWM-4.0.0.5-nobodyAtall-r2.img
Install via fastboot
Code:
Copy N1_CWM-4.0.0.5-nobodyAtall-r1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash N1_CWM-4.0.0.5-nobodyAtall-r1.img
Install via adb
Code:
adb push N1_CWM-4.0.0.5-nobodyAtall-r1.img /sdcard/
adb shell 'flash_image recovery /sdcard/N1_CWM-4.0.0.5-nobodyAtall-r1.img'
adb reboot recovery
Multiboot ROM Installation
- Boot into the recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Boot into selected option!
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
- Select multiboot->Create boot option from zip and then pick the flashable ROM zip. Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- If you need to flash additional zips for this ROM, Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the zip you need to flash.
- Select multiboot->Select default boot option and pick your newly created boot option
- Select multiboot-> Boot into selected option! (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
{
"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"
}
ROMS verified to multiboot
Well, any ROM should be able to multiboot provided the requirements stated above are covered. The following ones have been verified to work:
[ROM] CyanogenMod-7.1 for Nexus One
[ROM] NEXUS N1 Passion MIUI.us Presents MIUI Pure English [AOSP]
CM 7 ExtremeMod ROM by Ken Mood
Uninstall
- Normal reboots will boot from the phone's mtd partitions.
- This mod makes no changes to your phone's mtd partitions. Flashing a new recovery will uninstall the old one obviously.
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
Changelog:
(1/7/11) N1_CWM-4.0.0.5-nobodyAtall-r2.img
Fixed bug that flashed the multiboot ROM kernel in the phones kernel partition
Improved error reporting
(30/6/11) N1_CWM-4.0.0.5-nobodyAtall-r1.img
First version of CWM recovery providing the multiboot options
woww thanks
Well, this could be freaking awesome. I'll check it out at work
Nice one. Can we use CM nightlies that came after the RC?
method77 said:
Nice one. Can we use CM nightlies that came after the RC?
Click to expand...
Click to collapse
You can use it with any CM7 ROM
I am interested in this, i'm surprised that it hasn't created more of a stir.
I have installed the recovery, but don't want to do anything else without Nandroiding first. Only Nandroid seems to get stuck on "Backing up system..."
Any i doing something wrong?
Hello shorza,
To be honest, I've only been testing the multiboot part.
However, I think that backup works fine here:
Also the backup folder is created correctly:
~ # ls -la /sdcard/clockworkmod/backup/2011-07-01.06.49.58
drwxrwxrwx 2 root root 4096 Jul 1 06:52 .
drwxrwxrwx 5 root root 4096 Jul 1 06:49 ..
-rwxrwxrwx 1 root root 93489792 Jul 1 06:52 .android_secure.img
-rwxrwxrwx 1 root root 3670016 Jul 1 06:50 boot.img
-rwxrwxrwx 1 root root 37359168 Jul 1 06:52 cache.img
-rwxrwxrwx 1 root root 184136832 Jul 1 06:51 data.img
-rwxrwxrwx 1 root root 222 Jul 1 06:53 nandroid.md5
-rwxrwxrwx 1 root root 4194304 Jul 1 06:50 recovery.img
-rwxrwxrwx 1 root root 146908608 Jul 1 06:50 system.img
On another note, I'll be doing an update today to fix some bugs related to multiboot.
CWM 4.x has problems backing sd-ext, so that might be the reason why you don't see it (your pic shows you don't have an sd-ext partition to backup) and shorza does. It is also the reason why I haven't tried this yet - if it was based on AmonRa's I'd have jumped immediately, but since it is based on CWM I wanted first to see some feedback here...
Thanks for the help. Backup eventually worked, it just took a long time.
The problem is after zipping a new rom in multiboot, selecting it, then trying to boot into it, it took too long and I lost patience. It looked like it froze.
I'll try again tomorrow.
Maybe my sdcard is too slow.
shorza said:
Maybe my sdcard is too slow.
Click to expand...
Click to collapse
You need to be patient. It takes a long time to boot (especially for the first boot) and if the recovery seems frozen, this is a good sign - it means it's booting.
Posted -r2.
This fixes a bug that would flash the multiboot ROM's kernel to the phone's kernel partition. Also improves logging in case of errors.
Testing this out right now ... just got latest cyanogenmod nightly and latest miui (as of today) going on it and just switched back and forth. sucks about having to go into recovery to switch, needs to have a boot option when starting the phone haha.
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Will this work like a nandroid backup where it saves everythn from my last boot? Or will it save everythn on that same img. when i switch roms
looking at the directory structure, per multiboot rom it saves the boot.img, cache.img, data.img, and system.img .... I don't know how it uses them, but linux is magical in mounting images as a partition, doesn't have to be physical
This is because the ROM is run using the device's kernel and not the one that comes with the ROM as stated in the first post.
To make wifi work, simply copy your wifi kernel module from /system/lib/modules to this same did within the multibooted ROM.
Ellises said:
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
This actually works pretty well, however, the phone get quite hot.
[Q]Bug fixed??
I succeed multibooting
I got miui(main)&CM7(sub)
but subrom,cm7 can't use wifi
so I changed kernel but failed
and display
[mount expects 4 3args]
[error /sdcard/xxx... ]
[ status7 ]<<maybe
If you know what's the problem, plz teach me the way
thx and pardon my English
Team Win Recovery Project 2.8, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
***WHAT WORKS***
EVERYTHING and it's been made OFFICIAL
MAKE SURE YOU GET THE CORRECT VERSION'S I WILL NOT BE TO BLAME IF YOU FLASH THE WRONG ONE
READ THIS IF YOU FLASH THE RECOVERY AND THEN ASK ME QUESTIONS I WILL POINT YOU TO THIS THREAD OR EVEN IGNORE YOU
READ REGARDING ADB IN RECOVERY
TWRP IRC CHANNEL
DOWNLOAD
DOWNLOAD ---- MY BUILD
Thanks to
The TWRP GUYS
and football for his ruu's so i can get the img's i need
and milestoner for confirming it works
Mr anon
and all the following people
orb3000
morphly
hasoon2000
hasan_abeer
vogi
chrigel2000
AndroHero
ectodroid
[email protected]
Anon #1
Ixz
bboerny
Anon #2
Anon #3
sellers86
Wik
Anon #4
simonsimons34
caedanne
flipside101
morphly
bboerny
TWRP WEBSITE
**INSTRUCTIONS**
Download the file
then either use HASOON'S toolkit
or
Manual method
reboot into bootloader
fastboot flash recovery TWRPrecovery.img
SIDELOAD INSTRUCTIONS
MarylandCookie said:
I had the same issue and fixed it via adb sideload.
I have uploaded the latest binaries to my dev host account.
1. Download and extract these to a directory and copy the rom over into the same directory.
2. Boot up your phone into twrp recovery.
3. Select advanced and adbsideload (Your phone will be waiting for the file transfer.)
4. Open command prompt in the above directory you created with the binaries and rom.
5. Issue command "adb devices" (You should get the serial number with sideload next to it)
6. Finally issue command "adb sideload rom.zip" (rom.zip will be the name of your rom)
This will start sending your rom to the handset and will automatically install.
Hope the above helps
Link to Binaries:
ADB Binaries
Click to expand...
Click to collapse
Code:
CHANGELOG
19/11/12
Last unofficial build (all builds forward are official direct from TWRP)
AT&T added
data/media sorted
-----------------------------------
Build 1 16/11/12
1st build
LET ME KNOW OF ANY PROBLEMS
any feedback on this guys?
Wow. I didnt even see this. I couldve added it to my toolkit lol. ill wait til people say if it works and then ill add. Thanks Lloir!
if it work's i'll talk to dees_troy about making it official
So it's still untested? I would like to install it but I'm afraid it will brick my phone somehow..
Edit: Flashed it but I can't seem to browse through the sdcard, just the internal system (/sdcard vs /sdcard1) where the app/system etc. is located.
thecompany said:
So it's still untested? I would like to install it but I'm afraid it will brick my phone somehow..
Edit: Flashed it but I can't seem to browse through the sdcard, just the internal system (/sdcard vs /sdcard1) where the app/system etc. is located.
Click to expand...
Click to collapse
meh thanks dude, i'll look into this more when i get the HOX+
locking thread for now
Got a report that this is working fine, the sdcard is under /sdcard/media so it works perfect!
thanks milestoner for pointing this out!
Does this work with At&t HTC one X+?
Sent from my HTC One X+ using xda premium
samomamo said:
Does this work with At&t HTC one X+?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Now it does
Sent from my One V using Tapatalk 2
Just a few comments:
- can't mount SD Card in Recovery (or at least can't access to it)
- backup/nandroid is saved in (SDCard - DATA) / TWP
and not in (SDCard - DATA)/media, so can't access to the back-up
Steve0007 said:
Just a few comments:
- can't mount SD Card in Recovery (or at least can't access to it)
- backup/nandroid is saved in (SDCard - DATA) / TWP
and not in (SDCard - DATA)/media, so can't access to the back-up
Click to expand...
Click to collapse
cant access it from TWRP? or? i cant test sdcard mount as linux is being a *****, but it looks like it mounts fine, i have a nandroid and i can see it to restore......
*edit*
nevermind see what you mean, i'll sort it for the next build
I can confirm that mount points are borked at the moment. While in recovery the sdcard can be found in /sdcard/media. Backing up seem to work ok but backups are insanely huge (6.6GB for a compressed backup!). This is probably because everything including the whole sdcard is backed up. While TWRP itself finds the backups just fine, when android is running they are located in /data/TWRP. I haven't tried to restore a backup yet.
I'm a little bit worried about what will happen later if I try to restore one of my backups that are made with the current TWRP version. Will the fixed version recognize and correct the mixed up mount points of the current version? If not, I can forget about all of my current backups .
---------- Post added at 01:18 PM ---------- Previous post was at 01:10 PM ----------
Just two more minor details: Time and battery values displayed at the top of TWRP are wrong. The battery stays put at 66% and time is shifted by a couple of hours.
Thanks again for your work!
milestoner said:
I can confirm that mount points are borked at the moment. While in recovery the sdcard can be found in /sdcard/media. Backing up seem to work ok but backups are insanely huge (6.6GB for a compressed backup!). This is probably because everything including the whole sdcard is backed up. While TWRP itself finds the backups just fine, when android is running they are located in /data/TWRP. I haven't tried to restore a backup yet.
I'm a little bit worried about what will happen later if I try to restore one of my backups that are made with the current TWRP version. Will the fixed version recognize and correct the mixed up mount points of the current version? If not, I can forget about all of my current backups .
---------- Post added at 01:18 PM ---------- Previous post was at 01:10 PM ----------
Just two more minor details: Time and battery values displayed at the top of TWRP are wrong. The battery stays put at 66% and time is shifted by a couple of hours.
Thanks again for your work!
Click to expand...
Click to collapse
yea the battery thing is a pain, time you can set yourself...the fstab is fine, it's other settings i need to sort out, just working on the AT&T one and then i'll sort this one out
@LIoir
you wont belive it but HTC ONE X+ source code for Kernel is out (sorry for writing it here), so i can start to look into it !
I will try to push the source to github tonight, so you can also have a look into it and if you still wont to, we can work together on it
Op updated!
Lloir said:
Op updated!
Click to expand...
Click to collapse
ATT FTW!!!! Unfortunately the link is dead. Thank you for your wonderful efforts none the less
sparkplug619 said:
ATT FTW!!!! Unfortunately the link is dead. Thank you for your wonderful efforts none the less
Click to expand...
Click to collapse
woops was a typo
http://cyano-rob.tuennerhoff-edv.de/RECOVERY/TWRP/evitareu/recovery.img
there's the link also link is fixed in the OP
Lloir said:
woops was a typo
http://cyano-rob.tuennerhoff-edv.de/RECOVERY/TWRP/evitareu/recovery.img
there's the link also link is fixed in the OP
Click to expand...
Click to collapse
If this works, can an AT&T user make a nandroid and upload the boot.img and system?
{
"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"
}
TWRP_3.0.3 for Samsung Galaxy SM-J510FN J5(2016)
Unofficial
Description:
TWRP_3.0.3 :
Based on TWRP for seed -twrp-3.0.3-0-seed 21.8M 2017-01-02 12:09:51
-Added item in the Backup section ->Modem
-Added Mount-firmware
-Added Mount-persist
OTG -Works good,you can install or Restore from external flash drive
-Theme TWRP-Works good theme-twrp-materialised-dark-light-play
Screenshot -Volume -and Power buttons save in externall SD
What should I back up in TWRP?
Bugs:
- PC mounting MTP (but adb should work,Windows 10 cant install MTP driver)
How to install:
Code:
1. Install device usb drivers and Odin
In Phone Developer options - On OEM unlock
2. Power off the device.
3. Boot to download mode (VOLUME DOWN/HOME/POWER).
4. Volume UP once.
5. Open Odin as an administrator, connect the device to a usb port,
and make sure a blue button appears and says "Added" in description on the left.
6. Select AP or PDA for older Odin and search for the downloaded tar file.
7. Uncheck auto reboot from the second tab.
8. Start flash and you should see the succeeded command.
9. Unplug the device and remove the battery.
10. Reboot to TWRP and enjoy! (VOLUME UP/HOME/POWER).
Screenshots:
NEW!!!
TWRP 3.1.0-0 for Samsung Galaxy SM-J510 J5(2016)Old versions:
Description:
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
TWRP_3.0.2
Fix : No error with third-party reboot,Reboot recovery
Fix :Removed cursor from the screen
Fix :Added in Wipe menu "Android secure''
Fix :OTG -Works good,you can install or Restore from external flash drive
Bugs:
- PC mounting MTP (but adb should work,Windows 10 cant install MTP driver)
View attachment TWRP_3.0.2_J510FN.tar
View attachment TWRP_3.0.2-1_J510FN.tar
Bro , check this:
https://forum.xda-developers.com/galaxy-j5/development/recovery-twrp-3-0-2-samsung-galaxy-t3406889
wolty said:
Bro , check this:
https://forum.xda-developers.com/galaxy-j5/development/recovery-twrp-3-0-2-samsung-galaxy-t3406889
Click to expand...
Click to collapse
Bro ,i I know this with bugs .For my J510FN this TWRP 3.0.2 J510Н -Reboot recovery dont work,cursor in screen,wipe without Android secure.etc
I have repaired these bugs.
Or for you all works ?
https://forum.xda-developers.com/showpost.php?p=69188548&postcount=34
https://forum.xda-developers.com/showpost.php?p=67988962&postcount=14
https://forum.xda-developers.com/showpost.php?p=68115566&postcount=17
https://forum.xda-developers.com/showpost.php?p=68345605&postcount=23
lemlis said:
Bro ,i I know this with bugs .For my J510FN this TWRP 3.0.2 J510Н -Reboot recovery dont work,cursor in screen,wipe without Android secure.etc
I have repaired these bugs.
Or for you all works ?
https://forum.xda-developers.com/showpost.php?p=69188548&postcount=34
https://forum.xda-developers.com/showpost.php?p=67988962&postcount=14
https://forum.xda-developers.com/showpost.php?p=68115566&postcount=17
https://forum.xda-developers.com/showpost.php?p=68345605&postcount=23
Click to expand...
Click to collapse
Recovery is not seandroidenforce
echo -n "SEANDROIDENFORCE" >> recovery.img
?
You change /dev/block/platform/7824900.sdhci/by-name/boot
To
/dev/block/platform/soc.0/7824900.sdhci/by-name/boot
Nice ?
In the other recovery when you rebooted from the recovery while the device is charging. The device enters the charging mode and not the system
The only problem is MTP
When I enter the backup option. Red letters appear saying that could not find something related to the firmware and the efs
Demicro said:
When I enter the backup option. Red letters appear saying
Click to expand...
Click to collapse
Hey bro!For me all works great,you're doing something wrong.There are no red letters.
Only MTP .
lemlis said:
Hey bro!For me all works great,you're doing something wrong.There are no red letters.
Only MTP .
Click to expand...
Click to collapse
In restore
This is normal or I should worry☺
Demicro said:
In restore
This is normal or I should worry
Click to expand...
Click to collapse
"EFS1 and EFS2" your backup was made with old TWRP .
New TWRP dont have partition EFS1 EFS2. Have partition EFS
Make backup with new TWRP- then restore will be without mistakes
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
I can not fix MTP
There is a problem with this TWRP, after flashing, my computer does not detect anymore my device (odin yes) so I cant open device files from computer...
Sent from my SM-J510FN using XDA Labs
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
lemlis said:
"EFS1 and EFS2" your backup was made with old TWRP .
New TWRP dont have partition EFS1 EFS2. Have partition EFS
Make backup with new TWRP- then restore will be without mistakes
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
I can not fix MTP
Click to expand...
Click to collapse
With this TWRP my laptop does not detect my device, so I can't transfer files throught usb cable' I use a sd adapter... How to solve this?
Sent from my SM-J510FN using XDA Labs
TheWalkingSans said:
There is a problem with this TWRP, after flashing, my computer does not detect anymore my device (odin yes) so I cant open device files from computer...
Sent from my SM-J510FN using XDA Labs
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
With this TWRP my laptop does not detect my device, so I can't transfer files throught usb cable' I use a sd adapter... How to solve this?
Click to expand...
Click to collapse
It is a known problem, which for now has not been resolved.
Mtp issues in recovery
The phone does not enter the recovery if it is connected to the charger. That is, when a reboot is made from the terminal
Reboot recovery
?
Charge mode
Demicro said:
The phone does not enter the recovery , when a reboot is made from the terminal
Click to expand...
Click to collapse
TWRP_3.0.3
It may be this version will work correctly from the terminal
In this TWRP_3.0.3 from TWRP Terminal reboot recovery comand works good
error unmounting \'/cache\' (no such device)
trying to format a partition to f2fs
to restore to ext4 I have to do it manually because if I try to farmat to ext4 the error appear
mke2fs -t ext4 /dev/block/bootdevice/by-name/cache
your mke2fs.conf file does not define the f2fs filesystem type
formating with mkfs.f2fs === succefull but twrp can't mount f2fs partition
Demicro said:
trying to format a partition to f2fs
to restore to ext4 I have to do it manually because if I try to farmat to ext4 the error appear
mke2fs -t ext4 /dev/block/bootdevice/by-name/cache
your mke2fs.conf file does not define the f2fs filesystem type
Click to expand...
Click to collapse
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
lemlis said:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
Click to expand...
Click to collapse
I can not restore the backup because twrp can not mount f2fs
I added f2Fs to the kernel for the future
flag in the anykernel zip
f2fs=true or false
and I will cheery pick f2fs(linux 3.18) from the official twrp source code for J7
Demicro said:
I can not restore the backup because twrp can not mount f2fs
Click to expand...
Click to collapse
Maybe dann need to make TWRP from your new version kernel with added f2Fs to the kernel for the future ?
Sorry,my english is very bad.I do not quite understand what I have to do?
New Recoverys with Aroma support for J5 2016
Here
New Thread Here:
TWRP 3.1.0-0 for Samsung Galaxy SM-J510 J5(2016)
Thread closed on OP's request.
Regards
Vatsal,
Forum Moderator.
{
"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"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.
I started a little Android Generic System Image installation Guide on my Github :
https://github.com/GBouerat/xiaomi_mi_pad_4
(work in progress)
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
P.Kosunen said:
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
Click to expand...
Click to collapse
It's a typo, thanks
Code:
fastboot oem device-info
Thank you very much, mate! Can we expect to see an official TWRP release as well as LineageOS 15.1?
PS: Does Android P GIS work well? Are there any known issues so far?
Please do include the build.prop tweaks mentioned here - those are quite necessary for the device to function as a tablet.
cRaZy-bisCuiT said:
PS: Does Android P GIS work well? Are there any known issues so far?
Click to expand...
Click to collapse
None of those P GSIs boot.
Anyone able to root using Magisk on v9.6.23 boot.img (http://en.miui.com/thread-3538488-1-1.html)? Magisk patched boot.img doesn't seems to boot for me and I have to revert to stock boot.img.
Edit: hah, never mind. I forgot to disable forceencrypt when i flashed the new stock kernel and it encrypted data. Had to wipe data and unencrypt to root again.
Magisk on GSI is incompatible with adb usb debug mode, no ?
GBouerat said:
Magisk on GSI is incompatible with adb usb debug mode, no ?
Click to expand...
Click to collapse
works fine for me
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
{
"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"
}
bartekm01 said:
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
Click to expand...
Click to collapse
Hallo
Where did you find this TWRP?
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Tanks!!
Encryption
bartekm01 said:
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Click to expand...
Click to collapse
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
jonklinger said:
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
Click to expand...
Click to collapse
I didn't install gsi
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
snke said:
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
Click to expand...
Click to collapse
No only TWRP. I didn't flash misc - I think that misc changing region but I did not found any information about it.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
arkansis said:
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
Click to expand...
Click to collapse
MiPad4 is only a partition. There is no b partition for seamless updates.
So far I didn't install any GSI but I've have installed China stable, developer and xiaomi.eu roms and I didn't have to resize system partitions. An ROMs are bigger maybe that's why You need to extend partitions but installation should end with error because of lack "b" partition
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
dzidexx said:
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
Click to expand...
Click to collapse
I'm agree, in my opinion It's the best GSI rom for MP4.