Related
How can this be fixed? I can still do the Vol Down + Power combination thing, but the phone will not load to my home screen via normal start up.
I have no idea how to fix this, seeing as it was caused by me applying a theme in Metamorph. I don't have SDK either...
I have a HTC Magic, 32B.
I'm trying to fastboot recover it right now, but even when my phone says FASTBOOT USB, the command prompt still says <Waiting for device>
I really need help.
I really need help right now, it's my only phone, and I'm not in the position to buy a new one.
I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
good post I'm sure this will help devs in the future
way to stay calm under pressure lol. good info.
Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip
Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though
Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.
Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.
I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.
I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?
I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework
may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!
I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement
http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing
Same thing here, was there any solution?
Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784
Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.
I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
georgepcde said:
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Good thought but no luck.
Thanks, though.
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
rgkjr1 said:
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Click to expand...
Click to collapse
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
smirneger said:
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
Click to expand...
Click to collapse
pmrmx774 said:
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
Click to expand...
Click to collapse
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
rgkjr1 said:
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
Click to expand...
Click to collapse
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
hey_joe said:
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
Click to expand...
Click to collapse
Thanks, hey_joe. I actually already tried that but decided to try again. This time it worked! I don't know what I did differently but bootloader is now unlocked!
Thanks, All!!!
Tablet ubislate 9ci hanging on bootloading
Dear sir/madam, I am new to this forum. I purchased a new tablet Datawind Ubislate 9ci. It is a 9 inch no-bluetooth tablet.
>Details:
>*.Android 4.1.1
>*.Rock chip RK2928
>*.KERNEL linux version 3.0.36 i was trying to install CWM through mobile odin and ROM manager but my tablet was not supported so i downloaded build.prop editor from google play and changed it to some other cwm recognizable model viz. Samsung, nexus etc. When i was doing the above mentioned procedure, suddenly my tablet is coming up to bootloading and hanging there only and not opening i tried to go to recovery by pressing power and vol but i am not getting recovery menu, i also tried to hard reset by pressing reset with a needle at the back but all in vain again hanging on bootloading i also tried press and hold power & vol- and several other combinations , all in vain so kindly help me and guide me Thank you
Hello there. First of all thank you for your support. I'm here because I have the same problem as OP, but first a little context.
I have already rooted my A700 before, without any difficulties. But after a crash, I restored it to factory and tried to redo the whole procedure.
So, here I am, USB driver installed (I had to modify android_winusb manually for windows to finally accept the drivers), adb up and running, adb reboot-bootloader executed and...
Acer screen, no text, just like the OP. And a yellow "Fastboot" device in my Device Manager window. So I'm stuck here. I've tried to uninstall/reinstall the google USB drivers to no avail, unlike OP. I can access the Acer recovery with the reboot recovery prompt, but I'm not confident enough to ignore the step in this tutorial.
Additional precisions : when the device is stuck with the Acer Logo (without text) trying to use a fastboot prompt (like oem unlock) only gives me the <Waiting for device> message.
I could use the Acer recovery to install a rom from external storage, but I'm unsure if it's a good idea to NOT use CWM or TWRP
Thank you, I'm starting to miss Android 4.4 (yeah, because the Acer update manager give an error 400)
Update : I did manage to access fastboot. Just as I had to modify android_winusb with the PID of my tablet when it was running, I also had to edit the file with the PID of the tablet waiting in fastboot. I didn't noticed they were different.
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
ibz100 said:
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
Click to expand...
Click to collapse
Your usb drivers are not installed correctly, reinstall the drivers and enable usb debugging in developer options. Check if you succeeded by typing in cmd (while the phone is in fastboot): fastboot devices. You should see a serialnumber if all went well.
Hi, @ibz100. It actually looks like your drivers are installed properly. At least your ADB drivers. You only use ADB while booted into the android OS, or from recovery. However, while you're booted into the bootloader (also known as fastboot mode) you'll want to use "fastboot" commands.
So boot back into the bootloader either the same way using ADB while booted into the OS, or from a powered down state hold Volume down(-) & Power keys. You can also use both volume keys + power to access the Nexus 5's secondary bootloader.
Once in fastboot mode, run the command
Code:
fastboot devices
If your serial number appears like it did for ADB devices, then your fastboot drivers are successfully installed. If not, then we need to get your fastboot drivers set up.
Read here if you need to install them. Feel free to reply here if you're having trouble installing them and I can help you through that as well.
Also useful: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If your drivers are properly installed, run the command "fastboot" without quotations to see a list of available commands to be used in fastboot. If you're still not sure what to do, just ask.
If you want to use ADB to apply the update.zip, boot into recovery mode (I'm going to assume you're using a stock recovery). Use the commands I mentioned above to get to the bootloader. Now use the volume keys to navigate from "Start" to "Recovery Mode" With Recovery selected, key the Power button. You should see a picture of an android with an exclamation mark with the text "No Command". From there hold down the Power button and tap Volume UP(+) once. This will boot you into stock recovery mode. From there use the volume keys to navigate to "Apply update from ADB". Power key to select.
Check out the Roll-up sticky guide by @rootSU for all the information you need to get yourself up and running.
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Again, if you need any more help just reply and let me know, I'm more than happy to help.
Try loading koush's universal adb drivers I was having the same problem but this solved it for me. Sidelosd worked a treat and running lollipop without problems so far...
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
ibz100 said:
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
Click to expand...
Click to collapse
Well I've had my fair share of driver issues. I blame my PC. Anyways, I know how frustrating it can be.
However going back to what I said before, since your ADB drivers are properly installed (being as your device ID showed up and reboot bootloader worked) I wouldn't think it's too far fetched that you already have fastboot drivers installed. Before you try deleting/reinstalling them, I would first boot into the bootloader and run the command "fastboot devices" (no quotes). If you device ID shows up in fastboot, there's no need to mess with your drivers.
Again, the reason ADB "stopped recognizing your device" is because you booted into fastboot mode. While you're in fastboot, you need fastboot commands.
If you boot back into the OS, or into recovery, ADB will recognize your device again. That's how it's supposed to be.
So power down the phone. Hold Volume Down(-) & Power until the phone boots into the bootloader and type;
Code:
fastboot devices
If your ID shows up in a similar fashion to the way it did in your screenshot, you're golden. Let us know how it goes! :good:
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
supwiddiss said:
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
Click to expand...
Click to collapse
nobody?