**edit:I feel like I posted this in the wrong place, but please feel free to help me work on this issue if you see this here...**
I am having a problem that I am hoping someone can help me figure out. It is almost a problem I have found several people have, but my situation does not match any of the solutions that work for others with similar issues. Here it is:
I have two tablets, both are Nextbook Ares 8 tablets but one has android 5.0 and the other has 5.1 on it. I wanted to put android 5.1 on both, so I looked it up and found vampirefo's guide to rooting and putting twrp on the 5.0 tablets and figured I would start there to get to where I could put 5.1 on it. Problem is, I put TWRP on both tablets and neither one can mount the data partition so I can't get anywhere with it. I screwed up the 5.0 with a borked 5.1 but I cannot restore it because I can't put my backup on it where twrp can see it.
I, of course, looked up the issue of not being able to load /data and found several solutions. The only thing that sort of works is to format data through twrp on the data partition. This makes it so that while in twrp I can mount the partition, but since I cannot access it to put things on it while the tablet is in TWRP I cannot put the backup on the partition while the tablet can mount the partition. If I reboot the tablet in order to put data on it(or even reboot the tablet straight from TWRP after a reformat and mount to TWRP again) I am no longer able to mount the partition until I again format it(which wipes out any data I have put on it). This is not related to having data on the partition, it is not related to having booted to another mode or connected to any device, and this is not related to anything I have done because the only thing I did after getting the tablets was boot them all up and check the OS version and that the tablets were both the same model number and then I rebooted to bootloader and flashed TWRP on and booted to that. The 5.1 tab has the same issue with not mounting /data, but I am most concerned with it on the 5.0 tablet.
Both tablets are model NXA8QC116
One came with 5.1 on it stock, the other 5.0
TWRP I flashed to both was 2.8.6.0 from vampirefo's post here: https://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
The tablets both see the data partition when booted normally, but not when in TWRP. That's all the information I know to provide, if anyone can help me figure this out I would appreciate being able to learn why and how this is an issue for me specifically in addition to just solving the problem. After all, I cannot find anyone else having this issue with Ares 8 tablets...they all seem to have no issue with this TWRP being put on this tablet.
Related
Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.
Gash128 said:
Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.
Click to expand...
Click to collapse
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee
erica_renee said:
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee
Click to expand...
Click to collapse
Worked perfect thanks! Wiped and flashed via odin back to 4.0 and then re-flashedback to 4.2.2 now no more problems:laugh:
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
My phone had been working fine for quite some time running praetorians 3.2.1 twrp and the weekly version of AICP 8.1 Last week I tried to flash Bliss 9.0 and everything went wrong. (Note I'm not blaming anyone for this, I know stuff happens when you play with your phone)
After much trial and error I finally got the stock os loaded through erecovery and got praetorians twrp back on. But, now when I flash into twrp and it asks for the password to decrypt data it rejects the password. When I installed the stock os this time it asked for a 6 digit pin instead of the 4 digit pin when I initially setup the phone but twrp won't take either the new one or the old one. I pm'd praetorian but he didn't know what the problem was.
I have a copy of removeencryption.zip which I think I've used in the past but now when I run it, even though it reports sucessfully installed, nothing changes. So now I can't do a nandroid backup of /data, although I can do one of system for all the good that does. I've tried official twrp and the 3.2.3 version referenced in the Bliss rom thread but I've not been able to get to the point I was at prior to last week, with data decrypted. In the blur of activity over the last week I think I tried to install a rom but couldn't because data was encrypted. Does that sound right?
If I'm stuck here that's ok - I've got the stock os rooted with xposed running and my favourite launcher installed. I can live with that on this great phone. But I'd like to get back to where I was before. Is that possible?
encrypted media filesystem will be mostly overwritten or a part of it, if not full (esp the critical start)
low level recovery tools will not recognize the data at all
only long shot is to dd your entire disk content as an image and experiment with it on PC while you enjoy the favorite launcher
What partitions get updated when one does the full update using the full image found in the firmware finder? I saw in one thread (ota update on rooted phone) a mention of flashing both ramdisk and ramdisk_recovery.
I wonder if doing such an update - hopefully with Pie after Saturday, might 'reset' my phone back to where I can decrypt data using praetorians twrp?
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?
Hi all,
Installing a custom rom on an XZ Premium; it's my first time dealing with this so its possible I missed something. I successfully installed TWRP and adb sideloaded the most recent Cherish OS rom. I was able to set up the phone with no issue, but upon rebooting for the first time back into system, it hits the boot logo, which animates correctly, but then hangs there indefinitely. I have wiped system memory, reformatted, and reinstalled, and the issue persists. I have also tried other ROMs. Arrow had the same issue, as did the Pixel experience, which leads me to believe that it's not an issue with the rom, but something with how I have configured the set-up.
I looked around for solution, but wasn't able to find much on the specific issue of only having issues on second boot, rather than initial. Any help would be appreciated.
I think your TWRP version is the Problem... (I think there were a lot of complaints about 3.3.?.? and higher) I had a similar Problem; TWRP wanted to use /data and if i formated the device, it would endless bootloop (I think because of the encryption the OS uses by default) So i decided to flash a older version (were this wasn't a problem) and I picked twrp-3.2.2-0-maple.img (maple because i have single SIM variant) and I didn't even needed to format the device and it still works (after i flashed Magisk and some other stuff/ "enhancements", that don't impact he OS) and everything still works smootly.
Maybe you should just flash a older version of TWRP (like 3.2.2-0) But i can't guarrantee, that it'll work on Pie(since i don't have it).