Has anyone gotten chainfire3d to work on the tf700t??
Mine simply fails to boot... was trying to get stratagus to work and thought this might help..
thx
Why would you need Chainfire? I thought that was in intermediary opengl drive to allow for non-Tegra chipsets to play Tegra games? The TF700 ... is a tegra device ...
The Play Store page clearly states that it isn't compatible with ICS or Jelly Bean, so you shouldn't use it. Trust me, I didn't read it either and tried it and "bricked" my device. Took me a while to get it back going.
Well i dont see why it would brick the device? i have tried it on my infinity and a wipe and reflash of cleanrom worked fine after...
I have also been running it on my jellybean samsung galaxy s2 and my ics motorola atrix 4g without any problem.. so it seems to me that
he hasnt updated the info....
The reason i wanted to try it is because of the app stratagus which i am trying to run does not work on tegra devices... therefore using
chainfire with a qualcomm plugin might do the magic.....
my tf700 was rendered unbootable with cf3d. had to reinstall cleanrom to fix it. didnt need to wipe.
Interesting. I tried it shortly after we received JB officially. Someone else also posted that it bricked them. It just hit me, I wasn't unlocked when I did it, so that's why. I didn't have your option of re-flashing because I couldn't access recovery. I had to use my SD and go back to ICS. Either way, it's not compatible with us for some reason.
Alitheia said:
Interesting. I tried it shortly after we received JB officially. Someone else also posted that it bricked them. It just hit me, I wasn't unlocked when I did it, so that's why. I didn't have your option of re-flashing because I couldn't access recovery. I had to use my SD and go back to ICS. Either way, it's not compatible with us for some reason.
Click to expand...
Click to collapse
If you were able to restore it, it was not bricked. You cannot restore a brick. It is the definition of the word.
Hey guys, I managed to render my device unbootable with chainfire too.
Its rooted but not unlooked. Will it work again after wiping data or what are the possibilities thaz I have?
Update: wiping data did not work. What else can I so?
Gesendet von meinem GT-I9100 mit Tapatalk
I would suggest install a custom rom like cleanrom so that in future such incidences you can easily reinstall.
liquiddarknessvi said:
If you were able to restore it, it was not bricked. You cannot restore a brick. It is the definition of the word.
Click to expand...
Click to collapse
That would be why I used quotes around the word in my first post...clearly it wasn't bricked, but it was scary nonetheless. I know the definition.
Anyone who is using the latest clemsyn kernel and can verify if chainfire is working?
Currently running cleanrom 2.3 with stock kernel as the overclocking didnt seem to improve my gaming exsperience
But if chainfire works with the new kernel then i might use it
Come ON WHAT THE ****?? LOL
Does anyone read Chainfire3D Description on Google Play it says clearly
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
Not mean to be rude but why people doesn't read, dont install this people...
well relax... it works on all of the 4 devices i have had running everything from ics to jellybean i dont see the problem...
Its clearly something with this particular device hmm well damn... cant realy use this device for a whole lot...
all the nice apps and games are running like crap unfortunately...
I've had a report of a unit being bricked after CF3D installation as well. In that particular case, the owner of the 700 was saved by still being inside the warranty period (and an exchange was approved), but I guess with some handiwork, the unit could have been revived.
Also: one brick is not necessarily equal to another brick. Phrased differently: there are hard bricks and soft bricks. Installation of CF3D seems to generate a soft brick, from which you can recover FI you have the right files, knowledge, and a fair bit of time and patience. A hard brick generally results in an expensive paperweight.
MartyHulskemper said:
Also: one brick is not necessarily equal to another brick. Phrased differently: there are hard bricks and soft bricks. Installation of CF3D seems to generate a soft brick, from which you can recover FI you have the right files, knowledge, and a fair bit of time and patience. A hard brick generally results in an expensive paperweight.
Click to expand...
Click to collapse
Thanks for saying this.:good:
Related
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char
Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
since HTC released the kernel code, I thought it would be easier to revert back to enterily stock
Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....
Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.
Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?
socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!
It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.
I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?
maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?
potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL
I have a LG Mach (AKA Cayenne, LS860) LG Apparently algo named the LU3000 "Mach" as well for w/e reason. There is a distinct lack of ANYbody developing for this phone. I would like to take on doing it myself, but I am unclear on how to start. I managed after about a week to root the stock rom, but I can't find any recoveries for it. How should I go about this?
I understand that this is a very in depth question and for most, it would be too much to tackle. However, I have a background in C++ and Visual Basic (though I am a little rusty). Any direction would be nice and I am willing and capable of learning anything necessary to accomplish this.
Thanks!
Well this is a combination of bump / information. Since there is a lack of information regarding this phone out here, I figured I would share the method I used to root this phone. It works on the stock 4.0.4 rom.
http://forum.xda-developers.com/showthread.php?t=1886460
I was thinking about compiling TWRP for this phone myself, but I would like input from everyone if CWM would be a better choice? Input welcome
CorySCline said:
Well this is a combination of bump / information. Since there is a lack of information regarding this phone out here, I figured I would share the method I used to root this phone. It works on the stock 4.0.4 rom.
http://forum.xda-developers.com/showthread.php?t=1886460
I was thinking about compiling TWRP for this phone myself, but I would like input from everyone if CWM would be a better choice? Input welcome
Click to expand...
Click to collapse
I just won this phone, and I'm putting the term LG MACH ROOT/LG MACH BOOTLOADER in this thread so people can find it via google.
There is pretty much no developer love for this phone...
I don't care which way you do it. Personally I prefer TWRP because of it's touch controls.
Mgamerz said:
I just won this phone, and I'm putting the term LG MACH ROOT/LG MACH BOOTLOADER in this thread so people can find it via google.
There is pretty much no developer love for this phone...
I don't care which way you do it. Personally I prefer TWRP because of it's touch controls.
Click to expand...
Click to collapse
Well, it looks like its up to me and you:
Im going to compile TWRP tonight for it, and if all goes well, I will create a new thread with the rooting method and recovery explained. However, know that you will officially be person #2 to use this recovery image. All warnings and potential problems will apply.
Up for some fun?
I haven't got the phone yet actually. Briefmobile informed that I won and that sprint will ship it. I don't know anything more than that :/ I hope soon. It'd be fun to mess with the phone while my college break is going on still.
Sorry about the really slow replies. I should subscribe so that tapatalk notifies me.
I don't know when it will get here :/
But since you have it, do you know if the bootloader is unlocked/unlockable? Google is surprisingly of little use with this phone. I'd love to dink around with this phone since it's not my primary one (and I can't use cellular services on it)
Mgamerz said:
I haven't got the phone yet actually. Briefmobile informed that I won and that sprint will ship it. I don't know anything more than that :/ I hope soon. It'd be fun to mess with the phone while my college break is going on still.
Sorry about the really slow replies. I should subscribe so that tapatalk notifies me.
I don't know when it will get here :/
But since you have it, do you know if the bootloader is unlocked/unlockable? Google is surprisingly of little use with this phone. I'd love to dink around with this phone since it's not my primary one (and I can't use cellular services on it)
Click to expand...
Click to collapse
All good, it takes time to develop these things anyways. I should have a stable TWRP build within a few days, and a CyanogenMod 10.1 (Android 4.2) build complete in the next couple of weeks.
The bootloader is something I am going to tackle tonight. As you can tell, there is zero documentation on the web for this device. In fact, it received more attention when it was a concept than it does now. So for now, I have no answer on the bootloader. I hope so, or all my work is useless lol. However, root is obtained at a bare minimum
Anyone out there that comes across this thread that wants to find information on modding this phone, PLEASE post your interest here. Trust me, you won't find any other resources.
lg locked bootloaders
I have the lg motion, I don't know how close it is to the mach but I've been following a thread for several months that has been trying to figure out a workaround for the locked boot loader. Google all things root guide for lg motion and you might be able to find a decent starting point for your phones maybe even help them figure out the motion
Ok, well I think, for now at least, root is all we are getting . I have managed to develop and compile ClockworkMod Recovery TeamWin Recovery, and Cyanogenmod 10.1 for it, but realized after all that work that the bootloader is not only locked, but also signed with a digitally encrypted key. Basically in laymans terms: We are ****ed. So, if anybody manages to shmooze either Sprint or LG out of these unlock codes, let me know and I'll provide everything else. Otherwise, anything I have made will brick every LS860 it goes on. Sorry guys.
Oh boy is like Motorola all over again... So no flashing recoveries even?
Sent from my Galaxy Nexus using Tapatalk 2
Hey!
Sent from my LG-LS860 using Tapatalk 2
Mgamerz said:
Oh boy is like Motorola all over again... So no flashing recoveries even?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thats correct. At least from my understanding. I could be wrong, but without the ability to unlock the bootloader i dont want to try flashing recovery. Too risky for me. Ill give anyone who wants to try my twrp build but i wont accept any repercussion for it doing anythin negative
Give me your twrp build then
I just rooted it. Was super easy.
Tried adb reboot bootloader. Did nothing. Tried adb reboot recovery. Recovered the device. Can't seem to figure out a way to have it download software. (like nvflash) Wonder if there's a special cable...
Sent from my LG-LS860 using Tapatalk 2
So I already bricked two, lol. Not going for a third. I really wanna root this phone. I went as far as getting the firmware which is a cab file. But then I guess you have to convert that to a kdz file. Then decrypt the kdz file. Well it appears you need to be an LG Service tech to use the program. Was hoping there was work around for all this,
Sent from my LG-LS860 using xda app-developers app
LG_Mach said:
So I already bricked two, lol. Not going for a third. I really wanna root this phone. I went as far as getting the firmware which is a cab file. But then I guess you have to convert that to a kdz file. Then decrypt the kdz file. Well it appears you need to be an LG Service tech to use the program. Was hoping there was work around for all this,
Sent from my LG-LS860 using xda app-developers app
Click to expand...
Click to collapse
I rooted it, it was easy using the sony tool that does the adb backup remount bug, but that's as far as I got. I uninstalled a bunch of crap off of the system partition and its a lot faster now, too bad I can't get that activation screen to go away.
Just pulled the newest OTA. I found it in /cache. I tried to get the URL but instead I made it so it no longer sees there's an update... I have the zip file however, and inside of it there is patches to just about everything in system, and updates to magazines, chrome, and LGBookmarksProvider.
There's also a command to install a recovery image:
#!/system/bin/sh
/sbin/write_recovery /dev/block/platform/msm_sdcc.1/by-name/recovery
Not sure if it's a good idea to flash that... forgot that it's still locked bootloader
EDIT: Finally figured out download mode... I just held all the buttons down when starting it and voila, it's there. I also hear you can use the LG Software update tool to flash back to stock, so we might finally have root that's safe
Does anyone have the BooksTablet.apk found in /system/app? I'm not sure why but it won't install the update cause the sha1 of that file fails I don't know where to find it.
Dont let this thread die! I noticed there was no dedicated forum for the LS860 development, I really enjoy this phone and would love some level of development for it. I can help as much as I am able.
jfm567 said:
Dont let this thread die! I noticed there was no dedicated forum for the LS860 development, I really enjoy this phone and would love some level of development for it. I can help as much as I am able.
Click to expand...
Click to collapse
Can someone rip me their BooksTablet.apk and BooksTablet.odex from their LS860 and PM me a link to it? I really am pissed off at the update prompt (I'm not sure why it's not working, I haven't touched it and I made sure I backed everything up... It won't validate BooksTablet.apk) I'm on the stock original version of the software ZV6 or something... not the ZV7.
I really don't want to go into sprint that much, though I might have to do that soon.
Edit: Just called sprint. They won't do anything for me and I'm not going to pay money for someone to reflash my phone. It's pretty ridiculous how factory images for devices aren't released. You know how many issues this would solve? That's why nexus devices are great. They're practically unbrickable.
Hey guys, try posting the mach in here so maybe it can get a forum for it.... And possibly some development.
http://forum.xda-developers.com/showthread.php?t=1660354
Hi, I have LG Mach (LG LS860) - the Root MANY ANDROID! [Upd: 17.04.2013] Sony method worked with software version ZV6, but I have purchased a new LG Mach with ROM version ZV7 (an update from Feb 20) - and this method runs but does not result in root - how can I roll this software version back or else get root in an alternative manner? - please help!
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too
Hello.
I wouldn't say I'm a noob, but maybe I am. Lol
I got a Hipstreet Aurora, HS-7DTB6-8GB, last year. Wasn't it's biggest fan, so I didn't use it. I recently got a Samsung Tab 3 7.0, of which I've rooted and flashed cwm recovery on it. I haven't flashed a rom on it yet, kinda waitin for CM to release for it.
Anyways, I decided to give my kid the Hipstreet. Then did some research on it and realized that I can root it and flash recovery on it as well.
So I rooted with Tasslehoff's rooting tool and flashed CWM recovery 6.0.2.8. Now I would like to install CM10 as found in original thread,
"http://forum.xda-developers.com/showthread.php?t=2343531"
Here's my question, and maybe here is the noob in me, I don't fully understand the specs laid out in the thread and what will work and what won't.
Can I install CM10 through the recovery in the state I have the tablet right now? Or is there things I have to be careful of. I don't feel like bricking it and going through those motions again.
At this point, can I just:
wipe/factory reset
wipe cache partition
*not sure if the delvic needs to be wiped*
install CM10 from sd
install google apps
install patch
reboot
and it's good?
Or am I going to have complications if I run it like that?
PLEASE HELP
just follow the instruction and it will be fine
iwjosi said:
just follow the instruction and it will be fine
Click to expand...
Click to collapse
I understand installing. I've done it on my kids Captivate. Im stuck on using terminal to figure out the modules, to see if I require touchscreen, g-sensor, and camera patches. I dont want to flash cm and g apps and not do the required patches. I inputed 1smod in terminal and said not found. Then entered getevent and it started running crazy script endlessly (didnt wait super long to see if it stopped). This is the part of the thread I did not understand. The module/terminal codes...
I figured it out and now it is runnin cm10. I looked up tutorial on android terminal. :good::good:
chubbs_aj said:
I figured it out and now it is runnin cm10. I looked up tutorial on android terminal. :good::good:
Click to expand...
Click to collapse
May I ask how well the tablet is working with the CM10?
bigbigbuddy said:
May I ask how well the tablet is working with the CM10?
Click to expand...
Click to collapse
Its running the same really. Even with the performance cranked up to 1008 CPU. It has a lot of lag and is finicky. In a nutshell... I bought my daughter a tab 3, lol. Now the all winner is my experiment tablet. But if all you have is an all winner, then I would suggest converting it as it gives you more freedom with the system itself. Like getting rid of garbage apps and such...
Hi everyone,
I just got my Shield today, and it have been a hard work setting it up
anyway, I have a few questions regarding rooting this thing:
1. Besides from some priviledges I get (ie: in Greenify, Backup apps, access to system partition), is it really worth rooting this thing? (I just found out that all the settings will be gone, everything has to be re-done again)
2. Is it dangerous? Is there a chance rooting screw-up something and this thing get bricked or constant error?
3. If so, is there a way to reverse (like phone ROMs)?
4. Do I have to re-root this thing after every nvidia system updates?
5. If so, is it a painfully long process to re-root?
Thanks everyone
siuking666 said:
Hi everyone,
I just got my Shield today, and it have been a hard work setting it up
anyway, I have a few questions regarding rooting this thing:
1. Besides from some priviledges I get (ie: in Greenify, Backup apps, access to system partition), is it really worth rooting this thing? (I just found out that all the settings will be gone, everything has to be re-done again)
2. Is it dangerous? Is there a chance rooting screw-up something and this thing get bricked or constant error?
3. If so, is there a way to reverse (like phone ROMs)?
4. Do I have to re-root this thing after every nvidia system updates?
5. If so, is it a painfully long process to re-root?
Thanks everyone
Click to expand...
Click to collapse
1 I root everything Android I have because of titanium backup. Being able to swap games to different devicesband not lose your data is worth it to me right there alone. Everyone finds their own reason I suppose.
2 and 3 it's really safe. Everything is readily available from nvidia and they are fine with customers rooting it. Even if the hardware breaks they will still RMA the device. But ya rooting it is pretty straight forward and there's several guides on it. There is custom recovery so you can create a nandroid if you mess something up. As long as you can access the bootloader You can restore the stock images via fastboot if you really mess something up.
4 and 5
Yes you have re root after each update but it's really easy to do. The hardest part of all this stuff is getting the drivers installed
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
1 I root everything Android I have because of titanium backup. Being able to swap games to different devicesband not lose your data is worth it to me right there alone. Everyone finds their own reason I suppose.
2 and 3 it's really safe. Everything is readily available from nvidia and they are fine with customers rooting it. Even if the hardware breaks they will still RMA the device. But ya rooting it is pretty straight forward and there's several guides on it. There is custom recovery so you can create a nandroid if you mess something up. As long as you can access the bootloader You can restore the stock images via fastboot if you really mess something up.
4 and 5
Yes you have re root after each update but it's really easy to do. The hardest part of all this stuff is getting the drivers installed
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thanks
I actually rooted it today after watching the Youtube video made by XDA-developers.
It was awesome and this thing is running fine so far.
siuking666 said:
Thanks
I actually rooted it today after watching the Youtube video made by XDA-developers.
It was awesome and this thing is running fine so far.
Click to expand...
Click to collapse
No problem
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
siuking666 said:
Thanks
I actually rooted it today after watching the Youtube video made by XDA-developers.
It was awesome and this thing is running fine so far.
Click to expand...
Click to collapse
Link to this video
CAuse im concidering rooting my shield too
hexitnow said:
1 I root everything Android I have because of titanium backup. Being able to swap games to different devicesband not lose your data is worth it to me right there alone. Everyone finds their own reason I suppose.
2 and 3 it's really safe. Everything is readily available from nvidia and they are fine with customers rooting it. Even if the hardware breaks they will still RMA the device. But ya rooting it is pretty straight forward and there's several guides on it. There is custom recovery so you can create a nandroid if you mess something up. As long as you can access the bootloader You can restore the stock images via fastboot if you really mess something up.
4 and 5
Yes you have re root after each update but it's really easy to do. The hardest part of all this stuff is getting the drivers installed
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I second this. Its quite refreshing to find a company that openly welcomes devs to tinker with their toys and utilize their devices to the fullest.