I tryed to load AOKP rom from this thread in the devlopement section [ROM][29.APR.2012][3G]AOKP (Android Open Kang Project) *OFFICIAL* [v2.1] Milestone 5!Thread. Any way I ended up in the recovery loop that they talked about. I figured no problem just flash my CMW backup. Well recovery dosent see any files to recover. Great. I hook up to my computer to fix by ADB but my computer will not reconize my TF101. Tryed to do the power button + vol up but once again computer fails to see the TF101. I have verified with anorther TF101 that my computer will see it. Have also tried multible cables with same results. So it appears my beloved TF101 has a bad connector although it does still charge. Anyway is there any other way to get out of this recovery loop. I am out of my warrenty period to have the connector fixed.
Does the computer see the tf101 in APX mode?
Well if you can Cold-Boot adb over network may save you. otherwise you need working usb
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
APX mode use NvFlash?
can you explain how to do this.
At reboot hold volume - and power button , when white text appears in left upper corner let go of the buttons and wait for it too cold boot
Hello
I bought an haipai i9377 (mtk6577). short after that i rooted it, (succesfull then when i tried to flash clockwork mod recovery( wich was build with CWM builder) it said ok but it ain't ok! (unsuccesfull
Now it wont boot and now i am stuck, i can still come into recovery. but download mode is not working any more.
Adb keeps telling me the device ' 1234567890abcdefg" dont know why that name, is offline BUT recognises it. when i put it in recovery windows detects it as an unknown device and when i install drivers it wont start. i don' t have really much options now i do got an backup of my recovery, bootloader and system image. But without getting into download mode or CWM i cant do really much with it ? HELP
P.S When there is no accu in it and put it into cable windows detects it for 2 seconds (preloader usb vcom android) ; Sound something is in* sound something is putted out*
Just had exactly the same problem here, Tried to update the bootloader and now I get nothing but the spinning nexus android logo and the USB is no longer being detected. Did you fix it?
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
OK well 5 mins later I managed to fix it, Went into 'Factory' Mode - Hold down power, Menu Key and Volume down for about 4 seconds - As the tex came up on the screen to start the auto test, hold volume up to cancel the auto test, Menu appears - Select Clear eMMC - and it will reboot - all fixed.
Hi,
My Transformer TF101 would not start, it got stuck at the ASUS boot screen. So I thought that I would restore the device by flashing stock rom using EasyFlasher. But I ran into problem...
I put the device into APX mode and updated the driver from Universal Naked Driver 0.72.
Once I do "Flash Asus stock zip / Unbrick" from EasyFlasher 0.8.3 a command window appear (see attached picture) and after a while the text in the windows stops at
[+] Sending bootloader...
Sending file: 100 %
The screen of my transformer lights up and says the following:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 033c20c140e04117
I waited several hours in this state but nothing happens. If I unplug the transformer from my PC I am not able to reboot it, the only thing that seems to work is power button + volume up to start APX mode and then connect to the PC.
Does anybody have some idea what could be wrong? I am thankful for all suggestions.
Hi.
Happy new year ...
Suggestions
power button + volume Down, after volume up ---> to start RECOVERY mode ????
---------- Post added at 12:01 PM ---------- Previous post was at 11:56 AM ----------
then reinstalled a rom, or restore backup...
I got a new (to me) TF101 for my OH for Christmas - I seem to remember the serial number was not mentioned in EasyFlasher either - however cutting a long story short, EasyFlasher didn't work, but I googled and used PIRI and was rooted and booted in no time at all. Hope this helps you.
Hi,
Thanks for the suggestions. Unfortunately I cannot boot into recovery, nothing happens when I press volume down + power. Since I cannot start it I cannot use adb so I guess the only option is to flash recovery/stock rom in APX mode. But here is where I run into problem, nothings happens after the bootloader is sent to the device as I wrote earlier.
joooeeel said:
Hi,
Thanks for the suggestions. Unfortunately I cannot boot into recovery, nothing happens when I press volume down + power. Since I cannot start it I cannot use adb so I guess the only option is to flash recovery/stock rom in APX mode. But here is where I run into problem, nothings happens after the bootloader is sent to the device as I wrote earlier.
Click to expand...
Click to collapse
Since you can still use the APX mode you should be able to restore the stock firmware.
From my experience EasyFlash works like a charm. But it has no option to install the APX drivers. You also need to download the stock image from the Thread.
Did a restore to stock just a few days ago.
Looking at your command you did not tell wheelie to install any ROM after the bootloader.
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc
Yeah, I'll do that today
Sent from my One M8
Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?
Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?
MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:
I wanted to install lollicop ROM that I downloaded from a thread in this forum.
It happened when I flashed TWRP by Rashr App and rebooted my phone
It got stuck on screen that's saying
[ODIN3]
PRODUCT: GT-I8262
VERSION: I 8262XXBNH1
HW REV: 8
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
and below it a green Android logo followed by
Downloading......
Do not disconnect USB cable during the software update!
I tried everything,
Volume up+ home+ power
Volume down+home+power
Removed battery
Connected to PC with kies installed but Odin couldn't detect it so can't install recovery from PC
fastboot is not detecting my device
installed latest drivers for Galaxy core but still nothing
Please show me a way if I could do anything with the help of phone or my PC
I don't want to change motherboard guys please help:crying:
This happened to me. You might have gone in recovery using rashr. Just use volume dn+ home + power until you see warning keep holding vol dn and home but leave the power when phone vibrate.
Note - keep holding the two until you see a warning and press vol up on warning. Odin will detect you
---------- Post added at 09:36 AM ---------- Previous post was at 09:36 AM ----------
But You need odin
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
And restart using it
---------- Post added at 09:37 AM ---------- Previous post was at 09:37 AM ----------
If works pls like
finally solved it
if other users facing same problem here is the solution stepwise
1. install samsung drivers from the original website of samsung only or from this thread http://forum.xda-developers.com/showthread.php?t=961956, there are a lot of drivers available on the internet don't pay attention on them, they don't work
2. download odin latest version
3. go into download mode- switch off the device
long press volume down+power+home button simultaneously, when the phone vibrates or something comes on screen, leave all butten,
you'll see a screen with two options
1. continue
2. restart phone
press volume up key for continue, now you see a logo of android and downloadin on screen-- hurrey- you're in download mode
4. connect your phone to pc with an original data cable
5. odin will detect your device where the ID is written, if it doesn't change port or usb
6. install twrp recovery on your phone with odin, download it from this post its working http://www.techdroider.com/2015/01/cwm-twrp-update-galaxy-core-i8262.html. chose PDA or AP option
7. when the odin displays pass disconnect phone
8. go into recovery mode- long press volume up+power+home all simultaneoulsy
when the logo of smasung appears leave the power key but keep pressing the volume up and home key
9. now you're in recovery mode, choose the download stock or custom rom from sd card,
there are other method too but i prefer this one, bcz its hasslefree and once you've installed custom recovery you don't need pc or any other thing to update or change your rom or whatever plus twrp supports touchscreen.
Thanks twrp and XDA for saving my money
WoW Alhamdulillah thanks brother :*
I have the same problem with you
You have saved my life and my money ^_^
ı have this problem but if ı do this will ı lose my data ??