Related
ROOT + CWM + ROM (cleaned stock ~ custom) for HCL Me Connect 2.0 Tab V2
WARNING , THESE PROCEDURES WILL MAKE YOUR DEVICE OUT OF WARRANTY AND MAY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK.
Make sure USB Drivers are installed on your PC.
------------------------------------------------------------
X. Rooting Steps:
1. Turn on USB Debugging on Tab
2. Download Vroot on your PC ( Google it or www.mgyun.com/en/getvroot )
3. Run Vroot & Connect your Tab to PC. Vroot will auto detect the device and root it..
------------------------------------------------------------------
XX. Installing CWM
1. Download and install two apps like File Manager with root access and SManager ( Script Manager) for console.
2. Grant root access to both apps.
3. Download recovery and flash from link:
http://www.mediafire.com/download/vf5xy1hb7kb12ha/HCL_Tab_CWM.rar
4. Extact the file (flash_image and recovery.img) on your internal sd card and after extarction, copy both files to root folder named "/dev" using File Explorer(with root access).
5.Enter root shell by running SManager Console.
6. Type the following commands:
Command 1:
chmod 755 /dev/flash_image
Command 2:
/dev/flash_image recovery /dev/recovery.img
( type the command exactly, care for no uppercases, better copy and paste)
6. After entering the command, u will get " recovery successfully updated"
7. Now u have recovery installed, u may boot into recovery by shutting down ur tab and pressing power and volume dowm button together for around 7 secs until logo shows up.
Congrats now u have rooted tab and a custom recovery CWM.
--------------------------------------------------------------------
XXX. ROM ( will update later)
I have not prepared custom rom but instead i have cleaned rom of my tab with all bloatwares and nice UI and launcher ( Screenshot attached) .
You may download the file ( ~ 220 MB ) and restore with CWM recovry by following below steps:
DOWNLOAD LINKS (FILE UPLOADED IN PARTS, DOWNLOAD ALL 3 PARTS BEFORE UNZIPPING):
http://www.mediafire.com/download/8prnbeuybkptnca/clockworkmod.zip
http://www.mediafire.com/download/cq9t74v0pdk4l4k/clockworkmod.z01
http://www.mediafire.com/download/7ukn7psr2byb2cw/clockworkmod.z02
1. First make backup of current rom through CWM.
2. Backup rom on ur pc by switching on the device.
3. Extract the contents of downloaded files into internal sd.
4. Goto CWM Recovery, then format system, format data, format cache and wipe format dalvik cache.
5. Now choose restore option to restore the downloaded clean rom..
WARNING , THESE PROCEDURES WILL MAKE YOUR DEVICE OUT OF WARRANTY AND MAY BRICK YOUR DEVICE. DO IT AT YOUR OWN RISK.
Thanks man i 've successfully installed clock work mod recovery 6.I am waiting for the ROM
Sent from my Connect-2G-2.0 using xda app-developers app
BackupTA
You forgot to mention BackupTA application before doing all of this..
It helps u revert ur phone to the original stock state as if there was never any tweaking..
Great way for not making the warranty void..
Cheers..
---------- Post added at 01:57 AM ---------- Previous post was at 01:52 AM ----------
Oh!!
Here's the link..
http://forum.xda-developers.com/xpe.../tutorial-backup-ta-partition-to-drm-t2234627
rom
waiting for the rom man
connect 2g 2.0
Thank You So much for this wonderful tutorial ,Now i've got CWM working on my HCL me connect 2g 2.0,All the other tutorials on other sites were not working
good work bro but waiting for the rom
Bro i have rooted and installed CWM Recovery by using your tutorial but Unfortunately i have deleted my rom and i have downloaded the stouk rom from the hcl (official website) but it is also in .img , so i can't even flash it throw the CWM Recovery, and if i switch on my tablet, it stuck on boot logo,
So, please bro made the custom rom fast as possible :crying:
and bro good luck for your future
Thanks
rom link added
rom link added, you may recover your device...
gautam908 said:
Bro i have rooted and installed CWM Recovery by using your tutorial but Unfortunately i have deleted my rom and i have downloaded the stouk rom from the hcl (official website) but it is also in .img , so i can't even flash it throw the CWM Recovery, and if i switch on my tablet, it stuck on boot logo,
So, please bro made the custom rom fast as possible :crying:
and bro good luck for your future
Thanks
Click to expand...
Click to collapse
I need help while extracting the file :/
The one file is in .zip and another two files is in .z01 and .z02 file and cannot be extract, Bro help me please
If you can give the screen shot please it would help me a lot
Thanks
MD5 mismatch
Bro I have extracted the backup file of the ROM and while restoring it I was getting an error of MD5 mismatch???? Any solution???
Waiting for rom
I hav install cwm recovery.can you post the link of cyanogen mod custom rom
hello everyone, please help me to port cm 12 for my tablet: HCL me connect 2.0. above stock rom files are missing.. techincal speciation are: 1 GHz cortex A9 CPU , 1GB DDR3 RAM currently running on android 4.1 jelly bean os.
please guide and help me to update my tablet andriod version..
Hi!
I update the Idol suite for 4.7 6039 phone version, it is a Windows tools ( sorry).
Log:
It use ADB tools
Can unlock bootloader
Flash TWRP 3.0.0-0 for Idol 4.7
Backup yur phone ROM (need root)
Can boot in bootloader mode
Can reboot from bootloader mode
Can boot in to recovery
Can simply reboot the phone
Can extract the files from a ext4 image, like system.img
Can flash a single image
Can pull to edite the build.prop file and create a flash zip for it
Can boot in to twrp 3.0.0-0 with out flashing ( useful to recover the phone)
Can pull the apks from system and create a flash zip ( If you want to change something in apps or change a pp for another than you want to flash it again )
Can edite the apk files and create a flash zip
Can create a new Splash image and a zip to flash it
It have idol drivers for windows
NOTE:
Some tools are not mine, I simply put everything together in one place!
I am not responsible for any damage they may cause to your device.
Use it at your responsability
Extract the folder from zip in to descktop and execute the Idol_Suite_V3.exe file.
New_Idol_4.7_Suite.zip
Any issue please tell me!
Enjoy it!
The tool is update:
Now you can modify boot and recovery to.
thank you dude.
You can upload the file again
Thanks!!!
Hi Persona78, first can i say what a fantastic job you have done, most of my research on the idol 3 4.7 points back to you, hats off sir!
I'm still having a problem and i'm really at a loss here after about a week of no returns.
adb refuses to recognise my 6039y when in bootloader so i cannot flash recovery, or ROM, or any command. I have all drivers installed correctly, vendor id of 0x1bbb is set in a.ini file in adb_usb.ini, i keep search for different approaches but turning up nothing!
Are there anything to suggest? I would be most appreciative!
Thanks, Marlin
My phone is the ASUS Zenfone 3 deluxe (zs550kl) model and its bricked only can enter fastboot or adb still but my os will not boot I tried going to asus website for stock firmware (UL-Z018-WW-11.40.71.37-user.zip) and stock kernel (ZS550KL_Kermel_11_40_71_37.zip). how do I install these to fix my phone unless there is a better way to make it boot. by the way im new to android I always had iphone jailbroken until last year I am android now but give me noob instructions for the how to. maybe I should add this I already have adb/fastboot installed and the commands for adb devices or fastboot devices when in fastboot mode both recognize my device so maybe my commands are wrong or something but I tried every way I could toinstill firmware and not sure what to flash kernel as the zip or the file unzipped please help thanks in advance. Not sure why this happened exactly but my bootloader is unlocked already but was never rooted so if there is another way to install another custom firmware besides stock I would like those instructions also thanks again
first off your phone is soft brick meaning all you have to do is flash the stock android software back onto your phone.
install to sd card -> boot into recovery (stock or twrp whatever you have works)
flash from sd
let it load (this will work if you have the correct files)
it will reboot and will work good as new again.
you shouldnt have to flash the kernal, just the UL-Z0 file.
That would have worked yesterday but im having another issue now basically instead of waiting for a response on here I went ahead and did other stuff now my recovery menu is not showing up so I cant install from sd now the only option I'm getting is fastboot so is there a way to fix the stock recovery option or even install a custom recovery which might be eaiser because my bootloader is already unlocked. I was going to try to flash stock recovery my self but not sure how exactly I know I use fastboot flash recovery (recovery file name in the folder) and I think it's .img but not sure so I think it will be either .zip or .img file type but not sure what it will be called if it's stock or custom and not sure where to find either. Last issue I'm not sure of is the actual files I downloaded from asus.com the firmware for my specific phone model not working when I try to flash it as the .zip file so my question is do you need to do something with it such as edit the script of something inside the zip of it and I also downloaded the kernel for my specific phone model from the Asus site and not sure if I needed it when flashing stock rom back to device or how to even flash it on the device please help if you can and I know some questions might be dumb to you but remember I'm a noob when it comes to Android recently left iPhone and I was a pro there every phone had a jailbreak and all types of stuff so I know I can get this just takes time I'm sure
I have this exact issue with a new Padfone Infinity A86... No access to stock recovery, only fast boot... But in my case I'm even unable to flash the recovery.img from a firmware package...
I'm wondering if you guys can help this person, maybe there is something in that solution for my Padfone
1: download the full firmware package
2: use sdat2img to convert the sparse system image to a regular one
3: use fastboot to flash the stock boot.img & the newly converted system.img
4: hoping you didn't flash the recovery partition, if you did, reflash the stock dump from the file in my Bootloader unlock thread via fastboot
5: reboot to recovery & do a factory reset
Read the documentation at each step, do your research, learn the process.
EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.