Related
Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)
anthraxx90 said:
Hi, need help with my tf300t, i was on latest cyanogenmod and twrp, after install rom manager i install cwm recovery for have autupdate and installation with cm10, after reboot to recovery it take me at twrp recovery, i reboot system and reboot again in recovery and now i'm stuck at asus logo, what can i do?
Tablet won't open the selection menu for usb recovery etc.
(If i must send it at asus support, unlock bootloader only invalidate the warranty asus or even that of the store where i buy it?)
(someone knows tell me about how much will it cost me?)
Click to expand...
Click to collapse
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager
tobdaryl said:
Do I understand you used rom manager to install cwm? If so you just flashed TF201 recovery ( cwm ) onto a TF300 unit.
Use this link as it was made just for this situation.
http://forum.xda-developers.com/showthread.php?t=1680570&highlight=rom+manager
Click to expand...
Click to collapse
can't access to recovery
anthraxx90 said:
can't access to recovery
Click to expand...
Click to collapse
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.
tobdaryl said:
I'll have to think a little about this problem. No recovery, no boot, no bootloader menu, correct?
While stuck on Asus logo try fastboot devices and adb devices, report.
Click to expand...
Click to collapse
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.
anthraxx90 said:
can't access to flash menu just asus logo and unlock bootloader on the top left of the screen.
Click to expand...
Click to collapse
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?
tobdaryl said:
Humor me!
Example:
I can run "adb logcat" and get logs long before unit completely boots or leaves the screen you are stuck on. Force power off by holding power till screen goes black power on, give one of the commands I gave above,. Do the same and try the other command. Report. You are pretty well trapped and we are looking for any way to process one command by adb or fastboot.
If neither of the above works we have a couple more option. but they will be handled much the same.
In looking at our posts I don't believe we are communicating very well.
Maybe someone else can come in and help you better.
Anyone?
Click to expand...
Click to collapse
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?
anthraxx90 said:
2 days ago i send my tf300 to asus but they called me this morning and ask for 150€ for repair (they told me: the flash memory must be change), i haven't this money, i take tablet to home this afternoon, there is a way to solve the problem by me without asus support? need help :crying:
Edit:I went to the center asus, and I taked my asus tablet, they told me that asus did that price (150€, i not accept that price and i take my tab to home), and that there may be a cable (I doubt it) that has the ability to connect your tablet to your PC even if bricked.
the tablet now is currently charging because battery is too low to poweron.
i hope you might help me. I'm desperate
The pc didn't recognize it in any way, try vol+ and power , vol- and power but nothing, can't access to flash menu and pc didn't recognize. how can i do?
http://forum.xda-developers.com/showthread.php?t=1766227 may help?
Click to expand...
Click to collapse
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!
tobdaryl said:
If you have cord plugged between pc and tablet and both powered on do you get anything if you use command ( adb devices )? I'm not talking about trying to get into any menu or using volume or anything else.
Just connect the cord between pc and tablet and give command.
You may have already done this but I'm not sure and it would be nice to know the message if the command fails!
Click to expand...
Click to collapse
What i must do exactly?
anthraxx90 said:
What i must do exactly?
Click to expand...
Click to collapse
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com
tobdaryl said:
connect powered tablet to pc and in terminal type - adb devices - tell me what response you get from command.
It may not work but is worth a try before you go farther.
If you have not set your path for adb you will need to cd into proper directory with terminal first before sending command. I can't even guess because I don't know your OS but since you had cwm you have used the terninal - Windows = cmd or command.com
Click to expand...
Click to collapse
I use windows 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://tinypic.com/view.php?pic=2rwn4nd&s=6
(on my pc in programs file i've an asus folder with driver usb)
ok i've done it http://tinypic.com/view.php?pic=1vptd&s=6
but no device are listed under: list of devices attached
anthraxx90 said:
I use windows 8
http://tinypic.com/view.php?pic=2rwn4nd&s=6
Click to expand...
Click to collapse
This shows us you are in your home directory and your os does not know where adb is located. You probably used fastboot to flash cwm to your tablet. Fastboot and adb are normally in the same directory and you need to cd to that directory as you did when you flashed cwm.
If you don't know where that is located you can search for adb or fastboot.
Sorry I don't have windows, I'm using Ubuntu on a mac (I don't even use mac but have it on an external drive if needed). We can figure it out if we are both patient.
So if the above does not give needed results tell me and we'll adjust.
Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.
anthraxx90 said:
Ok i've tried fastboot and adb but fastboot tell me:wait for device and adb devices can't recognize tablet, there are no device under the list of connected device.
I've tried fastboot reboot and adb reboot to test if the device was connected but nothing happened.
Click to expand...
Click to collapse
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.
tobdaryl said:
One step down. If you have tf300t on left side about one inch - 25.4 mm below sdcard there is a small hole (reset). With cord still plugged between pc and tablet, power on tablet and use a small paperclip to insert gently into hole. As you insert you will feel it stop, gently push slightly farther and you will feel a little spring.
This will cause your unit to restart and if we are lucky there will be a change in what happens with commands (adb - fastboot) and or what is displayed on the screen.
Click to expand...
Click to collapse
i've done the reset, but nothing change with adb and fastboot
anthraxx90 said:
i've done the reset, but nothing change with adb and fastboot
Click to expand...
Click to collapse
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.
tobdaryl said:
Only two things left that I know about. You previously listed a link http://forum.xda-developers.com/showthread.php?t=1766227 that might possibly work but at the position we are in currently if it doesn't work we won't know the difference and the drivers already on your pc that are known to work will be replaced so.
1.
I have seen a post somewhere that the case was removed and the battery disconnected and then reconnected and that allowed access to the bootloader menu by holding down volume while reconnecting the battery.
2.
Try the drivers listed above.
Videos for removing case for battery access
1.
http://www.firstpost.com/topic/orga...former-battery-video-KJihe-hpA4M-14773-4.html
2.
http://www.youtube.com/watch?v=9eOu4Y9D33Y
I don't like either choice but with no adb or fastboot access, no recovery, and no bootloader menu we are pretty well trapped.
Just thought of something I have read twice recently. Even though fastboot appears to not work give it the command two or three times. I think I would try this first. Since a stock blob contains rom and recovery I would try to flash stock 10.4.2.13 blob.
fastboot -i 0x0B05 flash system blob
wait here because this is a big file
fastboot -i 0x0B05 reboot
You would unzip stock 10.4.2.13 twice to get the blob. Place the blob into the directory where you found fastboot.
Click to expand...
Click to collapse
Ok i'll try to flash blob this afternoon at home, i hope it do something, cause i don't want open my tablet
Edit: i'm at home, the tablet's battery is low and it don't power on now, i to charge now and try
Nothing when i try to flash blob cmd is stop at waiting for devices.
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
mikaole said:
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
Click to expand...
Click to collapse
windows don't see the tablet, i've tried but nothing, no usb input sound, it doesn't recognize tf300, i've already driver installed on pc
This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:
Bump
Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .
have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options
Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.
yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
i've had good luck with mskip's toolkit in a similar situation
veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:
I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!
From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.
Hello,
I just came back from my honeymoon and all of my pictures are on my N4. Of course before I pull the pictures, I drop the phone is the screen is cracked and the touch does not work anymore.
I'm really desperate to get these pictures. I've read all over online but my problems are this with all of the help out there:
My phone is the latest 4.4.2 on T Mobile.
It has stock EVERYTHING (bought straight form google), and the USB debugger is not enabled. (next phone I get this is the first thing I'm enabling.
I've been trying to follow instructions online but a lot of items have changed between last year and Kit Kat now and some steps such as unlocking the bootloader seems to wipe out everything on my phone.
I've been trying to use ADB and Freeboot but really havent gotten anymore.
I've also read that I can maybe use a usb mouse to substitute and unlock my phone? USB OTG? How do I know if my nexus has that enabled?
I'm even considering getting a new screen so I can try to replace the current one and get my photos. I dont care what happens to the phone but the pictures are priceless to me.
Is there any thread or guide that incorporates 4.4.2? the more detail the better of course.
Much thanks in advance.
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Shubhamqweasd said:
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Click to expand...
Click to collapse
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
zhanism said:
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
Click to expand...
Click to collapse
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Shubhamqweasd said:
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Click to expand...
Click to collapse
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
zhanism said:
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
Click to expand...
Click to collapse
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
acejavelin said:
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
Click to expand...
Click to collapse
I have same problem with broken screen, i bought for 56$ full kit on ebay, no need separate glass from screen. took me 1h20min, never done before but what a relief seeing everything working
You do not need USB debugging to transfer files. On windows, open file explorer and with your nexus 4 connected it should appear on the left side as Nexus 4. Or if you have osx use http://www.android.com/filetransfer/.
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.
emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.
F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.
Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?
Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.
I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?
Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?
Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it