Related
Im looking for the boot animation for OS 1.0. Can anyone help me out?
I'm Br1ck'd's guy who was looking for the boot animation for you over the weekend. The problem I'm running into is that every ROM I can find is in the *.nbh format, so there is no way I can actually go in and grab the information. However, I haven't given up, and if I do find a way I'll let you all know.
werd!
10char
Awesome man. Thanks alot.
Sent from my SGH-T959 using XDA App
OK, so you're hosed with your request. Apparently, the boot animation is locked until at least Cupcake. So I can get you the Cupcake boot animation no sweat. But when I flashed my G1 back down to stock 1.0 there is no way to run Super User on it. You have root access, however when running something like Terminal Emulator and type "SU" you'll still get permission denied errors even though you have root access. Lame, I know.
So for giggles, I adb pulled every file from the root of the phone. No dice. There is no animations, period. Even searching every friggin' *.png file, there is nothing there for the boot animation. I can flash a new boot animation to the phone, but all that does is mask the original one, which is hidden somewhere in the *.nbh file. However, either I am not smart enough, or there is no way to do it as of yet, but I cannot get into the *.nbh file, period.
So I figured "OK, I'll try an emulator". That also failed, as the earliest emulator I can find is the emulator for Cupcake. So I then tried to use the emulator to flash a different ROM, which failed because as it reboots it goes back to stock Cupcake. Which is lame (they should really have a save state or something).
The next step I tried was downloading an older version of the Android SDK. Again, nothing available to me until Cupcake. I could have possibly loaded it in Eclipse, but I don't have Eclipse and don't prefer to have Eclipse, and I doubt that it would have made a difference since searching every folder in the SDK packs turned up nothing. I even loaded the SDK packs on my Mac, just in case there was a different set of files. Nothing.
Since I'm still on 1.0 I did try to do an ADB Shell, but any command gives me permissions issues. It's probably because of the root issue with the stock image. I don't really know, I just know I can't do it.
So my final attempt was that I downloaded a *.nbh explorer for the Windows 7 phones, but it doesn't work because of the signing issues.
Ultimately, you're not going to be getting the boot animation from me. I've tried and failed Sorry man. Good luck though!
You mean the "Glowing Android" bootanimation?
I was looking for it a few weeks ago, and made my own with the resources in the 1.0 build.
It's 800x480, you might have to resize it to 320x480.
http://dl.dropbox.com/u/122255/GlowingAndroid.zip
I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.
do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?
I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.
Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.
Yeah, for some reason it was downloading 404 page...
I reuploaded it.
I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys
Last week I brought a Morotola Xoom on ebay, it had 4.0 installed but I wasn't that impressed with it having got used to stock 4.1 on my phone.
I came across the great guide at http://forum.xda-developers.com/showthread.php?t=1477024 and used this along with http://wiki.cyanogenmod.org/w/Install_CM_for_wingray to unlock, root and install cyanogenmod 10.1 on it.
It was mostly a stress free install (although I managed to miss renaming the stock files that the post says causes Stock Recovery to overwrite CWM but it seems to still work OK.
My issue now is that I don't seem to have all the Google apps. It has gmail but not maps or market. I assumed that gmail isn't part of cyanogenmod so the 'gapps-jb-20130812-signed' file has installed (I think that file is the correct version).
It's not too clear from the instructions they read to me that you install the main CM zip and then Google apps without needing to re-boot in between, is this correct? I've tried a completely fresh install and also wiping the cache partition but no luck. But have not tried re-booting after installing the CM then installing Google Apps in a second boot, worth a try I guess.
Am I just making a simple noob error here? Thanks in advance for any advice.
A update, I've just tried formatting and re-installing again, only this time allowing a reboot into android prior to trying to install Google apps. One thing I've learnt is that the gmail app is part of the base install. Installing google apps appears to go ok but upon rebooting they aren't there. My next test is to try yet another clean install and an old version of gapps (gapps-jb-20120719-signed).
Chris
Motorola Xoom issues with 'Motorola fast-boot' replacing 'clockwork-recovery'
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Hmm a fun morning, I've lost times now at how many times I've had to reroot it. I've managed to get the Google play store apk and have tried using that (in addition to installing the gapps zip) it is loading but complaining of no network connection.
With regard to renaming the files ' /system/recovery-from-boot.p' and 'system/etc/install-recovery.sh' I've not managed this, when the tablet reboots into clockwork recordery its connection with adb is dropped. I've also tried doing them in terminal when booted and they don't seem to be there.
There doesn't seem to be anyone else commenting on this so I'll just plod along blindly :silly:
c_dunne said:
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Click to expand...
Click to collapse
Well, I'm with this problem too. I'm trying to solve this problem by myself, but no success at all. It do FC on google play every time it try to update. Every Google App (besides GMail) is doing FC with this CM build.
I tried to:
- Reinstall google apps
- Install another version (compatible with Android 4.2.2)
- Do the wipes again
- Install google play from an outside source (it doen't come with it).
But no success.
Any ideas?
miraidensetsu sorry for my delay in responding, I'm surprised that no other responses to this tread have been made. An update I've now resorted back to the stable release cm-10.0.0. Given it's nearly a year old I'd hope there'll be a stable release of 4.2 out soon.
Initially I had issues with the stock keyboard crashing all the time. But after searching about this I've installed the Google keyboard app and disabled the stock one.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms
I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method
Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRomsI did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method
Click to expand...
Click to collapse
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
I just finished installing UBtouch, without any problem
Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRomsI did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method
Click to expand...
Click to collapse
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.
Arthur Mateo said:
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.
Click to expand...
Click to collapse
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart
Zarosky said:
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart
Click to expand...
Click to collapse
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.
Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!
Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.
Arthur Mateo said:
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.
Click to expand...
Click to collapse
Arthur Mateo said:
Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.
Click to expand...
Click to collapse
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
In the device it looks like this:
Yeah, I think it goes back to Ubuntu Recovery Interfaces
Sanizol said:
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!
Click to expand...
Click to collapse
Hello bro, did you succeed ？
Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRomsI did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method
Click to expand...
Click to collapse
Have you ever encountered such a situation?
Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
Upon finally trying again, this is the error that I was getting. This occurs whilst the phone has booted to the ubports recovery menu but obviously files are still being pushed.
Do you mean you cleared the linux cache on the PC?
xxdgagag said:
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
View attachment 5575483
In the device it looks like this:
View attachment 5575485
Yeah, I think it goes back to Ubuntu Recovery Interfaces
Click to expand...
Click to collapse
Hi, I did not succeed, no. Mine gets to the stage of displaying that screen but I'm not sure if yours gets further or not as far. Mine seems to make a big deal about copying this one file and ultimately always fails. Yours seems to say it boots to recovery and then stops, though I find it difficult to read what it says on your screenshot because it is low resolution.
Did you succeed in the end by any chance since you last posted?
is there a way to install Ubuntu touch manually? Like using twrp for example.
For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)
Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards
walidham said:
Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards
Click to expand...
Click to collapse
Ok. Good Luck! It seems like you were working on it until quite recently though by the repository. Thank you for all the time you have invested so far!
Magzk said:
For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)
Click to expand...
Click to collapse
Thank you. I will try this out soon. I perhaps mistakenly assumed I would get away with just using sudo.