Hi all,
perhaps I am just getting to old - but I cannot seem to find the simple guide on how to root stock, international ROM. I have 2.3.2.7
Please note I am NOT asking how to flash the modded rom, but instead - how to root the newer Amazfit stock rom.
Many thanks in advance!!
Unlock bootloader, go to fastboot mode, boot using a modified boot.img with temporary (adb) root.
If you find a way to root Android 5.1 on a MIPS device, please tell me...
Hi thanks for the effort - I missed to mention I already tried that before posting.
Issue is that after flashing boot.img, watch loses adb connection and I cant proceed.
Reboot helps but temp boot image is no longer there, and then process gets back fo start.
Any help?
phnikola said:
Hi thanks for the effort - I missed to mention I already tried that before posting.
Issue is that after flashing boot.img, watch loses adb connection and I cant proceed.
Reboot helps but temp boot image is no longer there, and then process gets back fo start.
Any help?
Click to expand...
Click to collapse
Don't flash the modified boot.img, use it to get temporary root access in adb:
Code:
fastboot boot boot_with_root_adb.img
Keep the original boot.img that came with the ROM/firmware intact, so if you run into any problem a simple reboot should fix it.
Once you have a temp adb root privilege by doing like lfom mentioned, then follow this https://forum.xda-developers.com/smartwatch/amazfit/local-root-amazfit-watch-supersu-2-79-t3711327
anox said:
Once you have a temp adb root privilege by doing like lfom mentioned, then follow this https://forum.xda-developers.com/smartwatch/amazfit/local-root-amazfit-watch-supersu-2-79-t3711327
Click to expand...
Click to collapse
This only works with Pacefied IIRIC (or any other custom ROM that adds support to init.d), isn't it?
lfom said:
This only works with Pacefied IIRIC (or any other custom ROM that adds support to init.d), isn't it?
Click to expand...
Click to collapse
Works fine on my English stock rom.
There are some small mistakes in one of the sh scripts. I forgot exactly what I modified, but I can attach my modified script when I get home tonight.
Edit: Modified script attached
Just replace the original script with the attached one. All credits go to the original poster. I just modified his script a bit to root my rom.
My pace is currently on rooted stock 1.3.8a rom. As long as you can get root privileges from the temp kernel, I don't see why it wouldn't work on any other rom. It should also work on Stratos. I don't know for sure as I don't have one to try.
Thanks for all the help.
Happy again. Using Assayyed ROM kitchen and Saratoga's official 2.3.2.7 ROM thread I was able to mod the official rom and flash it back to device.
Kudos to all
anox said:
Works fine on my English stock rom.
There are some small mistakes in one of the sh scripts. I forgot exactly what I modified, but I can attach my modified script when I get home tonight.
Edit: Modified script attached
Just replace the original script with the attached one. All credits go to the original poster. I just modified his script a bit to root my rom.
My pace is currently on rooted stock 1.3.8a rom. As long as you can get root privileges from the temp kernel, I don't see why it wouldn't work on any other rom. It should also work on Stratos. I don't know for sure as I don't have one to try.
Click to expand...
Click to collapse
thank you very much, finally I can have a stock rooted ROM that supports browsers (the Pacefield and stockfield do not work for me, I guess it is something related with the webview service)
carloscolhao said:
thank you very much, finally I can have a stock rooted ROM that supports browsers (the Pacefield and stockfield do not work for me, I guess it is something related with the webview service)
Click to expand...
Click to collapse
I still cant figure out how to root my device. I am running 2.8.1.0 stock English ROM by Saratoga79 in my PACE.
Can you give me a little guidance. Things are going over my head...
iTalisman said:
I still cant figure out how to root my device. I am running 2.8.1.0 stock English ROM by Saratoga79 in my PACE.
Can you give me a little guidance. Things are going over my head...
Click to expand...
Click to collapse
Get temporary root with a modified boot.img that works with your watch, then run the shell script Anox attached in his post, that's what the previous posts say.
iTalisman said:
I still cant figure out how to root my device. I am running 2.8.1.0 stock English ROM by Saratoga79 in my PACE.
Can you give me a little guidance. Things are going over my head...
Click to expand...
Click to collapse
As far as I know there are two kinds of root.
1- if you want to install something through adb usb that requires root you can make a temporary root, see for instance post 2 from this thread https://forum.xda-developers.com/smartwatch/amazfit/rom-amazerom-pace-v1-0-20180618-t3805928
2- if you need root to use some app (e.g. to modify the DPI in the watch using the app "screen shift" version 1.0.0) you can flash the superSu using the script provided by anox in post 7 of this thread, for that you may need to make the temporary root first
you can then verify if you are rooted using for instance some of those apps in playstore.
by the way, browsers now work with the last version of Pacefield, so I prefer pacefield (that is already rooted and permanent) than the stock rom
carloscolhao said:
As far as I know there are two kinds of root.
1- if you want to install something through adb usb that requires root you can make a temporary root, see for instance post 2 from this thread https://forum.xda-developers.com/smartwatch/amazfit/rom-amazerom-pace-v1-0-20180618-t3805928
2- if you need root to use some app (e.g. to modify the DPI in the watch using the app "screen shift" version 1.0.0) you can flash the superSu using the script provided by anox in post 7 of this thread, for that you may need to make the temporary root first
you can then verify if you are rooted using for instance some of those apps in playstore.
by the way, browsers now work with the last version of Pacefield, so I prefer pacefield (that is already rooted and permanent) than the stock rom
Click to expand...
Click to collapse
hi there, currently im having a Amazfit Stratos 2 on International stock rom 2.3.8.0, unlocked bootloader with TWRP recovery and I still having hard time to figure out how to perma-root my watch.
it seems that i can't flash the script provided by anox in post 7.
illkid69 said:
hi there, currently im having a Amazfit Stratos 2 on International stock rom 2.3.8.0, unlocked bootloader with TWRP recovery and I still having hard time to figure out how to perma-root my watch.
it seems that i can't flash the script provided by anox in post 7.
Click to expand...
Click to collapse
I think you need first do a temporary root in order to run the anox script. Perhaps, in your case you can flash the supersu zip through twrp.
If anything works for you I don't know how to help. Sorry.
carloscolhao said:
I think you need first do a temporary root in order to run the anox script. Perhaps, in your case you can flash the supersu zip through twrp.
If anything works for you I don't know how to help. Sorry.
Click to expand...
Click to collapse
Which version of SuperSU is recommended to use is TWRP?
ronaldheld said:
Which version of SuperSU is recommended to use is TWRP?
Click to expand...
Click to collapse
I don't know, I never flashed the TWRP in my amzfit pace, sorry :/
carloscolhao said:
I don't know, I never flashed the TWRP in my amzfit pace, sorry :/
Click to expand...
Click to collapse
No problem.
carloscolhao said:
I think you need first do a temporary root in order to run the anox script. Perhaps, in your case you can flash the supersu zip through twrp.
If anything works for you I don't know how to help. Sorry.
Click to expand...
Click to collapse
thanks mate, i tried but no avail.
the watch was stucked in bootloop and i have to reflash the firmware again.
hmm did you install any custom ROM to your watch?
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
ronaldheld said:
Which version of SuperSU is recommended to use is TWRP?
Click to expand...
Click to collapse
previously i flashed TWRP that bundled with this tool: https://forum.xda-developers.com/smartwatch/amazfit/tool-tool-one-driversunlocktwrpfactory-t3874802 but somehow i failed to install SuperSu from this topic: https://forum.xda-developers.com/smartwatch/amazfit/local-root-amazfit-watch-supersu-2-79-t3711327
if you have successfully perma-root your watch with stock ROM, please do guide me through.
thank you
illkid69 said:
thanks mate, i tried but no avail.
the watch was stucked in bootloop and i have to reflash the firmware again.
hmm did you install any custom ROM to your watch?
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
at the time I flashed the superSU I had a stock ROM installed (found here in the forum, I don't remember which one). Then I made a temporary root (the img was found here in the forum too). Finally I use this temporary root to flash the superSU zip, I had to use the script provided by Anox here in this thread, instead of the original one.
If you cannot flash superSU, you may want to flash a custom ROM with perm root, I have using this in the last months: https://forum.xda-developers.com/smartwatch/amazfit/paceficator-project-wos-2-6-0-12-rom-v0-t3794922
you can also find other custom roms in the forum, also for stratos.
sorry I cannot help you more
Click to expand...
Click to collapse
Hi all, is it possibile to do a temporary root on Stratos with pace rom, bootloader on, sn null... I have Access to memory od this watch via windows? Thx in advance for any help.
Related
Does anyone know any root procedure for the Alcatel OT-997D?
root
The same goes for me, i like to know how to root my alcatel 997D, i saw a topic of the 993, one reply of a guy that had he's 997D rooted the same way, i tried it, but it doesnt work with me ...
anyone?
if you found a way, pls make a post with the ecaxt steps you did, so we can do the same?
Root
robin-sips said:
The same goes for me, i like to know how to root my alcatel 997D, i saw a topic of the 993, one reply of a guy that had he's 997D rooted the same way, i tried it, but it doesnt work with me ...
anyone?
if you found a way, pls make a post with the ecaxt steps you did, so we can do the same?
Click to expand...
Click to collapse
this method and the 993D has stopped working after a kernel upgrade, try this this way, if the last time out, then and now should.
Sorry for translate.google
1. download the utility View attachment unlockbootloader.rar
2. Unzip to your C drive
3. Run and choose unlockbootloader.exe ROOT Your Background
4. Wait for all operations. Console appears that self-close after the completion of the process of obtaining mouth
5. Download and install SuperSU
72angel86 said:
this method and the 993D has stopped working after a kernel upgrade, try this this way, if the last time out, then and now should.
Sorry for translate.google
1. download the utility View attachment 1470947
2. Unzip to your C drive
3. Run and choose unlockbootloader.exe ROOT Your Background
4. Wait for all operations. Console appears that self-close after the completion of the process of obtaining mouth
5. Download and install SuperSU
Click to expand...
Click to collapse
I downloaded this file but Avira detects it as a trojan. Is it safe?
root
this does not work for me, anyone else?
regards,
Robin
unlockbootloader.rar is not working
After the update IT does not work any more so i dont have root Any more
Sent from my ALCATEL ONE TOUCH 997D using Tapatalk
Klaasv00k said:
After the update IT does not work any more so i dont have root Any more
Sent from my ALCATEL ONE TOUCH 997D using Tapatalk
Click to expand...
Click to collapse
ok this is my problem to, ive updated the phone right of the store so no way to get root on my phone, thats to bad, any way to go back to stock?
Klaasv00k said:
After the update IT does not work any more so i dont have root Any more
Sent from my ALCATEL ONE TOUCH 997D using Tapatalk
Click to expand...
Click to collapse
As I can see from your other posts you rooted the 997D with the Root_with_Restore_by_Bin4ry_v15 solution. After that you did the system firmware update and you don't have root anymore?
I also updated the firmware of my 997D through my phone settings/about phone/system updates/check for update and after that I first tried to root my phone with the Root_with_Restore_by_Bin4ry_v15 utility and it didn't work.
Is there any way to rollback our firmware?
sibigr said:
As I can see from your other posts you rooted the 997D with the Root_with_Restore_by_Bin4ry_v15 solution. After that you did the system firmware update and you don't have root anymore?
I also updated the firmware of my 997D through my phone settings/about phone/system updates/check for update and after that I first tried to root my phone with the Root_with_Restore_by_Bin4ry_v15 utility and it didn't work.
Is there any way to rollback our firmware?
Click to expand...
Click to collapse
i have the 997A and can root it with restore, but i update software and i cant root it any more
Nanobyte109 said:
unlockbootloader.rar is not working
Click to expand...
Click to collapse
Before running unlockbootloader try to disable antivirus, and run as administrator.
root
i'm pretty sure the update is preventing the root. Badluck for us then? i know a bit of android, but i'm no developer so i can't make a rootfix by my own
Anyone here has some knowledge to get our nice device rooted?
72angel86 said:
Before running unlockbootloader try to disable antivirus, and run as administrator.
Click to expand...
Click to collapse
The root is not working with that tool
SuperOneClick: Step #7 .. after that, freeze
same here, tried both superoneclick and the binary root, both don't work anymore.
Nice move from alcatel to fix root in an update, if i only knew this before i updated
Also tried Unlockroot 3.0 (which was updated recently) but it doesn't work
ok, found this out, when you shut down the phone, press volume up + power button, phone starts in android recovery mode 3e, any possible chance to get the phone rooted this way?
c'mon guy's i want this phone rooted, getting resolution problems with games (software buttons of ics hide some of the screen) can't start some gps apps because of this stupid software buttons)
anyone dare to try this: http://www.mediafire.com/view/?ldao6p9eyjuu1f9
I'm prepared to even pay for a working root, so if anyone has found a way, pls contact me at pm
Any news on this subject? I love the phone, but I miss the SetCPU profiles I used on my previous phone, and a battery meter with percentage...
Nothing yet, I have tried every available method soc,unlockroot,bin4ary etc and nothing works after the firmware update.
Is there anyone who hasn't done the firmware update and can root his phone? If yes please do a factory reset and take a backup of his ROM and upload.
I guess our best bet would be a port of CWM recovery. Maybe I'll backup the stock recovery and use the CWM recovery builder this evening if I have the time
jman0 said:
I guess our best bet would be a port of CWM recovery. Maybe I'll backup the stock recovery and use the CWM recovery builder this evening if I have the time
Click to expand...
Click to collapse
I'll reply to myself: no way, since you need to be rooted in order to dump the stock recovery. Maybe if someone could try to extract the OTA update so we could examine the files and look if the recovery.img is there...
---------- Post added at 03:45 PM ---------- Previous post was at 02:46 PM ----------
Ok, I have managed to get something.
Following this tutorial by Bruno Martins (a well known rom cooker who's also a user here) I've been able to dump recovery.img from my Alcatel OT-997D: http://bm-smartphone-reviews.blogspot.com.es/2012/04/creating-rom-dump-of-your-mt65x3-device.html
The tutotial was meant for MT6513 and MT6573 devices, but looks like it works on MT6577 too.
Then, I've used that file with the Clockworkmod recovery builder at http://builder.clockworkmod.com/ and now I have another recovery image, which is supposed to be a CWM port for our Alcatel.
I'm still unsure to flash that recovery, since I can't be sure it will work. Mediatek based phones do not have a fastboot mode, so it's impossible to just try a recovery image without actually flashing it. In fastboot mode, you can boot the phone into a custom recovery without actually flashing it, so you risk nothing if it doesn't work
In case someone daring enough wants to try my custom recovery, I've uploaded it to my Mediafire account: http://www.mediafire.com/?7232aj7jhg7l4e5
The idea is that, with a working CWM recovery, it should be possible to flash Chainfire's SuperSU root zip and easily root the phone.
Of course I warn you this could ruin the recovery image on your phone, so don't risk doing it if you're not sure.
Hey everyone. How are you guys able to keep root with 5.1? After the update, towelroot didn't stick. Nor could I reinstall it. Supersu doesn't have access either. What do you guys recommend?
You have to re root.
MikeyLee said:
You have to re root.
Click to expand...
Click to collapse
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
lowao said:
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
Click to expand...
Click to collapse
I think someone said you have to use ADB to flash the new TWRP that is compatible with L on our devices and then flash SuperSU.
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
lowao said:
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=61577016&postcount=303
It pretty easy to get root and TWRP. Here are the instructions, taken from another thread. (Do you guys even read this stuff?)
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
ScoobSTi said:
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
Click to expand...
Click to collapse
kimtyson said:
3. Install supersu-2.49.zip (even though I didn't lose root)
Click to expand...
Click to collapse
I was wondering the same thing. Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
At this time it would be best to not flash twrp. Instead fastboot boot twrp.img then install beta.SuperSU. 2.49
Sent from my MT2L03 using XDA Free mobile app
Lollipop will check the recovery partition and if it isn't stock it will put it back. In order for TWRP to stick you must boot TWRP after you install to allow it to patch the lollipop rom. TWRP must not be read only or else it cannot install supersu nor patch.
You guys got a lot to learn, but this is good, because now maybe some of you will pick up some experience and grow while here on XDA
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
In addition, do not use TWRP from the official twrp website until Dees_Troy gets around to updating his personal device tree since they do not accomondate for the changes seen in Lollipop. You have been officially warned. Unless you like sweats, tears, and heartaches.
lowao said:
Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
Click to expand...
Click to collapse
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
kimtyson said:
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
Click to expand...
Click to collapse
Thanks for the link!
deleted
Hi,
I currently have .570 fw installed with root, dualrecovery, xposed,... and wonder how to update to .575 w/o losing them. Can I just create flashable zip and that's it, or should I use the original guide that I used to update from LP to MM ([Stock][Z2(D6503) 6.0.1 Marshmallow][.570][Prerooted+ TWRP + Xposed][LB])?
//UPDATE: If you want to upgrade too, then grab files from this post and follow "nurps" guide here.
//UPDATE 2 (To avoid misunderstanding):
1. Make sure you download both files from here
2. In PRF Creator, insert your FTF as FTF File, dummy_flashable.zip as SuperSU and RecRootV4_combined.zip as Recovery.
3. Flash in recovery, if you want xposed, flash it separately afterwards.
4. Wipe cache
5. Reboot and that should be it.
//UPDATE 3
Also works for .291!
Well and without losing recovery would be important too. I'm ready with PRF Creator, but where do I get that TWRP Recovery zip from that works with MM?
nurps said:
Well and without losing recovery would be important too. I'm ready with PRF Creator, but where do I get that TWRP Recovery zip from that works with MM?
Click to expand...
Click to collapse
I'm not sure that we are having the same issue... I am already on MM, with recovery, etc. And want to update to newer version of MM.
btw if you just want dual recovery for MM you can visit the guide I mentioned earlier. You won't get .zip, since it's flashed by adb, but it works just the same.
Yes and when you reflash you have to reflash a rooted image and also recovery, or its gone.
nurps said:
Yes and when you reflash you have to reflash a rooted image and also recovery, or its gone.
Click to expand...
Click to collapse
I see.. Now I know what you mean... The thing is... I would assume that you would just flash it the same way you did from LP to MM.. flash ROM (w/o recovery), then flash SuperSU, boot Android and use the adb recovery flasher... But i don't really want to spend hours getting things to normal if that doesn't work. So I'm hoping someone braver already done this and will shed some light on how it really is...
Actually I dont remember how it went, but now that you mention it, than a prerooted firmware should be enough, maybe I'll try tomorrow. Of course a flashable backup would make it easier if anything happens.
nurps said:
Actually I dont remember how it went, but now that you mention it, than a prerooted firmware should be enough, maybe I'll try tomorrow.
Click to expand...
Click to collapse
Yeah... The problem was, after flashing MM and SuperSU, you had to pray that when Android boots up, you will have root permissions. If not, then it was game over, as you no longer had dual recovery...
Anyway... If you'll try, let me know how it went. I would really appreciate it!
Prerooted PRF creator file didn't work, root is lost.
nurps said:
Prerooted PRF creator file didn't work, root is lost.
Click to expand...
Click to collapse
That's what I was afraid of... Have you tried flashing SuperSU after flashing ROM? I know that you can insert it in the ROM, but just to be sure I find it "safer" to flash separately.
Because I got an error on supersu I actually did reflash it, but the same error message appeared. Should have stopped there and reflashed my backup....I didnt...
nurps said:
Because I got an error on supersu I actually did reflash it, but the same error message appeared.
Click to expand...
Click to collapse
And do you remember what error it was by any chance? We could probably find out why you lost root permissions that way...
No, sorry.
nurps said:
No, sorry.
Click to expand...
Click to collapse
That's a shame... Nevermind, what version of SuperSU were you flashing?
can u fetch me the ftf link ?
medalogii said:
can u fetch me the ftf link ?
Click to expand...
Click to collapse
Not sure what link you mean... Can you be more specific?
nurps said:
Because I got an error on supersu I actually did reflash it, but the same error message appeared. Should have stopped there and reflashed my backup....I didnt...
Click to expand...
Click to collapse
It's annoying, but at least you won't lose anything, as long as you have that backup... Now, you will have to downgrade to LP, root, flash back to MM, get recovery, flash your backup and done (if you want root back, that is of course, which I would strongly recommend for MM, as there are some things that would really bother me, if I didn't have root).
It's not the best solution, as it takes quite the time, but at least you have backup... could have been worse, take it that way...
Sorry my bad, I Was looking for the ftf now I'm downloading it with xperifirm,, now I'm looking for the recovery and supersu files to try,,
Sent from my D6503 using XDA-Developers mobile app
Thats a bit overcomplicated. I wasted some hours to find a rootable FTF though, 3rd I tried (D6503_17.1.A.2.69) worked, then it's just nuts dual recovery (with its own root exploit included) and restore.
For the other stuff I should have kept up, apparently for MM you include dummy_flashable for root not supersu and RecRootV4_combined is actually available as flashable recovery.
https://mega.nz/#!dtYQSYKa!V3cV1KUB2XPMn71wJHPPAwLrrVvB_hG7JPoun9WQ7AM
https://mega.nz/#!8woHjZyb!ksx9rXDSOnS_zUncNiYw0JbfUIt14YU61Fwc8Wrcjz8
nurps said:
Thats a bit overcomplicated. I wasted some hours to find a rootable FTF though, 3rd I tried (D6503_17.1.A.2.69) worked, then it's just nuts dual recovery (with its own root exploit included) and restore.
For the other stuff I should have kept up, apparently for MM you include dummy_flashable for root not supersu and RecRootV4_combined is actually available as flashable recovery.
https://mega.nz/#!dtYQSYKa!V3cV1KUB2XPMn71wJHPPAwLrrVvB_hG7JPoun9WQ7AM
https://mega.nz/#!8woHjZyb!ksx9rXDSOnS_zUncNiYw0JbfUIt14YU61Fwc8Wrcjz8
Click to expand...
Click to collapse
So, now you have .575 with root/recovery? And if, then you just create flashable.zip from your FTF and include dummy_flashable, flash in recovery and then flash RecRootV4_combined?
Nope not done yet. Trying now.
I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
If it is true, try SLTECAN twrp
echo124 said:
If it is true, try SLTECAN twrp
Click to expand...
Click to collapse
That didn't work out. "SECURE DOWNLOAD" is enabled in download mode and when I try to flash the recovery it tells me "check fail: recovery." I guess the bootloader is still locked. Is there any way I could still install a custom ROM? Root is working fine.
Try install flashify app then try twrp with it
echo124 said:
Try install flashify app then try twrp with it
Click to expand...
Click to collapse
There's no recovery image for it. The SLTECAN is only flashable via Odin which is not possible with the G850A.
Although I think we could get custom ROMs using Flash Fire if someone can port the ROMs to 850A. See: http://forum.xda-developers.com//at...tmas-heres-t3516196/post70011921#post70011921
You can create .img from tar or .tar from .img
Open tar.md5 with 7zip, extract .img to phone and use flashify, tell us if worked
Everyone thumbs up the post
vadosnake said:
I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
Click to expand...
Click to collapse
This works on Lollipop too ?
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
echo124 said:
You can create .img from tar or .tar from .img
Open tar.md5 with 7zip, extract .img to phone and use flashify, tell us if worked
Click to expand...
Click to collapse
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
vadosnake said:
I know this is not the best way to do so but I successfully got my G850A AT&T variant rooted using Kingroot 4.8.0.
Also when I boot up the phone, the lock icon turned into an open lock icon with the text "custom." Does that mean my bootloader has been unlocked?
I would like to install custom ROMs but had no luck installing twrp. Any ideas? I can try anything since this is a dead phone to me anyway.
Click to expand...
Click to collapse
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
KingOfTheNet said:
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
Click to expand...
Click to collapse
I have posted a tutorial for anyone interested in rooting
KingOfTheNet said:
Can you give us a tutorial guide on how to do it. Most of us (including me) have tried the version of king root that your using and it fails to root.
However, you have given us stuck with the AT&T variant of this phone a little bit of hope, as you confirmed it can be rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com//at...tmas-heres-t3516196/post70011921#post70011921 I used this guide, with Kingroot 4.8.0 instead of Kingroot 4.8.1 but I don't think it matters. The guide did say that you should keep trying until you get it to root. I got root successfully first try, twice, however.
PopTartKing said:
This works on Lollipop too
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
Click to expand...
Click to collapse
I got the same thing. I've heard AOSP ROMs are not going to work because of the locked bootloader. And TouchWiz ROMs will work if you port in an AT&T boot image making it "authorized."
PopTartKing said:
This works on Lollipop too
---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------
Flashing 850W TWRP soft-bricks the device with the message "System software not authorized by Verizon Wireless has been on the device ..." blah blah blah. I think a Safestrap recovery is better suited for this phone.
Click to expand...
Click to collapse
And there's an S5 version of Safestrap but it only works with a Kitkat kernel. It might work with the Alpha since they have basically the same specs. I might try it in the future.
Does the Kingroot version matter? I tried this with Kingroot 5.0.0 instead of 4.8.0, and while it seems to initially fail, it actually does work. Verified with Root Checker and Kingroot itself was able to give root access to apps. However, it appears to cause certain apps like Camera (Samsung's) and S Health to fail. Uninstalled Kingroot and everything was working again (albeit unrooted).
AlphaEcho35 said:
Does the Kingroot version matter? I tried this with Kingroot 5.0.0 instead of 4.8.0, and while it seems to initially fail, it actually does work. Verified with Root Checker and Kingroot itself was able to give root access to apps. However, it appears to cause certain apps like Camera (Samsung's) and S Health to fail. Uninstalled Kingroot and everything was working again (albeit unrooted).
Click to expand...
Click to collapse
You have to use 4.81 because later versions do not allow you to remove it and replace it with SuperSU.
OMG
IT ACTUALLY WORKED! I tried it twice and on the second time it worked. I am so happy! Now to find a custom rom for it!
I reverted to KitKat and rooted it so that I could use Xposed lol
PopTartKing said:
I reverted to KitKat and rooted it so that I could use Xposed lol
Click to expand...
Click to collapse
I want to revert to kitkat too
Can you help me?
ifgiovanni said:
I want to revert to kitkat too
Can you help me?
Click to expand...
Click to collapse
My AT&T Galaxy Alpha is running KitKat right now. I'll post the firmware as soon as I can (probably somewhere around 12:00PM Eastern) tomorrow up to mega.nz for all to use
Edit: Firmware now up: https://forum.xda-developers.com/galaxy-alpha/general/samsung-galaxy-alpha-att-sm-g850a-t3535938
Mine lost root access after a couple of days.
cjskevans said:
IT ACTUALLY WORKED! I tried it twice and on the second time it worked. I am so happy! Now to find a custom rom for it!
Click to expand...
Click to collapse
Hi,
i had TWRP before, but because of the lack of OTA compatibillity, i removed it.
So i am now trying to find an way to get MAGISK running without needing TWRP.
I read a lot about this particular way, but in my mind i am at an dead end...
so what i found:
patching boot.img and reflash it, sounds plausible, but how shall i get an dump, without root :/
using HWOTA, but i do not understand how it should work, it seems to use prepatched images, but i am wondering if they are compatible with the latest firmware (bla-l29 8.0.0.145(c432)), as they are using an modified kernel? (sry no expert in android images^^)
Thanks in advance
Daniel
Bumping in. I'm also on the same boat.
d0narr said:
Hi,
i had TWRP before, but because of the lack of OTA compatibillity, i removed it.
So i am now trying to find an way to get MAGISK running without needing TWRP.
I read a lot about this particular way, but in my mind i am at an dead end...
so what i found:
patching boot.img and reflash it, sounds plausible, but how shall i get an dump, without root :/
using HWOTA, but i do not understand how it should work, it seems to use prepatched images, but i am wondering if they are compatible with the latest firmware (bla-l29 8.0.0.145(c432)), as they are using an modified kernel? (sry no expert in android images^^)
Thanks in advance
Daniel
Click to expand...
Click to collapse
maxkento said:
Bumping in. I'm also on the same boat.
Click to expand...
Click to collapse
Use this guide to extract ramdisk.img https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
If update link brings you back to the search on TeamMT click the file list link and copy paste update.zips link to download.
Then transfer ramdisk.img to phone and patch in Magisk Manager, then transfer back and flash in fastboot mode.
Well looks like the root is going away from our devices
https://elandroidelibre.elespanol.com/2018/08/magisk-dejara-de-funcionar-en-moviles-huawei.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+elandroidelibre+%28El+androide+libre%29
mauricamo said:
Well looks like the root is going away from our devices
https://elandroidelibre.elespanol.com/2018/08/magisk-dejara-de-funcionar-en-moviles-huawei.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+elandroidelibre+%28El+androide+libre%29
Click to expand...
Click to collapse
Here is an english link covering the same issue which includes a XDA link to Magisk'thread on Huawei P9 update issue