!!!PLEASE HELP THANK YOU!!!
Hello everyone thank for taking your time to read this and for hopefully helping me out....
It started a week ago when I had notice that when I updated my Tablet (32gb LTE UK) I forgot to redo the Supersu function and TWRP so i went ahead and rebooted my devices and installed TWRP via adb fastboot not a problem there and i got into custom recovery and install Supersu and restarted the tablet like all the other 20+ times But this time around it stayed on the boot logo and thats as far as i get.
Now having done this many time before on this and my two other shield tablets and samsung phones I'm at a loss, as now when i boot into the bootloader with the options for me to use ADB it will not find my device. I've even gone ahead a installed the rather large and normally unnecessary Android Studio with SDK Manager and tried it with the google drivers instead of the shield driver that I've re-download just in case they had been updated.
* Tablet stays on Boot logo
* I can boot into Bootloader
* If i select fastboot screen goes blank but is on
* If I select Recovery tablet boots with Android laying down as if Sick
* I no longer had a Custom recovery (TWRP)
* ADB does NOT list my attach device
Sorry if I've gone one but as you can tell I'm normally good with this kind of stuff and have looked around for a fix but all have failed so far please if someone can help me that would be the Brilliant.
Cheers Chris.
check device manager in windows while tablet is in bootloader and usb connected. look for a device called fastboot and see if it has an exclimation. Download the atteched zip and look at the images for a visual guide on what to install for the drivers.
any solution??
Related
Hi,
A friend gave me a Storage Options Scroll 7" Model 51624 (TCC8902) with 2.1.
I found that cyanogen has a 2.3 Rom for this device so I tried to flash it.
I flashed the clockwork recovery and did my back up. Then I downloaded the rom from cyanogen and installed.
What was my surprise that when I restarted it got stuck on the main screen with the logo "scroll Storage Options"
I tried to enter the recovery but doesn't work!!!
I think my error was the rom I choose for flashing.
I used the Storage Options Scroll 7" resistive 8K, and I know now that mine is the same one but the resistive 4K.
I though I could do something if I could use the Adb commands and some inspiration but the problem is that my computer doesn't recognize the device (Android in yellow on device manager). I installed the Android SDK that has the google usb driver but still not working. I tried the VTC 5.0.0.1 drivers too but no luck either.
I desperately need some help to install the boot recovery and then I'll flash the right rom.
I use windows 7 x64 and a laptop with windows xp 32.
I've been reading the thread http://forum.xda-developers.com/showthread.php?t=1101094 but has 163 posts and I have to say that I didn't read all of them. Anyway I did a search about bricked scroll and didn'f find anything. If someone knows where to point me at I'll be very gratefull. I appologize if my posts is already solved somewhere.
Thanks in advance
there is a guide on getting android adb set up on the pc with modified drivers somewhere...
1st things 1st though, have you tried holding vol up while turning it on to get into recovery?
as long as you installed the custom recovery correctly (which im sure you did if you managed to install another rom), then you should have no problem getting into it.
unless, that is, you dont have any volume buttons to get into recovery / they dont work!
Sent from my MB860 using xda premium
To flash the cyanogen rom I had to enter the clockwork recovery with the power+vol up. So first thing I did after realised it wasn't going to load the rom was to restart the tablet into recovery but it doesn't work.
That's why I was thinking the posibility of flashing clockwork recovery again through the adb commands or maybe the boot.img (I think this img is the one responsible for boot). But as I said my computers don't recognize the device. Both says Android with the yellow warning.
I'm looking for this modified drivers but can't find them. any web site address?
I have downloaded the firmware from Storage options but as I cant enter into the recovery I can flash it.
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.
could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.
Did you get this problem resolved? I have the exact problem with the exact phone!!!
thank you very much
Hi --
I have a Samsung Nexus S that I bought used for development purposes.
I ended up using it temporarily as my phone so when that was ended I decided to do a factory reset of the device.
However, it did not succeed! I wound up with the green Droid lying down with the red triangle. I've tried various ways to reboot the device but it appears there is no ROM for the device to load up.
I am also unable to get ADB to recognize the device. It certain situations it will appear in my Device Manager (Windows 8.1 64-bit)
I see options to load a ROM via USB or "ADB sideways" from the recovery menu. However, since I can't get ADB to recognize the device and there isn't a micro SD slot, how do I get a new ROM on to this device? Is it even possible?
I only paid $40 for the phone on eBay but would like to return it to a usable development phone if possible.
Thanks
Rich
HI --
Okay I did discover that I can access the device via Fastboot so I guess I just need help on where to download the right ROM(s) to flash to the device?
Rich
instructions and needed files are here
developers.google. com/android/nexus/images
p.s. since I cant post links yet, I had to put an empty space in front of .com
Thanks so much.. I'll give that a shot.
Rich
let us know if you were succesfull or not
It should be quite straightforward. Let us know if assistance is needed.
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!
Hey folks,
I'm rather embarrassed that I have to ask for help here, but here we go:
I wanted to update my Moto G (1st gen) to Lollipop 5.1 (via this thread: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) and after toying around with it for a few hours got frustrated and did some stupid things, which I'm also having a hard time to remember.
From what I recall, I managed to flash the "GPE 5.1 ROM (Optimized) v1.1" ROM via TWRP, but when booting the phone got stuck on the BOOTLOADER screen for about 1 1/2 hours, after which I decided to turn off the phone.
After that I frustratedly started fiddling around in TWRP and wiped system, cache and some more things (derp :silly: ) and well... ever since then I'm trying to get a new ROM on my SD card, but I can't push via adp because my device is not found.
Here's the facts
- When I try to regularly boot up my phone, the Warning Bootloader unlocked sign appears
- I can access the fastboot screen on my phone (AP Fastboot Flash Mode (S) 41.11), the one where it says normal powerup, recovery, factory, barcodes, bp tools and qcom. When I connect via USB it says USB connected.
- I can get access the recovery rom TWRP (v2.8.5.0)
- When I try to push a ROM to my sdcard command line tells me "error: device not found".
aaand that's it. I really hope I didn't brick my phone.
I'm on Windows 7 x64 and I would really appreciate the communities help. After that I'll show myself out and leave my phone working for a while hopefully.
edit: one more thing. my phone gets recognized as "Fastboot falcon S" in windows when I plug it in while in fastboot flash mode and as XT1032 when TWRP is booted. obviously it doesn't get recognized as a volume in Windows Explorer, or I would have already transfered another rom on the SD card by now.
edit 2: I also tried connecting the phone via another windows 7 x64 laptop now. installed motorola device manager & minimal adb and fastboot, but same thing there. :|
edit 3:ISSUE RESOLVED for now. I used this: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 and it worked like a charm. Thanks everyone.
@covecove until there is fastboot, there is hope.