Here was a Guide. Someone said people don't care about Me or My Work so...
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
viper. said:
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
Click to expand...
Click to collapse
Wow......glad I got the JP version of a new phone for once! Otherwise it's still blowing my mind that Sony itself isn't scrutinizing root like damn-near every other manufacturer as of late.
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Just got my 5IV (UK) and exactly the guide I was looking for but just a simple question
My last personal Sony was the Z3C and unlocking bootloader/rooting that had drm issues with the official camera etc
Does unlocking bootloader with 5IV have any app issues, do the camera apps all work exactly as before and any other imporant Sony apps?
Will I be able to use Sony OTA updates?
If all good, I'll be unlocking and rooting this weekend, cant wait.
Thanks
rawdealer said:
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Click to expand...
Click to collapse
Bruh! You and me both!! I finally rooted my Asus Zenphone 6 this past October. A bunch of reading and forums lol. Also back 7-8 years ago there were plenty of Youtube videos. Now not so much! My Zenphone 6 just died today and I am 90% sure I'll be getting the Xperia 5IV which I was eyeing since announced. I was hoping my Zenphone would have given me one more year, but alas. I'm visiting here to get the scoop on rooting this in the event I want to. I feel your pain!
smudgy636 said:
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
Click to expand...
Click to collapse
HI, not sure if you solved it, had the same issue. So, as it gave an option to do full user reset (or something like that) I chose it. It then rebooted and I was back into the phone with the initial setup again.
I then re-installed the latest magisk app and it showed that magisk/root is installed.
As a test, I then installed f-droid and installed Adaway. I chose to configure in root mode,
the 'grant access' dialogue popped up and boom, root access provided.
Btw, if you do want to install Adaway too, enable systemless host in magisk preferences.
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
thany2 said:
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
Click to expand...
Click to collapse
So, no need to wipe all user data or?
how to hide root from GooglePay?
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.004s
Click to expand...
Click to collapse
Any Ideas?
hasztagL said:
how to hide root from GooglePay?
Click to expand...
Click to collapse
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Skv012a said:
So, no need to wipe all user data or?
Click to expand...
Click to collapse
I guess it was a catchall. Maybe if you've already been tinkering a lot, it might be a good idea to "start over", since Magisk can completely fluff up you phone if it's being interfered with. However, my phone was completely stock, other than being bootloader-unlocked, so in my case the answer is no, not needed.
No promises though. Just give it a go. Do have a backup ready.
thany2 said:
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Click to expand...
Click to collapse
Google Wallet not work with root. With DenyList still not work.
Matrixclonk said:
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
Any Ideas?
Click to expand...
Click to collapse
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
alexdo said:
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
Click to expand...
Click to collapse
Thanks man, I was in fastboot because when I went to bootloader I always got the message waiting for device. Also weird I had to reinstall the driver each time i went into bootloader :S
@Miustone Hey. I rooted my phone following your guide and I have a question.
Sony have released an update was wodnering if I flash the latest update, will my settings/data be intact? Apparaently the update is only small, just wish I could flash that...not the whole 3.3GB
Thanks
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Miustone said:
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
sad. i love your work.
Related
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings
Hi,
I'm brand new to this forum and my name is Jessy, and it's my pleasure to be here!
I recently bought this AT&T GoPhone (for around $29) at Walmart, and I was following this guide to allow me to use my SD Card as an internal memory storage unit for my phone, but I found out that I need to unlock the Bootloader, install TWRP, SuperSU and Link2SD apps to the SD card and my phone. Since this smart phone is similar to the Idol 3, could I use this method to unlock the Bootloader for my phone or do I have to try a different approach?
I appreciate your time and I look forward to contribute further to these forums! Thanks again!
-Jessy
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
Hey I used this app to remove king root and my phone bricked do you know how to fix?
ipodhero said:
Hey I used this app to remove king root and my phone bricked do you know how to fix?
Click to expand...
Click to collapse
My Alcatel Ideal 4060A froze a few times during the removal of KingRoot, but all I did was: turn off the phone, remove the battery, and finish the procedure once the phone was on. The phone was only $10 on Black Friday, so you could say it was only an experiment on my part. Unless it's a really good phone, where you can go to the manufacture's website and download the original firmware and install it through your PC, there's not much you can do to unbrick a cheap phone that is practically unknown.
Merazomo said:
Mario
Click to expand...
Click to collapse
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
shushi_boi said:
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
Click to expand...
Click to collapse
No problem. I'm glad you got the phone rooted. I originally picked up the phone to use as an MP3 player, so I removed most of the unnecessary stock apps with "System app remover (ROOT)", but now that I see how good the phone is (at that price), I plan to use it as a backup phone. It even has a notification LED light for unopened messages LOL; anyway, good luck.
My Alcatel bricked too using this method stuck at boot logo and does nothing... Any fix?
Thanks for writing rooting method for Alcatel 4060a Ideal Pop445. Need some help
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
I've been an iPhone user for many years, I'm almost new to android. I have unlocked the bootloader from the hidden developers options in the settings app. I haven't found any thing useful to root my new Alcatel Ideal 4060a (Pop 445) (at&t unlocked). There are tons of bloatwares and many apps that I can't transfer to sd card. I hope you two can help me out here as I don't want to brick my device.
Question 1: Do jessy did something wrong(regarding your given steps to root) that makes her device rooted OR she has just been lucky? Because someone just posted that he/she has bricked his/her device.
Should I go ahead and try my luck with your method you there would be some advice you would like to give?
Question 2: If I would be able to root this device, would I be able to install Android 6.0 Marshmellow?
Don't root this yet
Source thread:
http://forum.xda-developers.com/android/help/alcatel-ideal-4060a-bootloader-custom-t3476422/
c627627 said:
Same answer ValdamarlSaCOCK was given, goes to you too, feel free to ask any questions:
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Click to expand...
Click to collapse
Rooted already.
faxanidu said:
Don't root this yet
Click to expand...
Click to collapse
I have rooted with Kingroot 5; latest windows version on their website. Now I'm working on replacing it with Supersu or Supersu-me.
I think there always be some solution as far as you are seeing something on your phone's screen.
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Venryx said:
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Click to expand...
Click to collapse
Any solution for this? I want to replace King-O-Root with Super SU.
None that I know of.
I have another Android phone that I was also trying to get root on, and that one gets it temporarily using King-O-Root as well, but I'm too paranoid to try to make it permanent on that second one. Losing both my Android phones would be too painful.
If anything, I guess try the KingRoot program, from the pc, and then use the "SuperSU Me" app, as the person on the first page of this thread described. That way worked for at least one person apparently. (though the poster just after said it bricked theirs, so beware)
By the way, is your root from King-O-Root temporary (till restart) or permanent? I installed Super SU during the same launch I used King-O-Root, so I never got to see whether King-O-Root itself would have worked as a permanent (though non-ideal) solution. (I know that on my other Android phone it's temporary)
King-O-Root = Bricked Phone
KingRoot5 = Root Successful + it is possible to replace with SuperSU
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Recovery Retrieved!
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Ch3if-0f-Skull5 said:
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Click to expand...
Click to collapse
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
arolust said:
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
Click to expand...
Click to collapse
I pulled the boot file. Could someone maybe look at that? I cannot boot to the bootloader.
I could try to flash_image twrp to the recovery and try that.
I got this phone on black friday, shortly after I got root with kingroot 5 pc and it was all great, however I got greedy and replaced kingoroot with supersu :silly:. First reboot and it goes into boot loop. Now its been sitting in a drawer. I think that purify deleted some app it looks at boot.
It looks like the simplest way to get a restore is 'IF' TCL/Alcatel does an update, someone intercepts the signed zip file, then that zip file could be distributed and used with the stock restore.
Hopeful everyone here can work a better solution... thanks for all your hard work everyone.
yes u r right
many time happen with me, Happen with me on asus KA10, But i got fastboot update img lucky. hope that u will get Fast boot image some day or we may able to get recovery for this device . in that case your your phone may start working
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
the core question "How to unlock Alcatel Ideal 4060A (walmart) Bootloader?" still unanswered. Kindly help.
My phone is rooted, but not able to unlock bootloader so far ...
I just got this new phone. Can anyone give me working links and genuine tutorials on ROOT Procedures, TWRP and Custom ROM for UMIDIGI C2. Custom ROM is my biggest need. Thanks in advance for help.
Hi, did you find a working custom ROM?
I also have a C2 purchased for my son for xmas that I should have checked before buying if it was rootable as it has too much bloatware on it that I'd like to remove but can't as classed as system packages.
I've googled the web and not found anyone who has rooted one yet so hoping one of the excellent developers on here will have a go as its a nice phone, well spec'd and priced and suruprised given its been out since around June it hasn't been rooted yet.
Another Umidigi C2 user here, also interested in replacing default system. :angel:
TWRP for C2 not yet available?
Here is Root https://romprovider.com/2017/11/install-twrp-root-umidigi-c2/
Has anybody given a try?
I haven't yet and did download all the tools to my onedrive (work and home) unfortunatly my work antivirus system picked up dumpimage.exe as a risk and quaratined it although suspect thats a false positive or purely picked up due to the nature of the tool https://www.symantec.com/security_response/writeup.jsp?docid=2010-022501-5526-99&vid=24060
May have a try this evening although I'm not sure if once rooted its best to put the latest vanilla android on it (if possible) or just use the power of root to remove all the preinstalled 'system' crap?
MoiX said:
I haven't yet and did download all the tools to my onedrive (work and home) unfortunatly my work antivirus system picked up dumpimage.exe as a risk and quaratined it although suspect thats a false positive or purely picked up due to the nature of the tool https://www.symantec.com/security_response/writeup.jsp?docid=2010-022501-5526-99&vid=24060
May have a try this evening although I'm not sure if once rooted its best to put the latest vanilla android on it (if possible) or just use the power of root to remove all the preinstalled 'system' crap?
Click to expand...
Click to collapse
Hmmm.. First option seems easier..? :crying:
I had a go but despite adb reboot bootloader working (after enable Developer USB Debug and OEM Boot) I could't get fastboot oem unlock to work.
I've little experience of Android devices as my own mobile is an iPhone 6S which jailbroken on iOS 9.x and despite Jailbreaks of iOS being few and far between, when they do come they seem to be a lot easier to perform that most android roots which I'd have thought by the very nature of android's 'open' nature shouldn't really be as difficult with so many steps as they appear to be.
I think I'll need a better guide as the one mark332 posted with the root image (thanks Mark332...if it works), does seem a little generic and possibly untested?
MoiX said:
does seem a little generic and possibly untested?
Click to expand...
Click to collapse
Allthough I have rooted myself all my previous mobile phones, (Jiayou, ZTE, Xiaomi), nevetherless I agree, guide probably is not tested.. I guess we have to be patient, expecting some better.. From the other side C2 seems to be a good phone but so annoying because of bloatware..
There are some poor informations here https://4pda.ru/forum/index.php?showtopic=836202&st=320 but even with translator hard to understand.
It is only about replacement of the default launcher with Google's.
Any news for C2..??
Matinaki I wrote you a private message
unsuccess
MoiX said:
I had a go but despite adb reboot bootloader working (after enable Developer USB Debug and OEM Boot) I could't get fastboot oem unlock to work
Click to expand...
Click to collapse
I also gave a try. After typing adb reboot bootloader device booted in Fastboot Mod but after typing Fastboot Devices device manager suddenly does not see device. So, I'm stuck too..
Because of UMI's "Efuse partition protection" seems we will not able to root this phone. So, better to throw it to trash. No root, no phone..
Any news on this thread ?
I am the unlucky owner of an UMIDIGI C2 and I am extremely frustrated by the unability to change the default launcher.
I sincerely hope someone is able to help on this issue ...
wfoobar.
wfoobar said:
I am the unlucky owner of an UMIDIGI C2 and I am extremely frustrated by the unability to change the default launcher.
I sincerely hope someone is able to help on this issue ...
wfoobar.
Click to expand...
Click to collapse
For the moment you can do nothing.
There is some information here http://community.umidigi.com/thread-16167-3-1.html how to remove all that annoying bloatware and as I see "initiator" Included. If you try it, I guess, you have to install a custom launcher in advance.
Locked Bootloader
Hi guys
I tried with ADB Fast boot to unlock bootloader from UMIDIGI C2 but impossible. Experts, please help..!:crying:
Well..I guess many unhappy owners will like this information. After "clean install" of the official ROM, phone is completely clean of bloatware and also very friendly after Apex launcher installation.
Hey guys I’ve been here once or twice before but it’s been a while. I have some in the ass and I need your help please. I’ve been working at unlocking the boot loader on my Motorola Moto G power 2021 for two months now. The reasoning is for that I have no PC nor desktop rather one of my old android phones (Motorola Moto G7 Optimo) That I have had, Trying to figure out how to unlock my boot loader on my Motorola Moto G power 2021. I managed to unlock the boot loader finally but now I’m having issues with trying to install TWRP. My question is is that is there another custom room that I can install with two androids connected to USB – C double cable? I’ve been waiting for a long time to get my phone routed, please help and thanks
If you have one android rooted with magisk, there is an ADB/Fastboot Magisk module that might work for that, but I've never actually tried it. But I'm pretty sure one would have to be rooted. Another option might be to install linux on your phone. I have manjaro linux installed on mine but, again, it is limited without root because of selinux policy. With root, that can be disabled.
I also just noticed adb and fastboot can be installed in termux without root with
pkg install android-tools
You might try that.
If it workS, then YES, you can root without pc. Just 2 Android phones and a doubLe type c cable.
bryzone25 said:
but now I’m having issues with trying to install TWRP.
Click to expand...
Click to collapse
Don't install the TWRP we have now. Just boot it to use it with adb shell commands or a mouse. If you install it you'll get a bootloop, Dude says. I had to use it to extract my kernel for rooting.
Aaaannd the story thickens…. I ended up unlocking the boot loader with the two android phones and a USB – C type. However when I tried to flash Magisk, it flip my phone into a boot loop. Now, Me being the rookie that I am and trying to progress far too quickly, I Have relocked my boot loader and now I have a message which says no valid operating system can be found, will not boot.
Can someone please put me out of my misery and just go ahead and say that I am screwed?
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
arkansawdave74 said:
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
Click to expand...
Click to collapse
arkansawdave74 said:
so yeah I tried it again but the boot loader is still locked however I think the partitions are messed up after I was trying to flash magic and it fell right into a boot loop. Somehow it has actually gotten better and not continuously boot looping I can stay in fast boot but it won’t burn into anything else or power off unless it runs out of battery. But I do have the same code but it’s not taking hit it because OEM unlocking on developer mode is still locked.
Click to expand...
Click to collapse
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Bry2025 said:
I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy. If you know that phone with that carrier can be unlocked, keep trying. In Android I know you can copy/paste from the terminal. I hear some carriers make you wait so long before unlocking too, although I've never had a phone with that problem. A good friend told me just the other day he had a Boost phone that they made him wait 6 months to unlock.
As far as plans, I got this phone by accident and dropped and broke the screen the 1st day I had it, before the case arrived. When the case arrived, it was a case for the G9 Power, which I thought this phone was when I ordered it. So, next month I will order the G9 Power since I already have a case and screen protector for it. My last phone was the G8 Stylus (sofiap) and this "Power" just doesn't have the same great battery life. I also had the G7 Power (ocean) and it had excellent battery life. I meant to get the G9 Power for the 6000 mAh battery, but with it's higher resolution screen it's probably no better than this Power. I think all "Power"s should have a 720P screen for the better battery life. or at least a switch to select the resolution you want like on my Galaxy S7.
This phone needs some ROMs though, so if I can find the time, I will do my best to give it a couple, if luck is on my side. Maybe a Resurrection Remix and a crDroid or Bliss. But really, it's whatever I can get to build, so maybe none. Lol.
Bry2025 said:
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
arkansawdave74 said:
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy.
Click to expand...
Click to collapse
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
sd_shadow said:
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
Click to expand...
Click to collapse
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
arkansawdave74 said:
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
Click to expand...
Click to collapse
I think I used copy/paste in cmd.exe since windows 7, but I don't know when it started working.
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
Moto devices can be finicky.
You should be able to flash stock firmware with fastboot, but on windows rsd lite or the newer lsma work more reliably.
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
USB debugging doesn't effect fastboot mode, it's an adb function.
Edit:for locked bootloader
Booting stock .img may work for some devices
sd_shadow said:
USB debugging doesn't effect fastboot mode, it's an adb function.
Click to expand...
Click to collapse
Yes, but I was going to have him run
adb shell getprop | grep build.version.base
to figure out the software channel he needs. With the output I could find the exact build he is/was running on lolinet. That's hoping his bootloop is booting far enough for adb to enable though. adb shell wont work from stock recovery and adb shell from the quamp twrp we're using returns guamp device info. Wtf?
sd_shadow said:
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
Click to expand...
Click to collapse
On Linux fastboot seems to be flawless. I'm surprised to hear that it has trouble on Windows. But I think he's running fastboot from another android., which is so cool. Opens a door for root with no pc.
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
My Moto G power of 2021 is the one that I unlocked the boot loader with the code off of the Motorola site and then I tried to mess with Magis and it ended up boot looping so I tried to lock it again thinking that would help somehow and that’s where I’m at on that one. On the Moto G7 optimo I haven’t gotten anywhere with that one yet however I did get I haven't gotten anywhere with that one yet however I did get the Unlock data and put it on Motorola site and it said it can’t be unlocked. Also sorry but I’m new to this so I don’t understand about the splash screen and boot animation so please let me know what I need to do to give you that information.
Now with the phone to phone android to android, are used the Google app BUGJAEGER 3.0-full (164). Are used the command: fastboot oem unlock <unlock code> . And it unlocked right away.
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
I just got a laptop and I’m going to attempt to use the command prompt and copy and paste to see if I can get the unlock code for my G7 optimo but on the Moto G power of 2021, I did have all of it unlocked but now since my dumbass locked the boot loader again I can’t get back on the initial platform and get developer tools. If I can get the OEM unlocking toggled back on I probably can unlock it reflash the firmware and boot my phone again
<EVERYONE>
Just to recap, my Motorola Moto G power 2021 is Bootloader locked after Magisk Installation failure. I have messed around with it and have it stuck in Fastboot Mode after it was stuck in bootloop. Some progress but the boot loader is locked again because of a error of mine and now it will not take my unlock code that I used before. Mind you, I did all of this between two android phones and an app called BUGAEGER That is available on Google play