Related
I'm not allowed to post in the Development forum, so I will ask my question here:
I updated to ICS successfully by changing the update-script in the update.zip.
I removed the lines which delete the recovery or reinstall it; I deleted the whole recovery folder as well.
But now I can't get back into CWM, it just doesn't start, it stops during "booting into recovery kernel" ( it was not overwritten).
So, is the ICS update changing so much in the system that CWM stops working? (through google I found something about different kernels, but didn't understand it)
I think I'll try to install the original recovery, better than nothing.
(this may also be a warning to people who think that they can roll back to honeycomb with CMW - apparently, once the update was succesfull that's it with honycomb)
daniel
I think it might have to do with the updated bootloader that comes with the ICS OTA.
I just had a look at the "blob"-file in the update.zip and was able to unpack it with the BlobTools for the Asus Transformer (https://github.com/AndroidRoot/BlobTools). Inside it was an EBT-file, which, according to my research, should be an image for the bootloader.
Looking through the strings in the blob, it seems to be one indeed: "Bootloader Start at:%d ms".
So I guess the new bootloader loads the recovery system from a different address or partition than the HC bootloader, which is why CWM won't start.
So adding the lines for flashing the OTA recovery-from-boot.p to the updater-script and re-running the update over HC should theoretically solve the issue. Or, if that doesn't work, flash the recovery image manually and flash the blob via nvflash (I'm not sure, though, if that is possible without the keys).
Maybe then someone with enough reverse-engineering skills could determine what has changed in the update and patch CWM accordingly...
Similar Issue..
In CWM, from [ROM][JB] CM10 for Ideapad K1 [Updated 8/29] (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Any thoughts?
It will work again. Just find the file "k1recovery" from the system/bin folder of a rom that has it. Push it in the device, fix permissions and execute it using ADB. The combination Power Btn & VOL+ doesn't work on some devices.
Time to get the Nook HD+ rolling on Kitkat! XDA forum member succulent (aka Iamafanof) has given me permission to post a link to his blog with all the necessary info that you need, plus the all important links to download his CM11 4.4.2 roms.
I had previously been running his CM 10.2 builds with sgt7 and they were great. Now, been running his CM11 builds since 12/16 and they are very functional and run extremely well.
It is highly recommended that you read over his blog to get the info you need to properly flash it. It's likely that your current recovery, be it CWM or TWRP will be unable to flash 4.4. You can try and if it fails, download the zip recoveries for either CWM 6.0.4.5.x or TWRP 2.6.3.0 on succulent's website listed below. Succulent recommends CWM but I've had great success with both of them. If you have a problem flashing the recovery zip, extract the image file from the zip and flash either through ADB or the PS app flashify from within your OS. EDIT: You do need to update your recovery to one of the above-mentioned recoveries.
Note: succulent's 4.4 builds are scripted to automatically install CWM 6.0.4.5b when installing the rom. But, the catch-22 is that you need to already have CWM 6.0.4.5.x or TWRP 2.6.3.0 to install 4.4 roms. EDIT 01/14/14: Currently, succulent's builds are now scripted to automatically install TWRP 2.6.3.0 instead of CWM 6.0.4.5b.
New TWRP 2.6.3.0 and CWM 6.0.4.5.x recoveries: http://goo.im/devs/succulent/ovation/recovery If you choose CWM, 6.0.4.5b is preferred as it supports both internal and ext sdcard.
Needless to say, make a nandoid backup before proceeding and if you're not comfortable doing this...DON'T!
Link to succulent's blogsite with download links: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/
Note: There are two different builds, one for internal (eMMc) and one for sdcard, be sure to download and install the correct one. I am using the eMMc build,so I don't have any knowledge of how the sdcard build is working.
Additional link to succulent's rom builds on Goo: http://goo.im/devs/succulent/ovation/cyanogenmod/internal
On the Goo site, he also has his CM 10.2 builds that might be of interest to some of you. Note: His CM10.2 rom builds automatically install TWRP 2.6.3.0.
You must use KitKat 4.4 gapps. A gapps link is provided on succulent's blog site. Either use those gapps or the PA zero day gapps linked below. If you are going to use ART, it's recommended that you do use the PA zero day gapps for best compatibility. If you don't know what ART runtime is, google it!
All credit for the rom builds, as well as the new recovery images goes to succulent (aka Iamafanof). I am just spreading the news so we can all finally have KitKat on our devices.
EDIT: Just a reminder regarding the newer recoveries, CWM 6.0.4.5.x and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify. Play Store link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Google may decide ART isn't feasible and dump it going forward.
Note: Not all gapps packages are ART compatible, at this time it is probably best to use the Paranoid Android zero day gapps. Link for PA gapps: http://forum.xda-developers.com/showthread.php?t=2397942 Be sure to choose the current 4.4 gapps.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. , I found that it generally takes a while to "settle in" and should become more fluid/speedier over time.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
EDIT: Hey guys, just posting as new stuff comes up. Here's another possible alternative for those that may have a problem with either of the internal recoveries. XDA member sandsofmyst has put together a bootable TWRP 2.6.3.0 sdcard installer. If you use it, please post your results here and don't forget to give sandsofmyst a thanks click.
http://forum.xda-developers.com/showthread.php?p=48549135#post48549135
Enjoy!
Mike T
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
supergroverthm said:
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
Click to expand...
Click to collapse
Good tip and we always learn by trying. :laugh: I already had TWRP 2.6.3.0 from a previous rom, so my install of 4.4 was quick and painless. LOL
If you haven't already, hook this baby up with Xposed module by rovo89. Some really cool extra features without bogging things down with stuff you don't want or need.
Mike T
Oohh, I'm very very interested in this. Kept saying about memory optimizations for lower end device, have you noticed much performance differences? Pretty stable? Bluetooth, hdmi and everything work?
Sent from my HTC One using Tapatalk
Wow. Just wow
So now that you built it, can we expect it to become an official release soonish?
Thanks a lot for your work!
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
superanima said:
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
Click to expand...
Click to collapse
Well, I looked in the Language+input section under settings and Italiano (Italia) and Italiano (Svizzera) are in there. I was able to switch to them and then...not be able to read anything so I'm assuming it's right. haha. Going into the Play Store all of the app names are still english but their descriptions changed so, it seems like it mostly works. I believe language support is an app-to-app basis though, so if the app developer didn't include Italian tranlations then it's going to be in English or whatever native language the App is in. I'm not totally sure how the language support works. Maybe someone else with more info can fill in my blanks.
On to this ROM as a whole, I've been playing with it, coming from CarbonRom 10.2 and haven't noticed much difference but I dig it none-the-less. I've tested Bluetooth headphones and my HDMI adapter and both work just fine. If anyone is wanting me to test anything let me know.
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
aedgington said:
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Wow, I have 342mb RAM Aavailable with GAPPS installed according to cool tool!
I've enabled ART and its showing on dev options. What's the deal with this new method? Is it better, faster, etc?
felacio said:
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Click to expand...
Click to collapse
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
aedgington said:
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
Click to expand...
Click to collapse
Mine is showing ART in dev option after reboot...
supergroverthm said:
Mine is showing ART in dev option after reboot...
Click to expand...
Click to collapse
Have you noticed any difference between ART and Dalvik?
aedgington;4872557[LEFT said:
[/LEFT]0]Have you noticed any difference between ART and Dalvik?
Click to expand...
Click to collapse
Only that more RAM is available. Now showing 390mb RAM available.
Flashing CWM
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
EDIT: This doesn't work... flash_image seems to be scanning for some partition that's not available:
"error scanning partitions: No such file or directory"
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Nook HD Kitkat
chili81 said:
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I placed the files on my internal SDCard/Download and TWRP could see them and I installed.
Went here to get the zip file http://www.mediafire.com/download/c32pw4qf1l9a0mu/flash_recovery_TWRP_2.6.3.0_internal.zip
After installing the new TWRP and reboot I reset the old ROM then installed the new ROM and GAPPS.
norm883
That did the trick, thanks... I was thinking the older CWM would have same problem updating to newer CWM as it would KitKat.
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Decided to put some extra notes here for those that only read the last page. Also put this in the OP.
Just a reminder regarding the newer recoveries, CWM 6.0.4.5 and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. You should be reading his blog info anyway, so just scroll untill you see the links for those recoveries. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify right from within you current OS, ie; CM10.2 etc.
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Also, Google may decide ART isn't feasible and dump it going forward.
A couple of things to note, not all gapps packages are ART compatible, the gapps I linked from 1209 do work, I'm not sure about the ones linked on succulent's blogsite from 1208. I believe the PA zero day gapps are also ART compatible.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. I found that it generally takes a while to "settle in" and should become more fluid/speedier overtime.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
Mike T
FirePsych said:
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Click to expand...
Click to collapse
CWM and TWRP backups are not compatible, probably never will be unless some third party dev figures something out.
Mike T
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
some news...
some news... i have successfuly install TWRP and maked a backup of system/data/boot if anyone want to play with backup or try to flash it i can upload it (it's a 5gb folder, tell me wich file hosting you want)
i have try after backup to flash the CM rom and some Flyme but i have always the same error: "could not find 'meta-inf/com/google/android/update-binary' in the zip file"
Any suggestion?
ps: if anyone has a TWRP backup of his pro 5 i can try to restore on my...
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Toroman said:
Hi,
I also got my Meizu Pro 5 Ubuntu Edition a couple of days ago, and even I expected it to be not-so-polished, I couldn't believe the number of features missing and the number of unresolved bugs. Being a long-term Linux/Ubuntu user I will (from now on) closely watch the development process, but meanwhile I would like to use my new phone.
If you make it to flash Flyme, please share the full process.
It would be great if we could go back-and-forth Android/Ubuntu to check the progress from time to time (as Nexus can)
Click to expand...
Click to collapse
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
mobilezonerm said:
As we find someone that want share his TWRP backup, i think that a deep wipe and a restore from backup work...
Click to expand...
Click to collapse
In this thread there is a link:
http :// forum.xda-developers. com/meizu-pro-5/development/rom-cyanogenmod12-1-temasek-unofficial-t3358744
http :// xep.8800.org/ pro5/
But also on the Canonical site:
https ://wiki.ubuntu. com/Touch/ Devices
(Sorry for the spaces the policy doesn't allow me to post urls yet.)
I somehow thought that we can use official Flyme download from the Meizu website and the official Ubuntu turbo image without the need of installing TWRP or anything - and flash both via USB.
Functionality with TWRP would be a plus.
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Pleytos said:
Well I think you can. Press both Volume up + power button, that's the stock recovery where you can flash images from meizu. So you probably can get Flyme when you have Ubuntu, but when you want to go back I think you'll have to flash the ubuntu turbo recovery back through fastboot. I think you can go without TWRP.
Click to expand...
Click to collapse
Well the power + up gives (a kind of) recovery that shows a screen with the Ubuntu logo in the center - nothing else. I believe the android version has a different recovery?
Ah I never saw that screen. Yes Android/Flyme has a different screen: like this
You can try to to use the Ubuntu recovery to flash a Flyme Rom. I did it with TWRP, but never tried it with the Ubuntu recovery.
The Flyme Rom replaces the recovery and boots with both TWRP and the Flyme recovery, maybe even with a Ubuntu recovery (I can't image it to be that different.).
Edit:
You might want to back up your current recovery. I just flashed the recovery from Canonicals website, and its just the English/Chinese Flyme one.
just a moment... thank's Pleytos, but we need the TWRP backup folder... on yours link there are the CM rom and on the Canonica site there are only the update.zip....
Keep in mind, also the partitons are different on Pro 5 Ubuntu, for this the best is to have the entire backup of an android phone, both CM rom and Update.zip are not flashable by TWRP (i have try)
and Toroman the recovery that you see is the original recovery, if you flash the recovery on Canonical website you have the screen posted by Pleytos BUT with this recovery you obtain only the unlock of ADB in recovery and, as you can read from the screenshoot to make an update you have to put a "update.zip" on root directory of the phone that, unfortunally in ubuntu edition, is read-only file system... i have just unlock it from linux terminal with a "remount,rw" but if you try to copy update.zip (many versions) to root fonder there aren't space enough...
I've make lot of try in this day and i have find two possible solutions:
- flash a rom with MultiUpgrade 4.8.5 (official software used by Meizu, that not start because some token is missing)
as reported in a big russian forum
- make a total erase of internal memory and rewrite it with a image from android Pro 5 phone (TWRP Backup)
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
All done... guide in details:
- on windows install driver: Samsung_USB_Drivers_for_Mobile_Phones_1.5.9.0
- on linux: run from terminal "$ sudo add-apt-repository ppa:ubuntu-sdk-team/ppa" and "$ sudo apt-get install phablet-tools"
- download from here (http://people.canonical.com/~plars/touch/recovery-turbo.img) the recovery image with unlocked ADB
- turn off the phone and turn on with volume down pressed to enter in fastboot mode
- in windows go to the folder where you have fastboot / in linux open the terminal and give "sudo -s"
- make a flash of recovery (fastboot flash recovery recovery-turbo.img)
- now download the TWRP recovery (i've used the 3.0.0 on this forum) and from terminal flash it (fastboot flash recovery "nomerecovery")
- now you have to copy first a CM rom on the phone or sd, before flash the CM rom erase completely the system partition, flash it whit TWRP and only after you are able to flash Flyme rom
keep in mind to make a full backup by TWRP and save it on external archive before operate. (it's less complicate for future restore and help you if something goes wrong)
if someone need the backup of Ubuntu for his phone, ask me...
Ubuntu Dump
mobilezonerm said:
if someone need the backup of Ubuntu for his phone, ask me...
Click to expand...
Click to collapse
Hello, can you provide me full Ubuntu dump? Im very interesting to install native Ubuntu touch on Meizu Pro 5. Share the link, for example, on Mega or Google Drive
Need you help
mobilezonerm said:
Hi, i have from a couple of day the ubuntu edition of pro 5, for various reason i want to run android on it and also make an image of system to give the opportunity for android users to get the ubuntu experience... any help?
- i have flashed the recovery from canonical (recovery-turbo) with unlocked ADB
- i can access to fastboot and to adb trough recovery
- i have make a map of partitions (ls -al /dev/block/platform/*/by-name)
- i have try to copy the system to sd card ( dd if=/dev/block/sda41 <--- system partition of=/media/F49C-xxxx <--- my sdcard) but it not find the sd
- on the side of android flash i think that the procedure on this post maybe ok http://forum.xda-developers.com/show...53&postcount=3 but the software (MultiUpgrade 4.8.5) fail to start
- ever for android flash, i have also think to put a complete update.zip to the root of device but the / folder is read only system.
Any help for both purpose are welcome
Click to expand...
Click to collapse
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
mobilezonerm said:
Pleytos, one answer, wich room have you flash via TWRP? (both Ciano and Flyme, wich version)
Click to expand...
Click to collapse
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
tamyou2020 said:
can any one help me remotely to install android on miuze pro 5 which coming with Ubuntu , i download every thing but lost with steps, or can you provide clear steps so i can follow
Click to expand...
Click to collapse
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Hi , Am running Ubuntu over windows ( virtual box ) we can go with team viewer , or if you want i can install Ubuntu in separate machine , Please let me know how we can communicate
Pleytos said:
Hi! I flashed CyanogenMod 12.1 from Faust93, AICP 12.1 Rom from Faust93, and Flyme 5.1.6.0G & Flyme 5.1.5.0G via TWRP, It worked for me. I haven't been able to go back to Ubuntu though. Ubuntu-device flash doesn't work for me.
I can also flash Flyme with the standard recovery/ Canonical recovery by putting it on /sdcard/
Yes I can help you, are you running Ubuntu on your PC or Windows?
Before flashing Android, could you maybe help me with getting some Ubuntu files back? I can also help you through a chat or something if that is easier. Never mind I finally did it!I can still help you though, if you need me
Click to expand...
Click to collapse
Hi,
I've been away for some time, and I can see some nice progress in making Android work on the Ubuntu edition.
I might be repeating myself but it would be ideal if we (who own the Ubuntu edition) can go back and forth seamlessly. Unfortunately my flashing skills are buried in the ancient time of the HTC HD2 so I need some assistance (as probably more of us do). Here are some questions, I appreciate the effort and the help (assume I'm using Ubuntu on the desktop) (if something is easier in windows - please note). This would be a full circle:
1 Is it possible and how to make a COMPLETE backup of the Ubuntu edition phone (including the recovery and everything) to be able to get back to the factory condition (and using what tools/steps). I think I have read somewhere that OTA updates does not work with custom recovery or something similar.
2 after making the backup from question 1 - assume flashing official flyme to make it like a factory android device. (orig.recovery, OTA and so)
3 flash ubuntu back using backup provided with one.
I guess the ubuntu edition has the bootloader unlocked factory default.
Info on flashing CM or similar can than be like flashing it on original android - assuming (2) is working
As already said, just a remainder - Ubuntu recovery screen that came with the original phone is just ubuntu logo on the center on the screen - I don't know if it is important for any feature (OTA or something)
Best regards!
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Toroman said:
Also, looking around I have found this - seems interesting also
https://wiki.ubuntu.com/Touch/DualBootInstallation
Click to expand...
Click to collapse
Actually this is most interesting! I would love to buy this phone, ubuntu edition. But since it would be my primary device and ubuntu touch not quite there yet, I'm not. That page about dual boot seems outdated though. And it is about nexus devices
Being able to have dual boot with android or even as someone said above have a back up and every 2 months restore ubuntu and check the progress would be great.
Alas with the upcoming Update, on Monday I find myself in a plexing place on how to reinstall SuperSU once more via a TRWP that just terminates on a Black Screen on my 4k TV.
I had thought to try patching though my Computer Monitor via a HDMI to DVI Connector. And, allthough it does work well enough once fully booted. There is not a chance in Hell of it liting up for TWRP, or even the Bootloader for that matter.
While TWRP may we'll be the best recovery I was wondering if anyone has ever bothered to port a different Recovery to the Shield (e.g. Philz, ClockworkMod etc..)
Just as an aside would any of these other Recoveries suffer from the same bug? It would be a PItA if I had to wait a week before I went to visit my Old Man just to go though the motion (and embarrassment), of having to flash SuperSU on his FHD TV again.
While this doesn't exactly answer your question, TWRP does have a CLI. Once installed and in TWRP recovery, and connected via ADB, I believe all you have to do is issue the TWRP command to see it's listing of features and other commands. I've flashed su and other .zips to my shield this way a few times.
Here's the relevant link and documentation.
https://test.twrp.me/doc/openrecoveryscript.html
So, example would be
adb shell
twrp install /sdcard/SuperSU.zip
Are those commands to be sent via ADB, or Fastboot, or something totally other again?
~crap... I spent way to much time trying to fix the Old Man's GPS (WinCE) Device. I can't read any more lol.
Ok I think I managed to get as far as ...
Code:
# twrp install /sdcard/SuperSU.zip
TWRP does not appear to be running. Waiting for TWRP to start . . .
I can only suspect that it's hanging on the Permissions change Switch that you have to swipe though before actually getting into TRWP.
It may or may not be helping that I'm also loading TWRP off of the /sdcard/ instead of bricking my recovery fully by installing it outright.
NOT that it would kill the Shield off or anything as drastic as this. But I doubt I'll ever see the recovery again. Lol to heck with 4k!
Ok so I went back and, actually installed TWRP as the Shield's Recovery. And now it's working. So if I have to reinstall SuperSU, as I suspect I'll will after tomorrow's Update to Nougat. Then I should hopefully be able to reinstall SuperSU though the ADB Shell (as above)...
Again thank you kindly a signed a 4k'er!
First off I am not criticizing the amazing XDA developers here, and all the people that help make root and ROM's happen.
This is aimed at Essential the company themselves
I was under the impression the Essential Phone was sort of like a Pixel, or Nexus, or OnePlus type of phone. Meaning running a near stock Android OS, an unlocked device, easily rooted. For example when a new OnePlus phone is released, root is out super fast. But the reason the Essential Phone has not been rooted yet is because of Essential holding back the factory images on us still. I guess I have to ask why would Essential do this ? I thought they touted this phone as a open platform, very similar in idea to the old Nexus line ?
The Essential Phone has been out 2 months now, and the important files for rooting still have not been officially released to the public yet ? What's up with Essential holding back so long ?
https://ibb.co/mgaVcb Mine ist rooted
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Last I read was the boot image that was pulled didn't enable root with magisk and hadn't seen anything more from it. Did you have to do anything specifically?
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Interedasting.
It'd be great if you could provide further proof/instructions.
Thanks a bunch.
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either.
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
*Found the thread here:
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583
kchino said:
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either. Maybe it was a Larp ¯\_(ツ)_/¯
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
Click to expand...
Click to collapse
Pretty sure the staff that did the AMA was just the design staff, not software staff. As soon as the files are released it will take about a day I bet for root. I remember seeing a thread on reddit that you are referring to as well. I think the people who can root it won't until the files are released. One **** up and they have a very expensive brick.
Thanks for the replies. So any idea as to when this source code image files will get released from Essential ? What's their holdup ?
Agreed, dicey proposition with no factory images.
We have devs working on it. Root has been achieved and there's a TWRP build but the touchscreen doesn't work you have to use a mouse to navigate. Also, there's no factory images yet to go back to stock in case of a problem. Once they iron out the issues I'm sure someone will release a guide.
Currently on the Nexus 6P, that's getting bad. I really want the Essential phone, but only if root comes out for sure, also ROM's would be great.
Otherwise I may just wait for the OnePlus 5T announcement, and if it's $500 go that route instead. At least the 5T will have good development
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Man how did u root?? I really wanna root
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Can you provide the file for TWRP and boot img?
drocny87 said:
Can you provide the file for TWRP and boot img?
Click to expand...
Click to collapse
Just join the Discord Server and load it from there.
Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Thanks
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Z-Fire821 said:
Just join the Discord Server and load it from there.
Click to expand...
Click to collapse
What's the link to it?
ROOT
Guys, if you truly, truly want to root your device, follow these steps. Just remember, I am not responsible if you end up bricking your device (and neither are the main developers currently working on TWRP and Lineage). YOU ARE RESPONSIBLE FOR WHAT YOU DO ON YOUR OWN DEVICE! (also this probably voids warranty btw)
THESE INSTRUCTIONS ARE FOR NMJ20D.
Now, one more thing. Remember, this TWRP build is very much in alpha stages and there are some major bugs with it, including no touch support and no crypto. Also, when I rooted, I had to use my USB OTG Mouse in order to maneuver around TWRP, but with this method, hopefully anyone can do it, without the mouse. The boot.img I will provide is the NMJ20D boot.img with the patches that Magisk puts in when you install it, so it's not exactly stock. Also, you might need to factory reset your device via the stock recovery (and make sure not to boot it back up until after you flash Magisk) just in case, since TWRP is buggy with crypto atm.
You can find a dump of NMJ20D here, in case you need to fix a bootloop (due to a bad Substratum theme, etc...) -- (you'll likely need only boot_a.img and system_a.img (within the system_a.zip).
If you wish to return to stock in order to accept OTAs, feel free to flash the unofficial factory images here and, should OTAs still fail, you may be required to wipe your data, which can be done via "fastboot -w". (Side Note: I believe the script included within the unofficial factory images also flashes the firmware to both partitions, so if your fingerprint sensor is seemingly absent or not working, this might actually fix it, as it has for some custom ROMs on the Essential.
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course, your bootloader must be unlocked.
1. Reboot your Essential into fastboot mode. Once in fastboot mode, flash TWRP via
Code:
fastboot flash boot twrp-mata.img
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type
Code:
adb shell twrp sideload
and then
Code:
adb sideload magisk.zip
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
Code:
fastboot flash boot boot_a.img
4. Now reboot! You should now have root and stuff via Magisk!
Appreciate the root guide, guess I can pick one of these up now to play around with. Awesome!!
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk![/QUOTE]
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
shooterlgk said:
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk!
Click to expand...
Click to collapse
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..[/QUOTE]
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?
bmg1001 said:
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
Click to expand...
Click to collapse
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?[/QUOTE]
I should of took a picture cuz I can't remember but it does give me an error tho ..I'm gonna retry when I get home from work but I literally sat there for almost 3 hours attempting to root to no success