Related
Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
root alcatel ot 983
ahkronn said:
Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
Click to expand...
Click to collapse
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
mohamm said:
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
Click to expand...
Click to collapse
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
I need original stock alcatel ot 983 rom
hi guys
I bricked my ot 983 after flashing with different alcatel models rom
can some one please give me a copy of original stock rom for alcatel one touch 983
please
my email [email protected]
maybe your handheld is a brand new and nobody mod it yet
be patient bro and keep searching in google with any keyword
help me make tutorial on youtube
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
bro i dont know much about android stuff , but pls can you make a tutorial on youtube like this you can help me and millions out there for rooting the phone , ps help and thanks so much in advance
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
Where did you get the upgrade from ?
My story is like this: rooted, uninstalled some bloat from system and after a factory reset I'm stuck in the initial setup wizard (after completing almost all stages from setup it crashes at the end, after connecting at the google account - tryed to ignore that step but either way it crashes). Fastboot works but adb don't.
I do have another identical phone Alcatel One Touch OT-983 but with no root, with no modifications. Is there a way to backup the original/stock image and flash it over the malfunctioning one and restore it??
I tried with the proprietary upgrade tool from Alcatel but no succes as it close saying I don't need an upgrade because it's the last version of software installed in my phone. I thought even to broke intentionally the rom but I'm afraid that the upgrade utility from Alcatel will let me down, as I read that another users didn't managed to complete successfully the upgrading process. Is there a way to trick the system that has a previous version of Android?
Thank you for taking your time to read this and hope someone has an idea to solve our problem.
Have a nice day guys, you can contact me at puiocku at gmail dot com.
Have someone this stock rom (for Alcatel One Touch 983 (Valencia)) ???
Here is a Alcatel OT-983 rom, not sure which country it is from: https://www.dropbox.com/s/g2ljtrpqru3uihm/rom 983.zip?m
Here is my o2 uk backup rom: http://www.mirrorcreator.com/files/C4VEKHEI/OT-983_backup_uk.rar_links
this .zip file contains the boot.img, system.img and recovery.img
Someone needs to create a clockwork mod recovery for our phones now.
here is the sourcecode for this phone: http://www.mirrorcreator.com/files/85KDRTYP/OT_983_20130103.7z_links
Can't get to recovery
I have a bricked rooted OT 983, by error i installed a ZTE Blade's CM9 ROM and now i can't get my phone to recovery by using ADB that is the only way, i have downloaded the stock ROM but i don't know how to install it. :crying: PLEASE HELP!!!!!!!!!!!!!!!!!!!!
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Possible solution for getting back original ROM on "stuck" phone
ryanraven said:
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Click to expand...
Click to collapse
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
to Hajj_3 :
Tanks for share the ROM.. I need it to recover my friends phone..
I just got this phone, not looking to root it yet as theres no option for a custom rom yet.
didnt want to start a new thread as theres not really any section for this phone yet.
Everything was fine until i installed the firmware update. Now applications cannot access the mic. Some complain about it being in use by another app. others like video editor or sound recorder will record, but the video recorder there is no file, and sound recorder crashes when you hit stop.
Alcatels website is useless, wasnt working yesterday, today it is but cant find any contact details incase its a bug in there firmware. Everything works fine except for that. Which is annoying because i use RTA software and now it doesnt as it cant access the mic.
any ideas?
Hi guys,
I've rooted my phone with abd and udpate.zip a long time ago, and it was fine till some days ago it stopped from receiving calls and the home button does nothing when pressed, although in recovey mode it works.
I've done a hard reset, reflashed the recovery.img, system.img and boot.img I've found in this post with fasboot, but did not solve the problem.
I've tried a firmware update with Alcatel's own software but it just keeps saying my firmware is updated already. I've also tried to edit the proinfo file, but I don't know what to change in the file. You can see more about that method here: http://forum.gsmhosting.com/vbb/9772370-post8.html
My guess is that the files that are corrupted and preventing me from receiving calls are somewhere else than those img's I've flashed. Has anybody got a FULL backup of his rom (e.g. Rom Manager) so I can recover the phone completely?
Thanks!
upgrade software
bussand said:
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
Click to expand...
Click to collapse
The problem is, the upgrade software link doesn't work anymore :\.
ht tp: // ww w1. alcatelonetouch.com/global-en/ support/download/one_touch_ 983.html
(remove of spaces, im a new user so they won't let me post one)
Is there anyway someone can find a link for it because i have been searching for ages and haven't found one.
http://www.alcatel-mobilephones.com/global-en/support/download/one_touch_983.html
Preface to all of this I rather impulsively decided to unlock my boot loader and root then load a new kernel. I did not make a backup and did not do research before trying to flash the new kernel.
I was attempting to flash a new kernel when I got error 1 wrong partition probably something simple that I messed up. I googled the issue and one solution was to wipe the device long story short I completely wiped the device bricking it because I am DUMB luckily there was a solution to this in this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 I was completing this process when the internet at my apartment went down. I was on step 6 (loading twrp)and had to leave for work before the internet was back up. I have a functioning phone so I am happy for now. However there are issues with it. The system keeps attempting to update and fails every time. (from L29C636B110 to L29C636B158) How do I fix this? Do I just need to go through the rest of the steps of the rebranding guide?
I am still interested in loading a custom rom as I am dumb with EMUI. What are considered the best roms? The rom section here seems to be mostly dead.
I have found open kirin but I need EMUI 8 How do I go about getting that?
Sorry if these all seem like dumb questions but I jumped in with very little research and have been attempting to fix that problem but I would also like to complete this process before I become complacent with my phone right now.
hi there.
Use this guide : https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Do all the steps,u can upgrade/downgrade to any Rom(same brand) with this method (both Nougat and oreo)
and after u did them,u will have a locked bootloader with a brand new rom !
from there,u r free to do anything u want with ur phone
Note:if u want to downgrade from Oreo to Noughat, Or update ur current Oreo firmware(if unlocked) u need to use this method :
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Also u can find your phone firmware files here:
http://pro-teammt.ru/firmware-database/?firmware_model=mha-l29&firmware_page=0
Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.
Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.
brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.
Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.
I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.
Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:
So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.
Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.
You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img
Yup, it's working now. Thanks all.
I have successfully rooted mine and having adaway installed
Can you install stock android 10 or even android 11 now?
ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?
zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method
TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.
minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!
I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides
Make sure you flash boot.img in fastbootd
I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.
I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?
UPDATE: You can now get root on the Android 10 Umidigi A7 Pro using magisk.zip v25.2 (25200).
See post 10 for more info
----------
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
[reserved]
earlier today i managed to find a link for magisk canary. i dont have the device near me atm, but i believe the manager is v7.5 and magisk itself is v19.X. the output patch file comes out named differently with the older version (newer version appends a unique string behind the name). however, same results as before. boot loop.
one positive note tho: the patched boot file completes with a big green check rather than the runtime error, or whatever it was previously.
i tried pushing the patched boot file over fastboot and via the flash tool. same results regardless.
re-flashed the stock boot image and phone is back up and running. still no root though.
still leaning strongly toward it being a magisk problem, but ive seen mention of disabling some security features dealing with individual partitions, but that was on other umidigi models, so ill have to research further if nothing else pans out
found this tut mentioning vbmeta. otherwise, same process that ive been using with no success. figure its worth a shot. ill post back with results
rooting the umidigi a7 pro (magisk)
rooting the umidigi a7 pro (magisk). GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This guide is for advince users only! better guide comming soon on XDA (I have test this on my own umidigi a7 pro )In order to root your umidigi a7 pro you need to: 1) download device FW --> https://community.umidigi.com/forum.php?mod=forumdisplay&fid=235 (DO NOT download the EEA verison if you are not in Europe!) 2) download sp flash tool in case you brick you phone. --> https://spflashtool.com/ 3) unlock your bootloader --> https://www.getdroidtips.com/unlock-bootloader-umidigi-a5-pro-2/ 2) flash this vbmeta.img file with fastboot in bootloader mode. --> https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg cmd: fastboot flash vbmeta vbmeta.img 3) extract the boot.img from fw.7z file and patch it with magisk 4) flash your patched_boot.img in bootloader mode cmd: fastboot flash boot boot.img enjoy your rooted phone!!!
nope, the vbmeta thing didnt help. bootloop. i tried using the patch from the latest magisk, and the patch from the older version of magisk. same across the board.
double b26 said:
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
Click to expand...
Click to collapse
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
[RESOURCES]
magisk download archive
Download Latest Magisk zip v23.0 and Magisk Manager 8.0.7 and Root your phone
On this page, we will share the full instructions to download and install Magisk zip on your Android Phone. This tutorial is also for the newbies/noobs
www.getdroidtips.com
19deke55 said:
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
Click to expand...
Click to collapse
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
double b26 said:
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
Click to expand...
Click to collapse
Thanks. The Mediatek side of things is interesting as I have at least one Lenovo tablet that uses them and the Kindle Fire tablet I have also. Such a pain that manufacturers have went down the road of locking bootloaders the way they have. It used to be so easy to install ROMs. Oh well. C'est la vie.
Thanks for the info. I can't see me touching the Umidigi now for a couple of years. It would be more than my life's worth, lol. I'll copy the contents of your post for future reference.
Have a nice day. Hope you have success with your efforts and that your satellite connection improves.
I GOT ROOT !!
Sorry, I forgot to update this thread...
Bottom line is that there was a bug in magisk. It has since been repaired, and root procedure works 'as advertised' using magisk.zip v25.2 (25200)
After having no luck, I gave up. A few months later I tried again after reading about how magisk had a recent bug fix that sounded like it might have been the problem for this Umidigi. So, I grabbed a new build of magisk .zip, followed the tutorial, and it worked as expected. Pretty simple, once you have the resources ready. Not to mention, a windows 10 pc is all you need to get it done.
---------
My Metro by T-Mobile plan is no-cap-LTE, but doesn't have a hotspot allotment. I'm using a 'hotspot unlocker' magisk module to give me access to the hotspot. I believe it stops reporting hotspot activity back to the ISP, but I'm not sure. Regardless, I use a lot of hotspot data every month, but not a peep from the provider.
In conjunction with that, I'm running "VPN Hotspot" to tunnel hotspot traffic thru my phone's VPN connection. Otherwise, tethered data bypasses the VPN. The app is on play store and requires root.
I'm using the phones hotspot to serve data across to an old dd wrt router I have set as a repeater bridge. It runs a virtual wifi network, and other devices sign into that network. From there, behind the router, it operates as a normal home wifi network. Smart TVs, Chromecast, and all your tablet apps work as expected.
----------
I'm also running a few other modules, like viper audio. So far, so good. Really can't complain for a cheap device. It even gets decent battery life when serving data. About 10% per hour, avg running, but can go further if not running a VPN and close background apps .
---------
I'll look on the PC and see if I can compile a list of software, drivers, etc that were needed.