yashsingh1/xdaforums huggingface dataset:
[Remix Ultratablet General] RemixOS_Jason:
As far major upgrades (ie. migration from Remix OS 1.0 > Remix OS 1.5 > Remix OS 2.0) we don't foresee one. However, as the below thread is trying to do, we're trying to figure out what bugs are affecting users out there so that we can work on an update that will improve your overall experiences.

http://xdaforums.com/remix/remix-ultratablet/notice-ultratablet-issues-bugs-t3493596#post69679734

Thus far, we're working on:

1. [MENTION=668326]tomlogan1[/MENTION]'s issues he shared with us through private message

2. including Android's Nov 1 and Nov 6 security patches that has a fix for the Linux "DirtyCow" issue

3. an audio stuttering issue that is happening for certain audio apps

If you'd like to contribute to the list of issues we're working on, please list them (along with your Remix OS version number) in the thread I shared above. Thanks.
[Remix Ultratablet General] 11wallace11:
Posted this in the wrong thread.

See post: http://xdaforums.com/showpost.php?p=69891866&postcount=19
[Remix Ultratablet General] dboyd1950:
remix problems
[Remix Ultratablet General] RemixOS_Jason:
Abandonment implies that we won't even put out fixes, which we're working actively on now based on the feedback that has been given us.

However, again, there is no way for Ultratablet to be upgraded to Remix OS based on Android versions higher than 5.1 (Lolipop). The chip in the Ultratablet is only supported up to Lolipop. There is nothing we can do about that since this is a decision that NVIDIA made for the Tegra 4 chipset. This decision is not something we have control over.

If you do load other versions of Android over Remix OS, the biggest issues are how it responds to keyboard & mouse and how it orientates apps.
[Remix Ultratablet General] apescivolo:
Upgrades and bug fixes
[Remix Ultratablet General] apescivolo:
You mentioned that there will be no further upgrades to the OS due to hardware restrictions. You also mentioned that you would upgrade the V2.0 software and provide bug fixes, etc. The Mini keeps getting V2.0 upgrades and bug fixes. Please can you provide an estimated time frame when the next upgrade for V2.0 will be released for the UltraTablet?
[Android Q&A, Help & Troubleshooting] jayXzMx:
I've Liquid X1 powered by MTK6592 (single Sim), Need help someone could made a SP flash tool Rom. have search all over the internet but cant found it. I have issues with bootloop and unable to boot in to recovery mode. :D

Thanks in Advance.
[Android Q&A, Help & Troubleshooting] jayXzMx:
please help
[Android Q&A, Help & Troubleshooting] zadako_70:
. .pls help us.. Same problem here..need stock rom for acer liquid x1 s53..
[Android Q&A, Help & Troubleshooting] jpunkz:
yes same problem , need firmware Acer x1 s53 for flashtool
[Android Q&A, Help & Troubleshooting] Nonta72:
Download link (direct link): http://global-download.acer.com/GDF...UID X1&Step3=S53&OS=A12&LC=en&BC=ACER&SC=PA_6

Source: http://technationbh.blogspot.com/2017/03/acer-liquid-x1-android-kitkat-444.html

Or you can just use Google Search!
[Android Q&A, Help & Troubleshooting] jpunkz:
i have search google but nothing ,

i just found recovery stock rom like the link you gave .

i think no one shared that stock rom , i think this device Acer x1 s53 is locked bootloader
[Android Q&A, Help & Troubleshooting] Nonta72:
Read above!
[Android Q&A, Help & Troubleshooting] jpunkz:
yes i've Read it
[Android Q&A, Help & Troubleshooting] Nonta72:
Did you try it?
[Android Q&A, Help & Troubleshooting] jpunkz:
that's link only for recovery stock rom, not for spflashtool i have download it
[Sony Xperia M4 Aqua] ILoveMobilePhones:
Hi people of XDA,

I'm looking forward to unlock my phone's bootloader, but unfortunately in the service menu, the status of my phone says "Bootloader Unlock Allowed=NO" :(

Is there any way to change the "NO" to a "YES"?

Additional informations:

My phone is SIMLOCKED to a carrier

I have the 16gb model (E2306)

I have already contacted Sony, but they can't do anything :(

Thank you very much!
[Sony Xperia M4 Aqua] depressed_:
I think u can not do anything.
[Sony Xperia M4 Aqua] JohnTheFarm3r:
No, you can't unlock it. There is no way to do that with Bootloder unlock allowed: NO.
[Sony Xperia M4 Aqua] Ryan-sv:
same for me, i have the e2303, is there a way to root it? or there's something we can do?
[Android Q&A, Help & Troubleshooting] hhjkkh10:
I accidently bricked my phone and i tried everything on XDA. So i basically wiped completely everything on my phone including all the advanced options in advanced wipe this includes internal storage, system and USB OTG and the rest(using teamwin recovery). Now my phone just comes up with the samsung galaxy s6 startup screen. I have tried to flash custom roms onto my device. However it still says that my phone has no OS on it. I recently figured out my potential build number too, as i before had no way of finding out.

NOTES: The only things i have access to are recovery mode and download mode. I have no backups.

Thankyou for your help :)
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Download the firmware for your variant of S6 and use Odin to install while in Download Mode. Tons of tutorials and information in the forums here for your phone.

If that's over your head, use Samsung's Smart Switch for PC and use the emergency recovery option.

I would recommend getting familiar with Odin though if you want to play with your phone. It's a great tool and will be able to fix most any issue like this.
[Android Q&A, Help & Troubleshooting] Train88:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process [MENTION=385842]be_vigilant[/MENTION] did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.

What you need:

*MMB29P factory image (although MTC20F also worked for someone).

Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip

*My nandroid backup (its stock MMB29P, decrypted and rooted)

https://www.androidfilehost.com/?fid=24686679545612465

*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)

https://dl.twrp.me/angler/

*Android SDK or at least platform-tools (for fastboot, adb, etc)

The Process:

1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)

2. Extract the nandroid backup - doesn't matter where, I'll explain later

3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image

4. Flash TWRP (fastboot flash recovery twrprecovery.img)

5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device

6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.

***you must mount data again in TWRP after doing this, or you will not be able to see anything***

7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)

8. Restore my nandroid and try to boot.

9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that [MENTION=4905158]bogomil4e[/MENTION] kindly reported to wipe the EFS partitions

adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-

adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
[Android Q&A, Help & Troubleshooting] trlash:
Thanks Train, I would been lost. I replied to you gplus posting. Really appreciative for your work on this post. Thanks dude.

Ash
[Android Q&A, Help & Troubleshooting] Train88:
Bump
[Android Q&A, Help & Troubleshooting] cerj:
Double Bump
[Android Q&A, Help & Troubleshooting] djdarkknight96:
This needs to be pinned!
[Android Q&A, Help & Troubleshooting] pctechdroid:
I just used this and was able to get my Nexus 6P back up with your nandroid. I should not be able to use fastboot flash correct to get a full google stock?
[Android Q&A, Help & Troubleshooting] Train88:
Yes you should be able to... Or just unroot so that the OTA will work.
[Android Q&A, Help & Troubleshooting] im_Zak:
Dude. I don't know what to say. I really thought I lost my nexus 6p. But your tutorial worked like a charm. Thank you so much for sharing your nandroid and writing up an amazing tutorial!!! This seriously needs to get pinned!!????✌?

---------- Post added at 05:22 PM ---------- Previous post was at 05:17 PM ----------

BTW, I also was on MTC20F. Your nandroid booted the device. But I had to clean install MTC20F again so that the WiFi and sim started to work. Might come handy for some people... ??
[Android Q&A, Help & Troubleshooting] Train88:
I'm glad I could help! Thanks for the extra info! ?
[Android Q&A, Help & Troubleshooting] Lacrosse200760:
I have a similar issue, any advice on this... Updated to PureNexus Nougat fine, but even before that I had realized that my phone was not being detected through USB, no fastboot, recovery, nothing. So I flashed through TWRP to the current PureNexus Nougat build. All went good, except I now realized that the version of TWRP I have must be one with bugs on Nougat. Booting into recovery it just sits at the TWRP loading screen forever.

I can't get ADB through USB, can't get into Recovery, and Fastboot wont connect on USB. I can boot into the ROM just fine (not rooted) and can do ADB w/ wifi when booted up in Android.

Any ideas on how to fix my recovery and/or flash anything at all at this point? I am almost feeling like there must be something wrong with the actual usb-c port, but charging works fine, just no data connection at all (tried any different cables, Windows, Mac, different usb ports).
[Android Q&A, Help & Troubleshooting] im_Zak:
Is debugging on in your developer options.
[Android Q&A, Help & Troubleshooting] Train88:
What Zak said - you are not even in the same boat as the people that need this guide. You can get it to boot. I could not do anything besides go to fastboot(download mode) when I made this
[Android Q&A, Help & Troubleshooting] djdarkknight96:
You can flash recovery from phone terminal, Google the commands. You need root though, install super su from playstore. Otherwise you'll need to fix that adb issue.
[Android Q&A, Help & Troubleshooting] Lacrosse200760:
Installing SuperSU from playstore wont actually give me Root though. I like the idea though, maybe there is something that can be done around this.
[Android Q&A, Help & Troubleshooting] Train88:
Flash recovery through adb or android terminal, download the superSU zip, flash the zip in recovery. If you're having trouble getting recovery to stick, you need to flash the superSU zip immediately after you flash recovery. If you boot before doing that, android will try overwrite the custom recovery on boot
[Android Q&A, Help & Troubleshooting] Lacrosse200760:
Doesn't flashing recovery through adb require root? (only have adb wifi access when phone is booted into ROM)
[Android Q&A, Help & Troubleshooting] Train88:
No you don't need root to flash in adb. Just an unlocked bootloader
[Android Q&A, Help & Troubleshooting] djdarkknight96:
I have been very lucky to not have to remember but Train is correct. You should be able to push recovery via adb Wi-Fi. I forget root isn't needed to replace it, like Train said. "Kinda talking to myself as a reminder lol"
[Android Q&A, Help & Troubleshooting] TJ_bab:
Followed Your guide

at first, I couldn't repair the data partition. Then I formatted the whole device again and was able to repair data partition. But when I go to restore your backup, boot flashes fine but when it says flashing data, TWRP hangs and it reboots into the google splash logo screen.
[Android Q&A, Help & Troubleshooting] Train88:
It could be due to the storage option my 6P has (128 GB)... Try restoring everything but data. But essentially, it's the efs backup that you need if your issue was created by a bad backup from TWRP 3.0.2-1.
[Android Q&A, Help & Troubleshooting] TJ_bab:
Doesn't help

Stuck in bootloop.

Can't repair data partition. Can't flash anything in system or data from TWRP. Whenever I try to do that, phone just gets stuck and bootloops.
[Android Q&A, Help & Troubleshooting] Train88:
After you repair the file system (even if it doesn't work) you must mount data again or you can't see any zip/img files to flash anyways. When you flashed the factory image, did you use the flashall.bat or use adb to flash the parts individually?
[Android Q&A, Help & Troubleshooting] TJ_bab:
mounted data. went into restore it shows the backup and it even restores boot partition

Tried both flash-all.bat and also manually flashing all the parts.

Flashing happens from PC but phone goes into bootloop where the Google splash logo comes but it doesn't go any farther than that and starts bootlooping
[Android Q&A, Help & Troubleshooting] Train88:
Try flashing everything in this order:

Vendor.img

Bootloader.img

Radio.img

Boot.img

Cache.img

System.img

Then use command (this will wipe your internal memory):

fastboot format userdata

Then flash TWRP 3.0.2-2 and immediately flash SuperSU afterwards.

After all that, pick up with step 5 in the OP
[Android Q&A, Help & Troubleshooting] TJ_bab:
No help

My problem is, I cannot flash anything from TWRP.

I can copy files fine from my PC to my phone but whenever I try to flash anything into the system from TWRP, it hangs up and starts bootlooping.

Flashing from PC works via fastboot but bootloops when starting.
[Android Q&A, Help & Troubleshooting] im_Zak:
Have you tried fixing filesystem through twrp? Does any older version of twrp let you flash on your nexus. E.g twrp 2.8.7.0
[Android Q&A, Help & Troubleshooting] Train88:
You don't flash the nandroid, and you don't flash the factory image from twrp. You have to use fastboot, and a program like 7zip to unzip my nandroid, move it to the device, then restore
[Android Q&A, Help & Troubleshooting] TJ_bab:
I was talking about the restore, when it says restoring data, TWRP hangs , reboots and starts bootlooping.

Tried restoring without data (that means vendor,system,boot,EFS and everything else in the nandroid backup except data) and when TWRP starts restoring system, it gets stuck and same bootloop starts.
[Android Q&A, Help & Troubleshooting] Train88:
Did you do fastboot format userdata? And when you first flashed twrp, did you perhaps not swipe to allow twrp to modify system(it's the first thing you see on first open)? It's sounding like it's something like that... After you flash the factory image, did you let it boot up? Or keep it in fastboot?
[Android Q&A, Help & Troubleshooting] TJ_bab:
Yes I did fastboot format userdata

I allowed TWRP to modify system (duh, why not?)

I let it boot up to see if it works. It goes to the Google splash screen, reboots and does the same thing again and again. I guess it might be a hardware issue. I'm thinking problems with my eMMC

Thanks for your help.
[Android Q&A, Help & Troubleshooting] Train88:
Nah, i don't think it's the eMMC. Huawei replaced my 6P, but when my eMMC died, I couldn't even flash recovery. The only thing I could do was get it into download/fastboot mode. Tried flashing factory image, and it said "flash write failure"
[Android Q&A, Help & Troubleshooting] TJ_bab:
I just can't flash anything into system or data and I can flash from PC but can't boot
[Android Q&A, Help & Troubleshooting] Mangala_Dharma:
I am basically in the same situation as you are, cannot TWRP restore anything in /system and / data . I can flashall.bat no problem, I can flash MMB29P through fastboot, then TWRP [ tried all 3.0.2.0 , .1 and .2 ], trying to restore the nandroid TRWP hang up and reboot at either those two. I tried to fix the filesystem, doesn't change anything either.

I also tried with my own 7.0 nandroid and factory image and I have the same problem.

Could we force the restore through some dd adb command, and of so, how ?

thanks :)
[Android Q&A, Help & Troubleshooting] djdarkknight96:
Try mounting system and data before restore?

Just thinking:

You only have the issue with restoring the backup? Might be a bad backup..or are you using this one here? If you can boot factory but can't restore a backup I'm thinking a bad recovery image is the culprit. But you said you tried more then one?

To test: boot stock..if possible, but just set up a few things...make a backup...factory reset....restore Just made backup. But before going to restore..mount system and data. See if that works,, if not you might have a bad chip.
[Android Q&A, Help & Troubleshooting] Mangala_Dharma:
No, I wish I could boot :) I can fastboot the factory image, both the one in OP and current 7.0 , either through flashall.bat or through the individual commands. Fastboot doesn't show errors but still I bootloop.

When I try from TRWP I am not able to restore either a backup from 6.0.1 OP or my own I had done. EFS works, it's only data and system. I tried to fix file system, also even change file system, format and bring it back, no luck.
[Android Q&A, Help & Troubleshooting] djdarkknight96:
You have major issues if you cannot boot stock flashed from fast boot. It wipes everything so you must have a hardware issue.
[Android Q&A, Help & Troubleshooting] Mangala_Dharma:
Ok, thank you for your input. That's why I want to try dd commands then if not I'll see to bring it back, still in warranty.

*Edit* so, wondering why I can write on boot and efs and vendor partition but not on data and system, wouldn't that be on the same memory chip? Can memory fail like that for some partitions and not others?
[Android Q&A, Help & Troubleshooting] djdarkknight96:
It's one chip partitioned for system and data. Recovery and Bootloader have their own as well so if one goes you still have the other. You can corrupt a partition without the entire chip going bad. I think this is your case.
[Android Q&A, Help & Troubleshooting] Mangala_Dharma:
Ok, thank you for the explanation :) you have any idea if the partitions are recoverable in any way like dd commands? Wednesday I am going to town with the nearest mobile provider so I could bring it back, if there is any way to avoid the hassle I would be really glad of this. :)
[Android Q&A, Help & Troubleshooting] Train88:
I have a 128 GB version, and I woke up to my phone saying that decryption was unsuccessful - and that my files were corrupt (all this happened a week or two after I made this guide). I could not get anything to flash - not even recovery. Huawei replaced it even with the bootloader unlocked when I sent it in for warranty (I couldn't even relock it. Don't waste your time contacting Google - they said "they don't handle repairs"
[Android Q&A, Help & Troubleshooting] djdarkknight96:
Yeah if wipe didn't work then it's most likely hardware. Wipe will fix software corruption but not if it's a partition corruption. I don't know any commands to set them on Android. Windows I do lol https://iwf1.com/how-to-re-partitio...all-options-included-change-size-fs-type-etc/

Need adb to work..Might work with adb wifi. But this is very risky and could void warranty.
[Android Q&A, Help & Troubleshooting] Mangala_Dharma:
Thank you for the link, I'll explore the possibility, if not I'm still under warranty with my phone provider then Huwaei :-/
[Android Q&A, Help & Troubleshooting] hellfire bro:
I can't restore. It hangs on the wipe everytime. Any suggestions?

https://drive.google.com/open?id=0B7r8YF0vu1NdT1hZbWZTZGF6NXM
[Android Q&A, Help & Troubleshooting] djdarkknight96:
The video wasn't that clear. Did it have any mount issues? Try mounting system first then restore?

My only issues I have in recovery were mounting before doing anything. I have seen TWRP with this issue a long time.
[Android Q&A, Help & Troubleshooting] hashim71:
You sir are a lifesaver! I cannot thank you enough for these instructions. I only got this phone literally a day ago and thought I had broken it!
[Android Q&A, Help & Troubleshooting] Chabot1987:
Dude. Your amazing saved my phone. I was about 5 minutes away from going to get the new Pixel XL until I saw this thread. I tried everything and I was like "well it can't hurt" and bam back to life. Thank you so much
[Android Q&A, Help & Troubleshooting] djdarkknight96:
Got me back to CM13 from being froze on GoOgle boot logo comming from N. YOU SIR DESERVE A METAL!!!!!!!

:highfive:

DJ
[Android Q&A, Help & Troubleshooting] mxjcmxjc:
Thanks for sharing. I had to return two 6P's to Huawei due to the bootlooping and this is definitely a lifesaver. Downloading everything now and tucking it away on DP and Google Drive for future use.
[Android Q&A, Help & Troubleshooting] fapste:
Is this the solution for devices that can't go into recovery either? Or is this the solution for devices that boot upto Android dots animation? In general whats this guide directed for?

---------- Post added at 07:17 PM ---------- Previous post was at 07:07 PM ----------

Could you get into bootloader?

---------- Post added at 07:25 PM ---------- Previous post was at 07:17 PM ----------

Did updating to android N cause your phone to bootloop? Or restoring Nandroid backup from twrp did? I'm general what led to or contributed to your bootloop problem?

I'm kinda scared not to upgrade to Android N from 6.0.1 after hearing all these issues...
[Android Q&A, Help & Troubleshooting] Train88:
This is for people having issues created by the buggy twrp build a few versions ago, people trying to return back to MM from N, people who don't have a nandroid backup, etc.

Yes, when my last 6P died, all I could do was go into bootloader/fastboot/download mode. When the eMMC gets fried, you lose the ability to read/write anything from one partition, to the entire device (which was my case). I could not get the factory image, custom recovery, etc to flash. It would throw "error: flash write failed"

Edit: I *believe* what caused my boot loop was trying to restore a backup (to return to MM after trying 7.0) I created with the twrp version that had the bug that messed up efs. The newer twrp builds have fixed that now, but I'm perfectly content staying on DU10 till all the bugs in 7.X.X are worked out for certain.
[Android Q&A, Help & Troubleshooting] djdarkknight96:
Nah, was on PureNexus 7.0 then just flashed back to CM13 clean install and it looped on Google logo never getting to boot logo animation. Nothing would work once I tried CM13 until this fix. Now I'm back and enjoying my themes again lol.
[Android Q&A, Help & Troubleshooting] fapste:
What EMMC and ram name you had in your faulty 6p? Whats EMMC and ram name in your new device?
[Android Q&A, Help & Troubleshooting] Train88:
You mean DRAM? Not sure about my old one, but this one is 3072 MB HYNIX LPDDR4...both my old 6P and new one have the 128 GB Samsung eMMC
[Android Q&A, Help & Troubleshooting] fapste:
Does any one know what might be causing this EMMC frying issue? How to know if you can be affected by this problem?
[Android Q&A, Help & Troubleshooting] Train88:
Not sure if there's a definite pattern or not, because I've read about people having issues with both the Samsung and Toshiba eMMC ?
[Android Q&A, Help & Troubleshooting] DrFeelgood246:
I tried this method to fix my phone after it randomly started bootlooping from 7.1.1, but I can't access TWRP after I flash it. Any ideas?
[Android Q&A, Help & Troubleshooting] Train88:
Could you get onto recovery period? Like in factory recovery?