Related
I'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)
I have since returned this tablet. The go edition was just too much, or way too little for me to deal with.
The 7" variant shouldn't be considered a variant as it is only similar in shape and color. It is however still rootable. I am assuming you have adb and fastboot set up and know how to use them. Also if on windoze you know how to adjust if needed and to connect device with usb and the other little details I've overlooked. If not then I am also assuming you don't need to try this yet.
The root process is not difficult but tricky in that it is different. Before doing this you need to go to Magisk release thread and check out link for running Recovery Mode and read it all. You must have unlocked bootloader. The process goes something like this:
Edit: You will need the latest platform tools for fastboot to work properly. This link https://www.xda-developers.com/what-is-adb/ provides instructions for windows and Linux. Yes, you may need to update the tools in some Linux installations as not all repositories are kept up to date with regards to android-sdk.
1) Download mtk-su by @diplomatic to your pc.
2) Open a terminal in window where you have mtk-su. You can cd to it but this seems easier. Type the following "adb push mtk-su /data/local/tmp/"
3)Type "adb shell chmod 755 /data/local/tmp/mtk-su
4)Type "adb shell" you will enter a shell with no need to cd to anywhere. If you cd /data/local/tmp then you need to cd back out of it when root shell is achieved. If you run it this way your ready to go without changing directories
5) Type "./data/local/tmp/mtk-su -v" you now have a root shell. If for some reason you do not have root access, run mtk-su again, it will work.
6)Now the confusing part. You need to copy your recovery to patch with Magisk. You use "dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img your recovery should be in internal storage when you open your file manager.
7)Install Magisk Manager and open it to select install. Before install you tick advanced settings and tick Recovery Mode. You then select install. A toast will pop up and you select the bottom one which is to patch your boot.img file. Wherever you see boot you use your recovery instead.
8)Magisk will put your patched recovery labeled magisk_patched.img in your download folder. Transfer it to your PC.
9)In terminal on PC open window where you have your magisk_patched.img. Then use adb reboot bootloader.
10) Flash your patched img with "fastboot flash recovery magisk_patched.img" and you're done flashing.
11) Now the fun part, you hold power and volume+ until you first get a glimpse of the boot selection screen. AS SOON AS IT LIGHTS UP LET GO for a second,just a second, then scroll to recovery and hit volume- . If its already on recovery just use volume down, do not scroll around to it. Your tablet will boot into a Magisk rooted system and not recovery.
It can be tricky but however you boot your tablet determines if you're rooted or not. When Magisk Manager reboots after installing a module it know what it's doing and you don't have to do anything but wait on it. Whenever booting your system you need to make your first priority going to magisk to check if it's installed before trying anthing. You need to do this every time you boot until you have your timing right and confidence way up. Then you should probably still check.
From what I can see when not booted to Magisk rooted system, installed modules and changes made are obviously not working. It should stand to reason if Magisk is not installed that magisk modules won't work. Like I said, its not hard it's just odd to me. Don't know how porting recovery is going to go. Wondering if we will need to patch the ported img or port the patched img. It's is treble compatible, I've read a-only but don't know about gsi's yet. Keeping expectations low though.
When I had Magisk installed I was left with no recovery or I didn't keep it long enough to figure it out. When booting with hardware buttons and holding for recovery/unrooted system the tablet booted to an unrooted system bypassing recovery all together. Don't know if it was procedural error on my part or if that is the compromise that has to be made to have perm root for the time being. Flashing stock recovery via fastboot proposed no issues.
Good information, thanks!
What prevented the usual patched boot image method from working?
NFSP G35 said:
Good information, thanks!
What prevented the usual patched boot image method from working?
Click to expand...
Click to collapse
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.
My apologies I withdraw my question.... I see that the 7 is different from the 8 & 10 where the recovery.img is being patched instead of the boot.img I will make note of that when I start my video tutorial series for the onn line of tablets.
The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)
CaffeinePizza said:
The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)
Click to expand...
Click to collapse
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!
tek3195 said:
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!
Click to expand...
Click to collapse
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.
CaffeinePizza said:
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.
Click to expand...
Click to collapse
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.
tek3195 said:
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.
Click to expand...
Click to collapse
I do not plan on supporting the 7" tablet. Probably just burst some bubbles.
tek3195 said:
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.
Click to expand...
Click to collapse
What about modifying the boot.img to create the ram disk?
callihn said:
What about modifying the boot.img to create the ram disk?
Click to expand...
Click to collapse
Not sure I follow. The ramdisk it uses is in the recovery.img not sure what you would be trying to create or use it for. You lost me.
I've managed to unlock the bootloader, but the system boots up normally... Stock recovery if I choose recovery. Where did I go wrong?
i think your crazy also, I patched the recovery, and it doesn't work, it goes to a blank screen, if you had screen shots it might be more convincing, what does majick do taking over recovery, means using root from a p.c ???
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
if goes to majick recovery see if it's rooted with adb
---------- Post added at 06:17 PM ---------- Previous post was at 06:10 PM ----------
when you say building, found an interesting article where you might build or free ramdisk, even boot to majick root recovery, I'm just researching the idea
https://source.android.com/devices/bootloader/partitions/ramdisk-partitions
have you tried flashing with a gsi ROM, this sounds great
https://forum.xda-developers.com/pr...hVM2htbVVRNGhnUzU5ZktDUUNSZjlzdGE2bkk4TjhZY3M.
flashing gsi rom on surf 7, changed vbmeta to dtbo.img, got a black screen with no way to fix, no recovery ? does anyone know the proper way to flash one
This thread is presently about the development of a TWRP port to these devices.
The build is not yet working!
I am in the process of porting TWRP to my 3562 mostly out of pure spite for this stupid device. This thread is mostly for collecting my development process, for anyone who is interested, or wants to help.
Presently, TWRP will boot properly, and does function apart from UI issues and generally not being able to mount partitions correctly.
The UI draws in portrait mode (USB port at the top), but the touch interface responds in landscape mode (USB port on the right). This is very annoying, but it is still usable, so I haven't looked too far into it.
It seems to mount boot and userdata partitions okay, /sdcard is full of garbage data (encrypted? bad mount flags?), /system will not mount at all.
First order of business is to get /system mounted. It looks like this is related to vbmeta, so I have to sort out how to properly wipe the vbmeta on this device.
Here is my current image, if anyone is interested in trying it out: https://drive.google.com/file/d/1kMvKvocKY6AWRR-xkXIwisv27TmF6xcP/view?usp=sharing
I'll keep this updated as I keep working. As always, any input is greatly appreciated.
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
rolenthedeep said:
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
Click to expand...
Click to collapse
Thanks for moving, we were a bit OT in other thread. Yes the boardconfig.mk is for building from source. Does no good when using kitchen, I was just showing you an example of where and how rotation was handled. I still haven't followed up on changing rotation and touch input using kitchen, just got home from another heart catheterization. The only way to get a fully working fully functional twrp is to build from source, but without source code AIK is an awesome alternative. I just can't remember if we can change rotation and touch input in de-compiled img. We can ask @osm0sis if it is possible to edit recovery rotation via AIK. If you've not done so already, check out his work here on XDA. There are a lot of useful tools and scripts authored by him and a wealth of android knowledge that you can only benefit from reading.
Haven't ever messed with TWRP rotation myself, sorry. I'm sure it's something you can Google and find out though.
@rolenthedeep look at this may be helpful with rotation
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
mpalpha said:
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
Click to expand...
Click to collapse
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
tek3195 said:
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
Click to expand...
Click to collapse
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
mpalpha said:
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
Click to expand...
Click to collapse
I thought I was replying to someone else, but same applies. You're wanting to port one using kitchen the best place to start is here:
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
Where it gives the different screen resolutions go with largest, if it calls for a file not present in your device just skip it and don't add extras. There are a lot of guides but that one I know works rather well, I've used it on 3 diff devices. Cooking custom recovery in kitchen works but not always correctly. By that I mean that you may not have the ability to backup or restore or install. You may not be able to control brightness or some other setting or it could be that usb does not work. It can be a combination of any of those things and more. It can also be that you never notice something not working because it does everything you want it to. Just letting you know what to expect and saying that building from source is always best, even when it's unavailable.
If you ever get the time can you port TWRP to the 100015685-E?
@rolenthedeep here is a WIP fstab. I have commented out the partitions that were not first_stage_mount If you try it as is to try to get an idea of which parts are needed for recovery there is no sd card in it as it too is commented out for now. Got caught up in some other issues and stopped looking at it for a while. Maybe it will help a little.
Any updates on this? I have the 10.1 3562 version
Alrighty... So I'm in the weeds here after going through three variants of the Samsung JPop (Which have bootloaders locked up like Fort Knox) and decided today to break down and dish out $59 for this bargain device. First thing I did upon getting it home was fastbooting it, and was able to unlock the bootloader with no issue. (So easy, a caveman could do it)
I've read just about every thread in here and though there seems to be TWRP support for quite a few models of the Onn tablets, I didn't see this one in here. Right now I have a throwaway laptop which is installing ubuntu for building TWRP for this device. Now, I have NEVER built TWRP. But I have plenty of free time, ambition, and am willing to learn. I have the basic guide to building TWRP open elsewhere. I will take whatever help I can get on doing this, big or small. Building a basic TWRP image should be easy enough, but the guides don't really go into device specific details (as expected), so this is where I could use some veteran help.
Device Specs:
Model: 100026191
Out-of-the-box Android Version: 11
Display: 7" 1024 x 600 Resolution
Processor: 2.0 GHz Quad-core CPU
RAM: 2GB
Cameras: 2MP front & back
USB: Type-C
Ubuntu just finished, and I am getting the build environment ready as we speak. Will keep this thread updated with progress and hickups that may occur along the way. Wish this noob some luck!!!!
Alrighty, so here's what I've been able to come up with as far as more detailed system information. Sorry for the late post, had trouble getting wifi working on ubuntu but got it going.
I suspected a MediaTek CPU and was eager to do a readback with SP Flash Tool, but as you can tell from the provided screenshots, it's actually a Cortex-A53 CPU. my goal here is to some how pull my stock recovery out of here. I thought about dd'ing it but someone in another thread advised against it. Does Onn have stock firmwares hidden away in the internet somewhere? Or is there another tool I can use to pull recovery?
Good evening guys and gals. New day, new opportunity. So i'm still stuck at pulling off boot and recovery from this tablet. I used
Code:
/adb shell cat /proc/mtd
to no avail. Permission denied just like with dd.
Today, I got the MTK droid tool and hooked the tablet to it and got these results. Still no scatter file, still no progress on pulling these partitions. (I apologize for my dumbness yesterday, this device is in fact MediaTek)
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
guess i'll return it to walmart
was hoping to root it easily with twrp
just gonna go grab the 8' if this is how it ended for the 7'
thanks for the help though!
I need a firmware for the 100026191
TWRPN00b said:
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
Click to expand...
Click to collapse
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Just note that if you want to extract the original boot image, do NOT flash the Magisk image, it will permanently erase the original boot image. There is another way, I can walk you through it.
PseudoDistant said:
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Click to expand...
Click to collapse
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
alarmdude9 said:
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
Click to expand...
Click to collapse
My way of pulling the images should work on any Android device that ships Android 8.0+, however if you got it brand new, don't update it.
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
PseudoDistant said:
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
Click to expand...
Click to collapse
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
alarmdude9 said:
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
Click to expand...
Click to collapse
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
After you're done with that, and you're rooted.
`adb shell`
`su`
`dd if=/dev/block/by-name/recovery of=/storage/emulated/0/recovery.img`
Then connect your tablet to your PC and enable file transfer in USB settings, then just pull recovery.img out of your tablet and you have the recovery image.
PseudoDistant said:
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
Click to expand...
Click to collapse
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Update to Android 12 before using Magisk, just in case.
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Could you share the ota? This is the same model I'm using but its bricked rn
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
I will look for it. Saved it to a USB drive and of course it decided to be stupid and it is repairing now. Slow going but as soon as it gets done I will look to see if it survived and if so I will get it uploaded.
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
Sorry just noticed that the file that PseudoDistant posted is still good. I used this one....
https://forum.xda-developers.com/attachments/magisk_patched-25200_fvdeh-img.5794395/