Hi,
This is my first thread on XDA and I need urgent help.
I am using a rooted Lenovo A536. Few months ago, I rooted it and started messing with the system UI using Xposed and other apps.
I changed the boot animation several times when I got bored of the old one. Created custom boot animations and all and was changing the boot animation almost every 2 weeks.
But today, things didn't went as expected because of a stupidity of mine. I modified a boot animation which had two folders, namely "part0" and "part1". The thing I forgot to modify was the desc.txt. It was as follows:
480 854 20
p 1 0 part1
p 0 0 part2
As you can see here, I forgot to change the folder names in the txt file and they were "part1" and "part2" instead of "part0" and "part1".
I installed the bootanimation through JRummy Bootanimations app. After I rebooted the device, I could only see the image that was stored in "part1" folder. A few seconds later, the phone vibrated for a fraction of a second while the brightness turned down, as always happens when booting up an android device. But the image of part0 folder was still there. I could hear notification ringtones and all. I tried calling on that phone, the phone rang normally but that image from bootanimation was still on the screen. I swiped on the area where the receive/decline slider is placed. The call got answered. I could hear all the voices and talk normally. I tapped the area where end call button is placed. The call ended. In short, the device is fully working but that bootanimation image is acting like an overlay on the screen.
I can access the recovery menu but can't figure out what to do! I don't want to factory reset as I don't want to lose any of my precious data.
Can I flash a new boot animation, or remove the current one so that the overlay of bootanimation gets removed?
The device has stock recovery.
Can anyone help please?
I'll try to post a video of the device later so that you can better understand the issue.
Do let me know if you require any other details. But I urgently need the device. I don't have any other phone with me ATM.
If you got adb enabled you can push a new bootanimation to your device.
tys0n said:
If you got adb enabled you can push a new bootanimation to your device.
Click to expand...
Click to collapse
Could you please guide me doing the same? When I press the power and volume up keys, a chinese recovery menu opens up. I don't know what it is as everything is in Chinese. With this menu opened, when I connect my phone to USB cable and open up ADB, and type ADB devices, I get the following message! This means that my device is being detected and I can push the bootanimation.zip, right?
link: prnt.sc/e7v7j6[/url]
manav20 said:
Could you please guide me doing the same? When I press the power and volume up keys, a chinese recovery menu opens up. I don't know what it is as everything is in Chinese. With this menu opened, when I connect my phone to USB cable and open up ADB, and type ADB devices, I get the following message! This means that my device is being detected and I can push the bootanimation.zip, right?
link: prnt.sc/e7v7j6[/url]
Click to expand...
Click to collapse
That didn't work. I tried adb reboot command but it said that the device is unauthorised. Please accept the permission. It was something like that. Don't exactly remember.
I have a question. The stock recovery has an option "Apply update from ADB". When I open it, a message appears, "Now send the package you want to apply to the device with "adb sideload <filename>"..."
So, can you help me out please? It's really urgent! I've missed many important calls and whatsapp messages just because of that wrong desc.txt! :/
manav20 said:
That didn't work. I tried adb reboot command but it said that the device is unauthorised. Please accept the permission. It was something like that. Don't exactly remember.
I have a question. The stock recovery has an option "Apply update from ADB". When I open it, a message appears, "Now send the package you want to apply to the device with "adb sideload <filename>"..."
So, can you help me out please? It's really urgent! I've missed many important calls and whatsapp messages just because of that wrong desc.txt! :/
Click to expand...
Click to collapse
I don't think stock recovery will flash anything that's not signed with Lenovo's private key.
Yeah, first time adb connection from a new connected computer must be authorized on phone.
{
"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"
}
You could try to hit the YES button, as the touch still worked fine... Can be a bit tricky but that should do it.
tys0n said:
I don't think stock recovery will flash anything that's not signed with Lenovo's private key.
Yeah, first time adb connection from a new connected computer must be authorized on phone.
View attachment 4040059
You could try to hit the YES button, as the touch still worked fine... Can be a bit tricky but that should do it.
Click to expand...
Click to collapse
Hey,
I have successfully installed TWRP 2.7.10 using SP Flash Tool. What do I do now?
manav20 said:
Hey,
I have successfully installed TWRP 2.7.10 using SP Flash Tool. What do I do now?
Click to expand...
Click to collapse
Also, USB Debugging wasn't enabled on my device. So adb didn't detect it. I have already wiped the data partition as I mainly needed contacts and whatsapp and some apps that I already had a backup of on SD Card.
manav20 said:
Hey,
I have successfully installed TWRP 2.7.10 using SP Flash Tool. What do I do now?
Click to expand...
Click to collapse
That's great. ADB works from twrp now? file should be in same directory as adb.
You can google for commands but it should be something like:
Code:
adb push bootanimation.zip /system/media/bootanimation.zip
or
Code:
adb push bootanimation.zip /data/local/bootanimation.zip
It depends on where the file is stored..
Even if it doesn't..you can still put your working bootanimation.zip in your sdcard, then use twrp's built in file manager or terminal to copy/move files and change file-permissions if needed.
Thank god! I finally managed to delete the bootanimation.zip file from system/media using TWRP File Explorer and my device booted finally!
Thanks for your suggestions tys0n. Appreciate that!
Great!
TWRP sure make things easier if one makes a mistake [emoji14]
tys0n said:
Great!
TWRP sure make things easier if one makes a mistake [emoji14]
Click to expand...
Click to collapse
True that! I once tried to install TWRP a few months back, but was unable to do so due to some error. And I never tried to install it again because of laziness! If I had overcome this laziness and had TWRP installed at that time, I wouldn't have needed to go through all this! xD
Related
Hi everyone trying to install a new ROM (cm12 hopefully) to my phone, the phones boot loader in unlocked ive installed TWRP 2.8.5.0 every time i select the 2 rom and gapps zip files for flashing i get error message saying failed and back to the main menu.
Please can anybody help its driving me mad.
David Thompson.
dave0147 said:
Hi everyone trying to install a new ROM (cm12 hopefully) to my phone, the phones boot loader in unlocked ive installed TWRP 2.8.5.0 every time i select the 2 rom and gapps zip files for flashing i get error message saying failed and back to the main menu.
Please can anybody help its driving me mad.
David Thompson.
Click to expand...
Click to collapse
use cm-12.1 make sure you full wipe everything (except data/media you can still format data without nuking the internal sd partition)
Make sure you select the rom FIRST then gapps, also please for the love of jesus remember to flash the boot.img once you've finished flashing the rom + gapps.
If that still fails, give me the recovery.log file.
Getting knowhere just getting FAILED message in red as per your instructions ...
it fails after the rom and g apps install i dont even get to the boot.img
dave0147 said:
Getting knowhere just getting FAILED message in red as per your instructions ...
it fails after the rom and g apps install i dont even get to the boot.img
Click to expand...
Click to collapse
Per my instructions I also said get the recovery.log for me
go to ADVANCED > COPY LOG TO SD
once you have gotten the "fail" message.
then pull it off and upload it for me.
Recovery file see attached.
dave0147 said:
Recovery file see attached.
Click to expand...
Click to collapse
I see the problem, easy fix mate.
script aborted: This package is for device: endeavoru; this device is enrc2b.
Download the ENRC2B One which is the ONE X+ not the ONE X version
https://www.androidfilehost.com/?w=files&flid=28732
The latest one is at the bottom. I also suggest you read this : http://forum.xda-developers.com/htc-one-x2/help/wifi-data-cm-roms-read-posting-t3158955
Done as you stated above but my phone is now stuck on the CM12 loading screen the animation is running but it just stays this way (left the phone for over an hour and no change).
dave0147 said:
Done as you stated above but my phone is now stuck on the CM12 loading screen the animation is running but it just stays this way (left the phone for over an hour and no change).
Click to expand...
Click to collapse
Did you flash the bootimage?
Hi Lloir,
Not sure if i did this in the right order
1. added cm12 rom zip
2. added gapps file
3. swipped and installed the two files above no error message.
4. this is where it may have gone wrong i extracted theBOOT.ing file from the CM12.zip file and added that to TWRP recovery and installed.
5. Re Booted the phone and thats where it does nothing but run the animation.
David.
dave0147 said:
Hi Lloir,
Not sure if i did this in the right order
1. added cm12 rom zip
2. added gapps file
3. swipped and installed the two files above no error message.
4. this is where it may have gone wrong i extracted theBOOT.ing file from the CM12.zip file and added that to TWRP recovery and installed.
5. Re Booted the phone and thats where it does nothing but run the animation.
David.
Click to expand...
Click to collapse
You didn't read the link I gave you. Click the Here in my signature, and follow them step by step.
dave0147 said:
Hi Lloir,
Not sure if i did this in the right order
1. added cm12 rom zip
2. added gapps file
3. swipped and installed the two files above no error message.
4. this is where it may have gone wrong i extracted theBOOT.ing file from the CM12.zip file and added that to TWRP recovery and installed.
5. Re Booted the phone and thats where it does nothing but run the animation.
David.
Click to expand...
Click to collapse
The boot.img isn't supposed to be installed within TWRP. You have to manually flash it through fastboot
Holy crap GRRRRR
done what you said followed your instructions and flashed the boot.img from your link re started the phone and now im getting the white HTC quietly brilliant boot screen then nothing happens.
thanks for your help so far.
David
dave0147 said:
Holy crap GRRRRR
done what you said followed your instructions and flashed the boot.img from your link re started the phone and now im getting the white HTC quietly brilliant boot screen then nothing happens.
thanks for your help so far.
David
Click to expand...
Click to collapse
Ok lets go through this in easy steps.
0) open the ROM ZIP with winrar/7zip and pull out the boot.img
1) reboot into recovery and Wipe system/cache/data in recovery
2) Flash rom + gapps
3) make sure the phone is CONNECTED to the pc and assuming you read the instructions from the other post you have the android adb tools
4) reboot into fastboot it will show this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(random image off the internet)
5) open up the cmd on the pc and go cd to the folder where adb is, in that folder make sure the boot.img is in there and do the following :
fastboot flash boot boot.img
fastboot reboot
sorted.
I know the rom's all boot I test them before releasing.
All done thanks so much for the help one x plus is now update my accounts and apps.
is there a way of checking if theres new ROM updates for the phone?
thanks david thompson
dave0147 said:
All done thanks so much for the help one x plus is now update my accounts and apps.
is there a way of checking if theres new ROM updates for the phone?
thanks david thompson
Click to expand...
Click to collapse
Just check the forum dude. CM-12.1 is unofficial.
Glad your all sorted now, at least you learnt something from this
Can you help with this problem ... i can change my voice mail settings from 901 to 443 it say it wont change.
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
khaytsus said:
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
Click to expand...
Click to collapse
Ok cool i just made this guide for all the people who are affected by this bug myself included
Xmaster24 said:
Ok cool i just made this guide for all the people who are affected by this bug myself included
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well add 5 more guys I got 3 thanks here and another two on another help request
Fantastic!! Thank you. I have been pulling my hair out trying to figure out why my watch was all of a sudden "unauthorized" after updating. to 6.0.1
Guys just realised the whole cause of this when I flashed everything stock for the new update. It turns out that the actual cause of the problem was invisiblek's kernel and not the new system itself. sorry for any inconvenience this may have caused you.
(deleted)
New script
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Xmaster24 said:
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Click to expand...
Click to collapse
Thanks a bunch! Will be sure to give you credit on the thread.
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
GohanBurner said:
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
Click to expand...
Click to collapse
Make sure you have the adb driver installed, fastboot uses a separate driver and it does not require authentication either
KevinX8 said:
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Click to expand...
Click to collapse
i knew it has something to do with adbkey
Hi there,
I recently got the Homtom HT16 for just 50 bucks. I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the HOMTOM HT7.
Anyone knows if I can use the TWRP for the HT7 or is there any other way to root my phone?
Sorry for late response. On Russian forum you may find way to install recovery with Flash tool, however that didn't worked for me. Their TWRP recovery is useful for rooting. This is 100% tested, I own HOMTOM HT 16.
1. Install adb-setup-1.4.3 to enable adb, fastboot and Google USB driver on computer..
https://www.dropbox.com/s/wvsyab1iakpsswu/adb-setup-1.4.3.exe?dl=0
2.Settings-Developer optons Enable USB Debugging and Allow OEM unlocking
3.Put on sd card SuperSU-v2.78-201609011115 (this version worked for me).
https://www.dropbox.com/s/84xm1m7rxerg6kt/SuperSU-v2.78-201609011115.zip?dl=0
4. Turn off the phone, press Power and Volume up. You'll see new menu. Move with Volume up, choose Fastboot and press Volume down. Connect computer and phone with USB cable.
5. Find the directory where adb and fastboot are installed and position itself there . Hold Shift, right-click and choose Open command window here. ( If you are not the administrator, Windows 10 Start, Command Prompt (Admin) and position yourself in directory where fastboot is installed with cd command).
Copy TWRP recovery (recovery.img) in that folder.
https://www.dropbox.com/sh/t26oax8n96izp60/AACq00Cgo1iMFOWPAT8leRXZa?dl=0
5.Type and execute commands:
fastboot devices (check if device if recognized, you'll see the serial number)
fastboot oem unlock (press Volume up to unlock bootloader)
fastboot flash recovery recovery.img (install new recovery on phone)
6.Pull out battery, push it back . Hold Power and Volume up. You'll see new menu. Move with Volume up, select Recovery and press Volume down.
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
8. Reboot phone and check with Root checker application root rights.
(optional) If you need restore factory recovery and remove Superuser, to keep warranty valid.
https://www.dropbox.com/sh/s6dvqr8ge72otfu/AACgOQ7CgrVk94o0_K6ACXtIa?dl=0
Hi, all I received yesterday the z11 max. Install recovery with super your and comborom V6.2 all ok. Problem does not update ota, it tells me no updates. I have made to the wrong? Thank you.
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
{
"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"
}
---------- Post added at 06:41 PM ---------- Previous post was at 06:34 PM ----------
The image not visible, these are the error message:
'Could not mount /data and unable to find crypto footer'
`Unable to mount storage`
and so one....
pecs72 said:
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
...
and so one....
Click to expand...
Click to collapse
I downloaded the original fw from needrom, then I put back the original recovery.img, so now it's as original, but without root...
I don't know what is the problem, this procedure worked on my phone.
Look here:
https://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
**** my phone factory resseted it self
No matter what I do, my phone doesn't allow to be found when I make "fastboot devices".
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Edit : can someone backup his nvram partition? I lost my imei and with this phone any trick wont work...
dani the hack said:
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Click to expand...
Click to collapse
Hi, for me the SuperSU from holocen (see above):
togeter with the TWRP image, flashtools v5 and the description from needrom worked for me (not every emailprovider can be used to create an account):
needrom.com/download/homtom-ht16-4/
Greetings Rikski
Solution found in here!!
Use TWRP for cyanogen after installing it with sp tools v5.
Put SuperSU v2.82 or above in the phone or sd memory card go to custom recovery and install the SuperSU v2.82.zip file. Reboot and that's it. It works like a charm. :good:
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
How long does blinking take usually? It blinks all the time, I can't select Install ?!
This phone has now nearly 30 ROMs on needrom.com
Plus a non blinking custom TWRP recovery, go check it out:
needrom.com->Doogee->Homtom->ht16
I tryed to follow the guide of holocen (also used much of external information) but right now i'm stuck in a bootloop.
First of all i needed hours of reading and troubleshooting to get my adb "cmd" working proberly with the "bootloader mode" (cause of a driver problem).
After i was successful ("fastboot devices. fastboot oem bootloader) , i tryed serveral twrp recovery *.img's (officials first, holocen's later on), but i can't get the ht16 out of bootloop. Recovery flashing seems to be successfull though.
If i try "volume up + power" and start up the recovery manually, i got the twrp splashscreen, followed by a huge chunk of red "unable to mount xyz..." with a following bootloop (there are only seconds to see whats happening, an then the "HomTom" splashscreen reappears). I tryed "fastboot erase userdata" with no help. Was insecure about the "fastboot erase system" command though.
Maybe some of you guys are eager to help. I really tryed to read up as much information i could about this topic. I thank you in advance.
Target was to root the phone and to install some kind of lightwight custom rom (just to get rid of those frikk'n "trojans, bloatware-viruses, marketing horrors" which are messing with the stock rom. Hopefully everybodys know right now what i'm talking about).
I try to respond quickly, but i can't garuentee.
Thank you very much for reading.
Best regards
B4dLuck
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
hi guys and girls
i was messing around with my phone and some how stopped gboard from working after android starts. this means that i cant enter my password, and am stuck at the lock screen.
i have adb+fastboot, and if a start the phone in recovery mode the phone is listed with "adb devices" but not authorized "adb: connect error for write: device unauthorized" , so i cant get my data off and factory reset and i cant install another keyboard program
i also tried entering the password using this methord -> https://stackoverflow.com/questions...ocked-phone-when-password-contains-as-first-c
is there a better way for me to enter my password via adb ?? or something else i can do to regain access ?
any suggestions are welcomed.
ps. its a ulefone armor x3 with Mediatek MT6580 chip set. phone is stock, never rooted. OTG not supported, no debugging enabled.
cheers
gazza
ga77a said:
i cant install another keyboard program
Click to expand...
Click to collapse
Can you login to the playstore from a computer and install gboard
Not_Rich said:
Can you login to the playstore from a computer and inst
Click to expand...
Click to collapse
hi not_rich
thank you for the reply
i did already do that, and the keyboard did install, but is not activated.
let me clarify exactly what happens when i start the phone, so as to give you a better idea.
when i switch the phone on and it boots up i have to enter my password which works, then i have to enter the sim card password which works, then i have to re-enter the first password again for android to unlock. it is on the second occasion that the password dosent work and i am locked out. the keyboard dosent pop up, and i cant tap the keys.
regards
gazza
ga77a said:
hi guys and girls
i was messing around with my phone and some how stopped gboard from working after android starts. this means that i cant enter my password, and am stuck at the lock screen.
i have adb+fastboot, and if a start the phone in recovery mode the phone is listed with "adb devices" but not authorized "adb: connect error for write: device unauthorized" , so i cant get my data off and factory reset and i cant install another keyboard program
i also tried entering the password using this methord -> https://stackoverflow.com/questions...ocked-phone-when-password-contains-as-first-c
is there a better way for me to enter my password via adb ?? or something else i can do to regain access ?
any suggestions are welcomed.
ps. its a ulefone armor x3 with Mediatek MT6580 chip set. phone is stock, never rooted. OTG not supported, no debugging enabled.
cheers
gazza
Click to expand...
Click to collapse
Is your data important or a working phone?
Boot into fastboot mode if possible using following combination
Credits: HardReset
At first switch off the device by holding the Power key for a few seconds.
After that press and push Volume Up and Power buttons together for a short while.
Let go of all keys when Boot Mode pops up.
Now select "Fastboot" by using Volume Up to scroll down and Volume Down to confirm that.
Now open command prompt window on your computer and make sure you have fastboot drivers installed.
Then type fastboot erase userdata
Your phone will reset.
{
"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"
}
hi mvikrant97
thanks for replying to my post
yes the data is important to me, and this is why i havent already factory reset my phone.
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
regards
gary
ga77a said:
hi mvikrant97
thanks for replying to my post
yes the data is important to me, and this is why i havent already factory reset my phone.
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
regards
gary
Click to expand...
Click to collapse
If your data is important then we can backup your firmware first and then flash it back to the phone.
ga77a said:
what i think i need is, a way to input my password via adb or some other way, maybe via sd card.
Click to expand...
Click to collapse
You mentioned in your original post that usb debugging is turned off, afaik you need it turned on and able to access the phone because you get a security prompt on the phone.
It seems with fastboot you dont need usb debugging, that seems the only option, I am no expert on fastboot as I have only used it once.
thank you mvikrant97
i'm using fastboot version 28.0.2-debian
but i dont think the fetch command is installed !
what commant should i use ?
cheers
gazza
not_rich
thank you anyway rich, for trying to help me.
[SOLVED]
so out of frustration i installed many keyboards via playstore, then i realised that Gboard was installed but not activated so i reinstalled Gboard via playstore , then restarted the phone and it Gboard was acive.
thank god this is over
hope this helps somebody else.