Related
UPDATE: See post #5 for the fix. It's really simple!
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
It should work. Once latest version of casual is done try upgrading to latest version of whichever recovery you are gonna use. All the recoveries in casual are out of date and may just need to reflash recovery. Sounds like gonna use AOSP base so might as well stick with CWM as that is what you are going to end up with and what the AOSP devs support. While on TW can try upgrading it also as it the dev preferred recovery on TW. Shouldn't be the Mac if everything is actually unlocked, rooted and is flashing a recovery.
prdog1 said:
While on TW can try upgrading it also as it the dev preferred recovery on TW.
Click to expand...
Click to collapse
Can you please clarify this particular thought for me? I understood everything else.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
You must have a newer GS3, the newer devices (made within the past few months) have a higher revision internal card reader that breaks some recoveries. (I know because I flashed a sprint gs3 that had the same exact issue).
The fix for this is to have a recovery built with the fix in it, which is upstream in the cm-10.2 kernel, but not in any official recoveries yet.
Let me see if I can find the exact commit for you... I know invisiblek fixed it
EDIT: heres the sprint thread of info (DO NOT FLASH THE FILES THO THEY WILL MESS UP THE VZW GS3)
http://forum.xda-developers.com/showthread.php?t=2391616&page=31
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
jmsclbwmn said:
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
Click to expand...
Click to collapse
Oh man! Thanks for posting how you got it to work. I've been trying to figure out what to do for almost 2 days.
I would of probably still be googling away if I hadn't found this. Thanks!
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?
Hi I just got this tablet GT-P5113. It has been a long time since i used odin or did anything with samsung devices. In fact I havent really had to do any modding in years because I switched to nexus/pixel and those just work snappy and clean out of the box. But samsung has far superior hardware so I want to breath new life into this. It is running 4.2.2 now. I dont need to put android 11 on this thing but something like 6 or 7 would be good.
I downloaded odin i see it has changed a bit. so to put twrp on this what part of odin do i use? BL, AP,CP, or CSC?
Most of the stuff on these fourms are outdated and the links dont work. once I get twrp on this I should be food to go and figure out the rest.
I haven't flashed more than 3 devices, but for TWRP it has always been AP in those cases.
If you flash a complete stock ROM it's much more than Recovery, so in those cases you flash separate files like bootloader (BL) etc...
Decide which ROM you want to try and read what Dev recommends in terms of Odin version and TWRP version. But a newer version than recommended should be fine (Odin).
I use 3.09 for my old P3100 but also 3.14 worked for me.
I also recommend getting the same stock ROM you already have from Sammobile.com + make a backup before modding.
For Root I have no recommendation. If Dev recommends Magisk for the ROM, try it and see.
The ROMs I tried was rooted with SuperSU 2.82 even if it's outdated nowadays. Our devices are so old so SU is fine if you ask me.
And most of the time it's SU in the ROM thread by the Dev anyway, so choose ROM and the thread for that and go from there
Android go apps
So I have the latest version of twrp on this and android is running really good and stable. The issue is it has no ram. Just basic with nothing else. Running it is taking up 85% of the system resources.
I found a. Zip that is supposed to. Enable low. Ram. Mode. But it fails on twrp install. It class. To work with devices 4.4.4 and higher. I did disable the Google app and install the lite version which helped alot and I got a memory cleaner app. Supposedly flashing this zip makes the system think it's android go and will allow to install go apps. I think this tablet would benefit greatly fr{m this mod. I was wondering if I have to mod the build. Prop. I will. I. Just want to know.Your thoughts on this matter as always thank. You for your opinions I respect. You and your advice. I found these two files on the web.
mojorisin7178 said:
So I have the latest version of twrp on this and android is running really good and stable. The issue is it has no ram. Just basic with nothing else. Running it is taking up 85% of the system resources.
I found a. Zip that is supposed to. Enable low. Ram. Mode. But it fails on twrp install. It class. To work with devices 4.4.4 and higher. I did disable the Google app and install the lite version which helped alot and I got a memory cleaner app. Supposedly flashing this zip makes the system think it's android go and will allow to install go apps. I think this tablet would benefit greatly fr{m this mod. I was wondering if I have to mod the build. Prop. I will. I. Just want to know.Your thoughts on this matter as always thank. You for your opinions I respect. You and your advice. I found these two files on the web.
Click to expand...
Click to collapse
Are you talking about Low-RAM Property Patcher the thread is here:
https://forum.xda-developers.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373
Perhaps your ROM doesn't support Go features, and in that case the developer has to update the ROM.
Tab_Triggerhappy said:
Are you talking about Low-RAM Property Patcher the thread is here:
https://forum.xda-developers.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373
Perhaps your ROM doesn't support Go features, and in that case the developer has to update the ROM.
Click to expand...
Click to collapse
my rom is 6.0 will the one you linked to work since its for 8?
yeah the rom is basically bare bones aosp. But without anything installed besides gapps nano it uses 80% of the memory. I did disable the google app and install the go app and that helped alot. I am trying to enable low memory mode I found this:https://www.nextpit.com/turn-smartphone-into-android-go-device It says it enables low memory mode and then when you go to the play store all the go apps are availabe. so it looks like it tricks it into tinking that android go is the os. I dont know what the specifice differences are between android and android go besides go is a more stripped down version made for devices with lower end specs. They dont nmake a go version for the galaxy tab 2. Im just trying different things to make it work. This is how I learn how to do things. The great people at xda sharing their knowlage with me.
Tab_Triggerhappy said:
I haven't flashed more than 3 devices, but for TWRP it has always been AP in those cases.
If you flash a complete stock ROM it's much more than Recovery, so in those cases you flash separate files like bootloader (BL) etc...
Decide which ROM you want to try and read what Dev recommends in terms of Odin version and TWRP version. But a newer version than recommended should be fine (Odin).
I use 3.09 for my old P3100 but also 3.14 worked for me.
I also recommend getting the same stock ROM you already have from Sammobile.com + make a backup before modding.
For Root I have no recommendation. If Dev recommends Magisk for the ROM, try it and see.
The ROMs I tried was rooted with SuperSU 2.82 even if it's outdated nowadays. Our devices are so old so SU is fine if you ask me.
And most of the time it's SU in the ROM thread by the Dev anyway, so choose ROM and the thread for that and go from there
Click to expand...
Click to collapse
I did alot of work to get this thing back to life. First sammobile doesnt have the stock files anymore its too old. But one of the guys on the fourm had one and gave it to me. I had an older version of twrp installed and thats why i could not get anything higher than 4.4.4 or magisk. I found a newer version of twrp under the unified galaxy tab 2 development. Once i installed an updated version of twrp I was able to instal android 6 and root with magisk. it even passes saftey net. Now I am trying to disable as much as i can because it is using too mjuch ram. over 80%. It is a work in progress. Thank you for your tips. This is how I have always learned was by asking and the very knowledgeable people here at xda giving me tips. The development community is full of good smart people who like to share their knowledge.
Hello again,
I have the Tab2 P3100 and found stock firmware at Sammobile, but I had to register and become Premium user if I remember correctly. Old firmwares are archived.
Anyway... it looks like the thing I linked is the same that you linked.
I'm going to test it in my tab. My ROM is based on 6.1, will report back
Edit:
No, I get error message when installing zips and can't get it to work. LineageOS.
Best tip I can give is to install everything you want to use and then get rid of Gapps. Well, unless you use some Gapps stuff...
Tab_Triggerhappy said:
Hello again,
I have the Tab2 P3100 and found stock firmware at Sammobile, but I had to register and become Premium user if I remember correctly. Old firmwares are archived.
Anyway... it looks like the thing I linked is the same that you linked.
I'm going to test it in my tab. My ROM is based on 6.1, will report back
Edit:
No, I get error message when installing zips and can't get it to work. LineageOS.
Best tip I can give is to install everything you want to use and then get rid of Gapps. Well, unless you use some Gapps stuff...
Click to expand...
Click to collapse
Yeah gapps are really memory hungry. I dont really need to use this tablet for anything special. Its more the chalenge than anything else. And I learn so much doing stuff like this. Years ago I got y first android phone the lg g2x. Not too long after that I discovered xda and just started reading and asking questions. Then one day I took the jump and learned so much just by asking the devs questions and you know getting them a beer here or cup of coffee there. I love xda for that.
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.
Hi y'all. I'm new to the forums of XDA Developers. But, I'm not new to technology, phones, PC's, etc. I'm a noob in flashing a ROM to any specific phone. So, I decided to get help of other people to correct my issues. Any help will be really appreciated So here's what I've experienced:
I have the Samsung Galaxy A20s (SM-A207F). I want to flash a ROM on it (not custom ROM!). So, it currently runs OneUI 3.1 based on Android 11 and has 3 GB of RAM which means it will not support Android 12. And that's precisely what happened. I'm sick of Samsung's in-house OneUI and I wanna get the stock Android literally in my phone. I'm tired of using launchers, customizers, etc., because they don't do much. And now I'm on the verge of flashing my phone. I have downloaded the GSI of Android 12 and 11, since I wanna get Android 12 on it. And if it doesn't work, I'll just flash Android 11. Now, I'm aware of the risks involved in this process. It can soft brick my phone or even hard brick. But I don't wanna get the Pixel because this phone does the job smoothly, but un-intuitively due to Samsung's Android skin. I have unlocked the bootloader sucessfully, and yes, that did erase my whole phone. I don't have any data anyway. So, I tried flashing the phone with Odin on my PC. Since i have only a single .img image and Odin only accepts .tar files, I had to convert it to a .tar file. I used ImgToTar to do the job. Now, there are several fields in the app. Specifically, CP, AP, CSC and HOME CSC if I remember the names correctly. Now, i only have one tar file, so where should I put it? And also, I tried putting it in the AP column, and it failed halfway miserably. The phone still worked fine after rebooting though. Now I'm waiting, and I hope someone helps me.