Related
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows
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
begonia (Xiaomi Redmi Note 8 Pro), MIUI 11.0.6.0
I had an unfortunate series of events that resulted in a booloop. Basically:
- Magisk suddenly stopped working one day, after 1.5 year of no issues. I did nothing related to it recently, except just using root functionalities in e.g. Tasker
- I flashed newer Magik 23 and also updated TWRP fom 3.3.1 to 3.5.2
- everything worked fine up until one restart, which resulted in TWRP encryption problems. Right before restart I'm pretty sure I installed Viper4android. I could still get into system with a workaround of TWRP's "Decrypt user" hanging into button reboot, but Magisk/root wasn't working anymore
- so I thought reflashing Magisk and dm-verity/forceencrypt would help, but here's where the bootloops started. During the flash attempts I saw some partition mounting errors since the device was decrypted, so maybe that caused some data issues?
I tried now:
- downgrading TWRP to 3.3.1 - decryption works fine in it and I can flash problemlessly from it, however, doesn't help with bootloop. Reflashing Magisk/dm-verity zips from it also didn't help
- flashing recovery ROM (the same MIUI I had - 11.0.6.0) changed nothing
- flashing fastboot ROM in MiFlash with "save user data" option changed nothing, except I guess confirming the issue is with data
- last thing I tried was flashing uninstall.zip for Magisk since that removed its data folders, which I thought may have got corruped, also to no avail
I know it would probably get fixed with data wipe, but I need the data - I have hundreds of apps with lots of configuration for permissions, notiications, etc. and my recent backups from few months ago vanished because SD card got lost. I have a TWRP 3.3.1 backup of the data now, too bad I didn't do it before updating Magisk/TWRP - lesson learned... So the question is - what can I still do to further debug and fix this without losing data?
I read that reading these logs may also help with debugging, but not sure what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
Please help
Bump. Any help would be appreciated
Plug in the USB cable with the phone powered off. Then issue the commands
Code:
adb devices
adb wait-for-device
adb logcat
from your Windows CMD or Linux terminal: it will hang waiting for the device to come on-line, now power up the phone. The logcat should start scrolling off then.
While it's turned off:
Code:
$ adb devices
List of devices attached
mfaajbdu5s79pfhy unauthorized
If you `adb wait-for-device`, the cmd just waits and you can't enter next command.
`adb logcat`, if I skip the above, waits for device itself, but nothing happens, it just restarts to TWRP and the commands still hang. I can use logcat while in recovery though, that's what I did above
Ok, so I just went ahead and tried the following, too:
- made sure the TWRP data backup can get restored, just in case
- wiped data through TWRP, still the same (re)bootloop into TWRP. I tried both factory reset and advanced wipe with Dalvik/Data/ntenal Storage/Cache.
- so I tried reflashing 11.0.6.0 using MiFlash with that erasing data. That at least worked and phone boots after doing this, but unfotunately not what I'm looking it
- I then tried to get TWRP 3.3.1 back. I got into that and the usual rooting steps were invalid - recovery_fromboot ile was not present in system_root/system. Maybe that's not just present in downloadable ROMs? No clue, but doing the rest of required rooting steps - Magisk 23 install -> Close AVB (TWRP action) -> Remove dmverity (TWRP action) resulted this time in infinite type of bootloop, not sure why, waited for over 30 minutes
- so I reset into TWRP and tried flashing the dmverity zip that's from xda. And this is definitely what caused previous (re)bootloop as after flashing that its more or less the same time length before boot stops and restarts into TWRP. Now, weirdly, while installing this there was an error this time, saying that nvdata cannot be mounted
So I guess the problem before was with mounting nvdata? I see it's something related to phone's IMEI. How does it work exactly, is it somehow related to /data partition? Why wouldn't it mount? Why does it work with pure standard flashed ROM? Is it supposed to be empty when you look at it with TWRP's file manager? Could be something else but this is my only clue right now...
EDIT: oh, you can mount it in TWRP and that works fine, it's not empty. Not sure why that install scipt suddenly stated claiming it can't be mounted, by the end of log, though.
Completely no insights?
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
And bump
Let's try a bump again
And one more hopeful bump. I'm even willing to pay/donate for any useful insight that will lead to progress with this as my old backup phone is becoming unusable and I don't want to start setting up this one from scratch again.
One last bump before trying in a new topic.
TLDR: what's the best way to debug a bootloop? Do the logs above help or is there something else?
Destroy666x said:
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
Click to expand...
Click to collapse
Titanium backup is now broken, at least the recovery is now broken. You also are not allowed to start duplicate threads.
Titanium backup doesn't really help me anyways. And ok, I guess I'll keep bumping it then...
Can you access fastboot?
So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers
Re-flash Stock ROM.
Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.
Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer
what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?
No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.
you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com