so i bricked my Firefly Mobile Allure 64 LTE which is a rebrand of Ulefone be touch they said; trying to flash ulefone's rom. and bang!
im trying to revive the phone. problem is any driver i install, whenever i plug it on computer(installed the driver needed/win10 64bit) it ignores the driver i installed and it connects to the computer like a normal connection with our without battery(normal use:file transfer etc.) can't get the phone to META mode
anyone?
jocelator said:
anyone?
Click to expand...
Click to collapse
Hello and welcome to the XDA community, the forum rules for this forum states that no bumping is allowed.
If you are able to access adb, you can do adb reboot recovery, if not, tell us the results. Try to access fastboot too via adb reboot bootloader or adb reboot fastboot. If you are able to access fastboot, you can flash the .zip or .img of your system.
RAZERZDAHACKER said:
Hello and welcome to the XDA community, the forum rules for this forum states that no bumping is allowed.
If you are able to access adb, you can do adb reboot recovery, if not, tell us the results. Try to access fastboot too via adb reboot bootloader or adb reboot fastboot. If you are able to access fastboot, you can flash the .zip or .img of your system.
Click to expand...
Click to collapse
oh... my apologies sir.
i dont know how to use adb. can you give me a guide or tutorial.
jocelator said:
oh... my apologies sir.
i dont know how to use adb. can you give me a guide or tutorial.
Click to expand...
Click to collapse
It is okay, just download and install this and connect your device. Open adb up and type adb devices, tell me what it says. Connect your phone in different modes (like recovery or bootloader) and test the adb devices or fastboot devices and report the results!
RAZERZDAHACKER said:
It is okay, just download and install this and connect your device. Open adb up and type adb devices, tell me what it says. Connect your phone in different modes (like recovery or bootloader) and test the adb devices or fastboot devices and report the results!
Click to expand...
Click to collapse
in the guide "USB Debugging MUST be turned ON in the device for ADB to see it" i dont think i can do that since i cant open the phone since it is hard bricked
jocelator said:
in the guide "USB Debugging MUST be turned ON in the device for ADB to see it" i dont think i can do that since i cant open the phone since it is hard bricked
Click to expand...
Click to collapse
But did you plug it in in different modes though? Also, try out this univeral unbricker that I wrote https://drive.google.com/open?id=0B6vSHGXxJIWmalZoWnNaTVczT0E
RAZERZDAHACKER said:
But did you plug it in in different modes though? Also, try out this univeral unbricker that I wrote https://drive.google.com/open?id=0B6vSHGXxJIWmalZoWnNaTVczT0E
Click to expand...
Click to collapse
what different modes? enlighten me
jocelator said:
what different modes? enlighten me
Click to expand...
Click to collapse
Fastboot, sideload, recovery, all kinds of stuff that enables you to access it through adb or fastboot.
Btw, that tool I gave you, I scripted it while I was tired and I didn't test it (nightly build) but this one I tested today and it works marvelous.
Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Leonardo_f said:
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Click to expand...
Click to collapse
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
GarciaGotti said:
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
Click to expand...
Click to collapse
I don't know whether you can enable USB debugging through fastboot ... i'll leave that to the experts.
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
khajoor said:
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
Click to expand...
Click to collapse
yeah i got that part, but when i try to flash or write anything to the device using fastboot i get nothing but errors so im guessing usb debugging must not be enabled
I'm sorry to say, you cannot enable USB Debugging through fastboot.
Hit the thanks button if i helped answer your question
Those errors have nothing to do with USB debugging. Your bootloader might not be unlocked so the flashing commands aren't working, or you're using wrong commands. USB debugging is at the ROM level and is for enabling adb while booted into the ROM. At the bootloader level, only fastboot commands work if the bootloader is unlocked. adb does not work. You need a custom recovery like CWM/TWRP for adb to work, and this recovery has to be flashed via 'fastboot flash recovery <recovery name>.img' on an unlocked bootloader.
Sent from my Nexus 7 using xda premium
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
lotuxete said:
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
Click to expand...
Click to collapse
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
jwoegerbauer said:
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
Click to expand...
Click to collapse
True, I can see my Xiaomi on "Windows Explorer", but it's an empty folder because I can't select MTP mode instead of "only charge" mode that it's launched by default.
What if I flash a TWRP recovery (I'll need to open bootloader first) and then from TRWP I try adb?
It must be a solution... if profesional people can do it so we do.
Thanks.
Iv'e been looking around for a root for my device and I can't seem to find a root. Is there even a root for it yet?
Guys come on. Its been almost 4 months now and still no root. I just want to delete all the bloat ware off my device so that I can use it more.
Well I guess there isn't a root for my device. If anyone needs to root this device your out of luck.
Perfectly fine Android build per se; you want to change what?
You were joking, right? Going into the about/device and tapping on the kernel version lets you pick a ROM from microSD.
One supposes that you would use adb to make verify all your build assumptions are OK, grab Android developer kit and blobs on your development box of choice, and build your new improved ROM. Boot to glamour-shot portfolio FTW.
Separately, Internet reports are that Kingroot.net works, at least from the Windows side (perhaps after a little name tweaking from that side of adb resource names; see the perfectly serviceable P10A7100 note on Reddit. On the Android side I'm still looking at a spinner and '01%' root acquisition progress. But then I should give Kaspersky and Malwarebytes the day off while this is going on, right?
Hello,
New to the adb thing. I want to say first off, that this tablet has to be the worst POS I have even had. Its has 32 gb of memory but I can only use 6 of it for apps before it slows to a complete useless doorstop. Could anyone reccomend a good rom image?
I have the same issues. Can't believe they would sell such a POS! That's Best Buy a crap store that used to be one of the best.
Insignia NSP10A7100 rooting
Any luck finding more info on root for this device? I've only tried kingroot so far from the apk but no luck. Also trying to find more info on how to root manually (without a script) or how to write my own script? I've enabled developer options, enabled bootloader unlocking. I can run adb from my ubuntu box but adb reboot bootloader just reboots? I see the option when tapping kernal to update a .zip file but what file? I haven't seen any roms or recovery's for this device. Any help is appreciated!
Insignia NSP10A7100
I was playing around with adb and fastboot tonight and did learn a few things. I had to use "sudo fastboot flashing unlock" to get the bootloader unlocked. Whatever that switch is in developer options to unlock did not seem to unlock anything. I did a getvar all and the output showed it as locked. sudo fastboot with no options gave me the list of commands to use. After reboot there was a screen that warned about the bootloader being unlocked and that it was not safe. I thought it was going to be stuck there but it did finally reboot into a fresh system. I've got files with the output of getvar all and bugreport if any of that info would help anyone with the rooting. If anyone can point me to more research I'll continue to play with this.
mjhack said:
I was playing around with adb and fastboot tonight and did learn a few things. I had to use "sudo fastboot flashing unlock" to get the bootloader unlocked. Whatever that switch is in developer options to unlock did not seem to unlock anything. I did a getvar all and the output showed it as locked. sudo fastboot with no options gave me the list of commands to use. After reboot there was a screen that warned about the bootloader being unlocked and that it was not safe. I thought it was going to be stuck there but it did finally reboot into a fresh system. I've got files with the output of getvar all and bugreport if any of that info would help anyone with the rooting. If anyone can point me to more research I'll continue to play with this.
Click to expand...
Click to collapse
I just got one and trying to access fastboot. I have model p10a7100. When I pick fastboot from recovery mode, I momentarily get resting android with "no command" and get recovery mode again. Because of low ram, I would like root access to install magisk for modules. Please explain your unlock method.
Fred Simm said:
I just got one and trying to access fastboot. I have model p10a7100. When I pick fastboot from recovery mode, I momentarily get resting android with "no command" and get recovery mode again. Because of low ram, I would like root access to install magisk for modules. Please explain your unlock method.
Click to expand...
Click to collapse
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
mjhack said:
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
Click to expand...
Click to collapse
Teach us your adb method. I have tried everything and it won't enter fastboot mode. If I type adb reboot fastboot, it just bypasses fastboot and boots up the tablet to android.
Update: I entered the adb command adb reboot fastboot and I get a giant green screen with a walking android robot in the center. Then I lose contact with the tablet. Never saw that before.
fastboot
Fred Simm said:
Update: I entered the adb command adb reboot fastboot and I get a giant green screen with a walking android robot in the center. Then I lose contact with the tablet. Never saw that before.
Click to expand...
Click to collapse
That is what I did also although I used "sudo adb reboot fastboot". Still not sure if the sudo is required? The giant green screen means you are in fastboot mode now. Type "fastboot" at the terminal to see a list of commands. The one I used to unlock was "sudo fastboot flashing unlock_critical". Type "sudo fastboot flashing get_unlock_ability" to find out if you are able to unlock the bootloader. This is as far as I got. Apparently I could now flash an image if I could find one that would be compatible. If you get any further or find one let me know.
mjhack said:
I have had no success trying to get root access. I only got the bootloader unlocked. I used adb to reboot into fastboot mode.
Click to expand...
Click to collapse
mjhack said:
That is what I did also although I used "sudo adb reboot fastboot". Still not sure if the sudo is required? The giant green screen means you are in fastboot mode now. Type "fastboot" at the terminal to see a list of commands. The one I used to unlock was "sudo fastboot flashing unlock_critical". Type "sudo fastboot flashing get_unlock_ability" to find out if you are able to unlock the bootloader. This is as far as I got. Apparently I could now flash an image if I could find one that would be compatible. If you get any further or find one let me know.
Click to expand...
Click to collapse
I lose all connectivity at fastboot. PC doesn't see it anymore.
Fred Simm said:
I lose all connectivity at fastboot. PC doesn't see it anymore.
Click to expand...
Click to collapse
Are you on Windows? I'm on Ubuntu. Not sure what would cause that. Maybe someone out there with more knowledge will chime in. Good luck.
Here is a link to a temp cwm recovery and root instructions for a nuvision 8 inch tablet. According to the post it might work on other intel based tablets. Disclaimer: You may brick your device. I still can't establish an adb connection to test this. I have adb with the tablet booted. I lose it in fastboot or recovery. I was able to unbrick my nuvision after 2 years of waiting for a method.
https://forum.xda-developers.com/android/general/nuvision-tm800a510l-info-root-recovery-t3471186
mjhack said:
Are you on Windows? I'm on Ubuntu. Not sure what would cause that. Maybe someone out there with more knowledge will chime in. Good luck.
Click to expand...
Click to collapse
Winblows 10. I think it's a driver issue.
Fred Simm said:
Winblows 10. I think it's a driver issue.
Click to expand...
Click to collapse
I was wondering if it might be a driver problem. You could try Virtual Box and run Ubuntu that way. I may try that cwm down the road. Thanks for the info.
insignia ns-p10a7100
tony5100 said:
Iv'e been looking around for a root for my device and I can't seem to find a root. Is there even a root for it yet?
Click to expand...
Click to collapse
i am waiting on thumb drive from insignia with source code
wmhaganjr1013 said:
i am waiting on thumb drive from insignia with source code
Click to expand...
Click to collapse
Did you ever get the source code for this tablet?
Hello,
I have specific problem.
I was on the stock rom 10.3.6... with root and twrp installed. So I wanted to update to Miui 11 and I uninstall Magisk and done the update through the twrp.
So, in order to back magisk I wanna to go to twrp via fastboot and PC. But I am constantly getting message "ADB devices unauthorized". Anyway... this is only happening when phone is shutted off(in order to go to fastboot mode). When phone is turned on everything is fine and I can se device via adb command prompt. I tried any written solution on internet but nothing could solve the problem. When I connect turned on phone I regularly get the question to authorize phone and I click ok. And while phone is turned on everything is fine and I have accsess to internal and external memory of phone.
Is there any possible solution to solve this stuck ? Is there some other way to boot into twrp besides fastboot ? For now I would skip installing magisk via stock recovery or without twrp access.
Thanks infront !
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
EugenStanis said:
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
Click to expand...
Click to collapse
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
visinacgile said:
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
Click to expand...
Click to collapse
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
EugenStanis said:
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
Click to expand...
Click to collapse
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
visinacgile said:
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
Click to expand...
Click to collapse
No problem. Leave it like it is for other users :highfive:
Please help me. My computer doesn't recognize Mi A3 while on Fastboot mode. I connect the phone to computer but whenever I run adb device in command prompt and it's not showing my device. Please help me! ?
Barbiox Dogg said:
Please help me. My computer doesn't recognize Mi A3 while on Fastboot mode. I connect the phone to computer but whenever I run adb device in command prompt and it's not showing my device. Please help me!
Click to expand...
Click to collapse
For fastboot you must use "fastboot devices". ADB and fastboot modes are completely different, learn more about them for example here https://www.makeuseof.com/tag/use-adb-fastboot-android/
I got it to work. I used another computer. I think I am having issues with ADB drivers on my computer. I will see what I can do.
Barbiox Dogg said:
I got it to work. I used another computer. I think I am having issues with ADB drivers on my computer. I will see what I can do.
Click to expand...
Click to collapse
First of all, you'll need to learn the difference between ADB and fastboot (they also use different drivers). If you follow one of many guides, you should be able to get it working in a few minutes. [emoji846]
Quick reminder:
ADB - used when phone's fully running
Fastboot - phone in a special mode ("turned off"), ready for flashing