Related
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.
So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?
Sorry forgot to add current firmware pic
s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?
Hi,
A couple of years ago I bought my HTC One m8 via eBay. It did say it was a VZW one, but me not being a US citizen nor living in the US, it didn't set off any alarm for me...
And so it took me by surprise that I am unable to tether my internet connection via bluetooth nor wifi, and that VZW went the extra mile to disable the FM receiver. Further more, living outside the US, I'm still running the Kitkat version, since no OTA update can reach me
And now to my actual question - I have bought a sunshine licence and got it running but I am not sure what are the next steps. My goal is to get the regular stock ROM (perhaps still rooted), so ill be able to enjoy FM, tethering and regular updates.
I'll much appreciate your help, and though I'm sure this kind of question has already been asked, I was unable to find it.
Thanks,
Saar.
Guttmann said:
Hi,
A couple of years ago I bought my HTC One m8 via eBay. It did say it was a VZW one, but me not being a US citizen nor living in the US, it didn't set off any alarm for me...
And so it took me by surprise that I am unable to tether my internet connection via bluetooth nor wifi, and that VZW went the extra mile to disable the FM receiver. Further more, living outside the US, I'm still running the Kitkat version, since no OTA update can reach me
And now to my actual question - I have bought a sunshine licence and got it running but I am not sure what are the next steps. My goal is to get the regular stock ROM (perhaps still rooted), so ill be able to enjoy FM, tethering and regular updates.
I'll much appreciate your help, and though I'm sure this kind of question has already been asked, I was unable to find it.
Thanks,
Saar.
Click to expand...
Click to collapse
If you are on KitKat you can get S-OFF using sunshine.
If you already bought a license then you may already be S-OFF. Check in bootloader. Power down device. Then turn back on using volume down + power to check in bootloader.
If you are S-OFF you can update to latest Android 6.0 Marshmallow, and flash a stock rooted ROM to enable tethering.
You could flash the RUU or flash firmware + ROM.
andybones said:
If you are on KitKat you can get S-OFF using sunshine.
If you already bought a license then you may already be S-OFF. Check in bootloader. Power down device. Then turn back on using volume down + power to check in bootloader.
If you are S-OFF you can update to latest Android 6.0 Marshmallow, and flash a stock rooted ROM to enable tethering.
You could flash the RUU or flash firmware + ROM.
Click to expand...
Click to collapse
Thank you!
I'm also unable to connect to the LTE network, so I'm on 3G. What should I be looking for, if I want an RUU (I'm a total noob around the whole flashing and ROMing territory... seems to me the RUU is the "safer" bet), FM, tethring, LTE, and preferably staying with Sense? I read a bit about the GPe port, but I guess it wouldn't have Sense.
I'm sorry if that's the wrong place to ask.
Thanks!
Saar.
Guttmann said:
Thank you!
I'm also unable to connect to the LTE network, so I'm on 3G. What should I be looking for, if I want an RUU (I'm a total noob around the whole flashing and ROMing territory... seems to me the RUU is the "safer" bet), FM, tethring, LTE, and preferably staying with Sense? I read a bit about the GPe port, but I guess it wouldn't have Sense.
I'm sorry if that's the wrong place to ask.
Thanks!
Saar.
Click to expand...
Click to collapse
I'm not sure about LTE, as you're not on Verizon network.
but GPe ROM is great now that we have the Marshmallow firmware.
FM Radio was removed from Verizon devices, but great Devs have gotten it working again I do believe.
Anyway, IF you are S-OFF, which you haven't confirmed yet, but I am going to assume you are, as if you aren't you shouldn't have any issues getting to S-OFF (and for $25 it's very much worth it).
Ok, once you are confirmed S-OFF, you want to flash the new MM firmware.
This can be found here.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
flash this one:
"6.21.605.3_FULL_firmware.zip"
You will need an SD-Card or know how to use adb - guide will be in thread I linked above.
After you are on the latest firmware, you want to fastboot flash the latest TWRP custom recovery found here:
http://forum.xda-developers.com/showthread.php?t=2717928
Then you can flash a stock MM ROM, a GPe ROM, or a custom MM ROM.
andybones said:
I'm not sure about LTE, as you're not on Verizon network.
but GPe ROM is great now that we have the Marshmallow firmware.
FM Radio was removed from Verizon devices, but great Devs have gotten it working again I do believe.
Anyway, IF you are S-OFF, which you haven't confirmed yet, but I am going to assume you are, as if you aren't you shouldn't have any issues getting to S-OFF (and for $25 it's very much worth it).
Ok, once you are confirmed S-OFF, you want to flash the new MM firmware.
This can be found here.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
flash this one:
"6.21.605.3_FULL_firmware.zip"
You will need an SD-Card or know how to use adb - guide will be in thread I linked above.
After you are on the latest firmware, you want to fastboot flash the latest TWRP custom recovery found here:
http://forum.xda-developers.com/showthread.php?t=2717928
Then you can flash a stock MM ROM, a GPe ROM, or a custom MM ROM.
Click to expand...
Click to collapse
Thanks!
Oh, right, I forgot to mention I've achieved S-Off. Shouldn't I use the m8vzw_AllInOne_Firmware first? I'm real scared getting my phone bricked..
Guttmann said:
Thanks!
Oh, right, I forgot to mention I've achieved S-Off. Shouldn't I use the m8vzw_AllInOne_Firmware first? I'm real scared getting my phone bricked..
Click to expand...
Click to collapse
I wouldn't steer you the wrong way.
If you read closely that's for Lollipop, we're want Marshmallow
andybones said:
I wouldn't steer you the wrong way.
If you read closely that's for Lollipop, we're want Marshmallow
Click to expand...
Click to collapse
after fastboot of firmware the phone is stuck on the htc powered by android screen... IT wont shut down nor power on. just stuck on it
Guttmann said:
after fastboot of firmware the phone is stuck on the htc powered by android screen... IT wont shut down nor power on. just stuck on it
Click to expand...
Click to collapse
This is because you only flashed the Marshmallow firmware, but are not on a Marshmallow ROM.
You want to hold volume up + volume down + power for about 10-15 seconds, the phone will reboot, let go of all except volume down, this will get you back into bootloader.
Now you will need to flash the TWRP custom recovery I linked to you above.
Then in TWRP recovery you will flash the Marshmallow ROM of your choice.
There are a number of great ROMs out that support Marshmallow, and I'll be kind enough to link you all of them.
Lyapota Jazz #10 Marshmallow - SENSE ROM
- Lyapota is one of the nicest and smartest Developers.
-- his MODs are found in many many ROMs, including mine, he used to put out MOD Packs, but now he releases ROMs, and they are top notch, I highly suggest one of these
Lyapota Blues #021 Marshmallow - Google Play Edition ROM
- again one of the best ROMs you can flash, this one is Google Play Edition, the one above this is Sense.
Google Play Edition Marshmallow 6.0 MRA58K.H10
- stock based ROM ported from the HTC One M8 Google Play Edition Phone with Verizon support.
Pure Stock Verizon Marshmallow ROM
- stock pure ROM made from the latest Verizon Marshmallow OTA
-- the best choice if you want something stock
ViperOne Marshmallow
- one of the most customization Sense ROMs ever made.
-- also is very stable, but this has basically every tweak you can dream or think of, worth messing around with.
andybones said:
This is because you only flashed the Marshmallow firmware, but are not on a Marshmallow ROM.
You want to hold volume up + volume down + power for about 10-15 seconds, the phone will reboot, let go of all except volume down, this will get you back into bootloader.
Now you will need to flash the TWRP custom recovery I linked to you above.
Then in TWRP recovery you will flash the Marshmallow ROM of your choice.
There are a number of great ROMs out that support Marshmallow, and I'll be kind enough to link you all of them.
Lyapota Jazz #10 Marshmallow - SENSE ROM
- Lyapota is one of the nicest and smartest Developers.
-- his MODs are found in many many ROMs, including mine, he used to put out MOD Packs, but now he releases ROMs, and they are top notch, I highly suggest one of these
Lyapota Blues #021 Marshmallow - Google Play Edition ROM
- again one of the best ROMs you can flash, this one is Google Play Edition, the one above this is Sense.
Google Play Edition Marshmallow 6.0 MRA58K.H10
- stock based ROM ported from the HTC One M8 Google Play Edition Phone with Verizon support.
Pure Stock Verizon Marshmallow ROM
- stock pure ROM made from the latest Verizon Marshmallow OTA
-- the best choice if you want something stock
ViperOne Marshmallow
- one of the most customization Sense ROMs ever made.
-- also is very stable, but this has basically every tweak you can dream or think of, worth messing around with.
Click to expand...
Click to collapse
Iv'e flashed TWRP but am unable to load into it... I keep on ending either in the regulare recovery mode or the white screen. Any thoughts?
Guttmann said:
Iv'e flashed TWRP but am unable to load into it... I keep on ending either in the regulare recovery mode or the white screen. Any thoughts?
Click to expand...
Click to collapse
doesn't sound as if it flashed correctly.
can i see the output of the cmd?
andybones said:
doesn't sound as if it flashed correctly.
can i see the output of the cmd?
Click to expand...
Click to collapse
some progress... Ive managed to load TWRP. but how do I flash the rom so i could see it in twrp?
Guttmann said:
some progress... Ive managed to load TWRP. but how do I flash the rom so i could see it in twrp?
Click to expand...
Click to collapse
UPDATE: got the zip file on the phone, installed the ROM. - and now it goes straight into hboot everytime i try to boot the phone
Guttmann said:
UPDATE: got the zip file on the phone, installed the ROM. - and now it goes straight into hboot everytime i try to boot the phone
Click to expand...
Click to collapse
I need more info, how are you flashing the ROM. is it saying successful after flashing, which ROM are you flashing? are you wiping before?
I just put the rom onto a sdcard, find the rom on sdcard in TWRP, wipe and flash.
as long as you are on the correct MM firmware, and one of the linked MM ROMs there won't be any issue.
I've tested each ROM I posted for you to make sure to run into as little issues as possible.
that or you can always flash the RUU
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
andybones said:
I need more info, how are you flashing the ROM. is it saying successful after flashing, which ROM are you flashing? are you wiping before?
I just put the rom onto a sdcard, find the rom on sdcard in TWRP, wipe and flash.
as long as you are on the correct MM firmware, and one of the linked MM ROMs there won't be any issue.
I've tested each ROM I posted for you to make sure to run into as little issues as possible.
that or you can always flash the RUU
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Click to expand...
Click to collapse
I really appreciate your help!
Thats the ROM: http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Does it matter if I put it on the internal or external storage?
It says everything was ok as far as the installation is concerned, but says "Failed to mount '/carrier' (Invalid argument" and "Failed to mount '/reserver' (Invalid argument"
Guttmann said:
I really appreciate your help!
Thats the ROM: http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Does it matter if I put it on the internal or external storage?
It says everything was ok as far as the installation is concerned, but says "Failed to mount '/carrier' (Invalid argument" and "Failed to mount '/reserver' (Invalid argument"
Click to expand...
Click to collapse
the failed to mount carrier could be the issue.
hmm.
try the lyapota blues ROM
andybones said:
the failed to mount carrier could be the issue.
hmm.
try the lyapota blues ROM
Click to expand...
Click to collapse
i read online this error has something to do with the TWRP version, so i downgraded and it went away...
any how, I tried another ROM first, (dont remember which one now) and it seemed to work. It booted, asked me a couple of questions, and then went crazy, so I wiped it.
But now i cant seem to be able to copy the lypota zip to the SD card. Windows says it seems as if the device is unplugged or unresponsive... I made sure to wipe beforehand, but no luck.
Guttmann said:
i read online this error has something to do with the TWRP version, so i downgraded and it went away...
any how, I tried another ROM first, (dont remember which one now) and it seemed to work. It booted, asked me a couple of questions, and then went crazy, so I wiped it.
But now i cant seem to be able to copy the lypota zip to the SD card. Windows says it seems as if the device is unplugged or unresponsive... I made sure to wipe beforehand, but no luck.
Click to expand...
Click to collapse
You want the latest TWRP3.0.0
If you can't figure out how to flash ROM, ID suggest running the RUU so you at least have a working device.
:good:
OK.
So I switched back to the latest TWRP, and was able to upload lyapota's ROM and flash - and finally it worked!!!!! ? I'm not sure what the problem was with previous ROMs, but I'm happy it finally worked out.
Walking to University, listening to live FM radio and being able to share my mobile data with my tablet... Finally I got what I paid for.
Thank you!
hi, i saw what you dis for him, you are most kind, i was wondring if you could elp me too, i also bought a phone from ebay and also live outside the us, nd i cant seem to get te from my carrier wich is att mexico, ive flashed several roms after getting marshmallow from htc's software from my pc, today fastbooted baseband and nothing Please help, i can post any info of the phone that you like
thanks in advance
skp
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
It seems most phones shipping with android 10 lose touch response in TWRP. Yes you don't have TWRP but I think you're seeing the same behavior.
Plug in a USB c mouse and navigate with that should help you restore normal use.
try this thread https://forum.xda-developers.com/t/stock-rom-for-motorola-g-stylus-retail.4104451/
tatsunn said:
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
Click to expand...
Click to collapse
Where did you get the boot.img? The non functional touch screen usually means the ROM version the boot.img came from doesn't match the version of the ROM running on the phone.
EDIT - Whoops, didn't notice the age of the post. Didn't mean to bring this back from the dead.
So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.
Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.
You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img
Yup, it's working now. Thanks all.
I have successfully rooted mine and having adaway installed
Can you install stock android 10 or even android 11 now?
ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?
zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method
TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.
minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!
I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides
Make sure you flash boot.img in fastbootd
I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.
I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?