[Q] [A700] - Can't unlock bootloader-hangs on green Acer logo [SOLVED] - Acer Iconia A700 and A510

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.

Related

[Q] Unable to fastboot or recovery mode; just unlocked

Hi. I've recently bought my TF700 and upgraded to JRO03C.US_epad-10.4.4.25-20121228 (JB 4.1.1). Now I want to root my device, so I first unlocked the bootloader using the ASUS unlocker. That went fine, since it says "the device is unlocked" in the boot sequence. The device boots and works properly.
Now I wanted to get to the stock recovery mode for a backup, but it fails miserably. I get to the four icon menu (RCK, Android, USB, Wipe) and select RCK. Then an android icon with a blue rotating icosahedron in its chest apears for a couple of seconds and then a "dead" android with it's cover opened and a "!" enclosed in a red triangle. After a couple of minutes, the device reboots normally (I can force that by pressing down the power button for 10 seconds).
I tried to get to fastboot by choosing the USB icon, but it does nothing (just freezes in the four icon screen and stops responding to any other buttons); the PC doesn't see an USB device of any kind. I tried connecting the USB cable both before and after selecting the USB icon with no difference. I'm sure I have at least some good drivers because I can use adb with my device when the OS is running.
I'm new to this device, so I may be doing something wrong. Any suggestions? Thanks in advance.
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
_that said:
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
Click to expand...
Click to collapse
Thank you, _that. Whatever drivers it might need, I cannot install them because no USB device of any kind appears in my computer besides my keyboard. I think I should be getting "Starting Fastboot USB download protocol" or something. How can I get fastboot to work?
Sorry, it seems it was a USB port problem! I changed the port and the fastboot device is now available in my PC. Fastboot is now able to send commands like 'reboot' to my device.
Thanks for your clarification about the stock recovery mode, _that.

[Q] no adb and fastboot access - no root possible?

Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked
You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.
Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.
1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.
No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.
jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk

Nvidia Shield Tablet K1 stuck on Bootloader Info Screen / Bootloops -- Need help

Hey everyone. So some time ago I unlocked the Bootloader, rooted and flashed with custom ROM my Nvidia Shield K1 and flashed TWRP. All was going well untill I decided to flash another ROM with an app (which was stupid indeed) Long story short it seems now as if I have no ROM and no recovery and all I got is the "Bootloader info screen" or whatever its called.
So the only thing I can make it display is:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - Unlocked
Serial Number xxxxxxxxxxxxxxxxxxxxxxx
Press <Power> to select [...]
Continue
Fastboot Protocol
Recovery mode
Reboot
Poweroff
1. Using Continue does nothing, just says booting failed for like 100ms and goes back to where it was.
2. Fastboot Protocol just reboots the devices to the same thing after like 2 sec
3. Recovery mode same as Fastboot Protocol
4.Reboot and Poweroff does what it says
I've tried everything I could find online with it. No physical key combination can make it boot the ROM or TWRP.
I tried adb fastbooting with minimal adb and fastboot like Ive done times before with this Shield K1 and I cant make it see this device. ( "adb devices" wont list it)
I have tried using different USB ports, usb drivers, usb cables, PCs, fastboots and reinstalled everything multiple times and nothing changes.
I tried using any and every USB driver, ADB fastbooting Nvidia offers for this device.
The PC itself seems to detect the tablet just fine. Pluggin and unpluggin results in a notification and the android device is detected in Device Manager properly.
Powering off and on the tablet also results in a notification on the PC.
I have no idea what to do at this point and my last hope is this thread.
I had the same issue. Finally decided to reflash to stock and all is well

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.
Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse
Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.
I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?
'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!

I cant access twrp recovery

{
"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"
}
I recently unlocked my bootloader and flashed twrp. however when I try to boot into recovery it just keeps booting up as normal. Ive tried PWR & vol+ PWR & vol- and even PWR & Vol +- with no luck at all, I've even tried to re-flashed the recovery image. Cmd says it completes the command. I have no idea why it wont boot into recovery. Please help
xXsim00Xx said:
I recently unlocked my bootloader and flashed twrp. however when I try to boot into recovery it just keeps booting up as normal. Ive tried PWR & vol+ PWR & vol- and even PWR & Vol +- with no luck at all, I've even tried to re-flashed the recovery image. Cmd says it completes the command. I have no idea why it wont boot into recovery. Please help
Click to expand...
Click to collapse
Make sure you have the latest twrp. Download from here: https://eu.dl.twrp.me/maple/ the twrp-3.2.3-0-maple.img. Copy/move the image to your platform-tools. To flash the recovery use: fastboot flash recovery twrp-3.2.3-0-maple.img afterwards close fastboot and unplug your device then press and hold pwr and Vol- until the device vibrates (if you press and hold 'til twrp appears doesn't matter) and it should work.
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
AMHI said:
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
Click to expand...
Click to collapse
Well yours sounds like somc fastest driver is not being picked up. Recommend looking into ur fastboot drivers
lonewolfbtown said:
Well yours sounds like somc fastest driver is not being picked up. Recommend looking into ur fastboot drivers
Click to expand...
Click to collapse
I have tried several times to install and deinstall various drivers that seemed appropriate.
Tried it just again with the drivers from this link
gsmusbdrivers.com/download/adb-fastboot-drivers
(I am yet not allowed to write the complete link)
Installation process completed without errors but it doesn´t changed anything.
I am using Windows 10 and in the device manager I see the Sony driver ("Sony sa0116 ADB Interface Driver").
I also have a section with "Android Device" which contains "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface".
Should I see Fastboot drivers somewhere?
Remark: I also tried Flashtool.
When I start the software it says
"Device connected with USB debugging on
Connected device : Sony Xperia XZ Premium
Installed version of busybox : N/A
Android version : 9 / kernel version : 4.4.148-perf+ / Platform : 64bits / Build number : 47.2.A.8.24
Root access denied"
Adb interface is obviously for adb. Still sounds like a fastboot issue cause it'll say adb fastboot, fastboot device etc. When I install my drivers I try doing an advanced reboot and selecting disable driver verification so Google can bugger off and not fail my driver installs. If your having a driver issue that's where I would start. Also put phone in fastboot mode and run command fastboot devices and see what it says. If blank something is still wrong
AMHI said:
Hi,
I have a similar problem, searching for solutions now since days and have read tons of tutorials, but nothing helped so far.
Have unlocked my XP Premium, have put it into developer mode and activated USB debugging.
Have installed latest drivers and get a reply (<unlock code> device) when I type "adb devices" in the command window of the platform-tools directory. With "adb reboot bootloader" the phone goes into fastboot mode (blue led is on).
Downloaded the related / appropriate twrp image on my pc (into platform-tools directory) and typed "fastboot flash recovery twrp.img". Got the message <waiting for any device> and nothing else happens.
SuperSU App on my phone says "Root undetected".
Hope you have an advice......
Click to expand...
Click to collapse
Try doing this when you have your phone in fast boot and connected to your computer:
1. Go into devices manager and find the 'Android phone' icon
2. Right click on it and select 'update driver software'
3. Now select 'browse my computer for driver software'
4. Then select 'Let me pick from a list of device drivers on my computer'
5. Then double click on 'Android bootloader interface' and press OK.
I think that should do it I had a similar problem.
jaskaranb.jb said:
Try doing this when you have your phone in fast boot and connected to your computer:
1. Go into devices manager and find the 'Android phone' icon
2. Right click on it and select 'update driver software'
3. Now select 'browse my computer for driver software'
4. Then select 'Let me pick from a list of device drivers on my computer'
5. Then double click on 'Android bootloader interface' and press OK.
I think that should do it I had a similar problem.
Click to expand...
Click to collapse
Today I had the time for analyzing further with my phone.
Thanks lonewolfbtown for your suggestions.
I started with jaskaranb.jb´s tip first because is seems easier to do.
And: SUCCESS!!!!
I finally now got a reply when preforming fastboot commands.
I am really happy because now it seems I am almost done!
Only drawback is that I now get ´Flashing is not allowed in Lock State´ after I carried out the command "fastboot flash recovery twrp.img" (where twrp.img is the appropriate twrp image for this phone).
The phone is definetly bootloader unlocked. I more than doublechecked this during the last weeks in the service menue (*#*#7378423#*#*).
AMHI said:
Today I had the time for analyzing further with my phone.
Thanks lonewolfbtown for your suggestions.
I started with jaskaranb.jb´s tip first because is seems easier to do.
And: SUCCESS!!!!
I finally now got a reply when preforming fastboot commands.
I am really happy because now it seems I am almost done!
Only drawback is that I now get ´Flashing is not allowed in Lock State´ after I carried out the command "fastboot flash recovery twrp.img" (where twrp.img is the appropriate twrp image for this phone).
The phone is definetly bootloader unlocked. I more than doublechecked this during the last weeks in the service menue (*#*#7378423#*#*).
Click to expand...
Click to collapse
I had the same issue unfortunately it does mean ur bootloader is locked. You can check sony's website to see how to unlock it. The *#*#7378423#*#* tells u if you can unlock it or not if it says yes then your phone has the ability to be unlocked. But big WARNING before unlocking bootloader - JUST MAKE SURE TO DO UR RESEARCH ON DIFFERENT FORMS HOW TO UNLOCK IT. Because I unlocked it through sony's website and I rushed through it, so now my drm keys got deleted (with this some phone features go missing like video enhacment, camera only takes green photos and some more features that I'm not aware of). I fixed my camera by flashing Android 9.0 stock firmware on my phone (idk if other features are back).
jaskaranb.jb said:
I had the same issue unfortunately it does mean ur bootloader is locked. You can check sony's website to see how to unlock it. The *#*#7378423#*#* tells u if you can unlock it or not if it says yes then your phone has the ability to be unlocked. But big WARNING before unlocking bootloader - JUST MAKE SURE TO DO UR RESEARCH ON DIFFERENT FORMS HOW TO UNLOCK IT. Because I unlocked it through sony's website and I rushed through it, so now my drm keys got deleted (with this some phone features go missing like video enhacment, camera only takes green photos and some more features that I'm not aware of). I fixed my camera by flashing Android 9.0 stock firmware on my phone (idk if other features are back).
Click to expand...
Click to collapse
Thanks for your answer.
I am absolutly sure that my phone ist unlocked because exactly this keeps it saying everytime I re-checked it through the service menue (as I wrote in my last sentence). In fact this part I did over and over again.
Regarding the photo and video issue you mentioned I noticed a lot of helpful links during my comprehensive search through all kind of forums regarding my locked issue.
AMHI said:
Thanks for your answer.
I am absolutly sure that my phone ist unlocked because exactly this keeps it saying everytime I re-checked it through the service menue (as I wrote in my last sentence). In fact this part I did over and over again.
Regarding the photo and video issue you mentioned I noticed a lot of helpful links during my comprehensive search through all kind of forums regarding my locked issue.
Click to expand...
Click to collapse
Does your phone show a dialogue when you restart it saying ur phone bootloader is unlocked?
jaskaranb.jb said:
Does your phone show a dialogue when you restart it saying ur phone bootloader is unlocked?
Click to expand...
Click to collapse
No, it starts with the sequence I know from beginning.
First the white screen with "Sony", than whithe screen with "powered by android", then white screen with Xperia logo.
Finally got it!!!
The solution was: due to my fastboot driver problems at the beginning of the whole unlock thing I haven´t really inserted the unlock code.
So now I did and everything is fine: now I do have this warning message about booloader unlock when I start the phone.
Thanks for your support!!!
Hi guys,
i have the same problem. I have unlocked my bootloader (flash screen prompted at the beginning) i flashed maple img (G8141) but i cannot access TWRP neither on PC nor on smartphone. It stacks at sony logo and i have to restart manually.
Tried to update drivers but no success.
Any ideas on how to solve it?
Nereoz said:
Hi guys,
i have the same problem. I have unlocked my bootloader (flash screen prompted at the beginning) i flashed maple img (G8141) but i cannot access TWRP neither on PC nor on smartphone. It stacks at sony logo and i have to restart manually.
Tried to update drivers but no success.
Any ideas on how to solve it?
Click to expand...
Click to collapse
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
AMHI said:
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
Click to expand...
Click to collapse
thank you for your reply. I have tried that combination (plugged and unplugged to PC) but no success.
I have done the same procedure to a Z5 Premium few weeks ago, everything working.
Nereoz said:
thank you for your reply. I have tried that combination (plugged and unplugged to PC) but no success.
I have done the same procedure to a Z5 Premium few weeks ago, everything working.
Click to expand...
Click to collapse
If the TWRP is successful flashed on your phone than it shut worked - unplugged - at described.
At least this works for me (it really takes some time).
Otherwise you might need to use adb / fastboot commands to access the phone again.
AMHI said:
To access TWRP on the phone after flashing, I press Power and Volume- button as long as I see the TWRP screen.
This could take some seconds (10 - 20), depends on the state the phone is in at that time.
Click to expand...
Click to collapse
AMHI said:
If the TWRP is successful flashed on your phone than it shut worked - unplugged - at described.
At least this works for me (it really takes some time).
Otherwise you might need to use adb / fastboot commands to access the phone again.
Click to expand...
Click to collapse
I finally made entering twrp, doing nothing special, maybe I just needed a fresh reboot.
Actually I am experiencing problems with rooting, SuperUser did not work so i gave a try with magisk but to get it work I had to flask a stocke kernel that resulted in a wrong build. Now i have to flash a new ROM and start all over ..
Nereoz said:
I finally made entering twrp, doing nothing special, maybe I just needed a fresh reboot.
Actually I am experiencing problems with rooting, SuperUser did not work so i gave a try with magisk but to get it work I had to flask a stocke kernel that resulted in a wrong build. Now i have to flash a new ROM and start all over ..
Click to expand...
Click to collapse
No you dont, flash a kernel that matches your fw and flash magisk again
Beetle84 said:
No you dont, flash a kernel that matches your fw and flash magisk again
Click to expand...
Click to collapse
Flashed with newflasher and installed magisk. Everything ok now
So I have tried installing twrp on my G8141. After fastboot boot recovery.img, phone rebooted and hangs at SONY logo. My problem now is that no key combination whatsoever seems to do anything now. What can I do? Wait for the battery to drain and then restart?

Categories

Resources