[Q] P905V recovery brick

biggiesmalls657

Senior Member
Feb 2, 2011
343
61
48
If Knox still triggered? Ill believe so. K1 is now the current FW?
Try after install TWRP , wipe normal and go into the adv. wipe settings to format / System and / Data / Cache etc..
Reflash K1 again.

How does it looks like Jam of Wifi / BT ? does you received a FC? only Interruption ?
TWRP isn't for the P905V. I have just stock recovery. I have tried all three build numbers. When I flash anything other than NB1 build, I get the Original picture I uploaded.
 

Mad07

Senior Member
Sep 30, 2009
286
27
48
Hi,
my last idea: If your are on NB1, could you connect the Tab via USB with a PC, start Kies and update the Tab from them....
If I've rooted my phone OTA don't work, but via Kies the update was working ;) - if I want -
 

biggiesmalls657

Senior Member
Feb 2, 2011
343
61
48
Hi,
my last idea: If your are on NB1, could you connect the Tab via USB with a PC, start Kies and update the Tab from them....
If I've rooted my phone OTA don't work, but via Kies the update was working ;) - if I want -
Thank you for your help but it bricked again. I'm just gonna damage it and pay the deduction.
 

Mad07

Senior Member
Sep 30, 2009
286
27
48
very late thinking :
Odin was running under admin access? Virus scanner, firewall off? latest Odin version?
FW E4 doesn't work too?
 
Last edited:

biggiesmalls657

Senior Member
Feb 2, 2011
343
61
48
This version I've use also with my Tab.
Does you've try also the E4 Version in the meantime?

I don't know, how you can wipe your cache, data and/or system partition out of your Recovery-Menu and/or Key-Combi? Maybe there is a possibility for a real factory-reset.

btw.: does you know this thread ? http://forum.xda-developers.com/showthread.php?t=2795630
Yes the NB1 file is what makes it bootable but WiFi and Bluetooth jam and do not work. Ne4 update bricks it and NB1 doesn't let me root for some reason. Maybe I used Odin wrong, I did want to downgrade boot loader.
 

Mad07

Senior Member
Sep 30, 2009
286
27
48
With towelroot, the tool works only with kernel before round about March/May. After this day, the security hole was fixed. Till there is no possibility to install TWRP, you can not flash SuperSU with the recovery. Without root access, you could not push the needed files into the system partition via adb, too.
Does you found/read a way to inlook the bootloader? This is the biggest issue, that another bootloader couldn't replace...
Maybe some new information could be found here?
http://nasirtech.blogspot.de/2014/12/install-p905vvruank1-android-442-kitkat.html?m=1
 

Mad07

Senior Member
Sep 30, 2009
286
27
48
ones more ;)
If you've an root access with the B1 kernel, look into the Google market, search e. g. System cleaner2 and wipe your data, dalvik cache, system..... Maybe you must refresh after that your rom and try again... I'll believe that there are somewhere only wrong settings
 

biggiesmalls657

Senior Member
Feb 2, 2011
343
61
48
ones more ;)
If you've an root access with the B1 kernel, look into the Google market, search e. g. System cleaner2 and wipe your data, dalvik cache, system..... Maybe you must refresh after that your rom and try again... I'll believe that there are somewhere only wrong settings
No root with NB1 used too but I can't now.
 

biggiesmalls657

Senior Member
Feb 2, 2011
343
61
48
So reading some other threads where people encountered this problem. Two main solutions

1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.

Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
Heres a question? So I flashed stock on it and I don't think it flashed my boot.img cause its still says custom system status.

Edit: not at the boot screen just download mode. It will brick when I update it.