Related
Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:
T679noob said:
Hey, I just got a Nexus 7 16GB, yesterday. I'm familiar with CWM, Nandroids, flashing, etc...
I don't have ADB installed and am hoping to get opinions on the toolkits I've seen. Are they a good way to go, to obtain root and get in a position to flash ROMs. And which one would you maybe suggest? I'm running Win XP.
I want to run this kernel: http://www.derkernel.com/jb-seven.php (Trinity Seven)
I'd like suggestions on which ROM to run. Something stable, barebones and running 4.2. AOKP would be nice.
Thanks for hearing me out. Excited to get off of stock. :good:
Click to expand...
Click to collapse
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.
phonic said:
If you are already familiar with CWM, flashing, etc., then don't use a toolkit. You don't need one. Use adb and fastboot to unlock the bootloader, flash a custom recovery of your choice and the superuser zip you prefer. You could do it in a few minutes. There are multiple guides if you require assistance. It's a Nexus, so there are no tricks - it's simple and straightforward.
Once you get the custom recovery installed, you can then flash your kernel.
I prefer stock on mine. I've had a 16GB, 32GB and now I have a 32/3G. While I do replace boot/kernel with more enhanced ones, I prefer the stock image. But if you want to try out various ROMs, that's up to you and your preferences. Just make sure it's 4.2 compliant.
Congrats, the N7 is awesome.
Click to expand...
Click to collapse
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.
T679noob said:
Well, I can't even get the USB drivers to work lmao off to bed. Frustrated and delirious =D
I used http://www.ibtimes.co.uk/articles/4...ndroid42-jop40c-jellybean-ota-cwmrecovery.htm as a guide, but really have no idea what to do with these drivers. Toolkit isn't even working right to install them.
Click to expand...
Click to collapse
What operating system and version are you on
nba1341 said:
What operating system and version are you on
Click to expand...
Click to collapse
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)
Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.
OK so I got the drivers installed. Appears it wasn't working because I had the floppy drive checked. Now I still don't see the device in My Computer and I have the yellow exclamation point on MTP, in device manager. I read that you need WMP 11, which I have. Not sure where to go from here.
T679noob said:
Whenever I choose the folder containing the drivers, when trying to update in device manager, it won't let me select the folder.
Click to expand...
Click to collapse
Try PDAnet for drivers also make sure usb debuging is enable on the nexus
flicnflack said:
Try PDAnet for drivers also make sure usb debuging is enable on the nexus
Click to expand...
Click to collapse
I was actually just getting on to say that turning OFF usb debugging now shows my device in my computer
Now I can't get ADB to work. This is a little ridiculous. Gonna change to a Win 7 PC, I guess.
I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.
rmm200 said:
I would strongly suggest you spend a week just using the device before you consider putting a new rom on it.
You will have no basis for comparison unless you know what you are starting with.
Click to expand...
Click to collapse
Yeah, I'm actually going to stay on stock for the time being, but I want to flash the OC kernel. Noticing a little more game lag than expected.
T679noob said:
Windows XP 2002 Service Pack 3
If you mean Android, it's 4.2 (JOP40C)
Click to expand...
Click to collapse
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
While I personally run Linux on most of my computers, I honestly prefer to use WinXP if I need to run Windows.
First, I like the GUI. It's straight, simple and to the point. It's also widely considered to be Microsoft's best OS. The corporate market continues to use it a lot, and went ballistic when MS decided to end-of-life it. Also, on the rare occasions when I use Windows personally, it's usually because I need to run some app or connect to some device that is picky. And when that happens, I've found XP to be the most supported version around. In fact, I run it in a VM because a DVR system we use at the front gate of our HOA, which requires some specialized software, won't run on Vista or 7.
And in regards to the Android SDK, I imagine it's much easier to get running on that platform as well.
I'm unlocked, rooted, with a custom recovery. Thanks to anyone who had input.
Miami_Son said:
I can never understand why someone with the latest gadget would insist on trying to make it work on such an antiquated PC.:silly:
Click to expand...
Click to collapse
Thanks for your help. I dunno what I'd do without you.
phonic said:
It's also widely considered to be Microsoft's best OS.
Click to expand...
Click to collapse
By whom? I've been using W7 since Beta and RC1 and have had few issues with it (Vista is another story). On the rare occasion something won't run on it there is compatibility mode. The point of my post was that if you insist on using an OS that is now 3 iterations behind the most current version and you are having an issue with a newer device that wasn't really designed for that OS, then expect to have issues with driver support, compatibility and general operation. I just thought it was interesting (funny, actually) that in a forum where so many members are hell-bent on getting the latest greatest version of Android on their devices someone would still be using XP on their PC.:silly:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
:sly:
Sent from my Nexus 4 using Tapatalk 2
SimonP2 said:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
Click to expand...
Click to collapse
Yes, uninstall and forget about root kits and look and (most importantly) learn from here http://forum.xda-developers.com/showthread.php?t=2010312.
This is also a good source to read: http://forum.xda-developers.com/showthread.php?t=1469909
Thanks for the suggestions, guys. I still don't know why Nexus Root Toolkit didn't do the job when it worked so well and easily on my Nexus 7 but in the end I used the hippowise.com rooting instructions (using Google Nexus 4 Toolkit) and it worked a treat so I'm a happy bunny again
http://hippowise.com/how-to-unlock-root-and-install-a-custom-recovery-on-a-nexus-4/
I know it's more sensible to do it manually so that I know what has happened but in this case I just wanted the job done as quickly and easily as possible. I'll look into exactly what happened when time permits.
Cheers,
Simon.
^^ Learning opportunity lost.
Ditto, I've heard nothing good about toolkits and never used them, and consequently have never had the weird problrms I hear associated with them. Set up fast boot, setting it up can be a pain sometimes but its a one time thing. Using it is too easy and it never fails.
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
SimonP2 said:
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
Click to expand...
Click to collapse
To be honest, the learning curve with manual rooting is very straightforward. Heck, I found it quicker to unlock and root manually than through toolkits. You are literally just inputting a few lines into command prompt.
Sent from my Nexus 4 using Tapatalk 2
I can confirm that I have the same problem. Stuck at "Booting TWRP Temporarily" logo, doesn't move... Nexus 7 2012 Grouper 16GB.
I tried a new "red theme" this morning.
Now I can't boot or even get into "Fastboot".
I was running CM 10.2 .
Done all the ADB tricks I know plus various tools.
Held various buttons over 30 second, even cussed at it.
Am I making a trip to Walmart later ??
thanks
Yeah
Same here. I can not get my linux ubuntu computer to even recognize it in bootloader mode. Very weird. I have all tools installed and I am in the right PATH. Done this many times with many other devices. This sucks.
jmm701 said:
Same here. I can not get my linux ubuntu computer to even recognize it in bootloader mode. Very weird. I have all tools installed and I am in the right PATH. Done this many times with many other devices. This sucks.
Click to expand...
Click to collapse
Got a refund.
Now trying to find another......really like this tablet.
Nevermind
I figured it out. I just forgot to do "sudo" first before running any of the fastboot commands. Ubuntu did not recognize the device until i did that. Once i started using sudo everything it recognized and running again. I knew there was no way i bricked the thing.
kdkinc said:
I tried a new "red theme" this morning.
Now I can't boot or even get into "Fastboot".
I was running CM 10.2 .
Done all the ADB tricks I know plus various tools.
Held various buttons over 30 second, even cussed at it.
Am I making a trip to Walmart later ??
thanks
Click to expand...
Click to collapse
Its really almost impossible to cripple the fastboot bootloader. I have a couple threads on this where I tried to ruin the fastboot different ways on both the nexus 7 2012 and 2013 modles and I could not do it.
There is also a thread on how to get the fastboot back with the right series of buttons I have to find it for you and post it as soon as I can.
androidfr33k said:
Its really almost impossible to cripple the fastboot bootloader. I have a couple threads on this where I tried to ruin the fastboot different ways on both the nexus 7 2012 and 2013 modles and I could not do it.
There is also a thread on how to get the fastboot back with the right series of buttons I have to find it for you and post it as soon as I can.
Click to expand...
Click to collapse
Im sure its a fairly simple fix, but the op gave up already and returned his tablet:thumbdown:
Hello, I have an a500 I rooted it a few years back, then took an update and since lost root. Kinda went back to messing around with phones and put the tablet on the back burner. The image ver. is acer_av041_a500_1.33.00_pa_cus1. I have tried one of the rooting options here and it did not root my device, . I can not find it now for some reason. any ways mainly I am trying to find out, is my rom on my tablet a stock version? can someone point me to a rooter that will unlock it thanks so much for any help.
the gingerbreak v1.20 apk is what i tried and it did not work.
first off i am not finding my version of rom listed any were in the official acer list. acer_av041_a500_1.33.00_pa_cus1 could acers ota of locked my tablet making me lose root but not flash their rom to my table? Or could the rom locked the boot loader? Any help at all even if to just point me in the right direction would be great, thank you
gage0727 said:
first off i am not finding my version of rom listed any were in the official acer list. acer_av041_a500_1.33.00_pa_cus1 could acers ota of locked my tablet making me lose root but not flash their rom to my table? Or could the rom locked the boot loader? Any help at all even if to just point me in the right direction would be great, thank you
Click to expand...
Click to collapse
Acer bootloaders have always been locked. Anybody wants to argue?
Now, first off, we need to know what version OS you are on.
If you are on ICS, with an ICS bootloader (give the version please) then there is no full root available unless you install the V8 bootloader from skrilax_cz.
Root involves full system RW. Not the half-root people promise.
MD
Moscow Desire said:
Acer bootloaders have always been locked. Anybody wants to argue?
Now, first off, we need to know what version OS you are on.
If you are on ICS, with an ICS bootloader (give the version please) then there is no full root available unless you install the V8 bootloader from skrilax_cz.
Root involves full system RW. Not the half-root people promise.
MD
Click to expand...
Click to collapse
First off thanks so much for the reply, i thought the boot loader was locked but was hopping it wasn't. First the tablet is working and this is the information i get off it.
adrodi version 4.0.3
image version
acer_av041_a500_rv16rb02_ww_gen1
build number
acer_av041_a500_0.009.00_ww_gen1
some of the problem i have had with some root methods is the fact that my only laptop i have right now has windows 8.1, and a lot of this stuff pre-dates windows 8, that and i am not really failure with 8 yet. I was able to disable the apc controls i think it was called, i was needing to disable it because this one script needed it disabled to try and root my tablet. But then i had a driver issue were windows 8 would not see the tablet.
another thing do not know if this matters or not but under image P/N it say unknown.
hmm, found some information i could not find before. according to another web site i do have an official os and that i am on ics. Still trying to find out why image p/n is unknown, and how to root.
gage0727 said:
another thing do not know if this matters or not but under image P/N it say unknown.
Click to expand...
Click to collapse
Welcome to acer :good:
P/N does not matter.
gage0727 said:
First off thanks so much for the reply, i thought the boot loader was locked but was hopping it wasn't. First the tablet is working and this is the information i get off it.
adrodi version 4.0.3
image version
acer_av041_a500_rv16rb02_ww_gen1
build number
acer_av041_a500_0.009.00_ww_gen1
some of the problem i have had with some root methods is the fact that my only laptop i have right now has windows 8.1, and a lot of this stuff pre-dates windows 8, that and i am not really failure with 8 yet. I was able to disable the apc controls i think it was called, i was needing to disable it because this one script needed it disabled to try and root my tablet. But then i had a driver issue were windows 8 would not see the tablet.
Click to expand...
Click to collapse
And you are right. Most of the stuff pre-dates win8. However, NVFlash doesn't matter.
I would prefer you do this under a Win7 machine if you can find one.
the only windows 7 machine i have access too right now is at work, and they have the dang thing locked up tighter then a drum. I am going on vacation at the end of the week, when i get back plan on getting windows 7 and putting it on the laptop. I have xp but the laptop is a 64bit system. Main thing for me is i get the information, everything i find i save it to my drop box account for now.
gage0727 said:
the only windows 7 machine i have access too right now is at work, and they have the dang thing locked up tighter then a drum. I am going on vacation at the end of the week, when i get back plan on getting windows 7 and putting it on the laptop. I have xp but the laptop is a 64bit system. Main thing for me is i get the information, everything i find i save it to my drop box account for now.
Click to expand...
Click to collapse
I'd give the babsector file a try on yr xp laptop, you never know it may do the trick....
The gingerbreak root file u tried is for gingerbread builds so try icsRoot altho it may not work with win8
If the updat.zip definitely don't work then you have to have the cpuid. Have u had the tab connected to the pc previous to your tabs troubles??? Usbdeview will retrieve the cpuid in this instance. You can d/l it from the cpuid guide. Also check the root guide in my Sig, a lot of useful files u need you can get from there.
Good luck and to @Moscow Desire a big, helllllooooo and kiwi hug 4 u too my friend and yes like u , I'm still lurking about the place
Rgds Donna
Sent from my HTC_PN071 using Tapatalk
I habe the cupid and the sbk#, just having trouble getting the drivers to work when i try to plug it in in apx mode om my windows 8.1 machine. Looking at getting windows 7 next week.
Ahh ok m8 algudz
Sent from my HTC_PN071 using Tapatalk
well i may be getting a windows 7 disk tomorrow and if i do and am able to get windows 8 off the laptop and windows 7 on i will try again tomorrow night.
Found what you where looking for : Acer_AV041_A500_1.033.00_PA_CUS1
Its on blackthund3r thread.
http://forum.xda-developers.com/showthread.php?t=1816560
Scroll down to civato post, he mentions he's got it.:fingers-crossed:
I didn't read all 13 pages, but that is a really good thread to have a look through. :good:
Hope this helps if your still looking.
---------- Post added at 03:01 AM ---------- Previous post was at 02:03 AM ----------
HasH_BrowN said:
Found what you where looking for : Acer_AV041_A500_1.033.00_PA_CUS1
Its on blackthund3r thread.
http://forum.xda-developers.com/showthread.php?t=1816560
Scroll down to civato post, he mentions he's got it.:fingers-crossed:
I didn't read all 13 pages, but that is a really good thread to have a look through. :good:
Hope this helps if your still looking.
Click to expand...
Click to collapse
Sorry wrong info, I jumped the gun. :silly:
Anywho, have you tried using virtual machine allowing full access to host PC, then either windows or Linux?
You could also try a liveCD.
That is if you like the windows 8's. Change to 7, set your BIOS correctly and watch partitions don't get screwy. I just had to install 7 the other day. The partitions got messed, so erased everything with gparted. Went into BIOS checked safe boot settings, wiped the key so it would reset user back to setup. Then started install without a hitch.
Hope that helps.
A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.
sinndissension said:
A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.
Click to expand...
Click to collapse
There are no drivers. That's what shows up when you're hard bricked.
Sent from my Nexus 5
Try this method http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Tried flashing stock image through fastboot?
No fastboot, no recovery, no anything. /:
I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.
sinndissension said:
I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.
Click to expand...
Click to collapse
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5
jd1639 said:
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5
Click to expand...
Click to collapse
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4
Mashed_Potatoes said:
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4
Click to expand...
Click to collapse
Dude, jtag is his only option. He's not going to find drivers. I'm not trying to be an a-hole just stating the facts.
Sent from my Nexus 5
qhsusb_dload is what is used to initially load firmware onto the phone. (From what ive read so far) so i cant imagine the company that does this are the ONLY people that the software to do so, unless theres some hardware stuff they do, (which i havent found any proof of this). Still worth a shot to me, and like i said, im just trying to give it a SHOT. Not looking for people to just say, "oh its not possible" unless they have experience with this sort of thing. Thanks.