While updating T-561 I lost access to screen, I can only see it in adb mode and on odin but gets stuck at 'Setup connection' when trying to push md5
(Device not rooted, OEM and USB debugging was off when I lost access to it)
Any ideas how I can recover it since I don't even see what is going on on the device?
For those who are interested to know how I fixed it, it was more like trial and error blindly to make phone boot into recovery. Volume down + Home + Power a few seconds and then quickly Volume up and check if it has gone into recovery mode.
Related
OK, so I flashed the wrong ROM today (I9000HVJH1) and the phone now boots into recovery everytime the battery is inserted. I have tried all the tricks to get back to download mode with no luck. The device is recognized by the USB in recovery and was able to push the root update file but can not get it to apply sdcard:update.zip (just sits there and doesn't respond to the power button unless i hold it). Interesting thing is when I plug the USB in and insert the battery, it never goes to charging, it boots into recovery.
Tried:
1. Plug USB
2. Hold vol up (and down but the keys are now backwards in recovery)
3. Insert battery
and
1. Power down (removed battery)
2. Hold vol up + down + power
and
1. Hold vol up (and down too for a few hundred times)
2. Hold power until Samsung logo then release
and
all combo's with and without the USB plugged into the phone.
Beside the tricks shown on the forum, can anything think of a way to get this phone into download mode instead of it constantly booting into recovery? ADB see's the device, just no root access or knowledge of how to get it to apply the update.zip that would root the device.
Thanks~!
http://forum.xda-developers.com/showthread.php?t=741027&page=3
Wrong section. This belongs in general...
Sent from my messenger rabbit
UPDATE!!
After going to T-Mobile on Monday to buy a new Vibrant, I started to think about how to get the "bricked" one working again. I was able to admit defeat for long enough to get a new one but was bothered that I couldn't fix my old one.
I started to think about what I could and couldn't do with the "bricked" one. It would constantly boot start to Android Recovery with error about CSC. No matter what combination of buttons pressed, held, release, the darn phone would never get back to a download mode. Since it could never boot into the OS, ADB seemed impossible. The GOOD news (as it turns out) was when it booted into recovery if I disconnected the USB and reconnected, my computer recognized it and Odin saw it on COM10. I began to look at the batch file for the one click root and noticed the line "adb reboot download". I had messed with ADB the day I screwed up the phone but always tried to do commands after typing "adb shell" and without super user access, I felt doomed. Last night I thought what the heck and powered up the old Vibrant and it went straight to recovery. After another 45 minutes of trying to manually put it into download mode I opened a command prompt and typed "adb reboot download" and the freaking phone rebooted into download mode!!!! So after flashing back to stock I now have fixed the phone
So for anyone who can't get their Vibrant to stop rebooting itself into recovery here is a simple breakdown of what I did.
1 - Power up phone (mine went straight to recovery)
2 - Un-plug the USB and plug it back in (computer should recognize the connection)
3 - Open command prompt and change to the directory that has adb.exe
4 - Type "adb kill-server" and then enter
5 - Type "adb reboot download" and then enter
6 - Phone should reboot into download mode and ready to flash
Make sure you have Odin open with the pit and pda file loaded as there seems to be only a short window of time in which the phone will accept the download and get the status bar moving. If you wait too long, repeat the steps above and start the flash quickly.
I hope this helps someone out that might be experiencing the same problem as me.
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
BrightHeart said:
I was running stock rooted Android KK 4.4.4 on Nexus 2012 Wifi Only with bootloader as unlocked. I attempted the Lollypop update 5.0.2 by OTA but it gave an error while installing and device rebooted to Kit Kat normally.....working fine. OTA was not getting done for some reason may be because i was rooted.
I downloaded the factory image nakasi-lrx22g-factory-2291c36b.tgz from google and attempted to flash it using Nexus Root Toolkit(v 2.0.2) with option "No Wipe Mode" as selected and then the device ran into fastboot mode... NRT run commands like erase system etc then the script gave an error "Failed" "remote -invalid state" while attempting to write bootloader. I thought that the problem is with "No Wipe" selected so i re-attempted it with "No Wipe" being unselected. BUt same error.
I searched the forum & found that the issue may be due to incorrect/corrupted bootloader. I replaced the bootloader-grouper-4.23.img which was in the factory image with the 4.23 bootloader taken from JWR66V as most people over XDA have said that its the working bootloader.
I had flashed the img downloaded from here - http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Flashing succeeded and Nexus Root Toolkit did not give error this time it said "OKAY" instead of "FAILED". But it did not proceed forward to flashing other files like system img etc. NRT was stuck at the Flash Bootloader - OKAY cmd.
I powered of the Tablet and Powered On again it showed "Booting Failed" at the Google Screen. I rebooted into Fastboot mode with "vol- and power" held together. It displayed the same screen as it did before i.e. displaying the information of Bootloader.
Product Name - Grouper
Variant - Not Defined Yet
HW Version - ER3
Bootloader version - 4.23
Baseband version - NA
Signing - Not Defined Yet
LOCK STATE = UNLOCKED
Then I read somewhere that after flashing the Bootloader img you have to run the bootloader by rebooting tablet with vol+,vol- and power button all held together.
I did that and wat i saw on computer screen was "APX device found" (((((
The device went into APX mode and since 2 days has not come out.
I tried pressing Power button for like 3mins with power adapter connected/disconnected by usb
I tried pressing vol- and power button for more than 5min. with system connected/disconnected with usb
Nothing worked...
I am wondering what took the device to APX because the bootloader was good one from "JWR66V". It was flashed with success by Nexus Root Toolkit. the device did run into fastboot mode once after flashing it. The Device went into APX after all the 3 keys "vol+ vol- and power" were pressed together. But according to key combo terms APX mode is activated when "Power" and "vol+" are pressed and it exits when "Power" alone is held for 15+ seconds.
What I feel now is that the device is in APX looping (similar to Bootlooping) due to some reason. Corrupted Bootloader can be one of that but its unlikely as flashing was successful and img used was authentic. One more reason of APX looping may be that nothing apart from Bootloader is present in it, no system no recovery. only bootloader is present.
Now what do I do to come out of APX ? Power button and Power+vol- etc not working tried them numerous times. It won't accept fastboot or adb commands as its in apx mode.
Its Out of Warranty so only 2 options left for me now
1. Battery Removal
2. NVFlash
I want to keep things simple so I am thinking of battery removal first. Does the battery removal reset nexus 7 ?
I have a feeling that its effect is same as the power button holding for 15sec. but will have to try. Although the Warranty is voided but will Asus people agree to provide paid service to me if i myself attempt battery removal by opening the back side of the device.
Incase this dont work I will move to nvflash
But I have a few questions regarding nvflash.
1. Does nvflash require blob n sbk even for an unlocked bootloader?
2. I can generate the SBK for my device using the CCSN number and try though but I want only a simple command which will reboot nexus into fastboot mode exiting APX mode.
any help will be appreciated.
Click to expand...
Click to collapse
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
shivambhai said:
U have done it in wrong way
U should have flashed the recovery and system and bootloader manually without nrt
Are able to detect your device via computer in fastboot mode
Click to expand...
Click to collapse
I used NRT normally as its directed in NRT's thread. Bootloader taken from "JWR66V" was flashed successfully but NRT didnot proceed forward. I powered of the tablet then pressed both volume plus & minus buttons along with power button simultaneously, I read somewhere that pressing all 3 butons is needed to start the bootloader, This resulted in device going in APX mode, although APX mode is activated by holding only vol plus and power button simultaneously. The device seems to be looped in APX i.e. not coming out of it.
It was detectable as a fastboot device earlier but after it went into APX its detected as an "Unknown Apx device" asking for driver, The Asus Transformer Pas driver is installable for it, but i doubt will it work in nvflash.
I jus need a little information about battery removal & nvflash. I have googled about them already but had a couple of queries which I have posted above.
Thanxxxx
Update
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
No idea brightheart
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
BrightHeart said:
Okay last night I attempted battery removal from the device. I took off the back panel of nexus 7 and disconnected the battery cable which is connected to motherboard socket. I reconnected it after 10mins and still no success. I removed it again and connected the device to computer by USB and I found something very strange. the computer detected the Nexus 7 as "Unknown APX Device" even after the battery was disconnected. I was wondering from where is the device drawing power to run? Is it by computer's USB port alone or is there any other power source in nexus7's motherboard like a CMOS cell is present in Computer's MotherBoard which keeps the clock ticking.
Whatever may be the case but it seems that APX Mode is capable of running in minimal power input.
Next test which I performed was to Hold the power button while it was connected to system by USB. After about 7-8secs the device powered off as the computer displayed USB device disconnected message and sound but it repowered on its own in next couple of seconds and again it was detected as "APX device" . Same result observed with simultaneous holding of volume minus+power button as well.
Now I have every reason to believe that device is hard bricked and looped in APX i.e. The Bootloader is corrupted or is not running due to some reason. The device has no option but to go in APX and sit there forever unless its flashed at low level.
I would like to give nvflash a try but i know that theres no1 yet who has made it success and then the only option remaining for me is to visit Asus service center and get some paid service done.
Query - If I visit Asus service center then will they perform software reprogramming i.e. Bootloader fixing or will they replace the hardware ? Incase if they replace the hardware then will they replace the whole board or just the memory unit(which contains Bootloader) from the board?
Experts here please put some light on this
Click to expand...
Click to collapse
Same Issue!
seanet1970 said:
Did you have any luck with this BrightHeart? I seem to be in the same boat now...
Click to expand...
Click to collapse
Looks like this problem is quite common and mostly affecting Nexus 7 2012 devices. Mine to got botched after a OTA update. Any possibilities of Google fixing this /RMA beyond warranty ?
Hi!
I have some interesting problem and I could not find any solution in web.
I have Samsung galaxy Tab 4 10.1 SM-T535 LTE.
For unknown reasons device went to "Device memory damaged" mode (white screen with blue notification) and only one button "Reset device".
Luckily this button to nothing (you can push on it as many times us you want - no reaction).
I tried to make soft reset (Power + volume down buttons) - no reaction.
Tried to lunch recovery mode (Power + volume up + home buttons), after that I get notification, that recovery mod is lunching, android error symbol appears (without any text) and device automatically reboots.
I tried to connect tab to PC, PC found the device, ODIN recognized it, but if I try to upload something, nothing is working (probably do to that, that I need to enabled download mode, but I cannot do it, because recovery mod not launching).
Maybe you have some suggestions.
I currently own an LG G6 AS993, and seeing as there is not going to be an OTA Pie update for the phone, I thought I'd go ahead and get a ROM instead. There's just one problem, and that is that I can't even get into the bootloader to unlock it.
Here's what I've tried:
1. Using ADB commands, adb reboot bootloader, adb reboot-bootloader, fastboot boot bootloader
The phone was recognized in adb devices, however, after entering these commands, the phone just booted normally back into android, like a normal restart.
2. Using the volume and power buttons. I held the volume up button and plugged in a cable that was connected to my PC, and it booted into 'Download Mode' and then proceeded to a "Firmware Update' screen. After pressing down the power button it brings me to another screen with the options to view some wifi details, 'Power Off', 'Phone Info', and 'Back', which brings you back to the "Firmware Update' screen.
I also tried the same but this time while holding down the volume down button, and it shows the phone booting for 2 seconds, and then turns off and proceeds to show the battery symbol with the amount of charge.
These are the only ways of getting into the bootloader I've seen for this phone, and they simply do not work, so if anybody could help that would be very much appreciated!
chauhan814 said:
I currently own an LG G6 AS993, and seeing as there is not going to be an OTA Pie update for the phone, I thought I'd go ahead and get a ROM instead. There's just one problem, and that is that I can't even get into the bootloader to unlock it.
Here's what I've tried:
1. Using ADB commands, adb reboot bootloader, adb reboot-bootloader, fastboot boot bootloader
The phone was recognized in adb devices, however, after entering these commands, the phone just booted normally back into android, like a normal restart.
2. Using the volume and power buttons. I held the volume up button and plugged in a cable that was connected to my PC, and it booted into 'Download Mode' and then proceeded to a "Firmware Update' screen. After pressing down the power button it brings me to another screen with the options to view some wifi details, 'Power Off', 'Phone Info', and 'Back', which brings you back to the "Firmware Update' screen.
I also tried the same but this time while holding down the volume down button, and it shows the phone booting for 2 seconds, and then turns off and proceeds to show the battery symbol with the amount of charge.
These are the only ways of getting into the bootloader I've seen for this phone, and they simply do not work, so if anybody could help that would be very much appreciated!
Click to expand...
Click to collapse
Hey Got same Phone LG G6 as993 and same problem... It wont get into unlock bootloader option after try several adb drivers... it only restarts. Dm me if any updates
Hello i am trying to root my 1year old heavy used phone . I am Stuck at the very first step.
Also it should be mentioned that it got a little bit wet by rain someday and then the volume down button was stuck (not mechanicly) it forced the volume setting to zero and had no sound.
I soft reset it . Than no change. had a hard time getting into recovery but i finally got there somehow i dont remember how.
Then hard reset it.No change....
After one day the volume key fixed itself and everything is working fine.
now after one month i was curious if i could root it. But i am not able to get into bootloader state.
I tried everything.
Debug options and oem bootloader unlock switch enabled, usb debugging enabled.
Usb adb says no permission (serial n visible)
Entering Recovery mode at power off state by
Pressing vol up and power button gets normal boot everytime but much faster logo visible at about 3sec.
pressing power + vol down = it takes 25sec
Booting normal .. and the same happens when pressing both vol keys.
I am releasing the keys at zte logo visible everytime
Something was strange : one time when i was trying something it bootlooped 3 times and then it was safe mode.
could there something in the volume button be broken? but the button work fine. I dont know.
Thanks for reading
update:
ok the permissions was a linux issue(start the adb-daemon with su), i can use adb now on this phone,
i can boot it in recovery now, but cant boot into bootloader
adb reboot bootloader leads to normal boot
in recovery, the reboot into bootloader option also normal boot