[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.
greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Grand Neo Plus Root
a
omametsnor said:
greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Click to expand...
Click to collapse
Hi There, I just came across your thread, because I'm in the same position you are, fortunately though, I've managed to root this phone without any problems, however it seem though that there is no custom ROM available for this device, at least nothing past KK, and that one I found didn't seem so stable, I tried to flash it and came back with an error!! So my friend won't be able to bring his phone out of the Dark Ages!! at least it's Rooted! and now he may be able to use some apps that do require root, It's the best I can do at this point. I used the link below to root sucessfully:
https://www.google.com/url?q=http://forum.xda-developers.com/android/general/root-galaxy-grand-neo-plus-gt-i9060i-ds-t3070302&sa=U&ved=0ahUKEwjds_Tn-sDOAhVG1B4KHe8xDC0QFggEMAA&client=internal-uds-cse&usg=AFQjCNFDnwTNwiFG6H8TI_hKXAeeWEOlRw
I realize it's kinda late but luck to you my friend:fingers-crossed:
By the way, This one is the Dual Sim Version, don't know if that will make a difference?!
I softbricked my phone. I was in TWRP and wiped everything including the rom that was on it. So i have tried flashing the stock back on using the various toolkits out there. I have also tried to push a rom file onto the sdcard. However it seems my computer is only detecting the phone in adp mode when its in recovery or sometimes when its stuck on the google logo screen. as soon as it goes into fastboot mode no more detection. Also it seems the bootloader is locked again. hwoever i cant unlock it as i cant get it into the adb mode on thr fastloader screen. someone please help. ?
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.
I need some help.
Last night I was updating to lineageOS' new nightly update with TWRP in recovery mode. I also like to run a custom kernel on of that for battery life reasons. In doing so, I mindlessly flashed the custom kernel (blackscreen 3.6.2) to the system image partition instead of the boot partition, then went back and flashed SuperSU, wiped the cache as I normally do.
My problem is that when I rebooted the phone it hangs on the stock LeEco boot logo without going past it. In addition I cant get it to go into fastboot or recovery no matter what button combination I use. In addition, I can't get adb or fastboot to detect it from my PC to do anything from there either. My PC does detect a "Portable Devices", listed as a D:\ drive, but this isn't helpful.
I could really use some help. I'd hate to think I bricked my phone with such a mindless mistake. If you know what's up or another post that can help me, please post it.
Pls disregard this post, I managed to boot into recovery when I plugged it in to my PC and turned it on with volume up and power
BlocforLife said:
Pls disregard this post, I managed to boot into recovery when I plugged it in to my PC and turned it on with volume up and power
Click to expand...
Click to collapse
thanks,bro.I have same problem, it work for me.