So I will tell you a story. I have a zte phone which is not rootable at the moment, I spent 11 months trying and two days ago I found a firmware with fastboot, because zte disables it on purpose. Novadays rooting is often a problem since oems lock everything and don't care, also we can say the same about users, they think that since Android adds functionality it's good to stay unrooted. Let me tell you that is a stupid way of thinking, not only you are accepting to use a phone as guest (also smartphones are so powerful to be considered pcs) but also you are doing it without knowing that oems leave backdoors on it. I really don't understand why people don't care anymore about rooting. I'm so sad. Now I made a discord server where I'm looking for people, devs in particular, but also other people are welcome, and I want to port qu1ckr00t exploit and make also new one, I'm sick of people and oems, I really don't understand is possible to be so dumb? I really don't know...
Yeah, the war against users has escalated.
I think the only way to delay the inevitable is to buy devices with things open at the lowest level.
I rate this on four levels:
Fastboot unlocked, can write most partitions
Fastboot critical unlocked, can write all partitions
Boot ROM and loader software available (e.g. EDL and Firehose for Qualcomm), can read/write all flash
SoC unlocked (e.g. SecureBoot off in Qualcomm), can boot anything
Even if things are open, "progress" means that things always get more complicated and more of a hassle.
Right now I have my cheap/locked/carrier-subsidized phone stock.
I have my Onyx Poke3 ereader Magisk-less rooted and modded.
Renate said:
Yeah, the war against users has escalated.
I think the only way to delay the inevitable is to buy devices with things open at the lowest level.
I rate this on four levels:
Fastboot unlocked, can write most partitions
Fastboot critical unlocked, can write all partitions
Boot ROM and loader software available (e.g. EDL and Firehose for Qualcomm), can read/write all flash
SoC unlocked (e.g. SecureBoot off in Qualcomm), can boot anything
Even if things are open, "progress" means that things always get more complicated and more of a hassle.
Right now I have my cheap/locked/carrier-subsidized phone stock.
I have my Onyx Poke3 ereader Magisk-less rooted and modded.
Click to expand...
Click to collapse
the problerm is that even if i have fastboot without a code to unlock the bootloader is meanigless, people have to make new exploits
Fastboot that requires a code to unlock and no code = No fastboot.
So, on that scale of 1 to 4 you have a 0.
Renate said:
Fastboot that requires a code to unlock and no code = No fastboot.
So, on that scale of 1 to 4 you have a 0.
Click to expand...
Click to collapse
You got the point, I'm in need of some dev who ports qu1ckr00t exploit to armv7l, since I tried some 32 bit version and the exploit was working but it found wrong addresses. But I can't push links here, maybe in private if someone wants to try porting qu1ckr00t using my kernel source. Unfortunately I'm not a dev so would be impossible for me
I'm not that versed in exploits, although I can see that this relies on crashing binder and using entry points in kallsyms.
Can you even see anything here?
Code:
$ cat /proc/kallsyms
cat: /proc/kallsyms: Permission denied
$ echo 0 > /proc/sys/kernel/kptr_restrict
/system/bin/sh: can't create /proc/sys/kernel/kptr_restrict: Permission denied
Do you have your specific (exact) boot.img? It's trivial to extract kallsyms out of that.
Speaking of fastboot. Have you guys seen the fake empty fastboot that Samsung installs on their devices? Samsung deleted the real fastboot and replaced it with a fake one that doesn't even do anything! Samsung did this on purpose to annoy their users
Skorpion96 said:
oems leave backdoors on it
Click to expand...
Click to collapse
Oh now I finally understand the purpose of this fake empty 'fastboot' on all Samsung devices that doesn't even seem to do anything
And then Samsung constantly force selinux enforcing down your throat on all their devices and there's nothing you can do about it even as root unless you hack your kernel. Sounds like fun right?
That's why I prefer Xiaomi devices nowadays. Cheap price, good hardware, easy to unlock (1 week waiting time which is kind of annoying but still somewhat acceptable), easy to root and debloat and customize
I think one of the major hurdles to achieving root nowadays are all these different read-only protection mechanisms which are shoved down our throats... And having selinux constantly enforcing doesn't really help
Speaking of Enforcing : Have you guys ever heard about the fake root?
It looks and feels like real root but it's fake and I can't do anything with it due to selinux constantly enforcing
Click here if you don't believe me.
{
"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"
}
SE Linux is not a problem.
Just write your own policy.
I do. Learn about secilc.
Step 1: Set permissive.
Step 2: Find out where the "denied"s are.
Step 3: Write your own .cil and recompile.
Get your boot.img
Extract kallsyms
Patch sel_write_enforce to just return with 0 in x0
Renate said:
Get your boot.img
Extract kallsyms
Patch sel_write_enforce to just return with 0 in x0
Click to expand...
Click to collapse
That's awesome but if phone can't be unlocked you can't flash that patched boot image
I was just looking at a boot image from lebigmac.
They're always throwing new stuff at us and I like to keep up with it. There was a small wrinkle in there.
I've seen uncompressed kernels, compressed kernels with extractor stubs, GZIP, LZMA. This one had LZ4 compression.
I'm kind of surprised that everyone seems to have still stuck with GZIPed CPIO for ramdisk.
Why not change it and upset everyone for some marginal benefit?
In any case, the strange thing with lebigmac's boot image is that I could extract the kallsyms but all the addresses were zero.
(This has nothing to do /proc/kallsyms or /proc/sys/kernel/kptr_restrict.)
Has anyone seen this before?
Here is the boot.img that @Renate was talking about in case anyone was wondering
It's from an older HTC U11 device that is giving me the fake root issue briefly mentioned above.
This is slightly off-topic though so please feel free to discuss this fake root issue in THIS THREAD instead.
I just thought I'd mention it here hoping that some Android vulnerability experts would chime in with a possible solution to my fake root problem. Thanks!
Did you check if recovery has the same kernel?
Maybe that doesn't have kallsym_addresse zeroed out.
Skorpion96 said:
So I will tell you a story. I have a zte phone which is not rootable at the moment, I spent 11 months trying and two days ago I found a firmware with fastboot, because zte disables it on purpose. Novadays rooting is often a problem since oems lock everything and don't care, also we can say the same about users, they think that since Android adds functionality it's good to stay unrooted. Let me tell you that is a stupid way of thinking, not only you are accepting to use a phone as guest (also smartphones are so powerful to be considered pcs) but also you are doing it without knowing that oems leave backdoors on it. I really don't understand why people don't care anymore about rooting. I'm so sad. Now I made a discord server where I'm looking for people, devs in particular, but also other people are welcome, and I want to port qu1ckr00t exploit and make also new one, I'm sick of people and oems, I really don't understand is possible to be so dumb? I really don't know...
Click to expand...
Click to collapse
What ZTE phone are you attempting to root? If it has a MTK SoC, I'd recommend trying MTKclient. It was able to unlock my ZTE Blade Vantage 2 (yes, a unlocked Verizon phone) and now I've got Magisk and all.
Smu1zel said:
What ZTE phone are you attempting to root? If it has a MTK SoC, I'd recommend trying MTKclient. It was able to unlock my ZTE Blade Vantage 2 (yes, a unlocked Verizon phone) and now I've got Magisk and all.
Click to expand...
Click to collapse
unfortunately is speadtrum
Related
What I have tried:
SuperOneClick (all versions) <-- Siege Tanks Were Doomed
Gingerbreak <-- Just sits there
Z4Root <-- doesn't do anything
Rageagainstthecage <-- doesn't work
tried flashing Clockwork mod via tcard like works for the ZTE Blade, phone pretends like it is working then reboots and no change, trying to start using the power button and vol - yields nothing.
tried cooking my own rom with the kitchen make the update.zip file
Do adb reboot recovery
the phone comes back to the android system recovery <3e>
I select the option to do update.zip from sdcard
I get:
verifying update package...
installation aborted...
I need root access to remove the AT&T preloaded apps that won't uninstall won't stay killed and are hogging all my space on the phone (limited storage). I would also like to be able to upgrade to 2.3.7 from my current 2.3.4 and possibly make my own roms.
I have emailed ZTE Chinese support to see if I can get an non pork filled rom the Indian who answered their tech support line didn't have an answer and told me not to flash the ZTE roamer rom (if I could even find it) because it will brick my phone. They have been no help!
What am I doing wrong in the android recovery (I have tried both installer scripts)? Is there a way to rebuild the system.img from the system folder that was created in the kitchen because I might be able to rebuild it into the .bin file that the phone will accept from a sdcard with the built in update feature?
Ok so I figured out how to repack the system.img I then dropped it back into the folder and used zte-pack.exe to build my .bin file. I go to the tcard update and it fails verification...is there a signature that needs to be made? I didn't see an option in zte-pack
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Not sure if there is away as of yet. Just did a fast search and it seems no root has been done for it yet
try another time z4root
I am unable to root my XT928 either...Good Luck!
Apo11on said:
i got the same phone with at&t....was unable to root it either, but i only tried super one click...
good luck and share, if you find a way.
Click to expand...
Click to collapse
I am soooo close just need that extra little bit of help, I will get it and when I do I will definitely share. I've only had a droid for 2 weeks and I have come this far, I am not going to stop. I have a BS in Computer Science and used to be a MCSE, I don't know this tech well enough yet but I will. Just hoping someone on here has the skillset I need to help complete this,
primanka said:
try another time z4root
Click to expand...
Click to collapse
tried it multiple times as I have with all of the one click exploits and custom rom trials
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
jcase said:
We got root, just need a forum to post, and maybe anotehr tester if someone is interested.
Shoot me a pm
Click to expand...
Click to collapse
Thank you kind Sir! jcase to the rescue again - spent a couple of hours with me and busted this thing open. I can confirm my AT&T Aveil ZTE Z990 is fully rooted now. Mad props to jcase
{
"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"
}
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
jcase said:
Will post instructions after I Get another tester and write it up, however I am submitting a CVE And reporting it to google/zte. It is particularly dangerous (as far as malware abusing it).
Click to expand...
Click to collapse
Just woke up and saw this...can't wait to test thanks. PM Sent
I can confirm it works..I am now rooted!
jcase said he will post later... was able to remove the annoying at&t apps and gain back 30mb using titanium back...now to learn how to flash a custom rom...
http://www.androidpolice.com/2012/0...e-avail-att-offer-quick-and-easy-root-access/
enjoy
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
schoolage said:
There are detailed instructions for rooting, unlocking, other ROMs and more on a Russian site but I don't understand much of it. If anyone can help out it would be great!
I'm prevented from posting links here but search for zte Roamer unlock.
Click to expand...
Click to collapse
we know about this - i'm fluent in russian. none of their file links work - it's an old thread on 4pda forums. you can use translate.google.com or several other engines, to translate web pages in real time.
according to ZTE although they share the same model numbers they have different radios (IE GSM / CDMA) and flashing the roamer to the avail will brick it. Apparently ZTE has not gotten the concept of using distinct model numbers yet...
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
theloon said:
I was able to get root by simply entering *983*7668#. watch the screen and you will see a message that says wait a few minutes for root. I then installed superuser and Titanium Backup proceeded to remove the apps I didn't want/need, I was also able to backup everything else that I wanted to!
Click to expand...
Click to collapse
How did you run Titanium Backup without installing a su binary?
shimapan said:
How did you run Titanium Backup without installing a su binary?
Click to expand...
Click to collapse
It just worked, even after a fresh flashing of the T card image.bin from ZTE.
Oh and heres a little batch file with needed files to automate jcase's procedure.
Greetings Everyone,
We have a team over at thriveforums (.org, not .com) who are trying to root the toshiba excite and we need help. If there were a Toshiba Excite thread here on XDA I would be putting this there.
Things we know:
-From the box, toshiba excite is able to be temp rooted through ADB via:
Code:
$ tputimg --des ../data/local.prop
$ echo 'ro.kernel.qemu=1' > ../data/local.prop
$ exit
[email protected]$ ./adb reboot
The only problem with this is that we get screen errors that looks like a boot loop, but is simply a jumpy screen. ADB still works.
-We cannot remount /system as rw because of sealime.ko, a kernel module which is loaded in init.rc that protects that partition. A modified boot image can remove this.
-We can't try modified images without a recovery or else we could brick the device without being able to flash the original boot.img.
-There is no fastboot.
-There is no flash_image.
-We cannot port any recovery image (including Clockworkmod via builder) because... (see next)
-We cannot flash anything to any partition other than the original images we pull from /dev/block/mmcblk0p1 and mmcblk0p2 (Recovery and Boot, respectively). I have used split_bootimg.pl to pull them into kernel and ramdisk.gz files, and made it again with mkbootimg and it works. But, once I decompress the ramdisk files things go to hell. I've used various guides I've seen to do so, but when I flash it back to the device the device doesnt accept it.
It seems the problem has to do with the compressed ramdisk file. Once you open it up then try to recompress it, it doesnt like it.
Things we don't know:
Is there another way to compress this file?
Is there a special option I should be using? ( --base, and I've used the other info from split_bootimg.pl)
**Edit**: I followed instructions according to http://b.oldhu.com/2012/02/16/how-to-unpack-and-repack-android's-boot.img-correctly/ and found that the
--base option should equal 0x10000000
Does anyone have any other ideas?
We need help here and i'm yanking my hair out. This is a beautiful (despite the slight screen leaks) quad-core tablet that I do not want to give up on.
**EDIT**: I have confirmed the problem. The issue is during the unpacking of the ramdisk:
If I:
1. Split the recovery image
2. rebuild the recovery image as is
Then
Everything is GO
But, if I:
1. Split the recovery image
2. Decompress the Ramdisk
3. Recompress the Ramdisk (no edits)
4. Rebuild the recovery image as is
Then
Everything breaks.
**EDIT** With help from Fuses, it seems that there is bytes of code that look like a signature that is generated outside the normal compression.
{
"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"
}
~WHH
and where next?
I looked at the Hex code from a recompiled recovery to the original recovery. Everything's different including the kernel. Which I think means there is some special way to compress is that we need to get from toshiba. Or, that theres an encryption.
Man I wish we could get toast on this Im sure he would love a good challenge
I wish you guys the best +1 on this.
Sent from my SPH-D700 using Tapatalk 2
Do u have an excite tablet?
t1nk said:
I wish you guys the best +1 on this.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
---------- Post added at 03:40 PM ---------- Previous post was at 03:26 PM ----------
who developed the compression method used? Can toshiba have the right to change the program to have some encryption incorporated. Or is it some new way of compressing developed by the android source team used in ics?
I dont understand the roadblock were up against.
maybe a little more knowlege on the subject would enlighten me
An Email:
We would like to inform you that the source code which
you have requested was shipped out to your designated address.
Here is the shipping details as follows;
*Ship via : UPS with YAMATO
*UPS tracking number : *********
*Ship date : July 3rd, 2012
*ETA : within one week
*Description of goods : CD-ROM
*Quantity : 1 pc
Thank you for your patience.
Yours sincerely,
Get mine next week
We would like to inform you that the source code which
you have requested was shipped out to your designated address.
Here is the shipping details as follows;
*Ship via : UPS with YAMATO
*UPS tracking number :
*Ship date : July 3rd, 2012
*ETA : within one week
*Description of goods : CD-ROM
*Quantity : 1 pc
Yours sincerely,
Linux Section of
| TOSHIBA DIGITAL MEDIA ENGINEERING Corp.
| _________________________________________________
| | Linux Information for TOSHIBA PC Website
| |http://linux.toshiba-dme.co.jp/linux/index.htm
Will that help us root?
Just wondering if having source from toshiba, will help us root
I'm surprised there is no root yet...and by surprised I mean disappointed lol. I wish I knew something to try and help out. Oh well, good luck
Sent from my AT300 using Tapatalk 2
wayneb02 said:
I'm surprised there is no root yet...and by surprised I mean disappointed lol. I wish I knew something to try and help out. Oh well, good luck
Sent from my AT300 using Tapatalk 2
Click to expand...
Click to collapse
+1!
Well, Fuses from the Lazypanda people believes its something that has to do with gzip. As in: a) different compression levels, or b) different version.
The different levels all compress to the same size, so I believe i can safely say that that is not the issue.
Unless I go through and try install/reinstall every other version, I can't test them.
I think there is something of a signature or hash that is being used. But, I am by no means an expert. I wish one of the smart devs (like the people who rooted the SGSIII) could hop on this, because I've been past my experience limit a long time ago.
News from DALEPL:
OK, I got some good news and some bad news... First the good news... I now know why we canot load an alternate recovery or modified boot image... Now the bad news... Toshiba has locked the bootloader, so if there is any change, it will not boot. I talked to a Toshiba Engineer and he let me know this. There is a brite side, but only a shimmer at this time. Several of the engineers have spoke up about this. The engineer asked me if there were any other tablets with unlocked bootloadres. I told him Asus and Acer are. He said that they (engineers) have sent a message to Toshiba Corpotate and asked about providing an unlocked bootloader, but they have not received an answer yet. What I am trying to get accross is that we do have advocates within Toshiba, but they too may get nowhere with this.
We talked about the fact that DRM will not work on a rooted device. He said he under stood this and this is what they conveyed to Toshiba Corporate. Only time will tell. So, as it stands, we would have to get an unlocked bootloader in order to get the device rooted.
Click to expand...
Click to collapse
Whthacker I think you would be a good candidate to request unlocked bootloader.
from what ive seen u communicate very well on the forums, you get your point accross, I think you should ask the for the unlocked bootloader. I think u would have as good a chance as anyone.
(what good is giving us the source code with out anyway way to use it on the device) because of the locked bootloader
They want us to be guinea pigs and look for loopholes that could or (as in cases now couldn't) help... For what I use it I have looked for an unrooted solution (as far as going usb tethering to get tcp) and use it as a display, but I noticed that C97 dual core runs Air Display just as good. Why spend the $100 more? Custom bikes & cars won't see a difference, well on price - cheaper -
nothing new on this?
Petition to Toshiba
No new updates yet. I've started a petition to Toshiba to unlock the bootloader. I would appreciate everyones signature. Thanks a lot.
https://www.change.org/petitions/to...tloader-on-the-toshiba-excite-line-of-tablets
matt11601 said:
No new updates yet. I've started a petition to Toshiba to unlock the bootloader. I would appreciate everyones signature. Thanks a lot.
https://www.change.org/petitions/to...tloader-on-the-toshiba-excite-line-of-tablets
Click to expand...
Click to collapse
Signed.
Was the 100th petition signer.
Hope we get somewere with this
Signed it last night. Hopefully we get enough signatures to make them reconsider
Sent from my Galaxy Nexus using Tapatalk 2
Hey, i have made a new tool for bruteforce any android devices pin code aslong as usb-debugging has been enable with 100% Guarantee, no root is required.
Proof
{
"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"
}
Of course, parallel mode is possible for speed things up
Since i cant post links you will find it under my github, just use github[dot]com/wuseman/WBRUTER - 100% Guarantee that pin will be cracked, let me know if there is any issues, thx
Source code can be found here: github[dot]com/wuseman/WBRUTER
Please let me know if there is any issues.
Howto:
Clone WBRUTER from my repo, github[dot]com/wuseman/WBRUTER
cd WBRUTER; chmod +x wbruter
./wbruter -a 4
This is my first thread at xda-developers.com so be nice!, the tool includes brute force via login screen too but there is already some tools for this, but this is kinda useless on latest android versions since phone will accept 4 tries only and then it will be locked.
I hope you will get some use of my new tool, enjoy.
What's the use of exploiting ones pin number if one can't access the service hence the screen is locked and access is required
PoochyXXX
PoochyX said:
What's the use of exploiting ones pin number if one can't access the service hence the screen is locked and access is required
PoochyXXX
Click to expand...
Click to collapse
Adb works even if the screen is off, not all devices is rooted just because usb debugging has been enable.
Also since this is no root I'm assuming this is one thru adb
PoochyXXX
PoochyX said:
Also since this is no root I'm assuming this is one thru adb
PoochyXXX
Click to expand...
Click to collapse
Correct.
It's a good rescue for phones that have no twrp hence root sadly its useful news is a formality of luck on one's preference of phone security if one doesn't have the process installed is it possible for one to activate usb debugging thru a command prompt and then push the apk to the system or system priv and activate the apk to start the brute force process..... If such is not permitted it would be good to implement in a future version of your project
PoochyXXX
PoochyX said:
It's a good rescue for phones that have no twrp hence root sadly its useful news is a formality of luck on one's preference of phone security if one doesn't have the process installed is it possible for one to activate usb debugging thru a command prompt and then push the apk to the system or system priv and activate the apk to start the brute force process..... If such is not permitted it would be good to implement in a future version of your project
PoochyXXX
Click to expand...
Click to collapse
That was a good idea, I will see how I can add a such solution. Thanks
wuseman said:
That was a good idea, I will see how I can add a such solution. Thanks
Click to expand...
Click to collapse
Any time we here at xda about making are androids more amazing then they already on are androids are like pokedex some are more sophisticated then others
PoochyXXX
Ive never used github or adb or any of this. Can you explain this like you would to a 12 year old? I really need to get back into my phone
wuseman said:
Hey, i have made a new tool for bruteforce any android devices pin code aslong as usb-debugging has been enable with 100% Guarantee, no root is required.
Proof
Of course, parallel mode is possible for speed things up
Since i cant post links you will find it under my github, just use github[dot]com/wuseman/WBRUTER - 100% Guarantee that pin will be cracked, let me know if there is any issues, thx
Source code can be found here: github[dot]com/wuseman/WBRUTER
Please let me know if there is any issues.
Howto:
Clone WBRUTER from my repo, github[dot]com/wuseman/WBRUTER
cd WBRUTER; chmod +x wbruter
./wbruter -a 4
This is my first thread at xda-developers.com so be nice!, the tool includes brute force via login screen too but there is already some tools for this, but this is kinda useless on latest android versions since phone will accept 4 tries only and then it will be locked.
I hope you will get some use of my new tool, enjoy.
Click to expand...
Click to collapse
I have a phone I need to unlock but I don't know how to get WBRUTER on my PC
S20 fe
Bennie049 said:
I have a phone I need to unlock but I don't know how to get WBRUTER on my PC
Click to expand...
Click to collapse
Hello.
Just clone the repository and run the command but you must have been authorized to this phone over adb before and things have been changed, as default nowadays adb will release keys after 7 days. Wich Android version is installed on your locked device?
Hi all new here glad to be a member
anyway i just unlocked the bootloader and rooted with magisk through BOOT.img patching.... my Question is, are there any custom roms or anything out yet for this phone? Android 12 .thank you so much
Thats amazing. From my own research i understand this phone is so new that people have yet the get their hands on it to work on it also the fact that it uses a mediatek instead of a snapdragon is a sticking point for a lot of developers even though its basically the same phone as the g power 22 and g play 21
Hi sam9566
Yeah I broke my other phone cheap . So I looked for an unlocked carrier phone close to me and Walmart had like 7 maybe. But they were in lockup couldn't find it. So I asked the guy in the back he looked around and took his key out and went into this metal cage that you couldn't see into and pulled one out and sold it to me really quickly . Then I had to wait 9 days for the OEM UNLOCK to be UN-greyed in dev options. But in those 9 days I waited for an email from moto for my unlock code but never showed. So I got on live site chat and within 2 minutes the person gave me the 20 digit code . And after 9 days I unlocked the bootloader, then I used the Lenovo software to get the factory Rom extracted the boot.img used magisk to patch then flashed.. lol been debloating the crap out this phone.. it uses 51% storage after setup is completed
nice lets try to actually keep this thread alive so maybe we can get a lineage rom for this phone eventually???
well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored
Yeah im still completely lost on how you did this could you possibly post a step by step guide???
lol ill try
1: download https://www.motorola.com/us/rescue-and-smart-assistant/p MOTOROLA SITE please be patient the program is slow just a warning if anyone thinks its hung..
2: Download magisk from GITHUB on your phone and install it.
3: download ADB_Fastboot
4: open rescue and smart assistant program and do the steps it says to do, then once it finds the ROM it MIGHT say already have latest... Say download anyway..
5: now once its done downloading dont do anything else. go to the download location and open the file and copy the BOOT.IMG to desktop or where ever you want it..
6: Now copy the BOOT.IMG to your phone's internal storage Download folder.
7:Run magisk and click top install then select and patch a file. locate the boot.img on your phone and patch it.
8: once done copy the patched file back to the PC i put it in ADB FASTBOOT folder. rename it too BOOT.IMG open CMD with admin rights or it wont work.
9: type (adb reboot-bootloader), should reboot into bootloader. now do this command (fastboot devices) make sure it see's the device.. then type ( fastboot flash boot boot.img ) -BOOT.IMG is what ever name you make it but for simple measures i did boot.img. let it finish reboot device with ( fastboot reboot ).. now open magisk and let it finish what its got to do...
10: ENJOY hope this helps someone out.. i never wrote a guide before as you can tell hahaha.. let me know if there is any QUESTIONS
Gonna have to dig out my windows pc ugh
lol what device do you have?
sam9566 said:
Gonna have to dig out my windows pc ugh
Click to expand...
Click to collapse
My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system
sam9566 said:
My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system
Click to expand...
Click to collapse
my bad i meant your 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"
}
samtron6 said:
my bad i meant your phone.
Click to expand...
Click to collapse
So what do i do next on my pc in still lost
sam9566 said:
So what do i do next on my pc in still lost
Click to expand...
Click to collapse
do you have bootloader in dev option enabled?
Yes
samtron6 said:
well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored
Click to expand...
Click to collapse
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.
dcluvsme said:
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.
Click to expand...
Click to collapse
same.
I was struggling to get my boot partition to flash (not found error). Ultimately I had to flash boot_a and boot_b as described here.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
hmm i didnt have to flash the boot a or boot b.. i just did the flashboot boot.img command. maybe i didnt do something right lol now im going to try this when i get time today.. thanks
Yes, you must flash boot_a and boot_b
All i can find are tutorials for the Neo and Pro versions of this device. Can this version be rooted? How?
recovery sideload+magisk
alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm still new, can you elaborate? Maybe possibly link a tut? Appreciate it regardless.
alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
What is recovery sideload?
useroso987 said:
What is recovery sideload?
Click to expand...
Click to collapse
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Well, i've been reading past days...
I've installed Delta Magisk through adb on Lineage OS 20. It was quite a fast and interesting process!
Thank you.
Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them. Every phone unlocks differently.
Kasjopea73 said:
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them.
Click to expand...
Click to collapse
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Kasjopea73 said:
Every phone unlocks differently.
Click to expand...
Click to collapse
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Kurt Krummbein said:
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Click to expand...
Click to collapse
The best thing to do is not to write anything anymore, you are no help here and it is better to disappear. This is a forum for development, not for throwing obstacles under someone's feet. Rooting this phone is trivial, just extract the boot.img from the rom you are using, not from any other, and in magisk make a patch, instructions you will find below the post. If you don't know what is going on don't write nonsense to anyone.
Instructions Steps: Unlock Bootloader and RootPlatform Tools:
For Windows:
Download File: Download
For macOS
Download File: Download
For Linux
Download File: Download
At first, you need to connect your device to PC via USB cable.
Next, head over to the platform-tools folder, then you have to type in CMD in the address bar and click enter. Command Prompt window will popup.
Now type the below command to boot your device into fast boot mode:
adb reboot bootloader
Next, you will need to get your device-specific unlock token. For that, execute the below command:
fastboot oem get_unlock_data
You will now get an alphanumeric character, that you have to copy all of the codes without the bootloader prefix. To follow this step, you may copy all the commands, paste it in a Notepad, and then delete the bootloader prefix. Further, make sure that there isn’t any space between any line of codes.
Now go to Motorola Unlock page and sign-in with your account. After this, copy that code and paste that into provided space. Then tap on the “Can my device be unlocked button”
Then, you will receive a Unique Key on your email. In normal scenerio, the code usually takes a few minutes to reach your email. But if not wait for few more minutes and you will get the code.
Go back the command prompt window and execute the below command. In the following command replace the UNIQUE_KEY with the key that you have received from Motorola.
fastboot oem unlock UNIQUE_KEY
Your bootloader is unlocked, after the whole process is done which will take few minutes. Now if your device doesn’t reboot to the system then you can use the below command to do it manually.
fastboot reboot
CONGRATULATIONS! YOU HAVE UNLOCKED THE BOOTLOADER OF YOUR DEVICE. NOW LET’S PROCEED TO ROOT THE DEVICE
2. ROOT MOTOROLA EDGE 30, PLUS ecc......Thera are two ways root motorola edge plus: one is flashing SuperSu Zip with TWRP Recover and another one patching the boot.img file. Currerntly, there is no TWRP Recovery for motorola edge plus, so we will be choosing the latter (patching) option.
Instructions Steps:
First download the stock firmware and extract the firmware file. Now search the stock boot file which would be named as boot.img. Copy this file to your Motorola edge plus.
Install Magisk Manager which you have downloaded earlier.
After installation, open magisk manager and tap on Install > Install > Select and Patch file (Here you have to select the boot.img file)
{
"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"
}
Magisk will start the patching process which will take just a few seconds.
After the patching process is done, you should see the magisk_patched.img in your internal storage’s Downloads folder.
Now you have to transfer magisk_patched.img to your platform-tools folder. Open CMD in this folder by searching “CMD” in the address bar and hit Enter.
Connect Motorola edge plus with PC via USB Cable and type the following command:
adb reboot bootloader
Now you have to flash magisk_patched.img and for that type the following command:
fastboot flash boot magisk_patched.img
The process will take only a few seconds. Once its complete, you may reboot your device via the following command:
fastboot reboot
Now you can open magisk manger and very the root as well.
CONGRATULATIONS! YOU HAVE SUCCESSFULLY ROOTED YOUR MOTOROLA EDGE PLUS.
There is another solution for making Root on Telegram groups. Unlock the bootloader and install TWRP then Magisk.
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
hans3103 said:
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
Click to expand...
Click to collapse
SafetyNet fix install