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?
Related
First, sory for my bad English
My KF was in Rom HDX Nexus 2.0 and I decided to up to rom cm11
But with some mistake and now my KF is bricked
I tried to unbrick it with adb tools but in cmd, adb devices attached is empty. I had tried some post in thread to connect my KF with my lap but is still the same
This is some post I follow
https://developer.amazon.com/post/T...p-the-ADB-driver-for-Kindle-Fire-Devices.html
http://forum.xda-developers.com/showthread.php?t=2588608&page=8
Pls help me
Do you have TWRP installed?
EncryptedCurse said:
Do you have TWRP installed?
Click to expand...
Click to collapse
Yes, Cause I had root my KF and install a HDX Nexus 2.0
And I can take it to fastboot mode by hold down power + volumn up, but I did not know to do anything
Help me
Anybody help me pls!
tuilakhang said:
Anybody help me pls!
Click to expand...
Click to collapse
When you turn your device into fastboot mode, does fastboot detect the device?
it seems you have an old bootloader...
you can try to unlock bootloader (look at original android development forum) and try send twrp using fastboot
Whatever you do - Never ever ever factory reset it!!!
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
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
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
unparalleled82 said:
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
Click to expand...
Click to collapse
Hi Unparalleled82,
So i think i was actually using "adb reboot bootloader " instead of the app at times so ive just tried it using the app however it still doesnt come up as a fastboot device. When i put in the command " fastboot flashing unlocked " i just get " waiting for any device " for ever.
Few things im wondering do you have exacly the same phone as me RealmeGT 5G rmx2202_11_A.25. Its good to know you have done it and the way you did it. Because mines not working the same way ( assuming the models are the same ) im thinking now its a driver issue perhaps .
So when im just doing adb sideload or something when the phone is booted into the OS i dont have the yellow triangles however in this fastboot mode i see this...
{
"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"
}
Which does indicated a driver issue however when i try to manually install the correct drivers windows tells me its already has the best driver. ( im browsing to the folder where ive downloaded the drivers here )
Ive tried installing them through the legacy hardware option which does install them but phone still doesnt show up in fastboot devices.
Ive also installed the driver using android studios ... you can see google usb drivers ticked.
Ive also googled how to stop windows from automatically installing drivers from windows update then uninstalled my device .. plugged it back in ... then installed them. However thinking now perhaps i should uninstall ... then install the drivers before plugging in the phone ? any ideas ?
Some more info this has reminded me of. Ive tried a different usb cable, a different usb port ( both usb 2.0 ) and a different computer already.
As for the powershell I'm certain i'm using it not the cmd line. I'm holding shift in the correct folder then right click, then open the power shell window.
Any more help would be amazing. Im going to have a look more into fastboot driver problems
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
unparalleled82 said:
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
Click to expand...
Click to collapse
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Piefrag said:
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Click to expand...
Click to collapse
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for a better cable
unparalleled82 said:
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for
Click to expand...
Click to collapse
Ahh got you now. So ive tried the cable sent with the phone and now 2 other cables and all of them have the same issue so im thinking its not the cable atm.
Ive seen on youtube a method for rooting it from anotehr phone.... i have no idea if it works but ive bought a usb c too usb c cable to give it a try at least !
Thinking now i may buy another usb A too usb C cable of good quality too make absolute sure its not the cable messing it up.
Piefrag said:
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
Click to expand...
Click to collapse
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
grown_man said:
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
Click to expand...
Click to collapse
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Piefrag said:
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Click to expand...
Click to collapse
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
grown_man said:
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
Click to expand...
Click to collapse
Thats it ! Thank you so much
Hi everyone, I'm in need of some help ASAP. I unlocked my ANE-LX1 phone's bootloader so that I could root it, but things went wrong. My phone is stuck on TWRP logo screen (No TWRP menu, only logo) and my PC doesn't recognize it no matter what. I can only access the fastboot screen but it means nothing when you can't use ADB commands. I really don't know what to do, please help!
@-Alf- Hope that you'd help
soslusos said:
@-Alf- Hope that you'd help
Click to expand...
Click to collapse
Hi, try to explain what exactly happened, step by step.
soslusos said:
when you can't use ADB commands
Click to expand...
Click to collapse
For what reason?
-Alf- said:
Hi, try to explain what exactly happened, step by step.
For what reason?
Click to expand...
Click to collapse
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
soslusos said:
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
Click to expand...
Click to collapse
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
-Alf- said:
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
Click to expand...
Click to collapse
First of all, thank you man. It was suggested by someone on XDA, I shouldn't have done it.
I think the regional code is C121, I bought it in Turkey.
The thing is my phone doesn't turn off. Even when I force it by holding the button, it just turns back on. It stays like that until the battery dies.
I can open the fastboot screen by holding the vol down button and it says:
ap_s_abnormal 64
phone unlocked
frp unlocked
Have you tried connect to PC, then press and hold Power + Vol Down for 10-12 sec?
soslusos said:
It was suggested by someone on XDA
Click to expand...
Click to collapse
I bet I know who it was
Yeah I tried that, it just opens fastboot mode after phone restarts.
soslusos said:
Yeah I tried that, it just opens fastboot mode after phone restarts.
Click to expand...
Click to collapse
Game over . Test point method & board SW or DC-Phenix is your friend (maybe...). Unfortunately, I can't help you with this, I've never done it.
Damn. I don't even know what they are Can customer services do anything with this? I guess I'll have to pay.
soslusos said:
Can customer services do anything with this?
Click to expand...
Click to collapse
I guess so. It's all a matter of money .
Haha yeah but some stuff you do on your phone might be irreversible, that's what I'm afraid of.
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (Or is it?)
soslusos said:
some stuff you do on your phone might be irreversible
Click to expand...
Click to collapse
Yes, e.g. damaged motherboard...
soslusos said:
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (
Click to expand...
Click to collapse
Of course I cannot say that for sure. But I can say for sure that doing 'data format' (running stock EMUI) on some TWRP 3.4. and above can brick Kirin 659 device.
@-Alf- Hey, my phone is finally fixed. Do you know what's the latest firmware for 9.1 and where to download it? I'll install that one after rooting my phone.
soslusos said:
what's the latest firmware for 9.1
Click to expand...
Click to collapse
Hi, .401 (for C432 region)
soslusos said:
where to download it?
Click to expand...
Click to collapse
via OTA update
soslusos said:
I'll install that one after rooting my phone.
Click to expand...
Click to collapse
I would suggest updating first and then root
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
soslusos said:
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
Click to expand...
Click to collapse
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
-Alf- said:
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
Click to expand...
Click to collapse
So I was gonna roll back to EMUI 8 to unlock the bootloader but this time there's no "Switch to previous versions" option... In phone settings it says LGRP_OVS 9.1.0.208, is that the cause? How am I gonna unlock the bootloader now? So confused, I don't want to mess things up this time
soslusos said:
LGRP_OVS 9.1.0.208, is that the cause?
Click to expand...
Click to collapse
Yes, it is. Incompatible or incomplete FW .
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
{
"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"
}