Related
Hi,
I got a GTablet for Christmas today and I seem to have had some bad luck with it...
When I first got the tablet, it wouldn't keep any of my settings (not the wifi connection, not the development settings, nothing).
I thought I could get around this by flashing a different image (I am a novice user, though I do have a very modded N1 -- except it's still stock, sort of).
So... I did not have a MicroSD card at all (it's Christmas, all the places are closed until Monday, and I did not anticipate any problems). Still, I was able to flash the image of TNT Lite...Sort of. I had no problems upon booting, with the familiar N1 X boot animation.
I could add things to the stock Android launcher included with TNT Lite, but not remove them (as soon as I sled the icon I wanted to remove over to the 'trashcan', it force-closed the launcher, but my icon was removed nonetheless).
I did have a slightly working Market (I had the half-star issue). I did not have Titanium Backup installed, so I attempted to restore a working Market by force-closing and clearing the data of the 'Google Services Framework' and 'Market' services... Didn't work, like I thought, so I then tried to sideload Titanium Backup.
There is where my big, big problem came up. As soon as I tried to load TB onto my GTablet, I had tons of Force-Closes (and the tablet sort-of half rebooted). So, I got them to go away and tried again. Same thing.
So, I gave up and vowed to try again tomorrow. Except, I might not be able to tomorrow... As soon as I turned the tablet off, all was A-Okay for the most part... Later, I thought I'd try a little earlier than tomorrow, so when I turned it on.... I didn't get any farther than the GTablet logo before I realized I was in an infinite boot loop.
Now, I'm stuck with a boot-looping GTablet and a not working Christmas present! Help, please.
EDIT @ 3:44AM (Dec 29, 2010)- [FIXED]
FIXED!
When you get an sdcard you can do a fresh install from the external sdcard.
Yeah, I know that.
I don't know if I'll be able to rescue it or not (like I said, I'm new to this, and I was under the impression that [Power]+[Volume-UP] meant 'load recovery mode' which would look like the one I use on my Nexus One).
Do you think I should try (if I can get out of the infini-boot) flashing to TNT Lite (the latest, I think 3.1.0.1 or something similar)?
I'm wary of flashing to that one again, since it seems to have some serious problems with my particular tablet (I searched and there were no similar problems to mine that I could find).
I don't know if I'll be able to sideload Titanium Backup, are there any alternatives to that in getting a working Market (I tried anything else I could think of, but nothing was ever able to sideload onto my Tablet, ever)?
Have you installed Clockworkmod recovery?
Read the main threads (tnt lite, vegan, installing gapps) and I believe you will find someone has had the same problems you have
Hi there! I got the MicroSD card today.
So, I was looking through the guide I had previously used (http://forum.xda-developers.com/showthread.php?t=842004) and now I'm going to try to install ClockWork Mod recovery .8 (the one they said works best here).
I will update this (or maybe make a new message if you don't mind, if I can't edit my posts) if I can successfully get it working.
EDIT @ 12:47AM (Dec 29, 2010)- [Downloading the recovery mod file]
I downloaded the 'gtab-cwm-v08.zip' file to my MicroSD card, and extracted the 'update.zip' and 'recovery' folders inside (I imagine that is correct).
Then, took it out of the computer and loaded it onto my GTablet. I turned it on and did the recovery combination with [Power]/[Volume-UP].
It gave the screen that said it was loading the image and then another screen (black with 'ANDROID' and some other text on the screen).
For just a second, an error-type screen flashed on the screen (big warning icon, not sure how to describe it, but there was no text nor a loading bar).
Then, it rebooted (and then again and again, so it's not fixed yet).
Not sure what I did wrong... <
EDIT @ 1:43AM (Same Day)- [Installing recovery/Fixing boot loop]
Successfully installed Clockwork Mod Recovery .8 after downloading a 'command' file from my ROM's .rar (I modified the file so that it'll say <load-info>sdcard2<load-info> instead of <load-info>sdcard<load-info>).
Repartitioned to 2048 and 0 for the memory settings.
EDIT @ 1:55AM (Same Day) [Boot loop fixed, now just trying to figure out what to do next]
Repartitioning to 2048 and 0 in the memory fixed the boot loop. Yes!
Now, I don't know exactly what to do next... This one is still in progress right now.
Sounds like you did it right. Where you got the Clockwork file may make a difference though. There are 2 of them out there. One is from a thread that has it setup to load from an external sdcard. The other from the internal. Quick way to see what you have is to open the command file inside the recovery folder and see if it says sdcard, or sdcard2. You want it to point at whatever method you are using to load it. Sdcard for internal, sdcard2 for an external card.
If you haven't tried it already, look at this.
After that just load the rom you want.
Beware though, you may have a strange model that won't work with that, some have been floating around..... Read the full thread too
This may also be useful to you: http://forum.xda-developers.com/showthread.php?t=842000
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
By the way... To address your initial issue of being in a boot loop. Get clockwork installed. Once installed go to advanced, partition sdcard. Use 2048, and 0 for the swap. That will get rid of the boot loop.
XANAVirus said:
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
Click to expand...
Click to collapse
You can find one in most any of the roms. The earlier TnT roms had them, others too...
They are all the same except for the sdcard, or sdcard2 thing I talked about so don't worry about finding a specific one.
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
XANAVirus said:
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
Click to expand...
Click to collapse
Nope. Once it is installed you don't need the sdcard anymore. Be sure to read my post a couple above this about fixing your boot loop.
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
XANAVirus said:
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
Click to expand...
Click to collapse
Reboot and see where you are... It should go back to where you were before you got the boot loop. The stuff on your internal sdcard will be gone though. So I hope there wasn't anything important there.
BTW, you can hit the back button on the side of your screen to go backwards in the clockwork menus.
Nothing important. I haven't even installed anything new or changed any new settings on my current ROM (that TNT-Lite).
I'm rebooting it right now as I type this.
EDIT @ 1:58AM (Same Day)-
Your steps fixed my boot looping problem. Thanks!
Now, I don't know what next to do. I don't have Titanium Backup installed (couldn't sideload it, I kept having problems).
I don't know if the Market is fixed yet.
Did it boot?
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Yes, thanks!
Awesome! Now I would boot back into clockwork and make a backup. You can rename them from a file manager too so they make sense..
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
I don't ever use titanium to do the market fix. I just use it to backup apps.
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Okay, I made the backup like you asked. So, now should I try to fix the Market?
Is there anything else that needs tweaking?
Any advantage over one from the other
Sent from my GT-N8013 using xda app-developers app
I Rio Wonder about that
Sent from my GT-I9100 using xda premium
this will be interesting hearing everyone's imput ... tho its all based on personal preferenceim sure .. i like cwr
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
droidstyle said:
I have used both in the past and still prefer CWM....no reason other than its what I learned to use when i was a noob....now Im a noob veteran.
Click to expand...
Click to collapse
I will second this, I like them both, in fact I still use TWRP on my Nook Tablet, but I've been using Koush's stuff for so long, over 3 or 4 phones now, that it just seems natural for me to use CWM.
TWRP for me. Its much faster and has nice features.
I use to be a CWM fan, that was until I started using TWRP on my Rezound. From then on I use TWRP, but I don't mind good ole CWM every once in a while.
TWRP because it's faster and the UI is easier to use simply because the tiles are large.
I like Amon Ra best of all. Oopps...wrong thread LOL!. I use TWRP on my Bionic and CWM on the Galaxy. Like mentioned above, CWM is what I learned on and for some reason it feels like more hands on.
Let me say this. My friend was running CM10 all the way from like september. I tried updating it in CWM but it gave me assert errors. Reflash TWRP on it, and flash latest nightlies no problem. Dirty flash too, just wipe dalvik and cache.
There isn't an objective answer that I can give. I'm biased towards pretty much anything that is alternative to what everyone else is using. Also, I have no data that would indicate one recovery is better than another. So here's my purely subjective answer.
I prefer TWRP over CWMR for several subjective reasons:
Coming from the original Moto Droid on vzw, I ran RZrecovery (a moded version of SPrecovery, which had an OC'd kernel and lots of options as well as charging while in recovery way before I had seen it anywhere else). Basically, I'm not accustomed to CWMR.
I'm not a fan of the differential backups that CWMR defaults to. I know it takes up more space to have an IMG or TAR for each partition I choose, but I'm a crack flasher and go back and forth between TouchWiz and AOSP based roms all the time. I need to be able to keep my backups completely seperate. No blobs. I need a golden master for each ROM I flash. With a 64GB externeal SD card and a 32GB internal card, I rarely run out of space.
I can name backups while booted into TWRP before you create the backup. The whole date being wrong in every recovery thing is indeed annoying.
I like the terminal. I prefer to root, flash, hack, etc etc on my own without help from apps and or pre-built tools (except for dsixda's android kitchen, which is so bloody easy to use it blow my friggin mind). So I don't need or want ROM Manager to do much of anything for me. I even flash TWRP via the terminal. GooManager always runs in the background, and hasn't really ever had the most up to date versions of TWRP, so I ditched it pretty fast. I hate apps that run in the background when I'm not using them.
I like the look and feel of TWRP. Its feels like a teeny version of android with a small but very functional UI. Only thing missing is a terminal emulator that I could use from within TWRP itself. (Choosing a command file to run just isn't the same, but it has come in handy)
I also like having backups go to a folder that is labeled with the device's SN. Seems like a really fantastical feature in the making, like a cloud based storage for TWRP could be somewhere off in the future, where you could backup multiple devices to one online storage space.
Its the only "alternative" in town. I like "alternative" aka not so main stream stuff, which is odd cause I'm not a fan of Alt Rock. More of a Hendrix, Zepplin "classic rock" (aka blues based rock n roll with lots of riffs on the minor pentatonic scale) kind of person.
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Ta,
ALQI
alquimista said:
Um, I don't really have an 8th reason. But I would like an OC'd kernel in TWRP to help speed up backups, but I dunno how viable that is.
Click to expand...
Click to collapse
Tempting, but with backups/flashing/recovery, I think slow and steady wins the race.
I used to use cwm, but with the change to blobs all of my backups stopped working. Even ones I just made.
so I stopped trusting it.
I switched to twrp. The backups are larger I think, but I trust them more.
Sent from my SCH-I535 using xda app-developers app
Haven't had any problems with TWRP, and it was the first I used. So pretty much just became acquainted with it and haven't seen a reason to switch.
I use CRW on my phone and TWP on the Kindle Fire. The best advice I can give is use what ever method the dev tells you to use, if he goes out of his way to mention it there is probably a good reason behind it.
One thing about CRW I wish would get fixed is the file name date being wrong (When it saves a file it gives the file a name based on the date but all current versions save it with an incorrect date (it thinks its 1970 lol) If i dont change it right away I end up with a bunch of mystery backups.
Another thing to remember about the latest CRW's is the blob. To save space during the saving of a backup a file (blob) is created that has any redundant info shared by backups in it. So all the info for your latest backup file isn't all in the file with that backups name some or most of it is in the blob file. So if you want two or three backups from your phone saved to your home computer make sure you take the entire clockworkmod file because if you take just the individual CRW backup file (1970 -blah-blah-blah) you will be missing all the info on the blob. CRW will let you restore with the partial file and that can get ugly fast.
I've always used cwr but I will give twrp a shot, love trying new stuff. And the date issue with cwr is really annoying. I'm sure it could be renamed but I don't want to change anything and get an md5 mismatch.
Sent from my SCH-I535 using xda app-developers app
So I got a new Nexus 5 yesterday, its pretty neat and fast but I've run into a pickle, first thing I did after open it was to unlock it, then I mess up a little and had to reflash the factory image, then what I did was to flash recovery again and root it, after that I pushed a backup I had from the entire sdcard partition from my previous phone... Everything seems to be working great but... the camera seems to be working, I can see through the camera but when I take pictures, they aren't displaying in the gallery, I don't even know if they are being recorded, I can't even take pictures with other apps. I imagine it must has something to do with the permissions but I'm not sure how to fix it, can you guys help?
Soy_Filipo said:
So I got a new Nexus 5 yesterday, its pretty neat and fast but I've run into a pickle, first thing I did after open it was to unlock it, then I mess up a little and had to reflash the factory image, then what I did was to flash recovery again and root it, after that I pushed a backup I had from the entire sdcard partition from my previous phone... Everything seems to be working great but... the camera seems to be working, I can see through the camera but when I take pictures, they aren't displaying in the gallery, I don't even know if they are being recorded, I can't even take pictures with other apps. I imagine it must has something to do with the permissions but I'm not sure how to fix it, can you guys help?
Click to expand...
Click to collapse
You need to wipe the storage again, then when you say push, don't use adb in recovery as this will screw your permissions and even prevent things writing. You'll have to boot into android, connect as an MTP device and drag accross via windows that way,.
Hope this helps.
I would start over again and not copy the entire sdcard partition. I have no idea what your other phone was and even if it had all the right folders to begin with, let alone what the permissions are
Sent from my Nexus 5 using XDA Free mobile app
rootSU said:
You need to wipe the storage again, then when you say push, don't use adb in recovery as this will screw your permissions and even prevent things writing. You'll have to boot into android, connect as an MTP device and drag accross via windows that way,.
Hope this helps.
Click to expand...
Click to collapse
It did, thanks
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
I downloaded the very latest Magisk from git ( https://github.com/kantjer/MagiskFiles ) version 13.3-170812-zip & then removed the Magisk App-booted into recovery-flashed the Remove-Magisk zip-cleared cache-rebooted into recovery-flashed the new version & NOW I have Magisk working properly.
I thought I'd offer a newbie perspective on the big brother BLOX2 (Life One X2 4 gigs /64 gigs).
I was planning to use BLOX2 AutoRoot, but I couldn't make it work. It got as far as unlocking the bootloader, then just sat there doing nothing. Same thing for BLOX2 ToolKit. (I think both problems were caused by my computer, not the software.) So then I decided to do the unlock via ADB, then Flash TWRP f=and BLOX2 Core from an SD Card.
My laptop (Lenovo ideapad FLEX4 running Win 10 Home 64 bit) does not like to recognize my phone. When I open a command prompt window and type in 'ADB devices' (ENTER) the computer pops up a notice telling me "the last USB device you connected to this computer malfunctioned and Windows does not recognize it." ADB returns an ambiguous statement that "a list of devices is attached" (to what, I have no idea). NONETHELESS, when I got frustrated and ran "fastboot oem unlock" it unlocked my boot loader in less than 2 seconds. Go figure.
I had to install TWRP a couple-three times as well before it "took" and stayed even after a reboot to system. I remember reading in a guide to rooting the Blu R1HD (if memory serves) that one ought to reboot into recovery after each step in order to make sure that the original image does not overwrite the new one. Don't know if this is related, but I followed that dicta from that point on. Lucky for me, TWRP installed right-side-up.
As for installing BLOX2 Core, the hardest part of this was putting the file onto an SD card in such a way that TWRP would recognize it. After that I popped it into the phone, booted up, opened TWRP. I found the BLOX2 Core file, flashed it and sat back to watch the magic happen. Line upon line upon line of pretty little code bits rolling by -- and all of it in black! No angry red lines to be found anywhere! As someone who is so far much better at bricking phones than modding them, this was truly a lovely site.
After this, there was really nothing left for me to do but BACKUP EVERYTHING! First I did a TWRP backup. (I have not been able to convince Nandroid itself to function on demand. It works fine on a scheduled basis, but when I try to run it directly it runs for three seconds, announces it is finished, and presents me with a non-file.) Then I installed one of my favorite apps: Titanium Backup. I setup TB to backup all system data and user apps on a schedule, and then ran the first one directly.
In all the excitement, I had forgotten all about Magisk, but a few hours later I noticed an icon labeled "Magisk." I clicked on it just to see if it was actually installed or just sitting there to install if I wanted to. When I saw that it was indeed the installer I just shut it down and left it alone. I strongly suspect that it was SU-Magisk failing to play nice that led to my bricking my first BLOX2, so I wanted to research how to get rid of it safely. Well, before I could get anywhere on that, the system on my BLOX2 started acting weird in familiar ways. Apps that I had not opened started 'closing' suddenly -- each one flashing a popup at the bottom of the screen that immobilized the touch screen until it was dismissed. When my first BLOX2 started doing this I thought I must have gone overboard with one of the longer-battery-life (Xposed) modules. So I frantically started zeroing them out to stock. This didn't help and the slippery slope had been crossed.
With my second BLOX2 I was a bit better prepared. I immediately uninstalled MAGISK and frantically ran every utility I could think of to be sure that there were no bits and pieces left to irritate SU into killing my phone. Just to be on the safe side I reflashed the entire BLOX2 Core zip, then backed up the result with both Nandroid and TB. This was a couple days ago, and my phone seems content.
I know that the BLOX2 Core I am running is not technically a "custom" ROM, but it still runs noticeably more smoothly than the original. Right now Settings shows 3.6GB total Ram, with 2.1GB free, which means that it is using about 1.5GB with screen on but only background stuff running.
As to my laptop's refusal to see my phone, I think the problem is in my PC. I have had nothing but problems with SP Flash, ADB, and all the various Qualcom-related tools. I have tried QFIL, SN-Write, WRTool, and the like. Even MTK DroidTools gives a message that there is nothing connected to the computer, then freezes. Go figure.
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
debianmain1 said:
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
Click to expand...
Click to collapse
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Augieboo said:
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Click to expand...
Click to collapse
No prob...glad the info helps.
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
debianmain1 said:
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
Click to expand...
Click to collapse
vampirefo said:
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
Click to expand...
Click to collapse
Update
I see they use different twrps,.
vampirefo said:
Update
I see they use different twrps,.
Click to expand...
Click to collapse
You can get the Mini one on BLOX2.com
Just for anyone that can't find the TWRP for the Mini: https://drive.google.com/open?id=0B6h1RP64aWh0a1UyaUc2ZlNzQ1E
You guys are using very old roms join Yureka Black and tinno p7210 common group for new roms and discussions - http://t.me/yuyurekablack