Database Develop

[ARC] Rooted 2.3.3 (4.0.A.2.368) [Locked Bootloader]

Do not try this if you have an unlocked bootloader or if you dont know what your doing!
I'm not resposible if you break or brick your phone!
If you're already on a rooted .184 and OTA update is available for you just update your firmware.
{
"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"
}
If there is no OTA update available for your device follow these instructions:
- Flash back to 3.0.A.2.184 Generic UK with the Flashtool 0.2.9.1
i would recommend that you Wipe User Data when flashing for a optimal flash and fully working OS.
- Use Gingerbreak 1.20 or Gingerbreak 1.20 (Mirror)
- Update your Arc using a OTA (over the air) update
(Go to settings-> About phone-> Software update)
- Enjoy your latest update in rooted 2.3.3!!!
SOLUTIONS:
If you struggle with the update or GingerBreak, either check your memory card for avaliable space or reformat it if your having problems.
If your having problems with the system or settings you should have Wiped User Data when Flashing.
Do NOT modify the system until your done updating to .368
honglong said:
I have a T-Mobile branded UK Sony Arc. It is sim unlocked.
Here are my steps:
1. I flashed the firmware in the original post .. Worked OK
2. I run Gingerbreak .. Worked OK
3. I run the software update on the phone and it gave me the 46mb update
4. I tried to update and it said it failed
5. I run the software update again. Failed.
6. Tried again and this time it came up with an update 96mb (the right update)
7. I updated and now I have the latest firmware and rooted.
Thanks to the original poster
Click to expand...
Click to collapse

This solution is working for me on my UK generic ARC. Thank you

how long does gingerbreak take?

KeizBaby said:
how long does gingerbreak take?
Click to expand...
Click to collapse
1 to 10 minutes.
What's different in this methode then the allready known methode --> [URL="http://forum.xda-developers.com/showthread.php?t=1115542"]http://forum.xda-developers.com/showthread.php?t=1115542[/URL]

Very thanks to Nepturion.
I have just upromed 368 UK by your method. This way is better than uprom with HK rom.

kistigun said:
What's different in this methode then the allready known methode --> [URL="http://forum.xda-developers.com/showthread.php?t=1115542"]http://forum.xda-developers.com/showthread.php?t=1115542[/URL]
Click to expand...
Click to collapse
Only difference is that this thread is for this specific firmware, plus this is not .181 firmware
.184 has OTA update to the latest, i dont think .146 have OTA to .368
I know on my phone i tried to update from .181 an then i needed to download a system on 50 MB approx, which i believe is not the latest

KeizBaby said:
how long does gingerbreak take?
Click to expand...
Click to collapse
For me it took about 2 minutes, kill all apps before starting so the process will go abit faster.

Now i cant remember or not, but is the SD card meant to un-mount when running gingerbreak ?

punkmonkey1984 said:
Now i cant remember or not, but is the SD card meant to un-mount when running gingerbreak ?
Click to expand...
Click to collapse
Yes its suppose to, after the un-mount there is about 30 more sec then the process is complete

Nepturion said:
Yes its suppose to, after the un-mount there is about 30 more sec then the process is complete
Click to expand...
Click to collapse
Yeah i thought it was meant too, but nothing happened, so i formatted my old SD card, and retried with that, then it worked ok.
Updated to new firmware now.

Im try this one let see .because 181 its not working ..hehehe

It works here.... followed instructions as in first post ... cheers
Sent from my LT15i using Tapatalk

4.0.A.2.368 Rooted, with a locked bootloader thanks.

Hello dear,
By the first I'd like to THANK YOU
I've do this steps on my Xperia arc from week ago, but when I try to update my phone
over the air, the version of software that have install on my cellphone is 3.0.1.A.0.145
and it's the latest update available
So can I do any thing to update my phone but with rooted 2.3.3 4.0.A.2.368 ?
Regards,

Works great, I did not even wipe my data

Is there a difference between the Generic UK and the Generic? Thanks.
P.S. I hope my question is right.

I have a T-Mobile branded UK Sony Arc. It is sim unlocked.
Here are my steps:
1. I flashed the firmware in the original post .. Worked OK
2. I run Gingerbreak .. Worked OK
3. I run the software update on the phone and it gave me the 46mb update
4. I tried to update and it said it failed
5. I run the software update again. Failed.
6. Tried again and this time it came up with an update 96mb (the right update)
7. I updated and now I have the latest firmware and rooted.
Thanks to the original poster

Thanks it works perfect!

wohooo!11
Works great
I did not even wipe my data
+1+1+1+1+1+1 * *
* *
*

Hello, I would like to know if this form of root is possible with the generic global firmware. Thank you

[NAE ROM] Got WIFI and DATA working

resresize piok here is exactly what i did to make Stock rooted NAE Rom working with DATA and WIFI
(I USED ODIN 3 TO FLASH PHILZ RECOVERY TAR)
FULL WIPE
NEED TO BE ON MK2
flash MK2 STOCK ROOTED
FOR SOME REASON IT ONLY WORKS WHEN I FLASH TRI FORCE ROM...
INSTALL TRI FORCE ROM 5.4 WITH CURRENT PHILZ TOUCH RECOVERY
LET IT BOOT
AS SOON AS IT DOES REBOOT INTO RECOVERY
INSTALL NAE ROM...NO WIPE...REBOOT SYSTEM....IT SHOULD GET STUCK AT SPRINT BOOT ANIM....ALL GOOD....NOW....
REBOOT TO DOWNLOAD MODE
FLASH NAE MODEM (FIRMWARE) UNCHECK AUTO REBOOT AND F. RESET
AFTER IT SAYS PASS....REBOOT PHONE USING POWER BUTTON....
SHOULD SAY ANDROID IS UPGRADING ...OPTIMIZING APPS .....ONCE ITS DONE.. UR GOOD
POSTED SCREEN SHOT
{
"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"
}

Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk

MK2
optimummind said:
Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
MK2

deeja303y said:
MK2
Click to expand...
Click to collapse
How can I tell which bootloader I have?

You can use an app like Root Checker or Phone Info from the Playstore.

does this knox void?

legasus233 said:
How can I tell which bootloader I have?
Click to expand...
Click to collapse
You can do that from terminal emulator by entering this command getprop ro.bootloader
Sent from my SPH-L720 using Tapatalk

SayWhat10 said:
does this knox void?
Click to expand...
Click to collapse
Flashing the custom recovery will trip KNOX.

This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi

That's not good

samjam keep us posted. Were you able to get wifi restored?
Data connection still holding?

samjam91 said:
This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi
Click to expand...
Click to collapse
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.

dumb question
samjam91 said:
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.
Click to expand...
Click to collapse
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...

kujanme said:
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...
Click to expand...
Click to collapse
Either in an adb shell or terminal emulator, type this:
Code:
getprop ro.bootloader
It should then return your current bootloader. If it's MJA/MK2/NAE you CANNOT downgrade it, because of KNOX.

[4.4.4][XT1039][OFFICIAL][TWRP/CWM] Stock Moto G 4G 21.1.46.en.EU

Stock with unlocked bootloader warning removed
Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
This is for unlocked bootloader only
Update brings:​
Android 4.4.4 Kitkat
SD Card Fixes
Instructions:
FLASH CWM
WIPE DATA/FACTORY RESET
FLASH ROM
FLASH Super SU (if you want to root)
WIPE DALVIK.
ENJOY!
Only tested with CWM
Dowload:​
Mega
Google Drive
If you want another filehost just ask and if the zip does not work tell me we will look into it :highfive:​

OMG!!!
About root procedure... Did anyone know about it?

Flash this Super SU
Ps: Is my update working ?

I didn't try it yet. I prefer TWRP, so I was going to test if it's working with it. But I just got the XT1039 last week, so I set it up to my liking, then I unlocked bootloader to root it, so second setup, and then I messed up deleting some files (don't really know what happened), so I had to set it up for the 3rd time just yesterday. I'm not in the mood of wiping it again just yet!
But i will
EDIT: Just installed it, with TWRP and wiping only cache. Works like a charm!

I did the update with the file above without any wipe (except cache)
Envoyé de mon XT1039 en utilisant Tapatalk

It works perfectly, thank you!
I was having some trouble updating to 4.4.4 using OTA as I changed a lot in the stock rom. After spending hours reverting changes, I still couldn't get it to work (without flashing stock and starting all over again, which I didn't want to do really).
Was thinking of starting all over again, flashing stock image, OTA to 4.4.4 and changing everything after that, when I came across your thread.
You saved me from spending hours having to start from scratch! Top job!
I only flashed your file from my OTG drive in TWRP , over my heavily changed system, and it works like a dream.
See this screenshot I took right after flashing and reboot:
{
"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"
}
So, yes man, you did it! Thanks again! [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk

Nice work Darius.
Also had probs with 4.4.4 OTA due to custom recovery/rooting.
This was easiest way to 4.4.4 happiness....

I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?

Will this work for the XT1039 from Great Britain? Build numbers are the same but instead of EU there is a GB. I bought mine from Amazon and it is the unlocked version.

Awesome!
Hi,
Just installed on my 4.4.3, wiping only the cache partition as you said. As far as I can see everythying works perfectly.
Thank you man !

guijarrelson said:
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Click to expand...
Click to collapse
The bootloader is proprietary so you need to ask Motorola for an unlock code. "Fastboot oem unlock" won't work. There are a lot of threads about this in Q&A and General.

I just finished updating my GB version to this EU version and it worked great! No issues to report. Installed CWM recovery, then EU 4.4.4., wiped cache then installed superuser. Fantastic work with no lost data. My 32GB sdcard works too!!!! AMAZING

I tried using a Sandisk 32 Gb sd card (bought in 2011, and still working perfectly in my old HTC Desire) that didn't work in this phone before the update, but it still doesn't. Have seen other reports about the same issue, so I guess not every sd card problem is solved with the 4.4.4 update.
The card mounts normally, I can see the files on it in any explorer, but it's not possible to read from or write onto the card.
Phone can't format the card, and a check with a Windows pc doesn't show anything wrong with the card.
Strange huh? Any ideas?

I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?

mhisani said:
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
Click to expand...
Click to collapse
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?

jkoetsier said:
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
Click to expand...
Click to collapse
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining

mhisani said:
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
Click to expand...
Click to collapse
Factory Reset does not touch your system partition. Only wipes your data.
Xposed would have modified your system partition to prevent ART. Flashing a new rom would restore your system partition to how it was.
Next time, either disable xposed before uninstalling. Or if that doesn't work, either fastboot flash the system.img chunks found in the stock firmware OR flash the same firmware in a custom recovery (if zip available). This will refresh your system partition and restore any changes without affecting your data.

Edit: ignore

Wait so will this work on the XT1045?

I have flashed this ROM and my SD card (Sandisk 16 GB) is still not recognized by the phone. Any advices ?

Pixel 5 with Magisk rooted, can't receive OTA.

My Pixel 5 (RD1A.201105.003.C1, Nov 2020) with Magisk rooted works fine until I tried to update.
When I installed Magisk, I turn off "Automatic System updates" in the Developer options.
{
"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"
}
Before check OTA manually, I Uninstall Magisk>Restore Images successfully.
Then I checked OTA manually, but got this:
Your system is up to date
Android version: 11
Android Security update: November 5, 2020
Last successful check for update at 20:48
I tried several times, but got the same, except the time stamp. So I re-install Magisk and restart. Everything is fine.
I tried to check OTA this morning, of course after uninstall Magisk and resotre image. Before I click the "Check for update" button, I found the Last successful check for update is 05:54. That means background check OTA when I was sleeping, without uninstall Magisk! I clicked the check button, all the same except time stamp changed to 8:04.
I'm 100% sure that the Auto update in Developer options is OFF. Why my Pixel 5 still check OTA background?
I know that with Magisk installed, OTA not available. But why OTA still not available after uninstall Magisk and restore image successfully?

I don't know if it has something to do with active oem unlocking. But if you haven't the stock boot.img installed and disable oem unlock you won't boot up your phone, because boot Partition isn't valid.
I would suggest you forget the ota and download the full ota update from android developer portal and install the update from your pc.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

I didn't sideload update & keep data with Magisk before. I do some research, some said sideload using OTA image but others said using Factory image. Anyone would help me with the detail steps? Really appreciated!
Raz0Rfail said:
I don't know if it has something to do with active oem unlocking. But if you haven't the stock boot.img installed and disable oem unlock you won't boot up your phone, because boot Partition isn't valid.
I would suggest you forget the ota and download the full ota update from android developer portal and install the update from your pc.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse

eric_4321 said:
I didn't sideload update & keep data with Magisk before. I do some research, some said sideload using OTA image but others said using Factory image. Anyone would help me with the detail steps? Really appreciated!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/guide-root-pixel-5-xl-android-11-r.4187609/
See #4 under the "Index" heading for Factory Image steps

Thank you for your help. The #4 is for Factory Image, would you please help me how to sideload OTA Image with Magisk rooted? Thanks again!
jsbeagle said:
https://forum.xda-developers.com/t/guide-root-pixel-5-xl-android-11-r.4187609/
See #4 under the "Index" heading for Factory Image steps
Click to expand...
Click to collapse

eric_4321 said:
Thank you for your help. The #4 is for Factory Image, would you please help me how to sideload OTA Image with Magisk rooted? Thanks again!
Click to expand...
Click to collapse
I've never done it. I've been flashing the factory image every month since the launch of the original Pixel. Remove "-w" if you don't want to wipe data. Its not that much trouble.
The Pixel images site has instructions for sideloading the OTA if you insist on going that route. https://developers.google.com/android/ota I have no idea if or how that works when rooted. You might need to fastboot flash the original boot.img first.

I have same issue. My phone won't receive any OTA updates, keeps telling me phones upto date but I'm still on August security update. Any figure out how to get it working again? Got magisk installed.

A question for a developer

What is my twrp password for user 0?
How do I get the phone running after updating to v22?

You need to provide much more information if you want anyone to help you…
What’s you phone brand and model ?
How did you install Magisk ?
What messages do you get ?
After doing what ?
What are you trying to achieve ?
Etc.
Please note that these are basic information that pretty much any person/service looking to help you will ask, be it here on a forum, a service hotline, your car mechanic, and even your doctor.
No one can read your mind, while you know what you did/what happened.
Also a title like "A question for a developer" doesn’t help a lot, as it doesn’t describe what is the issue or your goal.
A much better title could be "TWRP asks me for user 0 password".
Help the others help you !

Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.

QVA said:
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.
Click to expand...
Click to collapse
If you did not pay the developer, you have no right to complain.
You got a product for free, without any guarantee, and can’t expect any support either.
You are, however, encouraged to try and solve your problem, post your findings here, and help others.

we know that you update Magisk to v22 via Magisk app the question is how you "install" it... most devices would not have magisk pre-installed on there system

QVA said:
Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
Click to expand...
Click to collapse
This is a much better report !
I hope someone will be able to help you out.

I wanted to install using the first option in the application. The terminal showed up, performed some operations and wanted to reboot the phone. After that, only TWRP starts.

It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?

QVA said:
It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?
Click to expand...
Click to collapse
upload it and i'll patch it

@QVA There's no need for you to keep opening threads regarding the very same issue. You're currently posting about the very same issue in this thread and these two others:
https://forum.xda-developers.com/t/camera-stop-working.4248233/
https://forum.xda-developers.com/t/magisk-v22-update-encrypted-my-phone.4248421/
Keep everything in one thread, it makes it easier to follow the discussion and it keeps clutter in the forum down (please also note forum rule #5).
I suggest that you decide which thread you want to keep discussing this in and report the others for closure (I'm not a moderator in these forums, or I would have helped you with that myself).

Here is the file:
boot.img

{
"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"
}

I also tried to remove Magisk but it failed:

Thanks for your time, but the file you sent did not solve the problem.
Still booting into twrp screen.

you device don't run a/b partition like boot_a.img and boot_b.img??

I don't know, it's a normal phone with a normal system. There is a single boot.img file in the system archive.

looking at the magisk uninstaller log you have error "Boot image is patched by other programs! Cannot uninstall!" lmao you really messed up

why don't you just do a factory reset?

I do not want to lose 100gb of photos and application from the bank.

By the way @QVA, was your device encrypted before all this?
And have you tried the default TWRP decryption password (default_password)?
And judging from that photo you posted of the TWRP flash screen you were using an ancient uninstaller... Better to try the current (just rename the Magisk apk to uninstall.zip).