I know this has probably been posted before, butI couldn't find any answers in the posts I found.
The phone has OEM Unlocking turned on in Dev options.
I tried switching off and restarting and then switching back on.
fastboot devices is recognized but all of the fastboot commands I have tried except "help" return the Error - FAILED (remote: 'unknown command')
Why would this be?
It works with 3 other phones we have here to unlock the bootloader. I don't think Ive encountered this before.
Is it possible it could require some unlock key?
Is is a 2022 no name chinese brand.
Any advice is greatly appreciated!
Thank you!
do you run it in PowerShell or CMD?
PowerShell sometimes needs extra in the sytnax or it gets the "command" confused or calls it incorrect...
defcondoc said:
fastboot devices is recognized but all of the fastboot commands I have tried except "help" return the Error - FAILED (remote: 'unknown command')
Why would this be?
Click to expand...
Click to collapse
Answer is simple: Either device isn't booted into Fastboot ( Bootloader ) mode or Fastboot commands aren't supported at all.
FYI:
{
"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"
}
simply checks whether your device has been detected and recognized by your computer or not.
simplepinoi177 said:
do you run it in PowerShell or CMD?
PowerShell sometimes needs extra in the sytnax or it gets the "command" confused or calls it incorrect...
Click to expand...
Click to collapse
CMD
I do know what you mean when using powershell, however I haven't used that in a while.
IMO - I think it has to do with phone. I've done enough of these to know its probably the phone, but apparently not enough to know how to fix this one
Thank you!
xXx yYy said:
Answer is simple: Either device isn't booted into Fastboot ( Bootloader ) mode or Fastboot commands aren't supported at all.
FYI:
simply checks whether your device has been detected and recognized by your computer or not.
Click to expand...
Click to collapse
OK. Its booted into the Bootloader. It reads the device and serial.
Why would fastboot commands not be supported? Could the developer lock those out?
Thank you!
defcondoc said:
OK. Its booted into the Bootloader. It reads the device and serial.
Why would fastboot commands not be supported? Could the developer lock those out?
Thank you!
Click to expand...
Click to collapse
does anything come up if you do fastboot getvar all?
simplepinoi177 said:
does anything come up if you do fastboot getvar all?
Click to expand...
Click to collapse
Yes. all the usual phone info.
We have another phone here that is much older with OEM Unlocking Checked ON and can't unlock the bootloader either. It is a brand new UMX Tracfone with android 8 on it.
I'm my experience, the OEM Unlock feature is either grayed out or not available at all if the phone wasn't meant to have the bootloader unlocked.
So why have the option to unlock it, if fastboot commands won't let you unlock?
I'm wondering if you're platform-tools isn't up to date or your usb (cord or port) is doing something "funky"....
simplepinoi177 said:
I'm wondering if you're platform-tools isn't up to date or your usb (cord or port) is doing something "funky"....
Click to expand...
Click to collapse
I've checked over the most obvious stuff. I've tried two other computers as well. We don't have these problems with other phones.
Also, on the second older Tracfone. The command
Code:
fastboot flashing unlock
is accepted but it just hangs and nothing completes. I have to unplug the device and replug to access the bootloader again from CMD
I think maybe these phones need an unlock key or special file or possibly a different fastboot unlock command? I'm clueless as to why these two phones won't let me unlock the bootloader when the option to unlock is turned on.
Because these are some off brand chinese phones. Do they typically lock these types of phones down more often, disabling fastboot commands? Does anyone have experience with these types of phones that don't have access to fastboot commands? Are we wasting our time with these? Should I be asking in a different thread? Maybe a developer section?
defcondoc said:
Yes. all the usual phone info.
Click to expand...
Click to collapse
I asked because, if fastboot devices was the only thing that worked, then that just states the device is connected; whereas the getvar all proves it can actually at least read the data from the device -- doesn't prove it can write or execute other commands.
defcondoc said:
Because these are some off brand chinese phones. Do they typically lock these types of phones down more often, disabling fastboot commands? Does anyone have experience with these types of phones that don't have access to fastboot commands? Are we wasting our time with these? Should I be asking in a different thread? Maybe a developer section?
Click to expand...
Click to collapse
After a small bit of research, it does look like vendor's/manufacturer's can limit or restrict specific/certain fastboot commands...
simplepinoi177 said:
I asked because, if fastboot devices was the only thing that worked, then that just states the device is connected; whereas the getvar all proves it can actually at least read the data from the device -- doesn't prove it can write or execute other commands.
After a small bit of research, it does look like vendor's/manufacturer's can limit or restrict specific/certain fastboot commands...
Click to expand...
Click to collapse
Thanks. Yes, I seemed to have found the same info. However, it seems some are able to bypass in EDL mode. I'm not sure what that involves. It would nice to be able to delete the current rom and flash something else in EDL mode. Do you know if its possible to delete partitions in EDL mode and flash generic partitions from a another phone that has the same processor?
Or maybe we only need to target the boot.IMG. I can get into EDL mode but the software is requiring a firehose MBN file. I have tried generic and ones with the processor but have had no luck so I cannot get access to the partitions.
defcondoc said:
Thanks. Yes, I seemed to have found the same info. However, it seems some are able to bypass in EDL mode. I'm not sure what that involves. It would nice to be able to delete the current rom and flash something else in EDL mode. Do you know if its possible to delete partitions in EDL mode and flash generic partitions from a another phone that has the same processor?
Or maybe we only need to target the boot.IMG. I can get into EDL mode but the software is requiring a firehose MBN file. I have tried generic and ones with the processor but have had no luck so I cannot get access to the partitions.
Click to expand...
Click to collapse
Unfortunately, I know absolutely minimal concerning EDL mode. And because I am completely unfamiliar with the device make & model that you are attempting this with, even moreso I wouldn't even know where to begin with modifying partitions or the requirements of "firehose MBN file" and the such...
Hopefully you figure something out! Good luck to you!
Related
Hi all,
This is my first post to XDA and before I go any further I must say that i'm quite the idiot when it comes to android terminology and general modification of android as a whole. So if i'm in the wrong place, sorry!
I've got myself a One SV on t-mobile and have had it approaching 2 years now. I came to this phone from my previous HTC Desire (wish i kept it).
Back when i got my desire and started looking into customisation, performance etc i learnt a little about rooting and the pro's and cons surrounding it. "How hard can it be" so I went ahead and somehow installed CM on my desire. All was well and I never ran into too many problems. Now I've tried to do the same with my one sv (after having poor battery life, lack of storage and just all round lack of options) and i'm a little stuck.
I've tried to follow this guide > http://forum.xda-developers.com/showthread.php?t=2113671 and various others. The wording, however and process just seems beyond me. I've managed previously to unlock the bootloader via HTC however that's where i'm stuck (the easy bit).
BASICALLY what i'm asking, is for some kind hearted, patient soul to walk me through this, in dummies terms.
I'm almost certain i've soft bricked the device (don't ask me how) as there's some major issue now surrounding the dialer, contacts and sync. I receive the message "'android.process.acore has stopped" repeatedly, rendering my phone useless at the moment. I'm at a loss now and i need some help! any advice would be greatly appreciated.
Luke.
Ok, your bootloader is unlocked.
Do you have a working fastboot command? And what version of One SV do you have (k2u, k2ul,...)
A working Fastboot command... you've stumped me already im afraid. As i said i really haven't got a clue... i don't want to mislead you. How could i find out which version of the device i have? i've taken a peek behind the battery and i can't see anything.
From what i've just read i'd presume it's the k2_ul due to me being in England. If you know otherwise though, i can check?
You had to flash the unlock token with fastboot, right?
If that worked, you should have a working fastboot.
To know your version, connect your phone to pc, boot into bootloader (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same foldrr, where yourfastboot.exe is.
Type into cmd window:
fastboot getvar all
Put the output here, without your serial and imei.
When starting the phone in "hboot" i recieve the following
UNLOCKED
k2-UL PVT SHIP S-ON RL
HBOOT-2.21 0000
Including various bits of other info. Then going on to read;
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
If i connect the phone to my PC in hboot it won't detect or anything to be honest. Should i first connect the phone to the PC normally? as if to transfer files etc and then turn off the phone and boot in hboot? or am i doing something wrong.
Thanks for all the help by the way!
When trying to select FASTBOOT and then selecting BOOTLOADER from the following menu I receive a list of "no gift file" "no image" etc.
So from what you're saying, it's likely i haven't followed the flashing procedure correctly?
Bootloader has two modes: the one you have described "scanning for files" is the bootloader mode. The other is fastboot mode.
But i know enough.
With the command
fastboot devices
you can check if your device is recognised.
Try to check this:
connect your phone to pc, boot into bootloader/fastboot mode (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same folder, where your fastboot.exe is and run the cmd above. Look, what output you get in cmd window.
Maybe you need to install htc sync on your pc to get the latest drivers.
Hi, first off sorry for the late reply. Work has been mega busy. Bad news is that this hasn't miraculously solved its self over night. i've had a brick for nearly a month now with no way to call my contacts etc.
When starting the phone in fast boot (vol down and power on) and connecting to the PC i have no option for "fastboot usb" as you've described. I've tried to update HTC Sync manager. I've also tried various USB ports on the PC (i've had the issue before, whereby some of the ports haven't got the required power) and it's still not available. Is there any easy method to solve this?
Fastboot USB is not an option to choose, its only written on the screen, that you can see you are connected.
Take a look at this picture:
{
"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"
}
Connect your phone to pc, go to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.
---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------
As you are unlocked, you should be able to flash TWRP recovery (if your fastboot is working). From TWRP you can backup whats left and flash stock rom.
All under tbe aspect, the device is not screwed up.
As you can see, these are the only options i'm getting. The phone is plugged in via USB 2.0 and isnt being picked up by the PC at all. I've updated the HTC Sync Manager in hope of solving it that way but still no luck. Any other advice?
Is your phone booting and stable enought to get S-off (rumrunner.us would be your choice)?
Maybe try another pc or cable, you need either S-off or a working fastboot.
I can use the phone. The only real problem is inability to access contacts and the message " Unfortunately, the process android.process.acore has stopped." appears every 5 seconds or so.
Sometimes the message stops appearing and the phone works normally. This is what confuses me. Why is it only happening most of the time, not all of the time?
I dont really understand S-OFF either. I'm sorry i'm so useless with all of the terminology but i can't seem to manage without a very basic explanation of how to do these things. I'm totally to blame for this. I shouldn't have messed with the phone in the first place. Leaving it to the experts like yourself is best.
Have you tried a factory reset to solve this?
yes twice, im really out of options now so i may end up having to buy a new phone or take it to an expert
If your phone boots and it is fine sometimes, than you should be able to "rescue" it.
When the phone is in the state of the picture you have posted today, connected to pc with usb, then you need to hit the power button once to access fastboot USB.
Look at your picture: you are in Hboot mode, Fastboot is highlighted.
Hey, I've since managed to get the phone to this state with the USB plugged into my computer. Where am i going from here? It seems the cables i'd been using were faulty. Only one works!
Yeah, that is what we need!
Now you should try to do 2 things:
- try to backup your data with a app like Titanium Backup (if there is anything left, after your factory reset)
- Connect your phone to pc in this fastboot usb state, go (on your pc) to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.
yes! am i on the right track?
Yes, you are!
Remove the picture, it don't need to be public.
Download this recovery: http://d-h.st/m7F
Rename the file to recovery.img and copy it into the folder where your fastboot.exe is.
Then, in the cmd window type the command:
fastboot flash recovery recovery.img
You should see the progress on the phone screen in the corner of the upper right side.
I have read numerous threads on how to unlock the bootloader, however after the GTab2 7.0 p3100 is/was updated to JB 4.1.2 (VRBMI1), there is nothing i have found after a few days of looking and reading. Is this bootloader locked and no way to flash a custom ROM to it? Obviously, if this is a ridiculously dumb question, then I apologize in advance and the thread should be deleted. I just really would like to flash something really minimal to the 2 GTab2's that I have laying around to use them as home automation tablets in a couple of infrequently visited areas of my house. The stock ROM is really slow imho.
I do realize this is a very old tablet so it may be just too old to do anything with, regardless thanks very much for any help in this!
If you didn't buy it from a carrier and such, it's unlocked
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
To check if your bootloader is locked: install adb and fastboot to your computer as well as the proper drivers, boot your tab into download mode (power+volume down) and connect it to the computer with usb cable. Open a command prompt and type "fastboot devices" (without the quotes). If everything is right you will see your tab listed. Now for the check type "fastboot getvar unlocked" (again without the quotes). If the result is yes, your bootloader is unlocked.
Ok, so I already had adb/fastboot and odin 3 v 3.12 installed. Odin3 sees the device in both on and download states. adb doesnt see it at all in either mode. Windows 10 is my OS... Device manager see the tab unplug and plug in each time and I have used multiple USB ports as well. Any ideas? Chuck the tabs in the trash perhaps?
Trash is not a good idea It's probably a driver issue. Check that you have installed the adb/fastboot drivers, maybe there is an update to some driver you haven't done or seen yet. Also, try to install for your tab specifically the adb driver through the device manager (I don't know much about windows 10 so I can't tell you exactly how to do it, perhaps right-click on the tab or from some menu).
EDIT: Since odin works, try to install twrp with it. If it fails it's locked and you need fastboot to unlock it.
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
zulutron said:
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
Click to expand...
Click to collapse
"System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help."
are you really sure that you have a p3100?? it seems that you have a verizon varient of the tab 2. in this case dont flash p3100 stuff on your device. it will brick
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
zulutron said:
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
Click to expand...
Click to collapse
go to settings --- about the tablet. make a screenshot of this page and post it here.
Here it is. Thank for the help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://tinypic.com/r/2rzv3f8/9 <-- if the above doesnt work
zulutron said:
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
Click to expand...
Click to collapse
here you said that the tab is from verizon.
there is no rom available for your device.
i say it again
DONT FLASH P3100 STUFF ON THIS TAB !!
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
zulutron said:
Here it is. Thank for the help.
https://unsee.cc/tumezaso/ <-- if the above doesnt work
Click to expand...
Click to collapse
this is a sch-i705 and not a p3100. thats different devices
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
zulutron said:
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
Click to expand...
Click to collapse
look at the last 2 posts of the thread. all download links are dead since 1 year.
the best scenario for you. someone can help you out with the files. then you can install a damn old twrp recovery. with that you can backup your current system. nothing more.
there is no up to date twrp and no available rom for this device.
in this case unlocking the bootloader makes no sense, i think.
I appreciate the help for sure. I wont waste any more time on these tabs.
Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
{
"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"
}
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware
joygram said:
Hisense A6, A6L, A5 ... can not unlock bootloader
you can enter A5 hardware edlmode
teardown your phone
jump this point with clip(?)
and connect usb cable
if can not enter
you need take off power cable ( right bottom corner)
and retry
you can enter EDL mode
you need A5's QFIL firmware
Click to expand...
Click to collapse
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?
try step.
no adb required.
just jump point and connect power cable.
you should retry until catch QFIL catch port.
CrotteDeChien said:
Hi, thanks for the useful information.
Previously I bricked my A5 and was able to re-flash with 6.09.06.
I thought I would be able to issue the "adb reboot edl" command. But it didn't seem to work for me.
If I issue the "adb devices" command, I get the response "List of devices attached" with a number and the word "device".
I can do an "adb shell" command ... works well ... can go in there and put in some linux commands.
But when I issue the "adb reboot edl" command, it appears to work. The phone becomes unresponsive. If I issue the command "adb devices", it says that nothing is there.
But when I go into the QFIL program ... there is "No Port Available".
Any ideas ?
Click to expand...
Click to collapse
Anybody who knows:
How do you open the device without breaking it?
Ehere to begin to open it?
What tools (i.e. screwdrivers T5?) you need?
Does an Edl-Hardware USB-Cable works with the Hisense to enter Edl-Mode? How?
Yeah, how to open the Hisense A5?
Use something like a guitar pic (plastic plectrum) on the edge of the cover and open the cover carefully i.e. upper front.
lillo9546 said:
Yeah, how to open the Hisense A5?
Click to expand...
Click to collapse
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.
Hi Everyone, thanks you your tips.
I went to a phone repair place and paid them 20 AUD to open the phone.
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Reading more there is information regarding PCB (printed Circuit Boards) and the test points. These are the points we are mean to be "jumping".
What is the sequence of events ? Do I turn off the phone first ? Do I turn on the phone while having the points jumped ?
Do I connect the phone to the computer via USB first, and then allow debugging ... and THEN jump the points with tweezers or a paperclip ?
Any ideas would be greatly appreciated.
CrotteDeChien said:
I am having trouble getting the phone into edl mode, (which I found means Extended Download Mode BTW).
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
See after Step 6., but really be careful. Good luck
https://in.c.mi.com/thread-387857-1-0.html
Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?
Mehedi34 said:
Entered EDL mode after tearing down my phone. Flashed the "prog_emmc_.... .mbn" and "rawprogram_000b....." files with QFil successfully. But my phone just lights up, shows Hisense logo when try to start the device. Same bricked device.
Any idea?
Click to expand...
Click to collapse
Dear Mehedi,
use the base firmware 6.03.02 for edl-mode flashing in Qfil provided from gowin132
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Then flash this in Qfil see here some general infos
https://forum.xda-developers.com/showpost.php?p=82654769&postcount=79
use "prog_emmc_firehose_8937_ddr_000bf0e1.mbn"
from the package of joygram
Flash each partition in Qfil Partition Manager (Menu Tools)
After that reboot the device and it should work.
Then upgrade to latest 6.09.06 with TFMode (microSD)
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28
see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951
JLowe said:
see also here
https://forum.xda-developers.com/an...nfo-thread-t4101945/post82794951#post82794951
Click to expand...
Click to collapse
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132
Mehedi34 said:
Successfully unbricked my phone. Thanks everyone [email protected] @joygram @gowin132
Click to expand...
Click to collapse
Good to hear that you're successful! You can't soft brick these China Qualcomm Smartphones
Have fun with this great device!
5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
5 Methods to enter EDL mode on any Xiaomi smartphones [Qualcomm]
1. Boot EDL Mode via ADB Commands
2. Use Fastboot to Boot EDL mode on any Xiaomi smartphones
3. Use Hardware Buttons
===> Turn off your device.
===> Press and hold the Power + Volume Down buttons together and immediately connect the device to the PC.
===> It will automatically boot into EDL mode and LED lights may blink.
4. Use Deep Flash Cable
5. Use PCB Test Points
Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?
hammelgammler said:
Well I guess I bricked my phone. I had it rooted with google play services but wanted to reset it. After a factory reset it seems like I'm stuck in a boot loop or something and also can't get into TF mode to flash the original firmware again.
I had many services disabled but nothing uninstalled before the factory reset.
Does anyone know what I can do to unbrick it or get into TF mode?
Click to expand...
Click to collapse
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
I made a deep flash cable myself but sadly that doesn't seem to work either. Maybe I did something wrong with the cable but it seems all good to me. I can connect another phone with it and it functions normally, so the only thing that can be defect is the switch/button itself which shorts/connects the green and black wire together.
When I plug the Hisense in my computer with the button pressed it "starts normally" into the boot loop or something and when I let go off the button nothing happens.
As far as I read, you press the button, plug the phone into the computer and after about 8 seconds or so you let go off the button and it will boot into edl mode. But it doesn't seem to work for me.
Thank you. Any help would be very appreciated.
Edit: Okay I got it. For some reason I had to press the button on the cable, volume up/down and power button together for a few seconds until it showed up i QFIL.
JLowe said:
Just follow this here
https://forum.xda-developers.com/android/general/hisense-a5-root-gapps-customizer-t4097951
joygram uploaded a new version R04 which include original Edl firmware 6.09.06. So just flash this in qfil and then reboot to system and then go into qfil for root and flash the modified partitions.
If this doesn't work you can try the old way:
Before the way was as here described you needed first to in qfil 6.03.02 then going into TF-Mode to flash actual 6.09.06, reboot to system and then again Qfil for root,...
https://forum.xda-developers.com/android/help/hisense-a5-info-thread-t4101945
Good luck!
Click to expand...
Click to collapse
Same me. I had rooted it but i tried to reflash stock firmware and now has bootloop. How imcan fix? If i flash root it will boot, but i want to go back to stock
Mehedi34 said:
I used just my fingernail. You can start opening from the weakest point which is near the sim card port.
Click to expand...
Click to collapse
I also used my fingernail too, its easy to handle,
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Do you have ADB? is so do
Code:
adb reboot
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
{
"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"
}
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
jenneh said:
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
View attachment 5756167View attachment 5756169View attachment 5756171View attachment 5756173View attachment 5756175
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
Click to expand...
Click to collapse
Does ADB work too?
Arealhooman said:
Does ADB work too?
Click to expand...
Click to collapse
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
jenneh said:
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
Click to expand...
Click to collapse
Ah, i get it now, but doesnt samsung not have fastboot
Arealhooman said:
Ah, i get it now, but doesnt samsung not have fastboot
Click to expand...
Click to collapse
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
jenneh said:
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
Click to expand...
Click to collapse
Well, it was a good idea, but I do not think samsung supports fastboot
Arealhooman said:
Well, it was a good idea, but I do not think samsung supports fastboot
Click to expand...
Click to collapse
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
jenneh said:
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
Click to expand...
Click to collapse
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Arealhooman said:
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Click to expand...
Click to collapse
Spoiler: SHOW
Since I haven't messed with a samsung phone in almost a decade, I may be wrong, but if I had to guess, I would think that Samsungs come with a Preloader too, which is why there is a need for an external program like Odin.
But what a preloader is, is a layer below the Bootloader, it is what allows certain MTK or Qualcom devices to even be able to access the Bootloader.
I am a Nooby Cake and don't know much about anything, I just read a lot but if you are interested in what I have already read I started writing down the links for preloader knowledge on the last comment on this page of this thread and it continues into the next with nerdy rambling bs.
https://forum.xda-developers.com/t/mapping-out-the-g20s-internals.4416907/page-2
You can pm any questions just know I don't know much more than what I share on my threads haha. But I try to learn more everyday
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
.
Goddamn_srilankan said:
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
Click to expand...
Click to collapse
You are telling the truth. Unfortunately, the charge does not end. lol
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
karmastir said:
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
Click to expand...
Click to collapse
<3
Hi.
So, I was playing a game like everyday with my phone and then it suddenly stopped working and rebooted. After the reboot it got stuck on a boot-loop and wasn't unable to boot normally again. I got into the recovery and after many tries I was able to reinstall the ROM (PixelExperience 12-Plus) but after a few minutes it stopped working again and got into the boot-loop... again. I tried to reinstall the ROM again but I wasn't able to, so I decided to try with another recovery, I was using OrangeFox and after that I tried with TWRP. I got it to work with TWRP but then it crashed again but before doing it I got this screen:
{
"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 happened before and I was scared, "Did I just broke my phone?" I thought. So I asked a friend for help and he told me to try with Fastboot, he sent me a few command lines to try and... I ****ed up. The first line that I wrote was "fastboot oem lock" and the phone rebooted with this screen:
I literally locked the bootloader and now I'm unable to flash any ROM or even unlock it with MI-Unlocker 'cause I didn't have any MI account on the phone. I still can get into the fastboot but no more than that.
Is there anything that I can do? Or I should just send it to repair? Or buy a new brain for myself?
SalmonellaREAL said:
Hi.
So, I was playing a game like everyday with my phone and then it suddenly stopped working and rebooted. After the reboot it got stuck on a boot-loop and wasn't unable to boot normally again. I got into the recovery and after many tries I was able to reinstall the ROM (PixelExperience 12-Plus) but after a few minutes it stopped working again and got into the boot-loop... again. I tried to reinstall the ROM again but I wasn't able to, so I decided to try with another recovery, I was using OrangeFox and after that I tried with TWRP. I got it to work with TWRP but then it crashed again but before doing it I got this screen:
View attachment 5941189
It never happened before and I was scared, "Did I just broke my phone?" I thought. So I asked a friend for help and he told me to try with Fastboot, he sent me a few command lines to try and... I ****ed up. The first line that I wrote was "fastboot oem lock" and the phone rebooted with this screen:
View attachment 5941187
I literally locked the bootloader and now I'm unable to flash any ROM or even unlock it with MI-Unlocker 'cause I didn't have any MI account on the phone. I still can get into the fastboot but no more than that.
Is there anything that I can do? Or I should just send it to repair? Or buy a new brain for myself?
Click to expand...
Click to collapse
Lesson #1: Never do something when you don't know what the outcome will be, unless you're able to accept negative consequences. You should NEVER EVER lock the bootloader on custom firmware unless a custom root of trust has been installed, as with CalyxOS/GrapheneOS/etc.
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
If those don't work, your phone is bricked, and you're going to have to either have it repaired or replace it, both of which will be expensive.
V0latyle said:
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
Click to expand...
Click to collapse
That won't work, to unlock this phone you must use the Xiaomi official tool: https://en.miui.com/unlock/download_en.html
@SalmonellaREAL now you must pay to unlock it with an official Xiaomi account for EDL or you must go to an official repair center. I recommend you the second option, I never tried first.
Never lock bootloader unless the ROM has a self signed certifcates, in vayu there aren't any ROM with this.
V0latyle said:
Try to unlock the bootloader using fastboot flashing unlock or fastboot oem unlock
Click to expand...
Click to collapse
fastboot flashing unlock - Result: . . . FAILED (remote: unknown command)
fastboot oem unlock - Result: . . . FAILED (remote: Token Verify Failed, Reboot the device)
They didn't work, I'll try to send it to repair then. Thanks for replying!
swer45 said:
That won't work, to unlock this phone you must use the Xiaomi official tool: https://en.miui.com/unlock/download_en.html
@SalmonellaREAL now you must pay to unlock it with an official Xiaomi account for EDL or you must go to an official repair center. I recommend you the second option, I never tried first.
Never lock bootloader unless the ROM has a self signed certifcates, in vayu there aren't any ROM with this.
Click to expand...
Click to collapse
I believe you can still use ADB as long as you use the correct token for the unlock. I'm not very familiar with Xiaomi phones though so I'm not sure what the correct syntax would be.
I did find this:
GitHub - Canny1913/miunlock: A program that can be used to retrieve the bootloader unlock token for Xiaomi devices. (and unlock the bootloader)
A program that can be used to retrieve the bootloader unlock token for Xiaomi devices. (and unlock the bootloader) - GitHub - Canny1913/miunlock: A program that can be used to retrieve the bootload...
github.com
Description says it can retrieve the bootloader unlock token and unlock the device.