Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
frabass said:
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
Click to expand...
Click to collapse
On nearly all Samsung phones, recovery is a part of the kernel. Flash a new kernel, you've flashed a new recovery.
The stock kernel zImage is as official as it gets - nothing is more official than what was actually flashed into the device by the manufacturer and sold on launch day. The additional evidence that it's official is that it passes the bootloader signing checks, eliminating the "custom kernel" warning screen.
We won't see a samfirmware release until AT&T releases an update.
Stock rooted shouldn't affect OTA updates, however sometimes things you do WITH root (such as debloating) will interfere with OTAs.
Once an OTA update becomes available, expect its fixes to be integrated into ROM releases fairly soon.
FYI there are three components you should know about. Kernel>ROM>Modem
The kernel It's the core/kernel of an operating system. It's main functions are to interact with the hardware a.k.a. Device Drivers, to manage resources (things like memory management and processor time sharing a.k.a. multi-tasking), service interrupt requests, network services and the like. It also provides a System Call Interface (API) to the user space (apps running on the machine) so the apps can use system resources.
Now the why so many part... First of all in general there are MANY options available when compiling (building) the kernel. Things like CPU schedulers, file system support, system type support, etc. etc. etc. So there are many different ways to configure the kernel and that gives many options to "test" and see which might work better or not. Some of them are dead giveaways like compiling the kernel for MIPS and trying to run it on the SGS2 won't work but some are "tweaks" that may help a little or a lot, like CPU management options.
Second part of the why so many is the code. Again as mentioned above things like changing code to make the colors of the display more or less sharp (display device driver), make the file system faster (voodoo lag fix) or overclocking the processor, and different "modem" tweaks are all "enhancements" that people have made to the original Linux kernel source. So those things "creep" into existence over time, since there are many people working on them, and you see different versions of the Kernel from that as well.
Anyone that plays music can relate to the options available in that there are only 12 notes on a guitar fret board but millions (or more) ways to put them together to play music. There are certain things that have to be present in the Kernel (notes) but writing code to enhance them and/or combining options at compile time is much broader (music).
The ROM. ROM is actually Random Access Memory and we flash an image to the "ROM" (which it really isn't but I'll leave that one alone). The "ROM" in this case is the operating system (a version of embedded Linux), which is the basic software needed to run and admin the phone, things like the Kernel, bootloader, device drivers, and file system plus any user apps like the phone dialer, launcher, etc. that are included in the ROM. As you can imagine the possibilities of customization are almost endless when it comes to the ROM. Different kernels, different drivers, different apps and many combinations of those.
The modem is actually part of the kernel. It's the device driver for the phone hardware. Being that it's part of the kernel it "works with" other code that's elsewhere in the kernel and ROM that is "tweaked" for a particular phone in this case. So when you see "use an i777 modem with an i777 kernel" it's because the code in the modem is written to work with the other code in the kernel. It doesn't necessarily mean it will brick the phone and/or not work but it quite often means it won't work the best if it's not "matched".
Actually the modem is NOT part of the kernel. The modem firmware runs on an entirely separate processor (not one of the main application cores.) - the RIL (Radio Interface Layer - part of the ROM) bootloads that processor by sending the modem firmware to it via a serial port when the system boots.
The baseband processor is almost never listed in a phone's specs because it's a "hidden" part of the system. Very often a device like ours will have more CPU cores than just the advertised application processor cores. For example, early Qualcomm MSM7000-series chips had two processors, one for applications and one for radio. Some people labeled these chips as "dual core" even when they really weren't - the two CPUs were completely different.
Similarly, we have two ARM Cortex-A9 cores acting as applications processors, an unknown ARM core doing radio work (much simpler, slower, and power-efficient than the two A9s), and possibly another application-specific ARM core hidden in the GPS chipset. Maybe more.
ok so i just got a galaxy note clone, its not a 5.3 in screen, its a 5inch, 1gz processor, 4gb rom, 512 ram,dual sim, 3g device, the exact model is a PAE8000 Android 4.0.3 5 inch Screen Smartphone. or so its called on ebay. looks pretty lagit, i mean i cant see spending 500+ for a name, that just me though, anyways, not to get off subject. how would you go about rooting this thing and what roms would you use? would you use ODIN? based on what ive seen it looks like its running pure ICS.i guess what im asking is...has anyone on here played with one of these? any help, tips, tricks and rooting info would be great!
The problem with these china clones is that while it may look identical, but that's about it. Everything else is different.
I quite sure you cannot use any kind of method that is used for Gnote (root, roms, kernels) because the hardware/firmware is different thus it requires soft mods that is specifically compiled for your phone. Think your phone as another phone altogther and not in any way associated with Gnote other that its similar looks.
For rooting, I'm sure you cannot use odin because the program and files are specific for Gnote. Maybe you can use those universal rooting app, eg. Superoneclick, I won't say it will work... but you might get lucky.
Another problem is you have to search for clockworkmod that is specific for your phone.. because its phone specific and you may not want to flash Gnote's cwm on this device, you may end up with a brick phone.
I would not recommend rooting your device if you haven't found cwm for it because you may want to backup the entire phone in its stock condition first before starting to meddle around with system files after root. Experimenting with mods/scripts etc after root may have the side effect of having your phone unable to boot into android. If you don't have cwm, you may not have a backup to fallback too.
yea i know, just trying to see if anyone else has played with the same device, if anyone has, please chime in!
EDIT 3: I've decided to post this in other threads to get more eyes on it, with this being the home thread, here is the detailed post I will be making elsewhere...
Alright, I give up, I posted a thread about this, but looks like I'm just gonna have to post here (since I'm sure it has more people watching)...
So I've been messing around with my tablet, finally got to a point where everything is great...except touchscreen, camera, bluetooth, and the dpi seems higher than needed (unless thats intentional)...so I need to figure out what to do for compatibility...
Stock Tablet Info - YourPad P4 (Which I gather seems to be a BRONCHO A710 based on build.prop)
Retailer Page
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
CPU: ARMv7 Processor rev 2 (v71)
GPU: ARM Mali-400 MP
System Partition: 251M
build.prop info:
ro.product.model=A710
ro.product.brand=BRONCHO
ro.product.name=crane_a710
ro.product.device=crane-a710
Notes on CM10
Backed up everything first of course (so I have all stock system files)
Flashed the recommended LiveSuit Image here to get a good partition table
Installed CWM 6 as directed here (sideloaded Terminal App first)
Installed newest CM10 build from here
Installed newest CM10.0 gapps from here
At this point, I was able to boot CM10, but as mentioned, touchscreen, camera, bluetooth, and for some reason accessing status under Settings -> About didn't work (probably more, but I did not mess around to figure out what else was wrong).
I then attempted the procedure over again, but installed the compatibility pack for LY-F1 (lyf1_compatibility_1.2.0.zip), as I assumed my tablet was a clone of that...installing it before gapps caused booting to hang, but installing after allowed it to boot...but still no touchscreen or anything...
So at this stage, it looks like I need to build my own compatibility pack from the system files I saved from stock...but I have no idea where to begin with do that (I assume its not as simple as replacing files or editing the updater-script in a pre-built pack).
I could really use some assistance...I'm going to post this in 3 other threads with the home thread being the one I already created here
Thanks for any help to whoever can provide it!
Click to expand...
Click to collapse
EDIT 4: Someone requested my lsmod output, here it is for anyone else looking to help out...
8192cu 569557 0 - Live 0xbf16d000
dm9620 7763 0 - Live 0xbf161000
rtl8150 9012 0 - Live 0xbf15a000
mcs7830 6485 0 - Live 0xbf154000
qf9700 8497 0 - Live 0xbf14d000
asix 22700 0 - Live 0xbf142000
usbnet 23751 4 dm9620,mcs7830,qf9700,asix, Live 0xbf136000
dmard06 8994 0 - Live 0xbf129000
stk8312 5972 0 - Live 0xbf123000
mma7660 6410 0 - Live 0xbf11d000
sun4i_csi0 27428 0 - Live 0xbf112000
sun4i_csi1 26629 0 - Live 0xbf107000
gc2015 15431 0 - Live 0xbf0ff000
gt2005 15938 0 - Live 0xbf0f7000
gc0308 14842 1 - Live 0xbf0ef000
videobuf_dma_contig 5635 2 sun4i_csi0,sun4i_csi1, Live 0xbf0ea000
videobuf_core 18078 3 sun4i_csi0,sun4i_csi1,videobuf_dma_contig, Live 0xbf0e0000
mali 129944 8 - Live 0xbf0af000
ump 42238 15 mali, Live 0xbf09e000
ekt2201 4414 0 - Live 0xbf094000
hv2605 4656 0 - Live 0xbf08f000
sun4i_vibrator 2254 0 - Live 0xbf08b000
ft5x_ts 47042 0 - Live 0xbf07a000
sichuang 12615 0 - Live 0xbf072000
gt811 12263 0 - Live 0xbf063000
Click to expand...
Click to collapse
EDIT 2: Its a BRONCHO A710 according to the build.prop if that will help
EDIT: Currently all I need assistance with is finding or building a compatibility pack that will work with my tablet
Alright, so almost a year ago I posted about needing assistance with installing CWM on this device, and ended up being basically successful...but then I ran into issues figuring out what to do about whether to install cyanogenmod or not...so the tablet got put away never to see light again till now (yes, im pretty awful). So I've been doing some major professional level googling and im still at that point where I'm not 100% on what to do and don't want to take any risks.
Anyways, to make things clear, I need some assistance on installing CM10 (or even advice on if I should bother). Currently, the tablet works fine and I was able to modify the build.prop to allow more apps off google play to install...but I just am worried about future proofing this before getting invested in using it more often.
Another issue I'm at is figuring out what kind of tablet it is...from research and talking with others, I found/was told it was an Allwinner A10...but the processor is an ARMv7...and quite honestly I'm not 100% of whether or not Allwinner processors are actually ARM or not....
So here is some current pertinent information...
* Item detail page:
http://www.yourstoreonline.net/yourpad_p4_new_android_40/id2040716/product.html
* Tablet info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
CPU: ARMv7 Processor rev 2 (v71)
GPU: ARM Mali-400 MP
CWM v5.5.0.4 *Should I upgrade to 6 or something with touch support? As no Go Back option appears and causes alot of issues...*
* Partitions are laid out in the nanda/nandb/nandc... style
* System Partition is 251M
* CWM installed as I described briefly in an old thread here
* CWM doesn't seem to be 100% functional, but at least appear to be able to backup/restore...
Really, anything will help, even posts discouraging CM, I'm just looking for some clarity because without being certain, I'll either give up and use the tablet as is, or will let it sit collecting more mounds of dust till its so obsolete that we'll all be about google glass! Thanks in advance...
U maybe interested in looking at this thread of mine
EarthBoundX5 said:
Alright, so almost a year ago I posted about needing assistance with installing CWM on this device, and ended up being basically successful...but then I ran into issues figuring out what to do about whether to install cyanogenmod or not...so the tablet got put away never to see light again till now (yes, im pretty awful). So I've been doing some major professional level googling and im still at that point where I'm not 100% on what to do and don't want to take any risks.
Anyways, to make things clear, I need some assistance on installing CM10 (or even advice on if I should bother). Currently, the tablet works fine and I was able to modify the build.prop to allow more apps off google play to install...but I just am worried about future proofing this before getting invested in using it more often.
Another issue I'm at is figuring out what kind of tablet it is...from research and talking with others, I found/was told it was an Allwinner A10...but the processor is an ARMv7...and quite honestly I'm not 100% of whether or not Allwinner processors are actually ARM or not....
So here is some current pertinent information...
* Item detail page:
http://www.yourstoreonline.net/yourp...6/product.html
* Tablet info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
CPU: ARMv7 Processor rev 2 (v71)
GPU: ARM Mali-400 MP
CWM v5.5.0.4 *Should I upgrade to 6 or something with touch support? As no Go Back option appears and causes alot of issues...*
* Partitions are laid out in the nanda/nandb/nandc... style
* System Partition is 251M
* CWM installed as I described briefly in an old thread here
* CWM doesn't seem to be 100% functional, but at least appear to be able to backup/restore...
Really, anything will help, even posts discouraging CM, I'm just looking for some clarity because without being certain, I'll either give up and use the tablet as is, or will let it sit collecting more mounds of dust till its so obsolete that we'll all be about google glass! Thanks in advance...
Click to expand...
Click to collapse
U can check out my thread here on building livesuit images. You can get a CWM recovery file and using the tools posted dump ur stock rom and make a fully working livesuit image with CWM recovery instead of ur stock recovery. bt before u do that I must tell u, u have to be careful of what u do, as I will think u hav full working knowledge of linux and comfortable on working with bash. If u are then it all urs for taking...make ur stock image (also u will hav a backup if u try other custom ROMs) and flash it again to get ur tablet with CWM. after ur done just goto settings>backup and reset and there select reboot to recovery option. It will boot into CWM. but dont exit by rebooting. if u do that it will cause ur tablet to be stuck on android logo. u have to wipe data/cache and then reboot.
check this thread: http://forum.xda-developers.com/showthread.php?t=2318587
and if u wanna flash a recovery without all those steps, u can do the following:
copy the CWM file u download (it will be a .img file) into ur internal SDcard.
then in adb shell type su -c"cat mnt/sdcard/[cwm_file.im] > dev/block/nandg"
this will copy the cwm image into ur recovery partition, then goto recovery through settings>backup & reset > reboot to recovery option.
Ill take no responsibility if u brick ur tablet or anything happens while u do ur stuff. But anyways, these are tested methods, so do it at ur own risk. Enjoy ur CWM.
cybermate123 said:
U can check out my thread here on building livesuit images. You can get a CWM recovery file and using the tools posted dump ur stock rom and make a fully working livesuit image with CWM recovery instead of ur stock recovery. bt before u do that I must tell u, u have to be careful of what u do, as I will think u hav full working knowledge of linux and comfortable on working with bash. If u are then it all urs for taking...make ur stock image (also u will hav a backup if u try other custom ROMs) and flash it again to get ur tablet with CWM. after ur done just goto settings>backup and reset and there select reboot to recovery option. It will boot into CWM. but dont exit by rebooting. if u do that it will cause ur tablet to be stuck on android logo. u have to wipe data/cache and then reboot.
check this thread: http://forum.xda-developers.com/showthread.php?t=2318587
and if u wanna flash a recovery without all those steps, u can do the following:
copy the CWM file u download (it will be a .img file) into ur internal SDcard.
then in adb shell type su -c"cat mnt/sdcard/[cwm_file.im] > dev/block/nandg"
this will copy the cwm image into ur recovery partition, then goto recovery through settings>backup & reset > reboot to recovery option.
Ill take no responsibility if u brick ur tablet or anything happens while u do ur stuff. But anyways, these are tested methods, so do it at ur own risk. Enjoy ur CWM.
Click to expand...
Click to collapse
Thanks alot for the reply, your thread may actually be quite helpful for some other issues I didn't feel were worth posting about.
However, just to be clear, I do have a basically functional CWM installed already (done so manually by concating the recovery img to nandg). My main concern is whether or not to install CM10, and how to do so since I have a system partition under 300 MB. Also, I was hoping to find clarification as to whether or not my tablet is in fact an Allwinner A10...which I'm pretty sure it is, just dont wanna start following guides or instructions tailored for a completely different board...
Its an Allwinner for sure, bt if it has an HDMI output its an A10,A13 doesnt hav that. Else if its a dual core it can be an A31 or other allwinner CPU's. U can use proc/cpuinfo to get ur device cpu. A10/13 is i think cortex A8 but if its higher then itll b A9 or sumthing. And I know hw it feels cz no one here helped me,so I had to read alot,collect tools frm diffrent forums so that in future ppl dnt hav to suffer like me. Tkcre.
cybermate123 said:
Its an Allwinner for sure, bt if it has an HDMI output its an A10,A13 doesnt hav that. Else if its a dual core it can be an A31 or other allwinner CPU's. U can use proc/cpuinfo to get ur device cpu. A10/13 is i think cortex A8 but if its higher then itll b A9 or sumthing. And I know hw it feels cz no one here helped me,so I had to read alot,collect tools frm diffrent forums so that in future ppl dnt hav to suffer like me. Tkcre.
Click to expand...
Click to collapse
It has an HDMI out and is single core, so I'm betting my original conclusion from input is accurate that its an A10. Thanks alot for the detailed breakdown of each revision, there should really be a thread dedicated for just simply describing the different Allwinner tablets...(which it wouldn't surprise me if there already was, just difficult to find).
Well excellent, between your thread, what information I've read, and confirmation of it being an Allwinner A10, I should be good to go ahead and tinker with CM10...
EDIT: Regarding CWM, I think I'll probably stick with 5, since it looks like the nonfunctional features of 6 are ones not worth loosing...
EDIT 2: Well actually, I guess there is still the problem of my system partition size...
EDIT 3: Looking back at your thread, it appears you already had a solution for system partition....
Alright, so as I stated in your thread, I'm unable to reflash my tablet with the original firmware, or rather it gets stuck while booting. Since I have 2 of these tablets, I tried simply reflashing with LiveSuit with my installed CWM as the recovery.fex, this allowed me to at least access CWM on the currently nonfunctional tablet.
I'm thinking that something just went wrong with making the system.fex file? Any ideas?
Once its uploaded, I'll post the img file I ended up with...
EDIT: After having tried restoring a clockworkmod backup from my other tablet...I've still been stuck while loading Android...
EDIT 2: Here is the livesuit img I made, maybe you could unpack and see if anything strikes you as odd?
https://dl.dropboxusercontent.com/u/12443810/YourPad P4/yourpad_p4.img
EDIT 3: Screwed around, think I got everything sorted out, right now only issue would be deciding on a compatibility pack to use when installing CM10...
EDIT 4: Ya, so the only issue I have right now is to determine a compatibility pack to use for CM10, as my touchscreen, bluetooth, and a few minor things do not work...
http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
EDIT 5: Its a BRONCHO A710 according to the build.prop if that will help
EDIT 6: Which I've found is a clone of LY-F1, so I'll try messing with installing CM10 with that compatibility pack...although it appears many have had issues with it...which apparently I am having too, as its hanging on booting CM...
bump, updated OP
TM-MID850 compatibility zip
hello,
I may face the same issue in my TM-MID850 tablet. I could intall the rom successfully however the touch didn't work because I didn't install the compatibility zip . Actually, I tried to install any compatibility yet the tablet stuch at the boot screen, so I flashed the stock rom again .
Please if you could make your compatibility zip for your device , tell the way to make the same for my own one. I got all system files from cwm but I don't know yet which file I have to put in the compatibility zip !
Thanks anyway and waiting for any answer .
some information???
:good:
Hello to all
Dear colleagues, I would not change the topic of this thread, but I'm on the search for information with which to make a safe and very easy upgrade for users of Dragon Touch Tablet device with a processor A10 AllWinner precisely this model http:/ / goo.gl / CemoNN
I could make an important step is to make the ROOT of the device with just a few clicks with the tool Root_with_Restore_by_Bin4ry.
Now I would like to have more information on CM ROMs compatible with these devices and consequently not to bring problems or hardware failures, as might be problems in the wireless adapter, or low battery performance.
I would also like to know if there is any software that can make a true copy of the preinstalled ROM already comes with the device, in order to support it and reinstall in case that may give too many failures to update
You have some information about the recommended ROMs that can provide me.:good:
Greetings and thanks.
MemOoooO said:
hello,
I may face the same issue in my TM-MID850 tablet. I could intall the rom successfully however the touch didn't work because I didn't install the compatibility zip . Actually, I tried to install any compatibility yet the tablet stuch at the boot screen, so I flashed the stock rom again .
Please if you could make your compatibility zip for your device , tell the way to make the same for my own one. I got all system files from cwm but I don't know yet which file I have to put in the compatibility zip !
Thanks anyway and waiting for any answer .
Click to expand...
Click to collapse
Hi How did you manage this? i have flashed without correct compatibility pack so have no touchscreen, i have only power and volume buttons as all others are part of the screen. how can i get back to recovery to install a new zip?
(ADB Devices from windows machine cannot find the device)
Many thanks
ADB driver
bighead85 said:
Hi How did you manage this? i have flashed without correct compatibility pack so have no touchscreen, i have only power and volume buttons as all others are part of the screen. how can i get back to recovery to install a new zip?
(ADB Devices from windows machine cannot find the device)
Many thanks
Click to expand...
Click to collapse
I've found that if you boot the machine using the livesuite method of holding the volume +, connecting the usb cable and then tapping the power button 6-10 times, I can update the unknown device to Android Composite ADB Interface driver.
Hi all:
I recently purchased the following tablet from Best Buy on Black Friday:
http://www.bestbuy.com/site/d2-android-tablet-4gb-black/2469403.p?id=1219073320325&skuId=2469403
It's running an Allwinner A13 CPU, which I know can be rooted via a variety of methods. My issue is that all of the rooting solutions I have found use an exploit in 4.0.4 to install su and Superuser, but this tablet shipped with 4.1.1, so all of these methods grind to a halt. I have scoured the boards for anything and everything--I've tried the Sony Xperia tool, I've tried Uberizer, I've tried bin4ry's tool--literally nothing seems to work (although bin4ry's tool did seem to install busybox successfully.)
I would greatly appreciate it if someone could help me out--this tablet is borderline unusable because D2 does terrible things to their devices, and if I can get root I can install CWM and begin stripping out all of the bloatware and junk.
Any luck?
spectheintro said:
Hi all:
I recently purchased the following tablet from Best Buy on Black Friday:
http://www.bestbuy.com/site/d2-android-tablet-4gb-black/2469403.p?id=1219073320325&skuId=2469403
It's running an Allwinner A13 CPU, which I know can be rooted via a variety of methods. My issue is that all of the rooting solutions I have found use an exploit in 4.0.4 to install su and Superuser, but this tablet shipped with 4.1.1, so all of these methods grind to a halt. I have scoured the boards for anything and everything--I've tried the Sony Xperia tool, I've tried Uberizer, I've tried bin4ry's tool--literally nothing seems to work (although bin4ry's tool did seem to install busybox successfully.)
I would greatly appreciate it if someone could help me out--this tablet is borderline unusable because D2 does terrible things to their devices, and if I can get root I can install CWM and begin stripping out all of the bloatware and junk.
Click to expand...
Click to collapse
Hey there. I have the same tablet, and have been running up against the same dilemmas.. I'd really like to use this as disposable/travel device.. something that I dont have to worry about at all getting stolen or broken, but that can do the basic things a tablet should do.. But as is, it's jammed so full of kids crap that it has no room left on it, and trying to run JB on it it just rediculas.
I would really like to root it, de-bloat it, and flash a custom rom on it.. something very bare-bones to try and get some pep back in it.
Have you had any luck finding a root solution for this device yet? Nothing I know of has worked.
Thanks in advance.
Max
tf701mega said:
Hey there. I have the same tablet, and have been running up against the same dilemmas.. I'd really like to use this as disposable/travel device.. something that I dont have to worry about at all getting stolen or broken, but that can do the basic things a tablet should do.. But as is, it's jammed so full of kids crap that it has no room left on it, and trying to run JB on it it just rediculas.
I would really like to root it, de-bloat it, and flash a custom rom on it.. something very bare-bones to try and get some pep back in it.
Have you had any luck finding a root solution for this device yet? Nothing I know of has worked.
Thanks in advance.
Max
Click to expand...
Click to collapse
Hey Max:
I unfortunately never was able to get this rooted, and I threw everything I possibly could at it. I ended up returning it. Wish I had better news.
So far my device is magisk rooted and unlocked, with a few run of the mill tweaks here and there. Is anyone aware of this device supporting custom recoveries after unlocking? I suspect TWRP might work with minimal modification if any, but I haven't yet tried to flash anything beyond magisk and figured I would ask for other people's experiences here before I attempt to do so.
Thanks!
706trades said:
So far my device is magisk rooted and unlocked, with a few run of the mill tweaks here and there. Is anyone aware of this device supporting custom recoveries after unlocking? I suspect TWRP might work with minimal modification if any, but I haven't yet tried to flash anything beyond magisk and figured I would ask for other people's experiences here before I attempt to do so.
Thanks!
Click to expand...
Click to collapse
Somebody help i also have a new phone samsung a11 and successfully rooted it with magisk unlocked bootloader and rom that i found on sammobile (same model same CSC) and i want to also know if its possible getting the TWRP on a magisk rooted device without having any trouble
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is the device tree with a bootctrl error right now I don't have time to keep working on it for a while but if we get it working we can build ROMs and twrp
Working TWRP but very unofficial! But very useful!
Hi, so I just got this phone and I see there's not much on the postings like with links to a working TWRP, in particular. So I did some digging around and experented, and found this TWRP. It's from the Moto G9 Play (guamp). But it works, at least...
forum.xda-developers.com
See instructions by me to boot it from Android or use fastboot to boot it