Hello! So I 'm trying to get Lineage on my tab here, and of course you must install TWRP to do so, but after following tutorials and such with ODIN on how to do it, it finally boots back up into stock recovery. I try booting back up into Android but no luck, it just boots back into recovery. I tried going into download mode and flashing again, but it doesn't return with the normal light blue 'Downloading' screen, it shows the initial boot image with text in the corner, similar to normal download mode, says system status / current binary = custom, FRP lock off, etc. I plugged in to ODIN but it doesn't show up, neither when using plain old 'adb devices'. I've had some luck though, i can flash using adb sideload, or from an SD card via recovery mode, but nothing works since they're not signed apparently? Please someone help me if you can, im looking to use this as my daily driver mobile computer, since my laptop has a screen problem. Thanks in advance!
-xxpxl
Pixel 2 XL, Samsung Galaxy Tab E 9.6 (SM-T560NU)
Related
[SOLVED] Okay so I got my i/o tab back up and working. See this post http://forum.xda-developers.com/showpost.php?p=14586131&postcount=2.
1. I downloaded those 2 things.
2. I booted into odin mode by powering off the device and holding the power and the left volume (volume down) until it brings me to a usb and a triangle sign with an android figure.
3. Press Right volume (volume up) to select the right icon on the screen.
4. Plugin the tab to your computer and load the odin3 v1.85 application.
5. Press PDA and find the PDA_SIGNED_P7105.tar.md5 file
6. Click start and let it reboot and it should be fixed! (well that's what fixed it for me)
So I tried installing the starburst rom on my i/o tab that I won (from phandroid!), anyways I was on an unlocked 3.1 rom that was rooted. So I installed rom manager from the market to get cwm on it. After that I backed up my current rom, and then I flashed the starburst rom.
After the rom finished flashing it rebooted and is now stuck in a bootloop of continually showing the samsung galaxy tab 10.1 splash screen.
I can't get back into cwm at all. I've tried getting it back with odin and with nvflash. Also fastboot isn't working for me (says waiting for devices both on my windows and linux machine). I've tried flashing both stock recovery and cwm via odin and via nvflash but nothing is working.
I'm not really sure where to go from here. I've spent the last 5 hours or so on xda and google. Any help would be appreciated.
The first attached files shows what happens when I select the USB image, the second shows what I get when I hold down the power and down volume, and the third is me flashing cwm through odin, but after flashing it, I still can't get into cwm.
I'm not an expert, but you may want to check the file you are trying to flash as it may be corrupt. Maybe try redownloading and flashing with odin. If that does not work you may need to reflash your firmware, I think there is instructions in the dev form on where to download. Also check if the IO edition is different model from the retail WIFI version.
Hopefully this is helpful,if not I'm sure someone else will chime in.
I checked the md5 of it and it matched. How would I reflash with odin? All I can see that I can flash with odin is the recovery. I don't know how to flash anything on my tab in it's current state. I can't get cwm back, and all I get is fastboot usb mode and odin. Fastboot isn't working and odin says it flashes the cwm recovery correctly and everything, but then it's not there.
Thanks for your input, any input is greatly appreciated. Was hoping to get my tab updated to a touchwiz rom, now I can't even use it.
I had same problem happen with mine out of the blue and it's stock I/O.
Maybe the thing i'm flashing in odin isn't for the I/O tab?
kbutlermd said:
I had same problem happen with mine out of the blue and it's stock I/O.
Click to expand...
Click to collapse
Did you fix it? I had this happen once before but I forget how I was able to get fastboot to work to issue a fastboot -w command.
Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?
mjm128 said:
Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?
Click to expand...
Click to collapse
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup
used2hvatreo said:
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup
Click to expand...
Click to collapse
I think maybe my partition table is effed up? I'm not sure.
I tried fastboot and flashing the backup that I had on my computer (fastboot flash system system.img ; fastboot flash data data.img ; etc), but it just hangs at the samsung galaxy tab splash logo.
I'm using the ota that comes in the files for dummies in the dev forum.
thank you SO MUCH ... I was stuck for hours until I found your thread
but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????
Sheeda Talli said:
but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????
Click to expand...
Click to collapse
you are not in download or recovery mode. turn your tab all the way off, and then use the key-combo to get into the menu where you choose recovery or download mode.
then odin will see it
Jtag will available soon for 10.1
which key combination ??????????
there is nothing shown on my tab
no light
no charging sign
blank black lcd while in """'NVIDIA USB Boot-recovery driver for Mobile devices"""""" mode
in device manager
so good to hear that mine is not bricked
So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>
mjm128 said:
So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>
Click to expand...
Click to collapse
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..
gunzo71 said:
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..
Click to expand...
Click to collapse
Simply doing fastboot -w has never worked for me. It would just bootloop. Only way i've been able to restore it is through the steps I listed in this thread.
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
As I understand; If you're trying to boot it to recovery mode, it goes to fastboot mode, right?
If I understood right; you need just flash recovery to your device.
G2 has a different boot process from other devices. If bootloader failed to boot the thing you want to boot, it goes to fastboot mode. That's why it goes fastboot mode when you try to boot it to recovery.
Ah yeah, i just couldn't figure out how to get it out of Fastmode. I was a little confused about the difference between fastmode and recovery.
I seemed to have fixed the problem by AutoRec, for whatever that is worth. Now it boots into TWRP's recovery mode. Shouldn't be hard to get cyanogenmod now.
TheAmericannomad said:
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
Click to expand...
Click to collapse
if you want go back to stock and you can't enter in download mode you can try follow this but USE THE CORRECT FILES FOR YOUR DEVICE!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2477595
to extract laf.img from kdz.
http://forum.xda-developers.com/showthread.php?t=2600575
Give a thank to the OP of the threat.
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.
Hi, I've got a soft bricked S8. I've tried to flash stock firmware but with one, O2 it stuck on erasing at 32% and with another stopped at 24% with no command. When it boots into recovery, I get a whole list of messages at the bottom of the screen. The first one is, "#fail to open recovery_cause(No such file or directory)#" I've googled for hours and not really got anywhere. Recovery doesn't work. It's there but buttons are unresponsive sometimes. Download mode works and shows FRP lock ON and OEM lock ON. I am sure this has something to do with it but it's outside of my knowledge range. I've attached a picture of the recovery screen. Any ideas would be appreciated.
I'm new to these threads so I can't work out how to attach a .jpg of the recovery faults. Any advice would be appreciated
Same issue here
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.
Hello everyone,
I flashed teamwin today and afterwards lineagos. All worked like a charm. However, I tried getting root access using this tutorial (
), but there was an error message when I installed the "no-verity" zip. I rebooted it, all went normal and after another restart it now is stuck at the teamwin page.
I can go into download modus, but flashing teamwin again, does not result in any changes. Teamwin version is 3.6.2_9-0.
What can I do?
Thanks
Since I can't turn it of (I have to either go into download mode or get stuck at the twrp screen), I would really appreciate fast help
E: Fastboot and adb unfortunatelly don't seem to work, because the phone is not listed when I type "adb devices".
E2: I downloaded the "latest" Firmware from Sammobile, Flashed (only) the AP file (2,6 GB), choose "Auto-reboot" in Odin and after the reboot I managed to get into the normal bootloader -> Wipe cache and factory reset.
After restart Android 8 started to get set up.
If you encounter this: Be careful and make sure your battery is charged! Because when stuck in bootload it gets hot and apperently drains the battery quite fast.