Related
Hi every one,
My transformer was working fine... then came ICS, I was prey of the savage need to update, Made a backup with CWM and download the new rom.
What i did first was wipe cache and data, so far so good, flashed the ICS revolver beta, but in some point I screw it up and it just didnt boot anymore, just keep rebooting to CWM, couldnt turn off it keept rebooting, so I tryed flashing the new rom and... nothing it kept rebooting to CWM so I flashed back to revolver 3.1.* In booted OK, was runing fine till It crashed and restarted and couldnt get to CWM any more, Used NVFLASH trying to reinstall it but the screen stays off Windows detects it as a APX device but NVFLAS doesnt work since its a B70... it shows some letters in the screen but does nothing.
Please help me. Is there other way to install CWM maybe get acces to the files in the internal memory trough ADM or APX??
I would really apreciate any help, Im desperate!!!
Best regards,
IaxBay
Sounds like your recovery is missing. Can you still boot into revolver? If so reflash CWM recovery from within revolver.
Dead transformer?
Yes you are right, I think I messed up the CWM but cannot get into android at all.
Actually the tablet doesnt start, If I press the power button, or power+vol up or power+vol down... nothing works, but when I plug the usb windows recognice it and make the sound of device found, Actually It apears in device manager. I can get into APX, wich gives me hope... theres maybe a way to acces trough APX to install recovery or something...
If APX work and you have SBK v1, Tran Rouge has am nvflash version of their recovery
Yesss its alive!!!
Thanks so much to the creators of nvflash for saving my transformer.
it Actually my transformer happens to be a B70 I still it has to be SBK1.
Just follow thevinstructions of a video I found somewhere Ill post the link later cause i cannot seem to find it , anyway its working and im writing my horrible english in my revived tf101. Lesson lerned: READ A LOT about what your are going to do before you do it.
Thanks again XDA
I have a sl101. I only get eeepad screen. My son did something to the machine. I can get it to say booting recovery but nothing happens. I also can get a text that says cold booting Linux. Again nothing happens. Nvflash says USB write fail. But when I check adb the device is recognized. Is there a way for me to adb push a recovery in there for me to boot too, so I can reflash a rom. I have a little dilema here. I also was wondering if I can flash rom thru adb. I read once that's how they used to do it on g1. I don't know if I am speaking accurately though. Any kind of light shed on me will be greatly appriciated
Sent from my SAMSUNG-SGH-I997 using xda premium
not sure about the slider but i had a customer return yesterday with this exact issue on the tf101 and i couldnt get out of it. the tf just kept switching itself back on and getting stuck on the splash screen.
found this set of instructions but im not sure if its what you need or if it will work:
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
good luck
That is exactly what is going on with mine. The slider is basicly the same thing. I plug it in and I tries to boot. I thought you had to be booted into recovery or the rom for adb to work? That's why I believe this method you just revealed to me. Or some variation of it will work. I will be trying shortly.
Sent from my SAMSUNG-SGH-I997 using xda premium
not working transformer
i have asus tranfrormer 9.x.x.x, recovery 5.8.x.x, after i did superwipe , every thing is gone and i cant flash any rom through adb/nvflash saying cant write to sdcard (read only). any suggestions?
HELP : Same problem, no apx, recovery strange, no boot
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
densleonis said:
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
Click to expand...
Click to collapse
nvflash if your TF101 is compatible model.. (must B60 and below).
Or read Wolf's thread HERE. It might helped everyone here..
Thanks but everything needs adb connexion and as apx is not working, i can't connect ADB..
I have a B50 model
Nobody have a clue ?
well, I have to send it back to my reseller that will change it but before that I need to delete clockwork mode or brick it, how can i do ?
I tried every thread here, update rom does nothing, looks like it does not write anything on the tablet
Thanks in advance
try to follow this procedure...
http://forum.xda-developers.com/showpost.php?p=25636698&postcount=5
let me know
Hello, thanks, but as I can't get to apx mode, I can't use nvflash, so still stuck with my recovery, I tried to modify super Wipe package to do things but can't get through...
If someone can make a package to delete recovery, then I can try it on my tablet, I really yneed it to be bricked cause now it load with Rogue's recovery on and on, so the reseller will new it has been modified and I will have to pay to get it back ...
Thanks in advance
with the procedure posted in the previous link you don't need APX mode and don't need NVflash...
Just boot your TF in recovery mode and plug it to your pc...
remove all previous drivers and install the new one that you can find in the post
ciao
ps... at the end of the procedure you will have your TF101 with stock rom and stock recovery
I will try but even when I am on recovery, nothing appears in Hardware management, no recognition from My computer, still strange... And when I power + vol down key, It never says to presse vol up in the text in the upper left corner, just says booting linux kernel...
When I try to boot pressing vol up + power, nothing happens, not even the clics that can be heard when it powers up...
I had a similar issue when I used SuperWipe and discovered my ROM on the external SD Card could not be accessed by CWM
I tried pushing the file with adb but kept receiving errors - protocol, etc. I suspected it was a driver issue along with the fact that 64 bit systems don't always play nicely with drivers. I actually dug up an old hard drive and did a very basic install of 32bit Win7. I booted the Transformer into CWM and when I connected it to my PC - I pointed it to the universal naked driver. I was then able to successfully push the rom to internal storage and used CWM to flash it
Hello,
I tried to connect my tablet to an old Windows 2000, but still nothing happens
Hello every one, I finally sendt back my transformer to my reseller, now I can buy a new one...
Thanks again
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
V4lk0 said:
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
Click to expand...
Click to collapse
Just let the battery run dry. Then let it boot up normally without pressing any buttons when the battery runs out by connecting it to your charger. Hope it works!
Thanks for the reply. I tried that, but nothing happens, just the indicator LED on the power button turns on orange. The tablet does not boot on itself, if I connect the charger. I have to press the power button, but this results again in "Boot image verified failed"
Edit: Update. I figured out how to get into fastboot. I read something on google, with switching the screenlock switch on and off. That doesnt worked for me: The thing was, to hold the power button AND the volume button with the two knobs, then the tablet starts, to release the power button and THEN, while still HOLDING the volume button pressed, to switch on and off the screenlock button. Then the bootloader starts into fastboot mode, going into androidsdk and typed in cmd "fastboot oem unlock" solved the problem. The ROM starts and everything is fine
Why you don't write into the mentioned thread? There seems to come the issues from then ask there, sorry can't understand why opening new thread instead asking there.
Also the first time heard sucha thing, I also change the rooms from cm10 to Jacobus, back to stock, on cool one and to cm and back, to test everything and try something out.
Never had issues buy this ways
Gesendet von meinem GT-N7000 mit Tapatalk 2
I don't have the right to post in the proper thread, so I opened up a new one.
In order to install a JB based ROM, you need the JB compatible CWM. The version of CWM you used is apparently for ICS, so I am a little surprised it worked to install CM10. Where did this 6.0.2.3 come from? Use 6.0.1.5 from pawitp. I've used it and swapped/flashed ROMs at least ten times. Never encountered that issue (or any issue). As a matter of fact, I would just run Vorbeth's EasyRoot as it does all the grunt work for you. I've used it twice and it worked flawlessly.
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
V4lk0 said:
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
Click to expand...
Click to collapse
Hi I had the same issue after flashing from CM10.1 to CoolOne. However I fixed it by unlocking the bootloader => reinstalling recovery => flashing CM 10.1 back.
Did you have any luck recovering from APX?
Gullinbursti said:
Did you have any luck recovering from APX?
Click to expand...
Click to collapse
No, unfortunately not. I gave my tablet 2 weeks ago to the acer repair service and got it back today. The support said, that they have changed the mainboard and flashed the latest android on the tablet, but they did that on guarantee, so I didn't had to pay something ^^ Now it is running Android 4.1.1 Stock ROM from Acer.
Exact same problem
I am having the exact same problem. I am able to boot into recovery mode but then I get the android laying down with with the red triangle, question mark. My bootloader is unlocked but aftrer the update my screen is stucked on the ICONIA TAB startup screen.
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T
jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.
I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse
jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!
noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.
I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl
Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Silicon Knight said:
Nevermind fixed it. I am a dumbass lol I booted into stock recovery and factory reset, and now I am good to go.
Click to expand...
Click to collapse
this happens buddy you just have to boot into recovery and do a factory reset and wipe cache and there will be no problem
HAPPY NEW YEAR
So I had the same issue it sounds like, tried to flash PhilZ recovery over Odin seemed fine I put the PhilZ file and superSU files on the device to continue through and now I am unable to get into recovery mode only download and my tab does not turn off, it sits on the Samsung Galaxy Tab 2 10.1 logo unless I hold the power then it turns off and then right back on again.
Any ideas? I cant seem to find anything
Does your device boot up completely or just sit at the Samsung bootscreen?
swrght13 said:
Does your device boot up completely or just sit at the Samsung bootscreen?
Click to expand...
Click to collapse
Just the boot screen, not even past the first logo
You must have missed a step. Try the process again using this video tutorial: http://www.youtube.com/watch?v=sO3y7JCqfc8
Follow the directions step by step.
This is actually the video I was using, but, I have tried again and I cant get it to boot into PhilZ. I am able to get to download screen so I have tried a different version as well, but after it gets the pass it disconnects to reboot and then never boots or reconnects until I put it into download and reconnect the device.
Weird. This is the way I installed Phil's touch. I had no issue with it. Make sure your usb is disconnected from your device before rebooting. On the p5113, to get into recovery, hold down power + volume-down, when you see first Samsung big-screen, release power button and continue to hold the volume-down button.
Sent from my GT-P5113 using XDA Premium 4 mobile app
That's what I've been doing and it does nothing. Device sits at that Samsung Galaxy Tab 2 10.1 screen. The only way I can turn it off is to plug it into my computer and restart it until the battery symbol comes up and disconnect. That's it.
Not sure what route to take now, but, it still connects to odin and after flashing the PDA to it, it disconnects.
Ok. Tell me. Are you rooted? Can you boot up to your home screen at all? You must be rooted in order to flash a custom recovery.
Sent from my P5113 using XDA Premium 4 app
Rooted, running CM 10.2 [4.3.1]
I didn't even get to that step, I was flashing philz recovery in order to backup before rooting. I was unable to boot anything except the download mode, no recovery mode to factory reset and not able to boot the actual system at all.
I ended up trying CWM and flashing that to the device through Odin and was able to open recovery mode after that and have since flashed Cyanogen to the device and have everything good to go.
I dont know what was wrong with philz, but, I tried multiple downloads of the version we need and none did anything.
Problem is solved, but, there's got to be something wrong with philz recovery for this device or my tablet just doesn't like philz.
Thanks for your suggestions though I appreciate your efforts!
No problem. I'm glad you found a way to fix it!