I'm pretty sure we covered this somewhere, but I can't seem to find it at the moment...
I found one of these in a box while cleaning house, and I'm having trouble getting it to boot to system.
Fastboot works, I put TWRP 2.6.3 on it (anything newer doesn't seem to work).
Inside of TWRP adb works. I can push, pull, etc...
The problem I'm having is that inside of TWRP I am unable to mount any of the partitions, and so I cannot flash anything.
I have tried the Factory Reset and Advanced Wipe options, both options cause it to reboot directly in to to TWRP.
I'm not sure if the partition table is screwed up or what.
To be clear this is the US Nabi2-NV7A.
Related
I am a noob looking to try out the touchwiz rom,
My 10.1 is encrypted and trying to remove the encryption using the menu option in settings- factory data reset - it just reboots like nothing happened and asks for the password (I wanted to turn off/get rid of the encryption). I get a box open and android icon for a brief moment at reboot.
Using ClockworkMod Recovery v4.0.0.4 the wipe/factory reset option selected and it errors on the mounting /data. Can't mount or format /data too.
This 10.1 retail has a locked bootloader and is rooted.
Anybody? So far not bricked, ,
got it
I used odin and followed instructions here- http://forum.xda-developers.com/showthread.php?t=1119492
I lost clockworkmod and it did not recognize my password on reboot, but it did let me wipe everything.
You might have to wipe user data to get rid of the encryption. But you will loose all ur data
<bump>
I'm having the same trouble - and no amount of flashing various stock or CWM recovery gets me to a point where I can actually format / remove the encrypted partition.
The device had been rooted - and then encrypted - and it wasn't until I attempted to reboot into recovery with CWM (hoping to perform a factory reset) that I got into a boot loop.
Days, and countless flashing later - I'm no closer. The one thing I find interesting: when I flash particular (CWM) recovery / images, and reboot - I actually get the 'pre-boot authentication' page, which still accepts my encryption passphrase. It's after this point - that I'm just staring at a black screen.
Perhaps nvflash might be the right tool for the job - so off to learn about THAT. Every day, a new adventure - and another twist down the rabbit hole.
Thanks in advance to anyone with some insight / links / tips to share.
encryption owns me
SnoWake4Me said:
<bump>
I'm having the same trouble - and no amount of flashing various stock or CWM recovery gets me to a point where I can actually format / remove the encrypted partition.
The device had been rooted - and then encrypted - and it wasn't until I attempted to reboot into recovery with CWM (hoping to perform a factory reset) that I got into a boot loop.
Days, and countless flashing later - I'm no closer. The one thing I find interesting: when I flash particular (CWM) recovery / images, and reboot - I actually get the 'pre-boot authentication' page, which still accepts my encryption passphrase. It's after this point - that I'm just staring at a black screen.
Perhaps nvflash might be the right tool for the job - so off to learn about THAT. Every day, a new adventure - and another twist down the rabbit hole.
Thanks in advance to anyone with some insight / links / tips to share.
Click to expand...
Click to collapse
I'm facing what I think is a similar problem on an AT&T Galaxy s3 i747 with Paranoid Android. I had to encrypt for work email, and ever since then it regularly reboots whenever I try to do something (~25 second effort)... when I do the factory reset, or try reflashing a ROM, it seems to reboot before the action completes... Can you advise how I might solve this?
I've already tried CWM to redo everything... Factory reset does not complete as it always asks for the encryption password once started again... I just want to get back to unencrypted please. Any ideas? Maybe ODIN CWM then try a new install? formatting my SD card? Thanks in advance...
Hi, I had the same problem as above.
I was unable to factory reset with CWM recovery as it couldn't flash the data partition or sd card and couldn't mount them.
However, using the stock recovery, the factory reset and formatting worked fine returning back to an unencrypted device.
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
es0tericcha0s said:
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Yeah the factory blob flashed fine. I can use the device (the OS loads up), I can get into fastboot and from there to TWRP.
There is no backup, and from what I'v read about NVflash, you need to set it up before anything else...
I was hoping the factory blob would recover the partitions...
Is there a way to repartition it?
Maybe using fastboot erase for the data partition?
I guess maybe I am not sure of the exact nature of the issue. If /data was not mounted, you would not be able to install apps. Does it show the proper info in Settings / Storage? Have never seen a device that had the data partition unmount and still be able to use normally while booted.
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Bump...
Ideas/suggestions?
kevinbakon said:
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Click to expand...
Click to collapse
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
OfficerJimLahey said:
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
Click to expand...
Click to collapse
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results, but I do see the devise in fastboot, if I am in the bootloader screen
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Otherwise, I guess I could reinstall factory recovery, but I can't figure out how to do that either.
Unfortunately, the LG G Watch Tool doesn't seem to be working for me either. It just says "waiting for device"
Ultimately, all I want to do is get the latest stock OS installed and go from there
Any advice?
kevinbakon said:
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Any advice?
Click to expand...
Click to collapse
Wait, installed TWRP? If it keeps taking you back into TWRP, then "fastboot flash boot" was used, not "fastboot boot". Read my previous post for difference.
What were the backup errors? Did something not mount? If so, then this (coupled with the original issue), may be hardware related and out of your control.
See if you can get back to the bootloader first. The boot.img can be restored this way, and get you one step closer to booting.
Sent from my ASUS_Z00AD
Helllo yes it seems your partitions are all messed up. Considering that on android wear your "data" on it is almost all on your phone aswell it seems like a waste to try and recover it.
here is a link to the system,recovery and boot images from LCA43 https://www.androidfilehost.com/?fid=24052804347803309 just flash those to each partition correctly ie. fastboot flash boot boot.img etc
and wipe your /cache and /data partition. You will essentially have a completely stock device and if it still thosen't function correctly then it is a hardware fault
Here is a video on how to access bootloader from boot screen: https://www.youtube.com/watch?v=ftSCH7qihRI
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!