What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X
Related
While attempting to modify my wpa_supplicant in /system/app (not by any process listed here) I somehow managed to completely destroy my /system partition. Not a single file was left alive. My nook did not particularly like this, and now will not boot. I had installed cwm recovery through indirect's app, and cwm won't flash either of Barnes and noble's update zips for some reason. My question is, does anybody have a cwm compatible zip that will restore my /system, or can anyone point me to information on how to make one? Cwm's scripting language seems to be poorly documented, if documented at all. Thank you in advanced for any help! I worked on this for several days before posting.
Sent from my MB860 using xda premium
Have you tried with adb? If not then you haven't try it all.
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM mount /system, take the \system folder of the acclaim_update.zip(unzip it) and put it in C:\ntroot ( where adb should be) , cut \system\bin folder and put it outside so it will look like this C:\ntroot\bin, open CMD as administrator and run
>cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push bin /system/bin ( it will push all the files inside bin folder to /system/bin and override them)
Repeat the process with the other folders.
Wish you luck!
PS: if you have CWM backup you could even unpack system.img is easy but you need linux ubuntu is fine so you use your own modified tweaked and working system.
~ Veronica
Sent from XDA premium using my Nook Tablet
Thank you, I didn't know adb could push entire folders! I would still like to learn how to make flashable zips, though. Should I just read the source code or something? I really cannot find any documentation.
Sent from my MB860 using xda premium
Zapcorns said:
Thank you, I didn't know adb could push entire folders! I would still like to learn how to make flashable zips, though. Should I just read the source code or something? I really cannot find any documentation.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Pm celticwebsolutions user he just learned how to make flashable zips so he must have the documentation, I will look into it this week. Let me low if you managed to fix your nook.
~Veronica
Sent from XDA premium using my Nook Tablet
http://forum.xda-developers.com/showthread.php?t=1187313
http://www.freeyourandroid.com/guide/introdution_to_edify
http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
A cwm flashable zip must have a META-INF directory and whatever you're loading with a structure like below:
/META-INF
-/com
--/google
---/android
----/update-binary (file)
----/updater-script (file)
/system (or whatever you're loading)
'updater-script' uses the edify script language to mount, copy, set permissions, etc. Make sure this is in unix formatted text and not dos/win. Some CWM versions dislike dos/win formatted text. May as well make sure it's unix to avoid any issues.
You can just pull 'update-binary' from any flashable zip for the NT.
Once the zip is created you need to sign it, but CWM can be set to ignore that.
Just look at other cwm installable zips for examples.
http://downloads.androidsu.com/superuser/
http://forum.xda-developers.com/showthread.php?t=1458452
Igthorn said:
http://forum.xda-developers.com/showthread.php?t=1187313
http://www.freeyourandroid.com/guide/introdution_to_edify
http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
A cwm flashable zip must have a META-INF directory and whatever you're loading with a structure like below:
/META-INF
-/com
--/google
---/android
----/update-binary (file)
----/updater-script (file)
/system (or whatever you're loading)
'updater-script' uses the edify script language to mount, copy, set permissions, etc. Make sure this is in unix formatted text and not dos/win. Some CWM versions dislike dos/win formatted text. May as well make sure it's unix to avoid any issues.
You can just pull 'update-binary' from any flashable zip for the NT.
Once the zip is created you need to sign it, but CWM can be set to ignore that.
Just look at other cwm installable zips for examples.
http://downloads.androidsu.com/superuser/
http://forum.xda-developers.com/showthread.php?t=1458452
Click to expand...
Click to collapse
lol now i realized i've always played with the tools for make this but i have never used them to create update.zip's or flashable zips just to extract .img files and sign them lmao, i have made a tutorial about this in other forum toowhich will be posting here too, for now i leave the tools i used like unyaffs, etc which are needed and will make your life easier.
IMG_tools.zip
And this is the tutorial, just some more reference
~ Veronica
Good news, I just managed to make it fail to boot at a different point. That's not much, but its progress. Does anyone have any ideas? I did successfully restore /system (I think) so I don't know why I'd won't boot.
Sent from my MB860 using xda premium
Zapcorns said:
Good news, I just managed to make it fail to boot at a different point. That's not much, but its progress. Does anyone have any ideas? I did successfully restore /system (I think) so I don't know why I'd won't boot.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
unmount system, wipe cache, advanced> wipe dalvik cache, fix permissions in CWM try that and give more details of its status.
~ Veronica
Zapcorns said:
While attempting to modify my wpa_supplicant in /system/app (not by any process listed here) I somehow managed to completely destroy my /system partition. Not a single file was left alive. My nook did not particularly like this, and now will not boot. I had installed cwm recovery through indirect's app, and cwm won't flash either of Barnes and noble's update zips for some reason. My question is, does anybody have a cwm compatible zip that will restore my /system, or can anyone point me to information on how to make one? Cwm's scripting language seems to be poorly documented, if documented at all. Thank you in advanced for any help! I worked on this for several days before posting.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
find any CW flashable zip, get the 1.4 acclaim zip, copy all content from acclaim zip, EXCEPT META folder, to the CW zip, and put the CW zip, overwrite if it asked, you just produced on SD and flash it win recovery. You will need to re-root.
So, I managed to do the same thing...not to ask for help or anything but can someone provide a link to a CW zip that can get me back to square one?
I was finally able to fix it! Using Cobrato's flashable zip in the developer forum, i was able to flash a working system. It even included many of the apps i had been using before not available on the market. Thank you for all youre help.
Sent from my BNTV250 using xda premium
Zapcorns said:
I was finally able to fix it! Using Cobrato's flashable zip in the developer forum, i was able to flash a working system. It even included many of the apps i had been using before not available on the market. Thank you for all youre help.
Sent from my BNTV250 using xda premium
Click to expand...
Click to collapse
Great News!
Please update your OP title.
And link to the file that fixed it. I'm sure one of us other n00bs will do the same.
Sent from my PG06100 using xda premium
Heric1 was in the same situation but i gave him a link that i found in development with 1.4.0 stock ROM with indirect and cfoesch root methods and it worked ill post this links in My FAQ. Development should have the thread that was created to index all the ROMS updated and stickied
http://forum.xda-developers.com/showpost.php?p=21748940&postcount=57
~ Veronica
Sent from XDA premium using my Nook Tablet
I upgraded my GT-P7510 (p4wifi) from 4.1 to 4.2.2 and recently to PAC_Infamous 4.3 ROM. All was working well but I had very little free storage due to the Misc group being 10.09GB and appearing to include a duplicate of my SDcard storage (~8GB) I was advised I should have wiped all my data before flashing the ROM as the storage setup changed between 4.1 and 4.2.2
I'm afraid I should have waited 'till I was fully awake. I made the mistake of formatting the SDcard in my hope to have the cleanest start - and of course I lost my 2 zip files (as well as everything else)
I can still start up CWM (v6.0.1.5) and I have tried the sideload .zip route. I have Minimal ADB and Fastboot installed on Win7Pro and when I do 'adb devices' command I see 'C4F12871..... sideload' result in the list of devices attached.
When I do 'adb sideload filename.zip' I get - failed to write data 'protocol fault (no status)'
Any advice on what to do now? Could I use fastboot to push an image file (but I can't find one for P7510/16!)?
I do have the Samsung interface to SD adapter and I have tried putting the ROMs (PAC + gapps) on an SD card via this adapter. However, CWM can't see the external SD card so I still can't flash the ROMs
Can anyone please help this noob out of his hole?
Try 'adb push xxx.zip /sdcard/your/folder'
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
Try 'adb push xxx.zip /sdcard/your/folder'
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Very many thanks for the prompt reply. I did as said with the push just sending the .zip files to /sdcard
The main ROM took 207secs and the gapps took 114sec.
When I went back to CWM to try to flash the ROM there were no files found. I looked at the log but I don't fully understand it.
I have attached a picture of the log output. The top part (above No Files found.) was after restarting CWM and the lower part after trying to file the .zip files.
Can you help again?
Best wishes,
Stuart
Sorry, but I can't help you with that. My suggestion would be to reflash stock ICS again, flash the latest cwm (you're on a older version), then flash the ROM.
About the file system, if your files did not automatically move, then move it from /data/media to /data/media/0.
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
Sorry, but I can't help you with that. My suggestion would be to reflash stock ICS again, flash the latest cwm (you're on a older version), then flash the ROM.
About the file system, if your files did not automatically move, then move it from /data/media to /data/media/0.
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Once again many thanks. Your are the GREATEST! I updated CWM but the real thing was I used /sdcard as the push destination and not /sdcard/
My Tablet is now rebooting the PAC 4.3 ROM.
Best wishes and thanks again,
Stuart
Stuart-g3sna said:
Once again many thanks. Your are the GREATEST! I updated CWM but the real thing was I used /sdcard as the push destination and not /sdcard/
My Tablet is now rebooting the PAC 4.3 ROM.
Best wishes and thanks again,
Stuart
Click to expand...
Click to collapse
Ah, didn't realise that "/" would be the error. Thanks for letting me know.
Sent from my GT-P7500 using Tapatalk HD
Hey guys, worst part about samsung devices is always their EFS issues.. my samsung tool app has already gained support for SM-G900A, SM-G900F, SM-G900H, SM-G900T before root and custom roms are available, so first thing is first, root(when available) and backup EFS!
ive kept all downloads and discussion within the original thread here! - SAMSUNG TOOL APP HERE
this was made possible by leoaudio13 dumping his partition table!
I love u mate!
Sent from my SM-G900F using Tapatalk
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
leoaudio13 said:
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
Click to expand...
Click to collapse
gonna be hard though!
leoaudio13 said:
@ricky310711 : if you can make apk to backup efs , its great if you can make apk to dump partitions hehe! BTW ricky, link to proper partition table in Dev section : http://forum.xda-developers.com/showthread.php?t=2695363
Click to expand...
Click to collapse
actually thats not hard with root. lol
I'm working on recovery. waiting to hear back from tester(s) to see if we have a working img yet.
PlayfulGod said:
actually thats not hard with root. lol
I'm working on recovery. waiting to hear back from tester(s) to see if we have a working img yet.
Click to expand...
Click to collapse
it wasnt hard without root either
ricky310711 said:
it wasnt hard without root either
Click to expand...
Click to collapse
well you didnt get me the boot/recovery dumps til afterwards.
PlayfulGod said:
well you didnt get me the boot/recovery dumps til afterwards.
Click to expand...
Click to collapse
thats because nothing was accessible until after root, dumping system was easy, but any other directory/file on the device wasnt able to be read after until being rooted..
samsung didnt even include tar binary so I dumped over adb, then CF helped root and then we dumped raw images!
ricky310711 said:
thats because nothing was accessible until after root, dumping system was easy, but any other directory/file on the device wasnt able to be read after until being rooted..
samsung didnt even include tar binary so I dumped over adb, then CF helped root and then we dumped raw images!
Click to expand...
Click to collapse
yea system can be gotten with adb pull w/o root.
Check hangouts, got 2 imgs for yall to test.
PlayfulGod said:
yea system can be gotten with adb pull w/o root.
Check hangouts, got 2 imgs for yall to test.
Click to expand...
Click to collapse
corect! but some files I was still denied permissikn to pull from /system :/
ricky310711 said:
corect! but some files I was still denied permissikn to pull from /system :/
Click to expand...
Click to collapse
Gah!!! Im drunk ricky
Sent from my SM-G900F using Tapatalk
updated.
LTE devices have a QualcommChip, where everything is stored in the nvRAM, the EFS includes only files that have nothing but absolutely nothing to do with the IMEI.
Gesendet von meinem Nexus 5 mit Tapatalk
I backed up my EFS to internal storage but cant find it don't see no /data/media/SamsungTool/ (using EFS file explorer) just want to save a copy to the PC. What's the exact name of the backed up file so i can use the search feature? cheers.
Offica said:
I backed up my EFS to internal storage but cant find it don't see no /data/media/SamsungTool/ (using EFS file explorer) just want to save a copy to the PC. What's the exact name of the backed up file so i can use the search feature? cheers.
Click to expand...
Click to collapse
Backup to your External SD instead.
/storage/extSdCard/SamsungTool/efs.img
Sent from my SM-G900T
dynospectrum said:
Backup to your External SD instead.
/storage/extSdCard/SamsungTool/efs.img
Sent from my SM-G900T
Click to expand...
Click to collapse
Gotta buy a new sd card, But yeah did a search for efs.img and didn't come up, I'll wait and try when i get my sdcard.
G900s/g900l
Hi will it work on the G900S or G900L?
thehacker911 said:
LTE devices have a QualcommChip, where everything is stored in the nvRAM, the EFS includes only files that have nothing but absolutely nothing to do with the IMEI.
Click to expand...
Click to collapse
@thehacker911
For full backup, which partitions do you recommend?
Galaxy S5 SM-900P Partition table
you can still simply create a copy right?
I have always had rooted phones and my SGS 5 is no exception, it got rooted using CFroot in the carpark immediately on picking it up.
I have therefore always simply made a copy of the efs folder on to the external sd card which is then synced to my dropbox.
However I have not really kept up to date with developments in these areas, so my question is nowadays is this still enough to ensure the safety of my device and it's ability to connect to my carrier. In the past when I have had issues after flashing roms and things simply deleting the /efs folder and copying the contents of my back up into it and rebooting has always been sufficient to get my carrier back up and running is this still the case with the international SGS5 qualcomm variant or do I need to consider other elements?
When will it work for SM-G900V? I just rooted my phone today and would like to use this for my backups. I just tried it by using EFS backup and now it's stuck on a triangle with an exclamation mark that says Please Wait. Ugh! Help...
Good day everybody!
Today I want to share with you the flashable ZIP I made to enable init.d support in our phones. Root not required!
Works for every MIUIv6 variant (including dev ones) and probably for MIUIv5 and many other phones and ROMs, although I can't confirm (the process is very similar in many phones, so I think it should work in EVERY kitkat-based ROM - and maybe in JB/LP ones).
WHAT IS INIT.D?
Google is your friend. If you don't know what init.d is you probably don't need it.
HOW IT WORKS
It checks at boot time if there are executable files in /data/init.d and executes them in lexical order. Files with executable flag unset will not be executed.
OK, but why init.d in /data?
Because every system update erases /system partition, which in turn would erase every init.d script you made or installed. Placing them in /data ensures OTA survival.
It is similar to CyanogenMod's userinit feature.
The standard directory /system/etc/init.d is created as a symlink to /data/init.d to make init.d-aware apps work without ever noticing the difference.
Features of this mod
I have included an example init.d file which creates a test file (useful to see if it works, see below)
If you never wrote init scripts, that can be used as a simple template to begin.
This mod doesn't alter the kernel in any way, so it's pretty safe to install.
HOW TO INSTALL
Requirements
CWM/TWRP recovery
BusyBox (MIUI has it out of the box)
Any KK-based ROM (maybe works on other versions too but I can't be sure about that, just try)
Instructions
Just flash this in recovery and you're all set. I flash it every week alongside MIUIv6 weekly update.
How to theck if it works
After install (and a reboot), navigate to /data/local/tmp. If you find the file init.d-test.txt, then init.d support is installed and active
CREDITS
@udda90
I tried to flash your file on my redmi note 3g with the latest miui V6 developer version and it gives me error. I am using twrp recovery.
Have you any idea what is going on?
Sent from my HM NOTE 1W using XDA Free mobile app
davorzilic said:
I tried to flash your file on my redmi note 3g with the latest miui V6 developer version and it gives me error. I am using twrp recovery.
Have you any idea what is going on?
Sent from my HM NOTE 1W using XDA Free mobile app
Click to expand...
Click to collapse
The only thing that comes to my mind is that you could have ZIP signature checking enabled. My ZIP is not signed so it will not install unless you disable it. (signature checking is a good thing, for example it keeps you from installing corrupted ROMs. Disable it only for this time.)
But I can be wrong, you told me nothing about the error you have experienced in your device. What kind of error are you seeing? Copy it here so I can be more helpful Also attach recovery.log if you can.
Thanks for very fast answer. I appreciate your efforts.
I didn't use zip verification option.
I have photographed error message in twrp so I uploading that photo.
If you have any suggestion please let me know.
Sent from my HM NOTE 1W using XDA Free mobile app
davorzilic said:
Thanks for very fast answer. I appreciate your efforts.
I didn't use zip verification option.
I have photographed error message in twrp so I uploading that photo.
If you have any suggestion please let me know.
Sent from my HM NOTE 1W using XDA Free mobile app
Click to expand...
Click to collapse
Try unmounting data and system before installing. I've heard of people solved this way, also MIUI updates sometime fail because of this.
If this won't work, would you mind to send me recovery.log? TWRP creates it in /tmp after an install. It contains exact error code and text.
If you have ADB installed in your PC you can get it by typing in terminal:
Code:
adb pull /tmp/recovery.log
(In your device that file may be named or placed differently. Search for it )
I didn't try unmouting system and data, but I found twrp log. How can I send this log file to you?
Sent from my HM NOTE 1W using XDA Free mobile app
You can attach it to a reply, or you can use a service like pastebin and write the link here, or if it's short you can write it here directly.
Log from twrp
udda90 said:
You can attach it to a reply, or you can use a service like pastebin and write the link here, or if it's short you can write it here directly.
Click to expand...
Click to collapse
Here is the log, I needed a PC to upload it.
Thanks
davorzilic said:
Here is the log, I needed a PC to upload it.
Thanks
Click to expand...
Click to collapse
OK I figured out. ZIP fails because of different partition layout between note 3G and note 4G (I tested on 4G), so it cannot mount /data and /system properly. I am writing a new ZIP that should work for you, will be ready in minutes please stay here!
If it works for you I will replace it in the first post.
Updated ZIP
@davorzilic try that. Let me know if it works!
Just to be sure, first unmount data and system.
Thanks, I will try as soon as possible. I wasn't be online since yesterday.
Sent from my HM NOTE 1W using XDA Free mobile app
---------- Post added at 11:34 AM ---------- Previous post was at 10:40 AM ----------
Still the same error message. But maybe I don't know how to unmount data and system. Twrp only give me option to mount not to unmount. I just unchecked the system and data.
Sent from my HM NOTE 1W using XDA Free mobile app
Yes that's the correct way to unmount. Please could you send me again your recovery.log? It would give me useful directions.
This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk