Used the tablet for the first time in years, was working fine, rooted, unlocked bootloader, opened goomanager and clicked reboot into recovery and when my tablet rebooted it got stuck on the Asus splash screen.
I can however get the tablet recognized by my laptop in device manager as Asus Transformer Prime APX Interface.
Is it bricked for good? No I don't have a copy of the NVflash or whatever it is. I did at some point but the computer that was on is long gone....
I'm not sure if this will work for you...but you can try using the small pinhole reset button that's near the micro sd card. Just use a needle or paperclip to press down the reset button until the tablet restarts. I believe it just forces a soft reset...which will hopefully let you get past the splash screen.
The person in this post, (http://forum.xda-developers.com/showpost.php?p=61779883&postcount=12), said it worked for him in a similar sounding situation. Hope it works for you.
mattnmag said:
I'm not sure if this will work for you...but you can try using the small pinhole reset button that's near the micro sd card. Just use a needle or paperclip to press down the reset button until the tablet restarts. I believe it just forces a soft reset...which will hopefully let you get past the splash screen.
The person in this post, (http://forum.xda-developers.com/showpost.php?p=61779883&postcount=12), said it worked for him in a similar sounding situation. Hope it works for you.
Click to expand...
Click to collapse
No luck but thanks for trying
scottrod said:
Used the tablet for the first time in years, was working fine, rooted, unlocked bootloader, opened goomanager and clicked reboot into recovery and when my tablet rebooted it got stuck on the Asus splash screen.
I can however get the tablet recognized by my laptop in device manager as Asus Transformer Prime APX Interface.
Is it bricked for good? No I don't have a copy of the NVflash or whatever it is. I did at some point but the computer that was on is long gone....
Click to expand...
Click to collapse
You should be able to format the tablet and then flash a new recovery console using 'Minimal ADB and Fastboot' and then flash a new ramp via the newly installed recovery console.
NP
Nektopoli said:
You should be able to format the tablet and then flash a new recovery console using 'Minimal ADB and Fastboot' and then flash a new ramp via the newly installed recovery console.
NP
Click to expand...
Click to collapse
But how am I supposed to get Minimal adb/fastboot to see my device if I can't get to the fastbootscreen? the only way my laptop detects the tablet is by pressing power+volume up and that just detects in APX interface
scottrod said:
But how am I supposed to get Minimal adb/fastboot to see my device if I can't get to the fastbootscreen? the only way my laptop detects the tablet is by pressing power+volume up and that just detects in APX interface
Click to expand...
Click to collapse
Ok at this point you send it the command: adb reboot-bootloader
to see if it will 1)get the command and 2)execute the command
we know it's bricked but being about to send it command and have it attempted to execute them allowed me to wipe the recovery partition and flash a new TWRP recovery console.
Once you get a working recover console on the tablet you can flash a new ROM.
I am assuming you are on the correct bootloader and the device is unlocked and rooted.
NP
Nektopoli said:
Ok at this point you send it the command: adb reboot-bootloader
to see if it will 1)get the command and 2)execute the command
we know it's bricked but being about to send it command and have it attempted to execute them allowed me to wipe the recovery partition and flash a new TWRP recovery console.
Once you get a working recover console on the tablet you can flash a new ROM.
I am assuming you are on the correct bootloader and the device is unlocked and rooted.
NP
Click to expand...
Click to collapse
But the problem is I can't get into ADB or fastboot. Only APX mode. If I hold power+Volume up my pc detects the tablet in apx, if I reboot normally the tablet like stated before gets stuck on the ASUS logo screen. Sending this command does nothing and also adb devices does not list the tablet.
I was however running into issues getting my laptop to detect my tablet even before this issue and it wouldn't show up under adb devices then aswell.
I was still able to send commands with out the USB symbol on my tablet, you so have to get your laptop to see the tablet, are you running Window 7 or 8 or 10?
NP
Nektopoli said:
I was still able to send commands with out the USB symbol on my tablet, you so have to get your laptop to see the tablet, are you running Window 7 or 8 or 10?
NP
Click to expand...
Click to collapse
Windows 10, so when you say you were still able to send commands what was displayed on the screen on your tablet? Was it the black screen in APX mode?
I send the 'adb reboot bootloader' command, it rebooted the tablet which was bricked at the time. I got the 'unrecoverable boot error'.
I then held the VOL button down while holding the POWER button until it displayed the bootloader screen [The one with the green 'RCK, Android & Wipe Data' symbols in the center].
From there I was able to send fastboot commands erasing the RECOVERY partition and then flashed the correct TWRP recover console.
Once you get a working recovery console you can use it to flash a new ROM and associated ZIP files.
NP
Yes but when you sent the adb command what state was your tablet in? What was on the screen?
It was a few months ago but I believe it was the bootloader screen, this one;
{
"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"
}
NP
Nektopoli said:
It was a few months ago but I believe it was the bootloader screen, this one;
NP
Click to expand...
Click to collapse
Yeah it can't get that screen....
Do you get the fallen over dead android with the red exclamation triangle?
NP
Nektopoli said:
Do you get the fallen over dead android with the red exclamation triangle?
NP
Click to expand...
Click to collapse
No these are the only 2 screens I get....
1. Volume Up+ Power: Black screen. Detected by PC in APX mode
2. Volume Down+ Power: Asus Splash Screen. Not detected under device manager as far as I can tell.
Sorry but I don't know what 'APX mode' is and when I hold [VOL UP] & [PWR] the tablet vibrates and then nothing, blank screen.
NP
---------- Post added at 06:44 PM ---------- Previous post was at 06:38 PM ----------
Did you determent if the command: adb reboot bootloader
will reboot the tablet in APX mode?
NP
Related
I have done everything by the book
i have windows 8.1 installed it did not work , then i did a dual boot and installed windows 7 , still not working
Debugging also activated
I have installed the driver that came with flashtool and the z ultra driver
But whenever I hold the up vol key all it says is flash mode
Pls someone help me , I just got the phone , Never had this problem with all my old samsung !
Also i manage to downgrade they phone to 4.2.2 Build 14.1.B.1.532 C6833,
Also its rooted
and its say my bootloader is safe to unlock
Vol up is fast boot, vol down is flash mode.
After rooting the next step should be to back up the TA partition
Sent from my Xperia Z Ultra using Tapatalk
blueether said:
Vol up is fast boot, vol down is flash mode.
After rooting the next step should be to back up the TA partition
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
I already pressed the vol up button , its not going into fastboot mode
At the moment what are you trying to do that needs fastboot?
What steeps have you done
Can you post the output from flashtool when you have the phone powered off then connect it to the pc holding the vol up key
Sent from my Xperia Z Ultra using Tapatalk
blueether said:
At the moment what are you trying to do that needs fastboot?
What steeps have you done
Can you post the output from flashtool when you have the phone powered off then connect it to the pc holding the vol up key
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
Here
{
"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"
}
it never goes into fastboot , I need to flash kernel
Try like this:
Turn off your phone with the cable disconnected, open the Flashtoll, go to "flash device" and choose "fastboot mode" when the dialog box open press the Volume Up and connect the phone to usb cable, a blue light will appears, choose "Select kernel to flash" go and get the kernel..
i have done like this lots of time and always worked...
Hope this help...
Lc1975 said:
Try like this:
Turn off your phone with the cable disconnected, open the Flashtoll, go to "flash device" and choose "fastboot mode" when the dialog box open press the Volume Up and connect the phone to usb cable, a blue light will appears, choose "Select kernel to flash" go and get the kernel..
i have done like this lots of time and always worked...
Hope this help...
Click to expand...
Click to collapse
still not working I have tried every single thing i know ?
Open ADB and type "adb reboot bootloader". It should kick it into fastboot.
Sent from my C6833 using Tapatalk
When you press the Volume Key Up and plug the Usb cable what happen with the phone?
Does the phone turns On normally or do nothing? What colour appears on the led?
LordManhattan said:
Open ADB and type "adb reboot bootloader". It should kick it into fastboot.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I tried what you said and it still did not work !!! here is a screenshot
I just turned of the dvice but never took it to fastboot mode , it stayed on flashboot mode
Lc1975 said:
When you press the Volume Key Up and plug the Usb cable what happen with the phone?
Does the phone turns On normally or do nothing? What colour appears on the led?
Click to expand...
Click to collapse
When i press the volume up the it goes to flashmode mode no matter what , The greenlight comes up instead of a blue light
Also the phone keeps going ofd and on back into flashmode
flashmode the LED will go orange -> green -> off Yes?
Does the phone stay in flashmode, the last line of your last post confuses me...
At this point I would try to flash a new FTF incase the bootloader is corrupt. Have you tryed to do a factory restore from Sony PCC?
sigmaphi said:
I tried what you said and it still did not work !!! here is a screenshot
I just turned of the dvice but never took it to fastboot mode , it stayed on flashboot mode
Click to expand...
Click to collapse
ADB doesn't even recognize your device. Have you given ADB acceess to your device? When you connect your Ultra to your computer and type "ADB devices" it should ask you for permission on your Ultra. Grant it access and type "adb devices" again. Do you see a string of numbers etc.? If yes, that's your Ultra.
Navigate to the ADB folder where fastboot.exe is. Hold SHIFT and right click the space around the files (not on the files) and click "open command window here" or whatever it says. Then type "fastboot reboot bootloader". BOOM (in theory)
LordManhattan said:
ADB doesn't even recognize your device. Have you given ADB acceess to your device? When you connect your Ultra to your computer and type "ADB devices" it should ask you for permission on your Ultra. Grant it access and type "adb devices" again. Do you see a string of numbers etc.? If yes, that's your Ultra.
Navigate to the ADB folder where fastboot.exe is. Hold SHIFT and right click the space around the files (not on the files) and click "open command window here" or whatever it says. Then type "fastboot reboot bootloader". BOOM (in theory)
Click to expand...
Click to collapse
Its does see my my phone but it will never go into fastboot , it goes to flashmode
it just stay at waiting for device
blueether said:
flashmode the LED will go orange -> green -> off Yes?
Does the phone stay in flashmode, the last line of your last post confuses me...
At this point I would try to flash a new FTF incase the bootloader is corrupt. Have you tryed to do a factory restore from Sony PCC?
Click to expand...
Click to collapse
I think you might be right with the bootloader been corrupt , but i did a full factory reset today and it still will not go into bootloader
and the phone keep going off and on when it in flashboot mode
sigmaphi said:
Its does see my my phone but it will never go into fastboot , it goes to flashmode
it just stay at waiting for device
Click to expand...
Click to collapse
That is weird... It should work, but it doesn't...
Sent from my Desire HD using Tapatalk
Any tip guys ? Would be nice , Thanks
sigmaphi said:
Any tip guys ? Would be nice , Thanks
Click to expand...
Click to collapse
I'm really grinding my brain here, but I can't think of any other ways of doing it. If only we were neighbours!
Sent from my Desire HD using Tapatalk
LordManhattan said:
I'm really grinding my brain here, but I can't think of any other ways of doing it. If only we were neighbours!
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks , Also there is something i notced about the phone , if its off and i plug the usb to the pc , it goes on & off every few seconds into flashmode on its own without me free the up or down vol button ,
and since i cannot get into fastboot i cannot even unlock the bootloader
I have fresh install stock rom and repaired with Sony companion , No luck at all
Am thinkin of retuning the phone to the shop where i bought it and tell them I want a new phone,
If you know any tip to tell them so i get a new one it would be nice
sigmaphi said:
Thanks , Also there is something i notced about the phone , if its off and i plug the usb to the pc , it goes on & off every few seconds into flashmode on its own without me free the up or down vol button ,
and since i cannot get into fastboot i cannot even unlock the bootloader
I have fresh install stock rom and repaired with Sony companion , No luck at all
Am thinkin of retuning the phone to the shop where i bought it and tell them I want a new phone,
If you know any tip to tell them so i get a new one it would be nice
Click to expand...
Click to collapse
I would definitely try to get a new one, but that'll depend when you bought it. They'll also try to get it repaired instead of giving you a new one, but i'm not updated on German consumer laws, so i can't really tell you what rights you have, but again, time is important here, so you'll need to tell me how long it has been since you bought it. Also, it might be a little tricky to tell them that you were trying to enter fastboot so you could unlock the bootloader and void your warranty, lol. You can either go down that road and act like a pro, or you can act stupid and see how far that takes you
My kindle is brick and reaches the recovery mode but will not start, after trying to install c11
salvo22 said:
My kindle is brick and reaches the recovery mode but will not start, after trying to install c11
Click to expand...
Click to collapse
Please, if you want help, you need provide a lot more information, before you can get any help!
Which firmware is on it?
Which recovery is on it?
If Safestrap recovery, did you use extra slot or stock rom before brick?
Which rom did you have on it before brick?
After kindle starts you see gray kindle logo, gray orange kindle logo, or blank screen?
Is kindle restarting itself, or only stops on kindle logo and then nothing until you turn it off?
If you remember try to describe exactly steps leading to problem, thanks.
hdx 7 thor official frirmware
jeryll said:
Please, if you want help, you need provide a lot more information, before you can get any help!
Which firmware is on it?
Which recovery is on it?
If Safestrap recovery, did you use extra slot or stock rom before brick?
Which rom did you have on it before brick?
After kindle starts you see gray kindle logo, gray orange kindle logo, or blank screen?
Is kindle restarting itself, or only stops on kindle logo and then nothing until you turn it off?
If you remember try to describe exactly steps leading to problem, thanks.
Click to expand...
Click to collapse
Hello everyone, I was hacking my hdx hoping to put the CM11, but unfortunately in the build.prop change the inevitable happened.
now I can only go to stock recovery, the tablet starts, logo kindle fire gray and then black screen, I do not know how to go to fastboot, but I think I need a little ...
does anyone know how to fix this mess?
thanks in advance and sorry for my carelessness
soon will post a video on you tube
Better just answer the questions, then posting a video on youtube
futzmaster said:
Better just answer the questions, then posting a video on youtube
Click to expand...
Click to collapse
Kindle HDX 7 Thor Brick (you tube searc)
https://www.youtube.com/watch?v=FRw_AjwSdQs&feature=youtu.be
salvo22 said:
Kindle HDX 7 Thor Brick (you tube searc)
https://www.youtube.com/watch?v=FRw_AjwSdQs&feature=youtu.be
Click to expand...
Click to collapse
Thanks, but you still need to answer more questions, so we can get the picture of what happened:
Which official amazon FW you had on Kindle? 4.x.x, 3.2.7-8, 3.1.0, or?
Did you have Safestrap recovery installed? If yes, did you use stock slot, when you edit build.prop, or rom slot?
Is kindle restarting itself, or only stops on kindle logo and then nothing until you turn it off (this is not clear from video you posted)?
If you remember try to describe exactly steps leading to problem, thanks.
Until you answer these questions, you can try this:
The only thing we can try (AFAIK) requires working adb connection and it must be working from stock recovery, because its the only part of system you can use right now - so enter recovery and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try enter:
adb devices
it should return:
list of devices attached
xxxxxxxxxxxxx recovery
if you can achieve this, we can continue. If you dont have adb setup on your pc, here is how to for windows: Setting up the ADB Driver for Kindle Fire Devices
jeryll said:
Thanks, but you still need to answer more questions, so we can get the picture of what happened:
Which official amazon FW you had on Kindle? 4.x.x, 3.2.7-8, 3.1.0, or?
Did you have Safestrap recovery installed? If yes, did you use stock slot, when you edit build.prop, or rom slot?
Is kindle restarting itself, or only stops on kindle logo and then nothing until you turn it off (this is not clear from video you posted)?
If you remember try to describe exactly steps leading to problem, thanks.
Until you answer these questions, you can try this:
The only thing we can try (AFAIK) requires working adb connection and it must be working from stock recovery, because its the only part of system you can use right now - so enter recovery and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try enter:
adb devices
it should return:
list of devices attached
xxxxxxxxxxxxx recovery
if you can achieve this, we can continue. If you dont have adb setup on your pc, here is how to for windows: Setting up the ADB Driver for Kindle Fire Devices
Click to expand...
Click to collapse
thanks for the 'interest:good:
kindle-13.3.0.9
answer all the questions and provide as much informations as you can
futzmaster said:
answer all the questions and provide as much informations as you can
Click to expand...
Click to collapse
So I wanted to install the official version
update-kindle-13.3.1.0_user_310079820.bin
not installed then I changed on build.prop code from 300079820 to 310079820 because TWRP Recovery 2.8.1.0 - Thor does not work on os update-kindle-rooted 13.3.0.9 restarted once it is no longer party os
ADB and disabled
salvo22 said:
So I wanted to install the official version
update-kindle-13.3.1.0_user_310079820.bin
not installed then I changed on build.prop code from 300079820 to 310079820 because TWRP Recovery 2.8.1.0 - Thor does not work on os update-kindle-rooted 13.3.0.9 restarted once it is no longer party os
ADB and disabled
Click to expand...
Click to collapse
.
First of all, i think you should stay calm and don't do double posts because you don't get an answer in the speed you`d like to have...
The second thing is, you are asked to write all informations...
But you just post some pieces...
But anyway...
my last try...
You were on 13.3.09 and wanted to install 13.3.1.0?
Did you have OTA disabled before... Safestrap...????
then I changed on build.prop code from 300079820 to 310079820 because TWRP Recovery 2.8.1.0
Click to expand...
Click to collapse
this just makes no sense to me (why you did that)
salvo22 said:
.
Click to expand...
Click to collapse
Enter stock recovery and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and enter:
adb devices
it should return:
list of devices attached
xxxxxxxxxxxxx recovery
if you can achieve this, we can continue. If you dont have adb setup on your pc, here is how to for windows: Setting up the ADB Driver for Kindle Fire Devices
jeryll said:
Enter stock recovery and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and enter:
adb devices
it should return:
list of devices attached
xxxxxxxxxxxxx recovery
if you can achieve this, we can continue. If you dont have adb setup on your pc, here is how to for windows: Setting up the ADB Driver for Kindle Fire Devices
Click to expand...
Click to collapse
ADB is not enabled on your tablet
O.S not part
salvo22 said:
ADB is not enabled on your tablet
O.S not part
Click to expand...
Click to collapse
you saying that you did not enable ADB support in stock rom before playing with build.prop?
{
"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"
}
well then, my friend, I dont know, how to help you without adb access, you have bricked tablet, sorry
jeryll said:
you saying that you did not enable ADB support in stock rom before playing with build.prop?
well then, my friend, I dont know, how to help you without adb access, you have bricked tablet, sorry
Click to expand...
Click to collapse
you're not confusing part the operating system only goes to the original recovery (see you tube video)
salvo22 said:
you're not confusing part the operating system only goes to the original recovery (see you tube video)
Click to expand...
Click to collapse
Yes, I know your system can only boot to stock recovery.
Try to enter stock recovery, connect your kindle to pc or laptop and check if adb recognizes your device.
Without adb access you cant repair your kindle.
You can also try Reset to factory defaults, but ... its your choice, your tablet, but as I have read through forum Reset to factory defaults rarely help in case of unbricking...
jeryll said:
Yes, I know your system can only boot to stock recovery.
Try to enter stock recovery, connect your kindle to pc or laptop and check if adb recognizes your device.
Without adb access you cant repair your kindle.
You can also try Reset to factory defaults, but ... its your choice, your tablet, but as I have read through forum Reset to factory defaults rarely help in case of unbricking...
Click to expand...
Click to collapse
and can restore it once unlocked bootloader?
This is the first time it happens to me. I'm not an expert with cellphones, but i think this is a very weird situation.
This is the history. My cousin gave me his Moto X Play as a gift after he went to a local to repair the phone's broken display. It looked good well when i used it at the first time. But, when i tried to root that phone i have noticed a very weird issue....
The phone can't enter to a Fastboot mode when i press the buttons, and when i turn it on, it doesn't seem to have a boot logo. Im not sure about this situation, but im afraid that this phone doesn't have a boot logo, or fastboot menu.
-The phone doesn't seems to be rooted before, or have an another recovery, but i'm not sure about this.
-Everyting in the phone's system seems ok.
-The phone turns on with order (The right time and right boot), there's also the boot animation except that there's no logo.
-I have a little trouble with the phone's speaker, but, thats an another situation.
What can i do about? What do you think this is about? I can't talk with my cousin because his not living in my town, and he doesn't know about this.
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
RogerClark said:
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
Click to expand...
Click to collapse
.....
1. Yes! Pretty sure
2. Yes, the OS runs perfectly
3. I'm not sure about that, it may be
4. Nope
5. Not me, maybe another guy, but the phone doesn't seem to be rooted right now
6. Nope
Anny sugest?
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
RogerClark said:
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
Click to expand...
Click to collapse
I tried those before and nothing. Anything else you can think for me?
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
RogerClark said:
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
Click to expand...
Click to collapse
I have tried, but console says my ADB Device is Offline. What can i do? My ADB Tools are up to date
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
I'll keep that in mind, thanks a lot for those sugestions.
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
UPDATE: It seems i can access to bootloader from the computer, but screen is black when that happens. When i finaly entered to fastboot mode screen was all black and nothing happened. I noticed about this 'cause when i pushed the "+" button phone has restarted with normaly. What do you think about this?
As an extra, these messages apear when i write an ADB comand...
{
"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"
}
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
UPDATE: I've already unlocked the phone's bootloader, but can't flash the TWRP Recovery. When i try it says it was flashed sucessfuly, but, when i enter to recovery mode, it haves the stock recovery.
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
RogerClark said:
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
Click to expand...
Click to collapse
What do you refer with factory configuration? Actualy the phone are supposed to be on Stock. The phone has never unlocked by bootloader, i'm almost sure of that. So, for that reason i suppose the phone had never another rom.
Maybe i can be wrong, but. Why do you thing there are missing files?
Updated my phone to Android 7.1.2 today, using the built in updater.
Now when I restart, I get the following on the bootloader: "Your device is corrupt. It can't be trusted and may not work properly"
It still boots normally. But Android Pay doesn't work.
Any suggestions for fixing this?
I can't help, but I can confirm that the same has happened to me so you're not alone...
I had the same problem. I couldn't even start twrp anymore. I fixed it by flashing the full tos118c rom from fastboot. After that I let the ota install. I then reinstalled twrp and flashed magisk to root the phone. Now it boots without dm verity or corrupt message. Even the play store is now certified, so I can install Netflix without problem.
Also you can hide root so you can use Android pay.
WileyFox customer support?
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
jamesmcd05 said:
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
Click to expand...
Click to collapse
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Brilliant, thanks.
Didn't realise there were offical wileyFox builds available.
Much appreciated. I will give that a try
:fingers-crossed:
EDIT:
I got an error saying that:
target reported max download size of 535822336 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Also my phone was OEM locked.
I unlocked the device and tried again, but got the same error.
So I unzipped the contents and manually flashed each img,. which seems to have worked fine
I re-enabled OEM lock and now the phone boots without errors.
Thanks a million
Just wanted to say thank you very much for the thread info.
I also got the error messages, but realised that I was just being a bit hasty. Waiting a further 20 seconds gives a couple of other messages about other .sig files missing, but then the update continues and the flash is completed. The 'corrupted' and 'dm-verity' messages have now gone and the phone appears to be functioning properly.
Hopefully it will now update OTA to the next version and do so without corruption.
Thanks again
David
Wait a minute.
I'm a almost complete newbie but perhaps you guys can help me out.
Like davids-h I also got the errors and after over seven (!) minutes I get:
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished.
What can I do or should I do?
Thanks in advance!
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
rjl_12345 said:
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
Click to expand...
Click to collapse
Update: I managed to get the ROM flashed by removing the SD card and SIM. I have no idea why this would have been an issue but it was. I could then flash the ROM. Thanks
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
The steps documented by asg1977 have also worked for me.
I had the issue on a Swift2X that was delivered factory standard with a Nougat image. It occured while taking the phone out of its cover, pressing the power button in the process. After that the phone rebooted consistently with the corrupted warning. (Even tough the phone worked fine once past that screen.)
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks for this, but when I open a command prompt, and type in adb devices, I get a message saying that
'adb' is not recognized as an internal or external command,
operable program or batch file. I have developer options activated and usb mode is switched on and set to mtp devices. I have downloaded the 2 sets of files (USB drivers and ADB, and unzipped them to the desktop. Where am I going wrong?
EDIT - SOLVED IT! The command prompt needs to be opened inside the platform tools folder, whereupon it will find the phone, and the adb reboot "dm-verity enforcing" command will work. Prior to this, I had to revoke usb debugging authorisation between the phone and computer, then reconnect the phone the computer, so the phone could be seen by the computer. Command prompts can be very finicky about how they work, but I got there in the end.
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
---------- Post added at 02:33 PM ---------- Previous post was at 02:06 PM ----------
louisew92 said:
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
Click to expand...
Click to collapse
Sorted now thanks!
I had the same issue and WF support fixed it for me
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
{
"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"
}
3LzW said:
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
Click to expand...
Click to collapse
FTFY:
Something weird about posting links makes me fail posting the correct link: https:// imgur.com/a/NHjGV
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks from Poland, genius! It works
My phone has developed this problem after I flashed TWRP, I've tried to follow instructions so I can enforce the DM verity reboot in a command line interface but if I select fastboot my phone stays on a load up screen and doesn't change. The only other thing I can access is TWRP, will I be able to use the terminal in that to solve this problem?
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
I know this is old.. but just wanted to say I wasn't able to do this from my laptop via adb - but used the terminal via TWRP and it worked.
Thanks a lot from Wales
Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"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"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).