Develop Bugs

[ROM][ODIN]Odin One-Clicks(T-MOBILE,VIDEOTRON,MOBILICITY,WIND)

This is a set of Odin One-Click Packages. If you're unfamiliar with these, it is the factory firmware loaded in a compacted version of odin and flashing is executed in a single click. No need to check boxes, or worry about what slots to load etc. I do not own this version of the s3 so these have not been tested. They're packed in self-extracting 7z archives. They will not affect your flash count. Every device has a rooted version. Most have an unrooted version as well. If yours does not its because I damn near got carpel tunnel making these and my hands needed a break. Unrooted versions will be up soon.
Windows PC with Samsung Drivers installed is required.
Shouldn't be any problems but I am not responsible for any that may arise.
{
"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"
}
DOWNLOAD FOR T-MOBILE
DOWNLOAD FOR CANADIAN VARIANTS
AFH MIRROR
ENJOY!​

Look promising.. Too bad I've flash to stock a couple days ago.... Next time I'll give it a shot.
Sent from yo mama's couch

Anyone try this? I am tempted because the S3 doesn't have a one click heimdall return to stock. I soft brick my phone all the time and a one click solution is an easy way out of a bind.

can this be used to root a gs3 thats not rooted YET? I guess not because it doesn't unlock the device, right....

It can. Thats kind of the point. If by unlocked you mean the bootloader the tmo variants isn't locked

waiting for more responses before even attempting to do this...
not risking a brick lol

I have a tmobile s3 unlock and using it on mobilcity. Im curently on CM10. Could i flash stock mobilicity JB rom with this?
Sent from my SGH-T999 using xda app-developers app

Shivammcool said:
I have a tmobile s3 unlock and using it on mobilcity. Im curently on CM10. Could i flash stock mobilicity JB rom with this?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I can't say for sure but most likely not. You could probably do it without problems if it was only the system but these contain all the firmware including bootloaders and stuff so it would most likely cause a brick if you tried
EDIT:If it helps. Here is the Mobilicity version with only the system and boot.img so you can flash to the tmo version without risking a brick. Doesnt contain bootloaders so it'll be safe to flash http://goo.im/devs/billard412/d2can/MOBILICITY/Mobilicity_System_and_Boot_only.exe
Attached pic of it flashing to my sprint phone as proof its safe

I have a couple of questions here... Sorry if they are stupid questions or noob questions.
So using this 1-click method, you can get root on 4.1.1 JB T-mobile xxxJLA firmware. (or un-root back to factory without tripping counter)
When using this method, does it erase the users existing data and/or apps already installed on the phone?
IF YES, is it possible to make a backup, use this method to get root, then restore the backup to replace users data/apps/etc? (or is that a bad idea?)
After using this method to gain root access, do you get CMW and SuperUser ?

Yes this will give you root or unroot. Both versions will work to fix a softbrick. As far as weather or not they wipe I cannot confirm as I do not have tmo so I cannot flash all the files it contains. If you're not rooted yet theres really no way to back up apps and data so unless somebody confirms this doesnt wipe then assume the worst and backup internal storage. As i told ppl in the att section who asked, these are based on the original odin tar they are named after so if that wiped you this will too.
Now there is a trick I use when I flash the ones that wipe you and it always works for me. Before you start this,remove the back cover from the phone. When the flashing gets near the end grab the phone. When it finishes the screen will go black and itll reboot. Leave the cable plugged in and as soon as it vibrates and you see the word samsung come up,(before the galaxy s3 screen), pull the battery and keep it out until the red light comes on. Then stick it back in and reboot the phone and it should skip the recovery where you would otherwise be wiped.
That said I do not believe these wipe data but itd be nice to get a confirmation from someone who flashed it.

Whats up with this? Does it unroot properly? not many posts on it!

T999 Question
Will this Odin OneClick Rooted Tmobile T999 firmware work on a AT&T I747 Unlocked and Rooted Galaxy S3 ?
Also does this Odin OneClick come with the modem?
I heard that the T999 modem will not work on a AT&T I747 Galaxy S3 or am I wrong?
Thanks!

Misterjunky said:
Will this Odin OneClick Rooted Tmobile T999 firmware work on a AT&T I747 Unlocked and Rooted Galaxy S3 ?
Also does this Odin OneClick come with the modem?
I heard that the T999 modem will not work on a AT&T I747 Galaxy S3 or am I wrong?
Thanks!
Click to expand...
Click to collapse
That'd be right. I have these for the att variant here however.
http://forum.xda-developers.com/showthread.php?t=2031840
If your asking because u r using the att variant on tmobile this can be done without the modem and bootloaders so itd be safe on the att variant. If thats the case pm me and I can make it.

re: thanks
billard412 said:
That'd be right. I have these for the att variant here however.
http://forum.xda-developers.com/showthread.php?t=2031840
If your asking because u r using the att variant on tmobile this can be done without the modem and bootloaders so itd be safe on the att variant. If thats the case pm me and I can make it.
Click to expand...
Click to collapse
Thanks for the information, too bad that link was for the Un-Rooted AT&T firmware.
It would be nice to find one which is pre-rooted.
I would be using it on an AT&T Galaxy S3 I747 Unlocked and Rooted phone.

[BOOTLOADER] How to Install a Bootloader Update

NOTE: If anyone has any further questions about bootloaders on the S3, please note that I have moved on to another device. Sorry!
Hi everybody,
As you may or may not know, the latest builds of CyanogenMod 10.1 (and many other ROMs which use CM as a base) refuse to install without an updated bootloader on your device. Even if you bypass this requirement, the ROM won't boot. I haven't seen any clear-cut instructions on updating the bootloader except for a single post buried in the CM10.1 nightly thread, posted by Jiangyi, but that update also changes your modem, so I thought I'd throw together a thread dedicated to bootloaders only.
Step 1 - Identify your model
This subforum supports 2 different models; The I747 and the I747M. You can find your device's model in a few different ways:
While Android is running
In Settings, under About Phone, the Baseband version shows the currently installed modem firmware version. If your phone currently works on mobile networks, then you've probably got the right modem firmware for your model, and the Baseband version will start with either "I747" or "I747M". This is your model.
{
"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"
}
While the phone is off
Underneath your battery is a sticker showing your IMEI and other information, including the model number.
Step 2 - Download the correct update
You can install this updated bootloader in a couple different ways; Most people should be comfortable flashing ZIPs in their recovery (CWM or TWRP both work fine) while others may want to install the update via Odin. Choose your model and preferred method, and download the matching file from below.
I747U (AT&T)
I747UCALG1 - Jul 1, 2012 - boot_CWM_I747UCALG1.zip - 1.13 MB
I747UCDLK3 - Nov 3, 2012 - boot_CWM_I747UCDLK3.zip - 1.13 MB
I747UCDMG2 - Jul 2, 2013 - boot_CWM_I747UCDMG2.zip - 1.13 MB
I747UCUEMJB - Oct 11, 2013 - boot_CWM_I747UCUEMJB.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
I747M (Canada and overseas) (Updating this list shortly...)
I747MVLUEMK5 - Nov 5, 2013 - boot_CWM_I747MVLUEMK5.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
Check my Dropbox if d-h.st is giving you issues.
Step 3 - Flash the update
Depending on which type of update package you downloaded, follow one of the following steps:
Flashing with Odin
Download Odin: [link]
Put your phone into download mode. Some ROMs have this option in the Power>Reboot menu, otherwise just hold "Volume Down" and "Home" while powering on your device.
Launch Odin, then connect the USB cable to your device.
Click the "PDA" button and select the package you downloaded in step 2.
Click "Start" in Odin and wait for the process to complete. Your device should reboot automatically when the flash is complete, and you're done.
Flashing in recovery
If you've downloaded a flashable .ZIP from above, copy it to your SD card or internal storage. Reboot your phone into recovery mode (you can do this by holding "Volume Up" and "Home" while powering on your device; let go of the buttons when you see "Recovery booting..." in blue text in the top left of the screen) and install the .ZIP as an update. Reboot, and you're done.
Note: After flashing in recovery, you need to reboot before you (and ROM installers) actually see the new version number.
Did you brick your phone attempting to downgrade your bootloader?
There really is no reason to downgrade your bootloader; If you did it to be able to flash a ROM that doesn't recognize the newest bootloader version and therefore wouldn't let you flash, you should contact the ROM developer and tell them to add the newest bootloader version to their asserts. The latest bootloaders trigger eFUSEs within the device, no longer allowing it to boot from older bootloaders. These eFUSEs cannot be reset, but @-Mr. X- has come up with an unbricking method that may help you out. Check it out here.
If you're looking to update your modem as well, check my signature for a link to the modem thread.

Look forward to seeing a recovery flashable zip that updates the bootloader. Never have I seen that before. I have always used Odin for that. Thanks and looking forward to trying it out.
Sent from My Spiderman Themed I747

So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?

upndwn4par said:
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
Click to expand...
Click to collapse
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help. As a temporary option, you could just use the Odin update and then flash another modem on top of that.

dstruct2k said:
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help.
Click to expand...
Click to collapse
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.

upndwn4par said:
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
Click to expand...
Click to collapse
The link in my first paragraph does just that, but since this is affecting a lot more ROMs than just CM, people are going to need this information and a single post on a random page of a massive thread usually gets overlooked by 99% of people. The point of this thread is to make information easy to find and ensure that people are able to update their bootloaders and run new ROMs.
Like I said, the links to his work are temporary while I get my own files uploaded. Not exactly on the fastest of connections right now.

Added recovery-flashable bootloaders to OP.

i found this post very helpful and informative i think i would have been MORE confused having just been linked to a single post. the pictures and instructions are so awesome!
thanks man the community appreciates your work, you can ignore the rent a mods

If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2

mcala said:
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
Click to expand...
Click to collapse
Depends on whether they updated just the modem to DLK3 or the entire system. If you have issues flashing ROMs, try flashing this first.

thanks! :good:
saves me the hassle of going thru 2k+ pages

If your unsure about which bootloader you have, check >>HERE<<

So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....

Correct, the 4.1.1 bootloader does have the newer flash counter. It will increase your flash counter when you reboot if your not running stock (I think it checks the type of recovery installed and something with the kernel. I think.)

robbieas said:
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Click to expand...
Click to collapse
Using a recovery-flashable ZIP will not increase your flash counter.

And I take it you got his permission To post his work right?
Wayne Tech Nexus

I think it's ok to post links to other people's work, and to improve on it by creating another method of flashing, is it not?

Not without their permission it's not.
Wayne Tech Nexus

dstruct2k said:
Using a recovery-flashable ZIP will not increase your flash counter.
Click to expand...
Click to collapse
This is incorrect. Simply having a custom recovery period with the 4.1.1 bootloader will always increment your counter to 1 after a reboot. Triangle Away will reset your counter to 0, but upon reboot it will be back to 1.
This was my experience when I rooted from 4.1.1. Then I Odin`d back to 4.0.4, rooted, CWM, flased ROMs and my counter stayed at 0 through multiple flashes. As soon as I flashed this bootloader patch my counter went to 1 ater reboot. Triangle Away will reset to 0, but on reboot it goes back to 1.
Not sure it really matters, not sure why I even care about the flash counter... guess just want to hedge my bets in case I need warranty and can't Odin to stock before returning.

dstruct2k said:
Added recovery-flashable bootloaders to OP.
Click to expand...
Click to collapse
What does "OP"means?

New update for 816 lolipop release today

New software update 2.34.401.2
Can anyone tell how i can update my device if i have root and recovery
{
"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"
}
Sent from my HTC Desire 816 dual sim using Tapatalk

Look in the general forum for full guide. You need to go back to stock. Basically flash stock recovery and re-lock bootloader. If you loaded system mods then you probably have to run the ruuxx.exe for your model before doing the OTA. Otherwise you can try OTA after re-lock.

does anyone know how to delete this update? I clicked it by mistake and it installed and tried to update, but it messed with my root making some apps just showing grayed out SD and it keeps trying to make me try to install it again. I was thinking if I can find out where the install file is, i could just delete it and everything might go back to normal.

What is the update contains ??? Did anyone try???
Sent from my HTC Desire 816 dual sim using Tapatalk

I installed it on my Virgin Mobile A5-chl. Doesn't appear to be anything major, mainly just the Stagefright patch. I don't see any other improvements or changes. It was a small patch, so I'm guessing it was just the patch.

Andy1058 said:
does anyone know how to delete this update? I clicked it by mistake and it installed and tried to update, but it messed with my root making some apps just showing grayed out SD and it keeps trying to make me try to install it again. I was thinking if I can find out where the install file is, i could just delete it and everything might go back to normal.
Click to expand...
Click to collapse
The OTA file should be in your download directory. The install failed so it's going to keep asking. I'm not sure if it has an option to never install the update?
I'm seen that app grayed out thing. It's just the apps you've moved to your SD card through the apps page in settings. For some reason it sometimes takes a few seconds for the app to display correctly. I don't think it has anything to do with the software upgrade.
---------- Post added at 11:45 AM ---------- Previous post was at 11:40 AM ----------
joey jamal said:
What is the update contains ??? Did anyone try???
Sent from my HTC Desire 816 dual sim using Tapatalk
Click to expand...
Click to collapse
It's the Stage fright patch. Google it if you want to know more, but basically anyone can crash or take over your phone just by sending you a text w/video.

pcjunky said:
The OTA file should be in your download directory. The install failed so it's going to keep asking. I'm not sure if it has an option to never install the update?
I'm seen that app grayed out thing. It's just the apps you've moved to your SD card through the apps page in settings. For some reason it sometimes takes a few seconds for the app to display correctly. I don't think it has anything to do with the software upgrade.
---------- Post added at 11:45 AM ---------- Previous post was at 11:40 AM ----------
It's the Stage fright patch. Google it if you want to know more, but basically anyone can crash or take over your phone just by sending you a text w/video.
Click to expand...
Click to collapse
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?

Andy1058 said:
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?
Click to expand...
Click to collapse
It's a zip file with a crazy long name that I will not type, but it starts with OTA_A5_CHL_L50_DESIRE. You can find the full name in the link in the patch thread in the general forum.

Please any help I relock my device bootloader ana back to stock recovery but wen I install the ota update it just restart to fastboot and stopped nothing else ...Please help ad5ug I need the way that I can back to stock and recive update
Sent from my HTC Desire 816 dual sim using Tapatalk

Andy1058 said:
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?
Click to expand...
Click to collapse
I forgot to mention that after the update patch is successful the OTA zip file is deleted. I can't remember if the zip file is also deleted if the update fails, but if it isn't in the download (s) directory than it's deleted. Just download the OTA again and delay the install if you want to copy it to your PC to extract and examine the update.

Does anybody have a pure stock twrp or cwm backup before this OTA? I forgot to make my own. the RUU.exe keeps failing with "RomTool.exe has stopped working."my laptop may be at fault, but I can transfer files to and from my phone just fine. VM a5_CHL

jayblaze406 said:
Does anybody have a pure stock twrp or cwm backup before this OTA? I forgot to make my own. the RUU.exe keeps failing with "RomTool.exe has stopped working."my laptop may be at fault, but I can transfer files to and from my phone just fine. VM a5_CHL
Click to expand...
Click to collapse
Did you try uninstalling and then reinstalling HTC Sync? Can I assume you flashed stock recovery and re-locked boot loader?
Any chance you still have the Kitkat to Lollipop OTA update zipfile and can extract and flash the firmware.zip then run the Lollipop ruu.exe (not the new one with the patch). Take a look at this thread for how to info. Basically you're pre flashing the firmware that should be in the ruu.exe file so the ruu.exe shouldn't fail. Then the ota SF patch should run.

pcjunky said:
Did you try uninstalling and then reinstalling HTC Sync? Can I assume you flashed stock recovery and re-locked boot loader?
Any chance you still have the Kitkat to Lollipop OTA update zipfile and can extract and flash the firmware.zip then run the Lollipop ruu.exe (not the new one with the patch). Take a look at this thread for how to info. Basically you're pre flashing the firmware that should be in the ruu.exe file so the ruu.exe shouldn't fail. Then the ota SF patch should run.
Click to expand...
Click to collapse
Nope. don't have the update zip. I'm s-off. rooted. busybox. xposed framework. So much modding I can't OTA because my system files are tainted. but yes, I've uninstalled/reinstalled HTC sync manager on my pc. tried fastboot drivers from here at xda. even uninstalled all of the android sdk files and reinstalled. I'm currently on the 5.0.2 HTC release already. I was able to complete the ru u.exe on my newer laptop. but all I have now is an old Vista x86 laptop. I think the usb ports aren't the best to work with. flashed stock recovery, relocked boot loader several times over. just fed up I restored my rooted, xposed twrp until I can try a different pc.

All is well! Found a Kit Kat stock unrooted twrp backup on my external drive. flashed that, changed the boot.emmc to boot.img. flashed that. Redownloaded the first Lollipop OTA, extracted the stock recovery from the firmware.zip. flashed that. OTA'd the original lollipop release, then OTA'd the stagefright patch. started from scratch but got it done. bootloader stayed unlocked the whole time since I'm s-off. thanks for info, though.

Looking for CWM backup
I've already flashed recovery stock and re-locked
but OTA download corrupted

So, any option to install this patch without going back to stock, and re-locking bootloader ?

Marshmallow OTA update questions

Hey guys,
I have a few questions regarding the Marshmallow update to the One (M8). First of all, I own an international M8 on stock, rooted, with TWRP KitKat firmware version 3.32.707.9. I have not updated either my Sense Home (still have Sense 6 mainly), and most of my apps are the Sense 6 versions, which I prefer to the colourful Sense 7 versions. So, my questions:
I still haven't received the Marshmallow update at all. Do I need to update to Lollipop or will I receive a Marshmallow notification even while on KitKat?
If the above is not possible, then can I install the OTA onto my phone after downloading the zip file from a mirror directly?
Can I backup all the Sense 6 apps that I want, like HTC Clock, HTC Blinkfeed and such with Titanium Backup, update to Marshmallow and restore them, and expect them all to work properly?
Thanks.

1. You need to have lollipop 4.19.707.4 stock ROM to receive Marshmallow update. Won't get it on KitKat, lollipop lower than 4.19.707.4 won't get it too.
2. No
3. Yes & No ... but mostly No unless it's a full KitKat ROM running on Marshmallow firmware.

ckpv5 said:
1. You need to have lollipop 4.19.707.4 stock ROM to receive Marshmallow update. Won't get it on KitKat, lollipop lower than 4.19.707.4 won't get it too.
2. No
3. Yes & No ... but mostly No unless it's a full KitKat ROM running on Marshmallow firmware.
Click to expand...
Click to collapse
That's a bummer... Ah, it was time I cleaned out my phone and clean-installed all my apps and stuff anyway. Thanks for the help. I was hoping I could get the nice globe HTC Clock from Sense 6 in Marshmallow, it was quite useful...

Some updates - I realised that I deleted some system apps without making backups, and now I can't update to Lollipop (and thence to Marshmallow). Big mistake, yes. How do I find which apps were deleted, and how do I restore them? Or is it more prudent to simply make a Titanium Backup of my data, flash a TWRP backup of the new Marshmallow ROM and just restore my data?

SRSR333 said:
Some updates - I realised that I deleted some system apps without making backups, and now I can't update to Lollipop (and thence to Marshmallow). Big mistake, yes. How do I find which apps were deleted, and how do I restore them? Or is it more prudent to simply make a Titanium Backup of my data, flash a TWRP backup of the new Marshmallow ROM and just restore my data?
Click to expand...
Click to collapse
If you want the official OTA, none of that will work. OTA requires stock never rooted ROM.
You can restore a stock nandroid 3.32.707 from ckpv5's collection (link in his signature), and corresponding stock recovery, then do OTAs, all the way up to Marshmallow (if or when its released for your version).

Alright, I successfully flashed an un-rooted TWRP nandroid backup of 3.32.707.9, updated to Lollipop and thence to Marshmallow. I performed a factory reset and then restored all my apps and settings, and proceeded to flash TWRP and the SuperSU binary.
Lo and behold, my phone is now stuck in a boot loop. It gets to the 'One' screen, and then just locks up. I have to press Power + Volume Up to reboot it and switch it off. Any fixes? Also note that my USB port is, for some reason, also dysfunctional now. I can only connect to my PC in 'Fastboot AC' mode, and I've tried three cables already, two different PCs and all the USB ports in both PCs.
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?

SRSR333 said:
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?
Click to expand...
Click to collapse
If you try to do the steps in your first paragraph (Post #6), I'm pretty sure it won't work. Even though the ROM is back to KitKat, all the other firmware (hboot, radio, etc.) is still on MM, so the OTA won't allow you to update back to MM again.
Did you make a TWRP backup before you tried to flash SuperSU (you should always make a backup before applying mods; especially a backup of the unrooted, stock ROM)? If so, restore it. Otherwise, you may need to find a nandroid of the MM "707" stock ROM, or ask someone to upload it.
What version SuperSU did you flash? Versions before 2.51 or so don't work for MM, and will cause the no-boot condition. Also, TWRP should be latest version 2.8.7.0.

redpoint73 said:
What version SuperSU did you flash? Versions before 2.51 or so don't work for MM
Click to expand...
Click to collapse
This is where I messed up. I flashed 2.46.
I'll see if the OTA works, or else I'll just RUU Kit Kat, and then OTA.

SRSR333 said:
This is where I messed up. I flashed 2.46.
Click to expand...
Click to collapse
I suspected as much. In the future, keep in mind that new builds usually require a new SuperSU version.
SRSR333 said:
or else I'll just RUU Kit Kat, and then OTA.
Click to expand...
Click to collapse
That should work. I assume there is RUU for 707 version (can never keep straight which versions do/no not have RUU)? If there is a LP RUU for your version, it would be easier to run that (skip the step of the OTA).

redpoint73 said:
That should work. I assume there is RUU for 707 version (can never keep straight which versions do/no not have RUU)? If there is a LP RUU for your version, it would be easier to run that (skip the step of the OTA).
Click to expand...
Click to collapse
Now, my phone's USB port has stopped working. I can only charge it through my PC, and not get any sort of MTP connection. Something's wrong.

Slide down the notification then in the drop down select file transfers (for MTP) instead of charging

I don't get any notification. It's as if the phone doesn't even realise it's plugged into a PC, and just charges.

SRSR333 said:
I don't get any notification. It's as if the phone doesn't even realise it's plugged into a PC, and just charges.
Click to expand...
Click to collapse
You don't have these ?
{
"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"
}
What ROM that you have now on your device ? You already updated to MM, right ?
If it is your old KitKat ...
Install TWRP 2.8.7.0
Boot to TWRP recovery then enable MTP to transfer files from PC to device
Restore a non-rooted MM

SRSR333 said:
Now, my phone's USB port has stopped working. I can only charge it through my PC, and not get any sort of MTP connection. Something's wrong.
Click to expand...
Click to collapse
What do you mean "Now"? Which did you end up doing? Stock kitkat nandroid? KK RUU? LP RUU?
Try to go to Windows Device Manager, find the device, and manually pick the generic Android MTP drivers. See if that makes MTP or fastboot/adb work properly.

redpoint73 said:
What do you mean "Now"? Which did you end up doing? Stock kitkat nandroid? KK RUU? LP RUU?
Click to expand...
Click to collapse
I haven't done anything yet. I tried to connect my phone previously to try and enter fastboot USB mode before all this, and I noticed that my phone was only connecting as fastboot AC. I could not, and still cannot get any computer to recognise my device. I've tried a few other cables, too.
Edit: I have fixed this issue. It was a case of loose USB contact between my device and the cable. Tweaking some of the gold contacts on the cable helped, and my PC now shows my One M8 connected. Fastboot is connected as Fastboot USB, too. I'm going to perform a Titanium Backup, and then restore the Lollipop RUU and proceed with updating to Marshmallow. Hope it works out fine this time.
Thanks for the help, everyone.

New updates - I found an RUU for 4.19.707.2, and attempted to apply it, only to receive an error 159, stating that the RUU image size was different compared to the device image size. What's wrong?

SRSR333 said:
New updates - I found an RUU for 4.19.707.2, and attempted to apply it, only to receive an error 159, stating that the RUU image size was different compared to the device image size. What's wrong?
Click to expand...
Click to collapse
You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1
SRSR333 said:
Edit: I restored my Kit Kat nandroid backup that I made. My phone has been saved, but now I have to do this gruelling update process all over again. Isn't there a faster way?
Click to expand...
Click to collapse
Save all the hassle to restore a KitKat or Lollipop RUU/backups ... just restore non-rooted backup 6.14.707.1 - check my thread linked in my signature, you should find it on post #3

ckpv5 said:
You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1
Click to expand...
Click to collapse
Of course, but I saw in several places that if the M8 is S-OFF then this rule doesn't apply...

SRSR333 said:
Of course, but I saw in several places that if the M8 is S-OFF then this rule doesn't apply...
Click to expand...
Click to collapse
So .. your device is S-Off ?
What you read is correct for lollipop and below.
When it comes to RUU exe when you have Marshmallow firmware on your device or running a Marshmallow RUU exe, it works differently ..
That's the reason why I wrote "You can't use lower version RUU 4.19.707.2 when your current firmware is 6.14.707.1" as I know you tried RUU exe
Good luck...

Please help me my mobile not open after update
SRSR333 said:
Hey guys,
I have a few questions regarding the Marshmallow update to the One (M8). First of all, I own an international M8 on stock, rooted, with TWRP KitKat firmware version 3.32.707.9. I have not updated either my Sense Home (still have Sense 6 mainly), and most of my apps are the Sense 6 versions, which I prefer to the colourful Sense 7 versions. So, my questions:
I still haven't received the Marshmallow update at all. Do I need to update to Lollipop or will I receive a Marshmallow notification even while on KitKat?
If the above is not possible, then can I install the OTA onto my phone after downloading the zip file from a mirror directly?
Can I backup all the Sense 6 apps that I want, like HTC Clock, HTC Blinkfeed and such with Titanium Backup, update to Marshmallow and restore them, and expect them all to work properly?
Thanks.
Click to expand...
Click to collapse
Please help me
After update and mobile reboot and install update when it comelete it go to recovery and not open like the photo in attachment

Question A52S 5G (SM-A528B) Magisk Root

Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.

Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Click to expand...
Click to collapse
I also bought an A52 5G thinking I could unlock the bootloader and root but found no way to do it. A solution may come, but I just returned the phone for a OnePlus 9 5G (not pro) and I am pretty happy. Had it rooted in a couple hours. It was roughly the same price. I just don't like the "wakeup/on-off restart" button placement, coming from an LG V30 which had it centered on the back of the phone. If not for the 5G, The V30 is still a decent daily driver. Let me know if you find a way.

hammeru said:
It was roughly the same price.
Click to expand...
Click to collapse
don't talk nonsense. the 9er costs considerably more.

Hot-Proton said:
don't talk nonsense. the 9er costs considerably more.
Click to expand...
Click to collapse
I suppose your interpretation of price is correct, but it is still reasonable for a non-flagship phone IMHO.

Also buy Samsung A52s and not can rooting, always not starting - very bad :/

hammeru said:
I also bought an A52 5G thinking I could unlock the bootloader and root but found no way to do it. A solution may come, but I just returned the phone for a OnePlus 9 5G (not pro) and I am pretty happy. Had it rooted in a couple hours. It was roughly the same price. I just don't like the "wakeup/on-off restart" button placement, coming from an LG V30 which had it centered on the back of the phone. If not for the 5G, The V30 is still a decent daily driver. Let me know if you find a way.
Click to expand...
Click to collapse
That's strange, because looking around this forum, there's no issue with unlocking bootloader for A52, even the A52s.
With A52s though, there seems to be issue with rooting, according to OP. As a result, I'd suggest not unlocking bootloader unless someone who's already unlocked confirms that rooting works. There's no point in unlocking bootloader until then.

All I can say is my experience was different when trying to unlock the bootloader. I found it very frustrating and Samsung was no help.

I'm planning to buy this phone, but I heard somewhere that oem unlock option is missing from developer options but I dunno which model
Maybe I'll skip samsung phone

specialex said:
I'm planning to buy this phone, but I heard somewhere that oem unlock option is missing from developer options but I dunno which model
Maybe I'll skip samsung phone
Click to expand...
Click to collapse
The option is available with A528B. Maybe only US variants don't have it.

Yes, but still not possible ( unlock bootloader and OEM - OK ) susceful rooted :/

SAME HERE NO LUCK

The OEM unlock option didn't show up for me till I both updated *and* had a password.
I'm also having the bootloop issue after patching boot.img or the AP tarball with magisk.

I tried many times and failed

Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.
Click to expand...
Click to collapse
Tôi cũng đã thử mọi cách nhưng không thành công. hy vọng ai đó có thể giúp đỡ, ít nhất twrp cho A528b
Translated by GT: I also tried everything but no success. hope someone can help, at least twrp for A528b

If i would own this device i would look at the steps to get the device rooted on a exiting root method of another phone model of the same manufacturer with nearly the same processor.
That could do the trick especially if there needs to be flashed another zip file to get root like the case is for many android versions on different phones...

I found some sites that claim to have working root-methods, but can't verify they are working.
Site1 Site2 Site3
Can anyone please test this out? I want to buy this phone as it is a really good bang for the buck, but I have to know before if my rooted firewall AND my banking-app will work on that

revnu said:
I found some sites that claim to have working root-methods, but can't verify they are working.
Site1 Site2 Site3
Can anyone please test this out? I want to buy this phone as it is a really good bang for the buck, but I have to know before if my rooted firewall AND my banking-app will work on that
Click to expand...
Click to collapse
These methods do not work. See the description on those websites and compare them with the first post in this thread.

Jumpkid said:
These methods do not work. See the description on those websites and compare them with the first post in this thread.
Click to expand...
Click to collapse
Jap, I also thought that. So I think then we simply have to wait untill some ambitious people find working root methods

I have the same problem, is it resolved
{
"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"
}
Jumpkid said:
Having a long history of root/mods/custom roms, I recently came across the A52S 5G (Q3 2021 version).
An attractive phone, even for those choosing flagships as their daily.
The problem with this phone is bloat (lots of it) and lack of CSC-modability (or basically, freedom to fully admin your phone). And since adb-debloating gives you limited options, it's very tempting to unlock BL and root the phone.
I'm aware that the phone is new, so shared experiences are available only very limited. Therefore this thread.
I've looked trough rooting experiences with the A52 and the S21-series. And I've tried to root the phone the Magisk way. This basically means:
1) Unlock BL trough developer mode, reboot and long press up in DL-mode
2) Reboot, complete setup wizard, connect to the internet (Samsung's safety check)
3) DL Official Firmware (ie. via Frija) and extract the file
4) Transfer the AP .tar file, OR the boot.img, and patch the file with Magisk's canary release
5) Transfer the patched file, and flash the file trough ODIN (AP), without auto reboot checked
I've repeated the steps above a couple of times, but it doesn't matter what I do, something trips off the 'This Phone is not running Samsung's official software' at boot -- and the phone gets stuck in boot loop. The only option then I believe, is to flash the official software back, and start all over again (all data is wiped in the process).
If anyone had any luck rooting this phone, or sees a flaw in my method, please add to this thread. It may be of help to anyone of the community trying to root this phone. Thanks!
Edit: Flashed Indonesian CSC for the features I need the most. Debloated extensively trough adb. Will probably wait for a TWRP release for this model -- may switch if no rooting is available over a long period.
Click to expand...
Click to collapse
I have the same problem, is it resolved
Please help me root my phone A52S 5G

The question is, why do you want to root this phone? You will lose your warranty, 2-3 years automatic updates or have to install these manually.