Related
Hi all,
With yrs of experience with software, hardware, and up to high-voltage instrumentation electronics I am STUMPED!
I have been trying to root/unlock/flash the antenna on a razr m so I can use global pre-paid carriers IN THE US.
I was able to acheive this on my HTC Rezound in under 30 mins using XDA. (Given this just had to be programmed).
The strange situation I am dealing with here ---------------------------------------
Droid Razr M - Goal is to run on Net10, just traded off my HTC Rezound.
Problem = I ran every rooting program available to me, they all are having problems seeing the device. However, USB debugging and "Allow access" are activated. Reinstalled new Motorola drivers.
Radiocomm === I have the program set up correctly, found XDA post on this, it gave the same directions as some youtube videos and howardforums. It simply wont recognize the device (if I could acheive this I would be done). I then troubleshooted that problem, installing more drivers,
Ended up manually trying to root the phone. Still a no-go! (YES I am using a motorola usb cable on a high speed port rear of PC)
Still all fails.
Next step was reinstalling motorola drivers 2.3.9 for windows 7 64bit again (after removing them via control panel)
Then went with using ADB drivers, also found some people had success using PDA net. Installed it after removing others, then tried running pda net with motorola drivers installed. Still a no-go, device not recognized.
(When loading radiocomm I get the message "this installation is intended for 32-bit OS versions only. Please use the 64-bit version on this machine.)
- Same message for 11.11.11 and 11.12.2
Next it tells me "The installer was interrupted before Motorola Datacard drivers 1.5.9 could be installed. You need to restart the installer and try again. (Reinstalled drivers 4-5 times) restarted.... reinstalled radiocomm etc....
While troubleshooting your radiocomm guide, I found Motochopper (also doesnt see device, and says already exists (reset phone to stock with adb). Then attemptted EPRJ_EasyRootICS_MultiOS_V1.5, which fails three phone restarts then closes. It my phone has been successfully rooted. Also wrong!
There has to be some sort of issues between PC USB drivers and the drivers on the phone. Maybe hardware?
My PC Specs
4gb ram ddr3 1600mhz
AMD x4 B50 (550BE x2 unlocked) OC to 3.8
ASUS P8N SLI mobo
1tb Hard drive.
ATI Raedon 2gb gddr5 graphics
I think these posts I along with others are following trying to hot rod the razr m are simply outdated. A new one where all of the knowledge learned needs to be put into one thread.
someone suggested everyone on the forum needs to take a test first? I think thats a great idea, wouldnt have people compiling other's work into a "one click flash" that does nothing but type some code for you, asking for donations. And no support, incorrect drivers links, advertising in posts everywhere! BLAH
If you took the latest update the rooting utilitys won't work they patched the root methods in these utilitys
Sent from my XT907 using Tapatalk 2
mattz101783 said:
Hi all,
WiLAH
Click to expand...
Click to collapse
Post your phone info please.
Phone Info
Razr M xt906.
system version 98.18.78.xt907.verzion.en.us
Android version 4.1.2.
build date Fri May 24 2013.
(PS ordered an unlock code yesterday. They automatically gave me a refund.
I had traded for this phone last week. Assuming the update from verizon was completed. I have been reading into this, however when doing my research I took this into consideration. So many mixed issues/ideas for how to "re-root" but due to this device not being very old, and the gentleman I traded for this phone is on contract through verizon, he had no idea what rooting was.
Making assumptions makes an ass, well I assumed being a global phone like my HTC Rezound, verizon prepaid told me they could set up the antenna in-store to work for net10. I guess I've made an ass of myself havent I?
Anywho, 60hour work week starting tonight, hope I get this working! (15hr days)
That is the unrootable, un-unlockable new UD.
hmm
It successfully rooted, then reverted like I read it would. I have rootkeeper installed.
nobody has had any success taking off the update verizon sent out that made it impossible to root?
Just today, I got stuck in sideload, whiped the cache, and did factory restore reset all.
Wondering if I could take it back to a previous version, then root/unlock, then upgrade ics outside verizon (custom)?
mattz101783 said:
It successfully rooted, then reverted like I read it would. I have rootkeeper installed.
nobody has had any success taking off the update verizon sent out that made it impossible to root?
Just today, I got stuck in sideload, whiped the cache, and did factory restore reset all.
Wondering if I could take it back to a previous version, then root/unlock, then upgrade ics outside verizon (custom)?
Click to expand...
Click to collapse
Do this:
with the phone on press all 3 keys at once and hold till the screen goes black ( about 5 sec.).
then let off the pwr key. you should be in the bootloader menu. Be quick cause there is a short timeout and it will reboot. Toggle the vol- to highlight fastboot and press vol+ what does it say? 3 means UL bootloader.
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.
download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.
RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...
Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I
Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.
AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2
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.
Been searching and trying various things to fix my bricked phone. For some background of what initially went wrong.
I had the phone rooted following these steps.
http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
and then also had installed safetrap. I then wanted to use a custom rom http://forum.xda-developers.com/showthread.php?t=2616221 from here so I booted into safetrap recovery. (Was running 4.4.2 at this point.)
First I did backup my existing system to the sd card (maybe this will come in handy later in fixing things?)
Then I went to install and selected the three files I was suppose to use.
After i selected them, I realized I hadn't wiped things, so I left the safetrap install and went to the wipe option. I wanted to make sure I wiped everything except the SD card and here is where I probably screwed up... in the advanced wipe I selected everything to be wiped except for the sd card. It did it's thing. I then went back and selected "install" and here is where things looked different... I figured I'd be back to the option to select what to install, but instead it just went to a terminal window and it showed 'something processing' (Can't recall exactly what it said) and it was just stuck there. I left it for a quite a while (10 minutes or so) and still nothing, so I decided I'd try to start over, so I popped battery out and rebooted.
That's when all I got was the samsung splash screen.
At this time I "was" able to get into both recovery mode and download mode (Not longer can get to recovery mode... probably broke it based on stuff I did coming up.)
So then I was at the stage of googling and researching what to do. The option that seemed to come up over and over was this one http://forum.xda-developers.com/showthread.php?t=2663545 and I would repeatedly try it and everything looked to go well (saw stuff in odin installing) but at then end it just says "failed."
This led me to try the keis approach which I also so recommended. The initial attempt failed so I then tried the keis emergency firmware recovery option, but apparently something is wrong here since I don't see my device listed and have no idea what the recovery code would be.
I also had tried first installing the two kernels I had used that enabled me to first root my phone (listed in the first link NC1 stock and NI1 stock) and then using odin as described above, but same result.
Note lastly, if I now try get into recovery mode, I get the yellow message about keis failed to install (I can get the exact verbiage if it helps.)
Sorry for the lengthy explanation but figured some background might help. I can still get to download mode and use Odin so I figure there must be something I can probably do? Any ideas what to try would be greatly appreciated. Maybe I need to try and flash with a different PIT and different firmware? I'm just not sure what to try.
First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen%20Shot%202014-11-27%20at%2012.13.45%20AM.png
:crying:
Thread moved to Q&A
Please remember the word "bricked" is used to describe a phone that can no longer power on at all
Soft--bricked or sponged is used to describe a phone that at least can still get into download mode or LEDs light, etc.
Thanks
FNSM
rickcr said:
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen Shot 2014-11-27 at 12.13.45 AM.png
:crying:
Click to expand...
Click to collapse
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Sent from my Nexus 9 using XDA Free mobile app
Thanks!
jd1639 said:
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Click to expand...
Click to collapse
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!
rickcr said:
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!
Click to expand...
Click to collapse
Glad you finally got it working
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I've been reading for some hours and did not want to bother you with one more beginner's question but I prefer to ask before rather than pulling my hair off and discovering that I did something wrong. Here are my questions.
I have a Nexus 7 2012 Wifi with android v5.1.1 running on it, extremely slow.
1)To flush a new ROM I saw one movie on youtube that was using the android default bootloader, but here on the forum I read (and later learned what it means) about TWRP. Do I need to first install TWRP on my Nexus 7? can you please help me with a link to a tutorial or even better to a youtube movie on how to install it.
2) I remember a long time ago I flushed the v5 ROM by using an OTG USB Cable, I can't use an normal cable right?
3) Which ROM to choose. I'm not that picky, I guess any would be better than the current one. I read that v7 is pretty good, but there are too many ROMs and I got lost in the acronyms. I need a ROM that will run as fast as possible (at least decently). I do not need any google aps, but I read somewhere that sometimes if you choose a ROM without the gapps (I guess this is the acronym used right) then you do not get even the Google Play. I need Google play to install Chrome and a few applications for my son. (to learn a second language: Duolingo)
More than I do not need. It would be good if the battery would last longer, but it's not a problem if I need to charge it every now and then.
I learned that the ROM that I need is called grouper (wifi only).
4) OTA means over the air. Now I guess that all the rooms for android v7 are unofficial ROMs (meaning not provided by google, sorry if I got it wrong). In this case, does the OTA refers to the security patches provided by Google to patch their OS? or does it refer to the installation of a new ROM without the USB cable, directly from the internal memory
5) I do not care about the internal data, I can delete it all, but I did a factory reset of a Samsung Galaxy A10 (a more recent tablet) and I regretted it dearly, because I had forgotten the username and password that I created when I first used the device, and then I had to take it to an official Samsung repair shop to have it fixed, as it couldn't be used without the original account (username and password). I guess this is not the case for older versions. I can of course check my current Google account that I created while using this tablet for the first time. I checked the Users on the tablet, and I can't really find a Google account, but just a local account. In any case, could anyone of you confirm that if I clean all the data it shouldn't be a problem to install a new ROM afterwards.
Many thanks for your time and efforts in answering the above questions, but also to develop new cool great amazing ROMs that bring old devices back to life.
I think the easiest way to go is using Nexus Root Toolkit and Pure Nexus MM rom. Using NRT is pretty easy as long as driver works. It'll unlock bootloader and install TWRP. After installing rom install Parrot Mod and tablet will be reasonably quick way faster than stock lollipop. Thats what I have and it's still usable.
Sent from my Nexus 6 using Tapatalk
Hjicons said:
I think the easiest way to go is using Nexus Root Toolkit and Pure Nexus MM rom. Using NRT is pretty easy as long as driver works. It'll unlock bootloader and install TWRP. After installing rom install Parrot Mod and tablet will be reasonably quick way faster than stock lollipop. Thats what I have and it's still usable.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi,
I guess I should be doing something similar with this tutorial (ok the NRT version is newer now).
https://www.youtube.com/watch?v=tdFQtmgHC5M
And then flush the custom ROM that you were talking about the Pure Nexus MM Rom, which is not in the above video.
Do I need an OTG USB cable for that? I need to be careful and test first as the USB port connection was phisicaly tricky (I need to ensure the connection and then do not touch the USB cable anymore so that it does not disconnect). I think if I'm very careful it should be working eventually.
Many thanks
Any USB cable that allows computer to recognize Nexus 7 as a device is ok. Before doing anything make sure that full driver test is successful. Next is OEM unlock which will wipe the device, then TWRP flash and root. Then flash stock from NRT and boot.
Next download PN MM rom, copy to some directory on Nexus 7, boot into TWRP, install, boot. Repeat same with Parrot Mod (flash from TWRP). After that tablet will be usable. ROM build that I have is MTC19Z
Sent from my Nexus 6 using Tapatalk
Hey guys listen up, your gonna love this! I have a grouper too and i have it using 7.1.2 tried your methods and ended up here, its incredible if you can do these things :
1) Change your data and cache to f2fs which wipes your internal storage.
2) Install crdroid ROM from this week with june kernel.
https://forum.xda-developers.com/nexus-7/development/rom-crdroidv3-8-3-nexus-7-2012-t3710834
3) DO NOT install GAPPs (for ultimate otherwise pico I guess but this beast is old and tired we are trying for ultimate efficiency.)
Ohh and use NRT 2.1.9 to install your select couple of apk's thats it for performance.
4) Despite all warnings try ParrotMod it works for me.
Literally many times faster than PureNexus..