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"
}
Related
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?
{
"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"
}
Power off the phone .
Press vol down and power button and it will boot into boot loader
Connect the USB cable .
Go to ed300's post and download the twrp recovery for lollipop and KitKat.
If the base ROM on which u have flashed the new ROM was KitKat use the KitKat twrp.
Else use the lollipop twrp.
Extract the required zip file.
After connecting the USB , click on the file named Flash . after its completed click on Boot file .after that's also done again click the Flash file .
After that it will show (waiting for device )
And the phone will boot to the recovery mode and u can flash the ED300's ROM I prefer CM12.1
Good luck.
bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "
bvsbrk said:
bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "
Click to expand...
Click to collapse
Did u follow as I mentioned?
Which was the base rom on which u flashed CM
Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.
bvsbrk said:
Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.
Click to expand...
Click to collapse
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link
bvsbrk said:
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
aravindmj said:
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
that is not working every command window stopped at "waiting for device" anyway thanks a lot
bvsbrk said:
that is not working every command window stopped at "waiting for device" anyway thanks a lot
Click to expand...
Click to collapse
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
aravindmj said:
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.
bvsbrk said:
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.
Click to expand...
Click to collapse
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.
aravindmj said:
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.
Click to expand...
Click to collapse
Same thing bro the problem is something related to fastboot drivers which were gone from my phone
It worked for me . Can you send me a link where i can find CM12.1
Mahesh0001 said:
It worked for me . Can you send me a link where i can find CM12.1
Click to expand...
Click to collapse
https://forum.xda-developers.com/le...t-cm12-1-rom-lenovo-a6000-plus-withe-t3288805
My phone went into bootloop , i was using ResurrectionRemix 5.8.3 , i cant go into recovery mode. but can start bootloader.
I have installed Minimal fastboot , its showing no devices found when used "adb devices"
But shows the devices for command "fastboot devices"
I also tried flashing twrp.img using "fastboot flash recovery twrp.img"
But still phone not starting just stuck on looping the startup..Please helpppp
i get error when i hit flash.bat that device not found but it write the img file
What should i do?
My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.
johnwell4u said:
My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.
Click to expand...
Click to collapse
Flashing via phone is easy.
Just go to recovery wipe entire thing and then flash.
Mahesh0001 said:
i get error when i hit flash.bat that device not found but it write the img file
What should i do?
Click to expand...
Click to collapse
Make sure to use the recovery based on the rom that you where on before this thing happened.
And try executing the boot.bat file also. Do it simultaneously
aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
worked for me to open recovery again.. i am now trying to reflash MIUI8 android 5.1.1.:good::good::good:
Hey,
I had read in a few posts on xda that oppo had locked/disabled fastboot mode on their devices. I was wondering if somebody could test if adb reboot bootloader or adb reboot fastboot are working on the Find X and if so fastboot oem unlock is working?
Thanks in advance
i can confirm that Fastboot mode here it seems to be factory disabled.
adb reboot bootloader it only reboot device on normal OS and "Enable OEM Unlocking" switch it seems to be dead
Disabled mode:
fastboot mode
Avaiable mode:
Recovery Mode :
(adb reboot recovery)
Turn off your device.
Press and hold the Volume down and Power buttons simultaneously until the device turns on.
Qualcomm EDL Mode
(adb reboot edl)
Turn off your device.
Press the Volume Up and Power buttons and connect the USB Cable to the phone.
EDL => Emergency Download Mode
snowwolf725 said:
Disabled mode:
fastboot mode
Avaiable mode:
Recovery Mode :
(adb reboot recovery)
Turn off your device.
Press and hold the Volume down and Power buttons simultaneously until the device turns on.
Qualcomm EDL Mode
(adb reboot edl)
Turn off your device.
Press the Volume Up and Power buttons and connect the USB Cable to the phone.
Click to expand...
Click to collapse
Theoretically it's possible to unlock the bootloader and backup the device partitions through EDL right? Can it be used to emulate the functionalities of fastboot?
rezesius said:
Theoretically it's possible to unlock the bootloader and backup the device partitions through EDL right? Can it be used to emulate the functionalities of fastboot?
Click to expand...
Click to collapse
No, you also need OEM-signed programmer.
In addition, it's very hard to unlock bootloader through EDL mode.
Ref:
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
EDL = Emergency Download Mode
EDL mode is power than fastboot mode, but it's too hard to use.
You can flash specified partition, or resize partition size in EDL mode.
snowwolf725 said:
No, you also need OEM-signed programmer.
In addition, it's very hard to unlock bootloader through EDL mode.
Ref:
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
EDL = Emergency Download Mode
EDL mode is power than fastboot mode, but it's too hard to use.
You can flash specified partition, or resize partition size in EDL mode.
Click to expand...
Click to collapse
So literally this phone have no future??*
I don't think so. We just have to use what we can. Maybe get twrp installed through recovery mode
I'll recheck how it had to be done on the axon7. But if I remember, it was a similar issue.
We don't yet know what will or will not be unlocked in the international variant. Even if they just give it the OEM slider without an unlocked bootloader you can sometimes get root through magisk. In theory we should soon get owners in India and the Philippines with an international phone and we should have a better idea then as to what we're up against.
Adding insult to injury, when I asked Oppo India if they'll release the kernel source of the Find X, they immediately send a message back point blank refusing to that
rezesius said:
Adding insult to injury, when I asked Oppo India if they'll release the kernel source of the Find X, they immediately send a message back point blank refusing to that
Click to expand...
Click to collapse
Lmao.... killing it bro. Im not surprised from them..
avetny said:
Lmao.... killing it bro. Im not surprised from them..
Click to expand...
Click to collapse
Haha, knowing Oppo's track record it was kinda expected. I was just hoping they'd change their stance. This is truly a beautiful phone screwed over by their stupid policies
rezesius said:
Haha, knowing Oppo's track record it was kinda expected. I was just hoping they'd change their stance. This is truly a beautiful phone screwed over by their stupid policies
Click to expand...
Click to collapse
Absolutely agree sir.
As long as I can get root I can make it do what I want and that is where the line in the sand lies; no root is my deal-breaker.
krabman said:
As long as I can get root I can make it do what I want and that is where the line in the sand lies; no root is my deal-breaker.
Click to expand...
Click to collapse
{
"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"
}
wolfgart said:
i can confirm that Fastboot mode here it seems to be factory disabled.
adb reboot bootloader it only reboot device on normal OS and "Enable OEM Unlocking" switch it seems to be dead
Click to expand...
Click to collapse
Just bought mine in Thailand so I assume it's the global variant. The "Enable OEM Unlocking" works and so does the USB debugging switch. I haven't tried to use fastboot yet.
farang4u said:
Just bought mine in Thailand so I assume it's the global variant. The "Enable OEM Unlocking" works and so does the USB debugging switch. I haven't tried to use fastboot yet.
Click to expand...
Click to collapse
Just bought mine in India and can confirm Bootloader Unlock is availableand should be a piece of cake with OEM Unlock available in the developer options. Oppo Find X is not a mediatek device hence rooting should be easy with kingoroot. I am not rooting risking the security Oppo provides. I am not a developer who can undo it. Hence waiting ...
You have no clue, fastboot is disabled, even in new ColorOS 5.2 beta
yeah no idea we are all bricked with.this.device ?
Bring me in
InspectMyGadget said:
yeah no idea we are all bricked with.this.device
Click to expand...
Click to collapse
If you guys can send me that phone, I'll be able to do some tricks & tries, I've done that before with vivo devices, Oppo is also owned by BBK Electronics, So...
Oppo: Fastboot Disabled
Any update on this issue?
Ive got here an Oppo A7 , purchased for about $280 in the Philippines last December 2018.
"Allow OEM Unlock" can be activated in Developer Options.
But unfortunately "ADB reboot bootloader" seems only to restart the device. Key combinations for fastboot doesnt work either.
Damn stupid brand this is. Goin crazy these past few days untill I saw this thread. never thought of it to be this enthusiast-unfriendly
My phone is completely messed up right now. All I did was flash spark os (A12) over PPUI (A11) and then my phone didn't boot. I flashed that ROM via fastboot flash tool. I think it was the tool which caused this problem. After so many tries, my phone booted but wifi, sound and many other functions aren't working. Then I tried flashing some other ROM but TWRP/Ofox kept giving some "error 7". Then I tried flashing fastboot ROM with 3 versions of Mi flashtool but it keeps giving some kind of CRC flash error. Please help me I'm too much worried right now.
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
muneeb rizwan said:
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting this error continously
move it to c:\
muneeb rizwan said:
move it to c:\
Click to expand...
Click to collapse
now my phone screen has gone black and it won't turn on. Computer still detects it as I'm hearing some sound
I was flashing fastboot ROM using mi flashtool and it gave me error. When I tried to turn on the phone, it didn't turn on. However, when I connect it to PC, the PC makes some sound. What do I do now?
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
muneeb rizwan said:
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
Click to expand...
Click to collapse
I can't even boot into fastboot mode. Screen stays black no matter what key combo I try
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
StaryMuz said:
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
Click to expand...
Click to collapse
Didn't work. I guess EDL mode is my last hope now.
Starting EDL mode can be a problem. At present, perhaps EDL cables no longer work and if the phone does not allow you to enter the EDL by key combinations, the only test points left are on the phone's motherboard. With test points, the question is whether the correct points have already been found. The manufacturer does not inform about them.
What driver is loaded in Windows when the phone is connected?
So the test points are already known:
It works by disconnecting the battery to completely shut down the hardware. Conductively connect the test points (tweezers, scissors) and with the points connected, connect the USB cable plugged into the PC. This activates the EDL mode (sometimes only very briefly). You need to have MiFlash running beforehand and use "refresh" and "Flash" right away. If nothing happens, probably the EDL mode has already been switched off again.
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
StaryMuz said:
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
Click to expand...
Click to collapse
I wonder how did my phone boot into edl mode although I never opened its back cover.
And right now the problem is that Mi Flashtool is showing some edl authentication error. How do I resolve that?
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
StaryMuz said:
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
Click to expand...
Click to collapse
That's exactly what I used. I even tried the latest version but still no luck.
Shibu Shaji said:
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
Click to expand...
Click to collapse
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
Bro, connect to a VPN , change the language of auth window and bind your mi account details there. And give it a try on tool version 2017.4.25... If nothing works go for edl.
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
Bro, use the same version of flash tool that I mentioned above.. 2017.4.25 with flash all command.
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).