Hey everyone,
I'm trying to install adb on my computer running Windows XP and I'm getting the error message "Daemon not running, starting it now on port 5037; ADB server didn't ACK; failed to start daemon; error: cannot connect to daemon"
Now, I've set up adb just like this thread http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/ told me to.
I've also tried stopping my anti-virus and my firewall is not running so as far as I know, the port 5037 is not blocked. I've killed adb.exe and all instances and restarted phone and computer. Any help on how to resolve this?
Swiftly sent from my rooted Photon
What are you trying to use the adb for?
To push my photon-torpedo.tar file to /data/tmp so I can root my phone. I lost root after I installed an update and I had used a different computer with adb the last time. In desperate need to get this going lol. The latest OTA won't install due to error: /system/app/booksphone.apk
Swiftly sent from my rooted Photon
I have a question, and a couple ideas.
Do you have access to a computer at this point in time?
And if you can, just download terminal emulator. Same thing as the adb you're trying to install.
If you have a computer, save the Photon Torpedo file into a folder on your desktop, Then shift right click and run in command prompt. :] That should fix it. If all that doesn't work, try the AIO one click method.
http://forum.xda-developers.com/showthread.php?t=1217416
Hopefully those things will get you going.
I get permission denied when trying to push with terminal emulator (I typed cp /sdcard-ext/photon-torpedo.tar /data/tmp) and will the oneclick method work if I'm getting the error for adb?
Edit: I have superuser and busybox installed.
Swiftly sent from my rooted Photon
{
"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"
}
Here is a screen shot of terminal emulator attempts
Swiftly sent from my rooted Photon
I would say try it from a computer then. If you have access to one. That is probably going to be your best bet. Unless someone else has an idea. I've never tried to root from my phone directly, I've always done it with the command prompt on the computer.
Ok. But again, will the oneclick method work if I'm getting the error message for adb? Also, you don't know what would fix the error?
Swiftly sent from my rooted Photon
I believe you are getting the error message because you are trying to do it from your phone. The way I have my root folder set up is with moto fastboot extracted. And the photon torpedo file zipped and put in there. So if you wanna run it via command prompt, try that. It may be failing though because you don't have the fastboot file included. That is necessary I believe. But don't quote me. I just know everytime I've rooted again, I had no issues with that setup I mentioned above. Try that. And let me know if it works.
Edit..
I seem to recall not being able to access files unless you set them to "Run As Root" so that could also be your issue doing it from your phone.
Even though the error message on OP is coming from command prompt? And how do I set to "Run as Root"? Never heard of being able to do that before, I think.
Swiftly sent from my rooted Photon
The error is coming from trying to install the adb in the OP though, correct? And as I said, if you follow those instructions, it SHOULD work. If not, try the one click method. If those don't work. Then let me know, and I'll ask around. Cause those are the only ideas I have.
Ocr should work because the necessary adb files are in the .zip, just run the .bat
Sent from one focused MoPho
Thanks. I stepped away from the computer last night to watch the Cardinals win the NLCS lol When I get home tonight, I'll try the OCR method. And come to think of it, I seem to recall having to place additional files in either the tools or platform-tools folder; yet, the instructions did not lead me to do this.
Swiftly sent from my rooted Photon
Tried running OCR. Got the daemon not running error
Swiftly sent from my rooted Photon
Okay. Reboot your phone. Try again. If not try another USB port. If no on all those try a different cable. If still no. Then you got me.
Sent from my Photon via XDA
It's gotta be something with the computer i imagine
Swiftly sent from my rooted Photon
Also, trying to use rsdlite to flash the sbf. Rsdlite is not seeing the sbf file in its file browser. Is this a 64 bit driver issue or do I need a different version of rsd?
Swiftly sent from my rooted Photon
Still nothing? Hm. What verison of RSD are you using? But that shouldn't matter. Not sure what to tell ya Man. That is weird.
Sent from my Photon via XDA
Using RSDLITE 4.5.3 I just can't figure this stuff out. Every time I think I have things working, I run into another error.
Here is the bottom line:
-My phone was rooted.
-I installed [root] talk for video chat which modified my build.prop file
-I received notification of a new update with google talk video chat
-Update failed.
-Attempted wipe to get it to install. No luck
-Realized it was because of the build.prop but lost root in the process of wiping
-Had to get root back to replace the modify build.prop file
-Did that by reinstalling superuser and running terminal emulator commands
-Tried update again
-Success
-Another prompt for an update
-Failed due to /system/app/booksphone.apk
-No more root due to last update
-Need root to convert google books to system app which must have been changed while rooted
-Terminal emulator commands get permission denied at /bin/tar xf /data/tmp/photon-torpedo.tar
-ADB gets "adb server didn't ACK" error while running normal adb and one click root
-Rsdlite won't find the sbf file i downloaded so I can reflash everything back to stock
So that's my process so far.
Any other thoughts on the matter would be greatly appreciated.
Swiftly sent from my rooted Photon
This is my latest effort using Terminal Emulator
Swiftly sent from my rooted Photon
Related
4 in 1 Reboot Menu with Extended Power Menu Options
First off, a HUGE thanks goes out to chingy51o for always being a help on whatever it is I may need.
Also, thanks to -sqn and chingy51o for the source in which I ported this from. As well as Nilsp, for taking the time to test with me.
Instructions:
1. This file can either be installed via adb or compiled with your ROM.
2. If you are a developer, I REQUIRE that thanks be given where its due.
3. You are using this file at your own risk. No-one else can be held responsible other than yourself.
This mod is for 1.02.605.6 deodexed and rooted ROM's only
{
"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"
}
DOWNLOAD HERE
FLASHABLE ZIP HERE
Great mod, makes it even easier to flash all these fantastic roms coming our way!
So is this something anyone can apply to any ROM they're currently running just by pushing it via adb ? If so, where do we push it to?
will work on any 1.02.605.6 rom that is deodexed and rooted
So I dig through Root Explorer a bit and found android.policy.jar in /system/framework, I assume we just push it to there then do a reboot and we should be good to go?
rboddy said:
So is this something anyone can apply to any ROM they're currently running just by pushing it via adb ? If so, where do we push it to?
Click to expand...
Click to collapse
Yes, push it to /system/framework/
The question of how to adb push files comes up alot.
A long time ago I made it easy for myself since I do it often by creating the 2 scripts in the attached. Extract them to a folder and all you have to do is drag and drop the files over the appropriate batch file.
Just boot into recovery, mount system, and do this.
For example this jar file would be dragged and dropped on the
2_FRAMEWORK-Push_(Drop Here).cmd
This assume adb is in your system path. If it is not you will find out quick.
Do we need to be in recovery to push via adb on the Rezound? I tried doing it and kept getting this:
c:\sdk\platform-tools>adb push c:/sdk/platform-tools/android.policy.jar /system/framework
failed to copy 'c:/sdk/platform-tools/android.policy.jar' to '/system/framework/android.policy.jar': Permission denied
Am I doing something wrong or is the Rezound just a bit funky? I made sure to set everything to R/W in Root Explorer, since I was originally getting a "Read-only file system" error.
rboddy said:
Do we need to be in recovery to push via adb on the Rezound? I tried doing it and kept getting this:
c:\sdk\platform-tools>adb push c:/sdk/platform-tools/android.policy.jar /system/framework
failed to copy 'c:/sdk/platform-tools/android.policy.jar' to '/system/framework/android.policy.jar': Permission denied
Am I doing something wrong or is the Rezound just a bit funky? I made sure to set everything to R/W in Root Explorer, since I was originally getting a "Read-only file system" error.
Click to expand...
Click to collapse
you must be rooted... make sure the jar is either in your adb folder or you have adb in your path
adb remount
adb push android.policy.jar system/framework
adb reboot
I am rooted, and was trying to do this via adbWireless, so maybe the connection was wonky even though adb said my phone was connected. So I dunno what's happening, so instead I just Dropbox'd it over and moved it via Root Explorer, phone is rebooting now so we'll see if that worked, I'm assuming it should. Maybe the adb remount command would have helped. I'll give it a whirl with that for ****s and grins.
EDIT: Moving inside Root Explorer worked, thanks for supplying this file man! Sooo much better than the damn battery pull lol
How does one make this flashable? I did move it via rootexplorer but it's not showing the extra settings after boot.
Sent from my ADR6425LVW using XDA App
make sure adb is in your enviromental path....
then open cmd
type
adb remount
adb push android.policy.jar system/framework
adb reboot
Thanks bored! Great work! The entire community appreciates you sharing this! Its just in time for another build of CleanROM! Timing could not have been better.
Here is a flash-able zip version of the file. You can add it to OP if you want and can pull it from this post. Eitherway...
Thanks again for this!
-Scott
thanks.... added to op.... i was gonna make one but trying to focus on my rom instead... the 4 in 1 was a must though
That looks great! I always thought the quick settings menu had weird choices on stock.
Wondering if there's any reason you took out bluetooth though? I guess I don't use it that much but I turn it off whenever I leave my car at the shop cuz otherwise my phone calls/music go to the car if I'm hanging out and they have it turned on. lol.
lllboredlll said:
thanks.... added to op.... i was gonna make one but trying to focus on my rom instead... the 4 in 1 was a must though
Click to expand...
Click to collapse
I totally understand how that goes. Thats also a generic flashable that I use. You can add /app/ to it. I use it for testing changes....
So now we can just flash this through recovery?
Evo4gLI said:
So now we can just flash this through recovery?
Click to expand...
Click to collapse
the one scott attached yes
feralicious said:
That looks great! I always thought the quick settings menu had weird choices on stock.
Wondering if there's any reason you took out bluetooth though? I guess I don't use it that much but I turn it off whenever I leave my car at the shop cuz otherwise my phone calls/music go to the car if I'm hanging out and they have it turned on. lol.
Click to expand...
Click to collapse
it wasnt working properly... once i get my rom done i'll back up and try to lay it to rest
Thanks for the flashable zip!!! Worked nice & easy with CWM.
Sent from my ADR6425LVW using Tapatalk
I cannt install apk via android terminal emulator
i have tried
$cd /sdcard
$pm install apk.apk
but i always get this error message
[1] killed
DigitalPerson said:
I cannt install apk via android terminal emulator
i have tried
$cd /sdcard
$pm install apk.apk
but i always get this error message
[1] killed
Click to expand...
Click to collapse
If I am not wrong you have to use SU command first to get root access.If that is not working, Try installing the .apk using a root explorer such as ES File Explorer or File Explorer....
also make sure that install from non market sources is ticked from within settings
Sent from a desire z
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
glevitan said:
If I am not wrong you have to use SU command first to get root access.If that is not working, Try installing the .apk using a root explorer such as ES File Explorer or File Explorer....
Click to expand...
Click to collapse
I have tried the same commands from the windows cmd:
Code:
adb shell
$cd /sdcard
$pm install apk.apk
without SU and even the device isn't rooted ,and it works
but it doesn't work when I try the commands directly from the android terminal emulator
I am asking this question because i want to develop a program not just to install apk package
bombadier said:
also make sure that install from non market sources is ticked from within settings
Sent from a desire z
Click to expand...
Click to collapse
yes i have enabled installing programs fro unknown sources
but it doesn't work
try other terminal app.
I use terminal ide. it's cool.
DigitalPerson said:
I have tried the same commands from the windows cmd:
Code:
adb shell
$cd /sdcard
$pm install apk.apk
without SU and even the device isn't rooted ,and it works
but it doesn't work when I try the commands directly from the android terminal emulator
Click to expand...
Click to collapse
If you try it in gingerbread it will work. I have tested it. But on ICS it will not work. It is a bug in ICS su binary or in busybox.
I have tried terminal ide and tried to do the same thing on another device with Gingerbread and on Froyo
I always get the same error message
DigitalPerson said:
I have tried terminal ide and tried to do the same thing on another device with Gingerbread and on Froyo
I always get the same error message
Click to expand...
Click to collapse
I tested on ARHD GB . Which ROM r u using ?
sometimes I get this error message
{
"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"
}
musarraf172 said:
I tested on ARHD GB . Which ROM r u using ?
Click to expand...
Click to collapse
I have tried it on my nexus s with 4.0.3 rooted stock rom
and also tried it on android emulator with 2.2 and 2.3 and 4.0.3
non of them worked
DigitalPerson said:
I have tried terminal ide and tried to do the same thing on another device with Gingerbread and on Froyo
I always get the same error message
Click to expand...
Click to collapse
Interestingly pm install command works on ICS from ADB terminal on PC.
musarraf172 said:
Interestingly pm install command works on ICS from ADB terminal on PC.
Click to expand...
Click to collapse
yes it works from adb on PC
but it doesn't work directly from the android terminal
up up up up
up up up up
I have also tried to do the same thing on HTC Deire with CyanogenMod 7.0 ROM and kernel g37556d9
and I get the same error message:
[1] killed
same here
i am also trying to install an apk from terminal on my phone (htc desire currently trying out an ICS rom). I do not have a file browser so cannot install from that. i do not have adb as i am at work and cant put it on the pc. i do not have market access on my phone because i am on a boat halfway between norway and scotland. so my only option is through terminal.
i have tried the install command, the pm install command, the am start command to get androids built in package installer to do the install and nothing works. i get exactly the same as the screenshot above.
i've also tried inserting the apk into the rom zip then resigning and flashing the rom again and that doesnt work either. the app i'm trying to instrall is es file explorer as this would then enable installing from the file browser.
there really must be a simple way to do this but i cant find one that works.
the closest i got was just using install as with this the icon appeared in my apps list (after a reboot) but the apk was just copied not properly installed so the app didnt work when clicked on.
any help here would be greatly appreciated
cheers
update:
DigitalPerson this may help you too.
i kept trying and then decided to try a different apk, this time astro file manager. the following worked (in ICS on my desire)
su
cd /sdcard
install com.metago.astro_247.apk /data/app/com.metago.astro_247.apk
so the reason is either a problem with the original apk i was using or just the naming convention. i.e. the apk name should be in its "com.company.app.apk" format which can hopefully be found online somewhere.
further update
just some more info.
now that i have successfully installed astro i tried installing the original es file explorer apk from within astro. it worked fine which suggests the apk is fine so it was just the naming convention for the apk that i needed to have right. i havent seen this described elsewhere but i dont think there are many people out there who would have run into this problem. also i'm just learning with android so although my reasoning points to just the name of the apk being wrong i could just have got lucky and it could be something else completely.
anyway i hope this helps someone
I have a ZEKI 10" TBQC1063B tablet. It apparently an updated version in that it now comes with Google Play Store app installed from the factory. It has Android 4.1.1.
I started to try to Root the device, but was unsuccessful.
In my quest to debug Rooting, I started trying playing with ADB directly. I quickly discovered I could not get to 'first base' with ADB.
Yes, I have USB DEBUGGING enabled, and when my tablet is plugged into my PC, the tablet shows that icon of the Android face in the status line in the lower right screen.
I started to try different drivers (reading that such might be the cause of ADB not working), even though all of the appear to be working OK when I check in Device Manager. One of the attempts I made at drivers led me to those offered as part of PDAnet. While using PDAnet's drivers didn't seem to help, I did stumble upon a CLUE. The CLUE is that while installing the PDAnet drivers, PDAnet did successfully install its own app onto my tablet. I think that such requires ADB to work, no? Could someone confirm such (or not)?
I tried a PC program called AdbDriverInstaller. When I first tried it, it reported a Device Status error of "Driver Incorrectly". So, I uninstalled that driver (I belive at that point it was the PDAnet one), and installed a new driver from a collection called UniversalAdbDriverSetup6. Now, that looked better. AdbDriverInstaller now shows:
{
"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"
}
Looking better?
My problem is that ADB DEVICES still shows no devices:
Does anyone know of anything else to try? This is about the limit of my expertise.
Try!
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Kunal.Kene.1797 said:
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Click to expand...
Click to collapse
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
WaltA said:
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
Click to expand...
Click to collapse
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Also, this is a good tool..makes adb system wide as well HERE
Also, not sure when Android implemented this, you might see a box up asking for you to grant the PC permission to use ADB, grant it
WaltA said:
Click to expand...
Click to collapse
lacoursiere18 said:
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Click to expand...
Click to collapse
I unplugged and plugged my tablet in a few times (over a course of several days while I tried to debug this on my own). Both my PC and my tablet have been powered on/off and rebooted over that time too.
I believe I showed I ready tried those commands, with no success.
TBQC1063B Zeki tablet
Zeki TBQC1063B
Any roms available? This one seems to be stuck. I can get to the boot list, but haven't found a new rom for it. Or even the factory rom.
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
While you can (sometimes) install an OTA while your phone is rooted, you should never try to install one when it is fully unlocked (i.e. - custom recovery installed). You edit seems to indicate you fixed it, but if you're still having issues I know there are steps to get out of the bootloop you're experiencing, I just don't have off hand where they're at. Bottom line, if you're root AND unlocked (running twrp), you should never take an OTA as there's no reason for it. You can install one of the fine stock-based roms that have been updated to the latest VZW software and have no risk in doing so. Just for future reference
ToF_Itachi said:
So i read a bunch of threads and people said the new update was fine and wouldnt try to remove root. So i decided to give it a go and see if that was true. Well when it rebooted it keeps rebooting into twrp no matter what i do. Im not good with linux commands but how do i fix this? Also i only have one file to be modified and thats for the dual window mod so i could dual window all apps. Is this part of the problem?
I found a thread that told me some command lines to restart the phone without needing to wipe but how do i get rid of this ota update?
Click to expand...
Click to collapse
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
Follow this command lines and that will or should reboot your phone to before you tried to install the newest update. The same thing happened to me with the last update. Those commands came in handy.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Pays to have a copy of LG Flashtool and the stock firmware
See the first post here: http://forum.xda-developers.com/showthread.php?t=2907508
If you have a USB otg cable, you can put the flash...zip file linked in the post on a flash drive, then tell twrp to install that to clear the ota.
Alternately, twrp has a small terminal emulator. Look at the part of the post with the commands listed. Only input the su and two dd command lines, in twrp.
After either of the above, tell twrp to reboot to system.
Once you can successfully get back to your normal system, either freeze "System updates...." or use a file manager to rename the two LGDMSClient files found in /system/app, then reboot your phone one more time.
{
"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"
}
HTH!
Hello Everyone!
I need urgent help from you all because I am currently stuck in a very bad situation. Please please please!! Help me to get out of this. Let me start from the beginning of whatever I did. This is going to be a very long post so please bear with me.
Why did I try to root my device?
I have Realme 1 which works on Android 9 and does not support internal screen recording. So I thought rooting would help me and I would be able to create gaming videos.
1st Phase:
I researched about how to root my device.
I came to know that first I’ll have to unlock my bootloader.
I tried to unlock my bootloader and when I was running the necessary commands like fastboot reboot, it simply showed, “Waiting for device…..”
Now confused, I went to the Device Manager and uninstalled Android and its drivers from the category of other devices by mistake. Now, my problem was that, how to pass commands to my device?
Next, I deleted everything, and started from scratch. This time, I connected my device (via the same USB cable) and I did something (I don't exactly remember what I did, but ultimately it lead me to Windows Update, where I clicked on View Optional Updates and updated the driver. I am attaching a screenshot of what I had installed.
Next, I downloaded platform tools, extracted them and in the address bar typed cmd and did the following checks to ensure that my device can receive commands.
When device was powered on:
adb devices
Returned: _________ device
Next command:
adb fastboot (Something like that which took it to the fastboot mode)
Next Command:
fastboot devices
Returned: _________ fastboot
Satisfied that I was going on well, I unlocked the bootloader using the respective commands.
2nd Phase:
Now I knew, my bootloader was unlocked, so I did the next step.
I switched to fastboot mode.
Downloaded boot_patched.img for Realme 1 C.50
Next, I pasted it into the platform tools folder.
Next, booted my device into the fastboot mode, and gave the flashing command.
Confirmed it on my device using volume up key.
Gave fastboot reboot command to reboot my device.
Downloaded Magisk Manager and rooted my device successfully.
Downloaded RootChecker app to be sure and got the positive result.
I downloaded the apps I needed.
Problem Phase:
I had downloaded a banking app but it didn’t work because my device was rooted, so I searched, “How to hide root from banking apps?”
I came to know that the solution for this was on Magisk Manager itself. Magisk Hide
So, I opened the Magisk Manager and I was shown a prompt to download something (Or maybe I downloaded something from the settings? It was something like system host module or something like that) Now I don’t exactly remember whether my device rebooted or not, but let me continue.
So, I went to settings, enabled Magisk Hide, selected the app from which I had to hide root and opened the app. It didn’t work.
I searched the internet and saw that I had to reboot my device as well.
After I did that I faced a more serious problem. The app was still not working and my sim cards were disabled.
Now I panicked, I did the ultimate thing for which I had rooted my phone, I downloaded the game and the screen recorder. I chose the internal sound recording option, it told me to download some Magisk Module for it to work. So I did it.But it still didn’t work.
Now I was sad, I didn’t know what to do. Then ultimately I opened my RootChecker app and check the root status of my device and you guys won’t believe what I saw.
" No proper root access granted "
Super Problem Phase:
I decide that I’ll unroot my device. So, I set down to work.
I got to know that I had to uninstall the Magisk Manager completely. I did so and my device rebooted.
There came a wave of relief, my sim cards started to work.
I thought that my device was unrooted now, so I opened my banking app and it showed: “Your device is rooted! You can not proceed further.”
I was confused, I checked the rootChecker and it clearly said the same thing. No root access.
So, I searched the web again and I was told that if I remove some files like su and one more file (I don’t exactly remember the name) then my device will be unrooted. I donloaded the es file explorer but didn’t find those files.
I searched the internet again and found something new. If I reset my device, then the root will go away. I was very happy. I did a factory reset of my device and this time I didn’t check the banking app, I did one more thing which I was not supposed to.
Ultra problem phase:
I got to the fastboot mode using the same commands in the adb terminal and decided to lock the bootloader. I thought that the app had detected that my bootloader was locked so that may be the reason it was not working. I gave the command:
fastboot flash lock
(it was something like this, I don't quite remember)
I confirmed that I wanted to lock my bootloader.
And that led me to my doom.
I rebooted my device using the command.
My device never started.
After the logo, or to say while booting I was shown this error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it."
Then I though maybe I could just download the original boot and recovery file again then it would be all fine. I have those files and everything, when now I try to give those commands, they just show "Waiting for device...." Moreover the computer doesn't detect my device. The only thing I can do is just go to recovery mode.
Guys, I told you all everything that I knew please give me a detailed solution to the problem. I am also attaching some images so that you can see what exactly has happened.
Thanks in advance.
{
"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"
}
Sorry to say, but ... flashing unofficial/custom firmware and rooting has risk of bricking your device. And locking the bootloader was not the right/, best option
Maybe you have a chance to get it working again by flashing a complete firmware to it. Hopefully it will be successful after locking the bootloader