I just got a galaxy note for my galaxy nexus last night (traded) and I took it home and install goomanager and downloaded a rom that was "compatible" it saved to the directory that goomanager puts it in so I rebooted into CWMR and cleared cache / data etc then proceeded to install zip from SD Card. it started by saying flashing kernel 4% or whatever and then came back with an error. me being as bright as I am recently...I fixed permissions and rebooted thinking that it would at least let me back into recovery.
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot. Is there a way I can at least get it into Download mode? Hell stick a magnet on it to erase everything even?
I don't need another paper weight..I have an iPhone for that.
Can you boot into download? If so, use Odin to flash the correct kernel.
Can you boot into recovery? If so, flash the correct kernel.
If you can't do either one, your phone is bricked and you will need to send it for a repair. $50 and one week later you will have your phone back with stock 4.0.4 ICS rom. Its called a JTAG service, from www.mobiletechvideos.com. Many note user have gone there, from just this thing.
The jig that works with other phones 99% of the time won't work with the note.
Don't trust CWR. Get your roms from our developers.
Jig 99% Of the time won't work... you made that statistic up. If button combos aren't working it's definitely worth a shot, resistors are super cheap, especially compared to jtag which doesn't sound needed here yet.
And what do you mean. "Don't trust cwr get your roms from the devs here"?
That is a recovery... he didn't download anything with it, he used goomanager.
And even if he downloaded it from here...he would've flashed it in cwm... xda isn't a custom recovery...
So you tried holding the down volume button+ power to get it into download? Flashing a kernel will not remove your recovery/download mode unless you flashed a Rom not made for your device that installed something on said partition(s).
As for the jig...don't know statistics, but I am a one percenter. Worth a shot imo.
https://www.youtube.com/watch?v=6K-lvaAop2w&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I717 using Xparent Gray Tapatalk 2
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade. Josh from mobile tech gave me one of his he sells on the site.
As nun said, the combos should work, they are in the bootloaders, flashing a kernel won't effect those unless says kernel is for a different device, then you wouldn't get a single thing outta the device at all, no charging screen, no bootloop. Nothing. Whatsoever.
studacris said:
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade.
Click to expand...
Click to collapse
Right amigo 99% + 1% = 100%. You and Nunhugger are the only ones who said a jig worked for them. So actually its way higher than 99%. . . But you guys are ninjas. Your phone would probably reboot if you just told it to. I just wanted to kill the eventual jig question early.
And my response about CWR was because it sounded like he used the old app Rom Manager to see what was available. Clearly it was wrong so I told him not to trust it, and put in a plug for our developers.
When an update is released the forum gets slammed with complaints about bad flashes of incorrect kernels, and I have seen several members heal their phone by flashing the correct kernel. I just figured he was not accustomed to the button combos of the note and would get to that eventually. But if it was for the wrong device I wanted him to get his mind around the $50 and week wait.
Sheesh. . . decaf.
Well seeing that I can't Get into either mode and no button combos will work, I am assuming I need the JTAG. I figured an app like GooManager would have at least gave me the right roms for my device. it did say i717 but that could just be my memory playing tricks on me.
Man, I'm real sorry. But the JTAG service has been used by many, and with lots of positive comments. Good luck.
hahah thats okay, I mean its a great phone, definately not worth keeping in a draw collecting dust so I will go with the JTAG service. Thanks Guys!
You still have signs of life, it shows the charging animation, therefore your phone isn't bricked.
Do some searching on making a jig, I personally think it's well worth a try.
You could very well fix your phone for under $10 and have the satisfaction of accomplishing this yourself And have the know how to do it again...
It doesn't have the charging animation. just a dead black screen.
Then why did you say this?:
leveliv said:
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot.
Click to expand...
Click to collapse
That's more than a little misleading...
Will not boot...could mean many things.
From a easily fixed bootloop down to a brick.
Saying it was infinitely charging made it sound less severe.
if it weren't for that line, I wouldn't have bothered to tell you to use a jig.
JTAG it is
cris, why do you need to experiment with finding the proper resistance? Why should there be any variability in that circuit? Perhaps that is why some users have used up as many as six usb port replacement parts.
By the way, my 99% statistic is, like my entire post, just my opinion, and strictly a figure of speech. If it were a fact I was quoting I would have included a footnote. Remember those painful things? Do we have to include disclaimers for any figure we use? Sorry to mislead anyone!
I said "dead" because its not necessarily dead because a JTAG thing can fix it..and I said "charging" because to the normal person who didn't know anything was wrong with said device it would look like it was charging. But anyhow. I'm sending the phone out this week. I just don't understand why all the phones can't be as open as the devices straight from google.
You're phone is dead.
JTAG is akin to zombie, the phone needs disassembled and a special rig is needed to hook to the motherboard and flash EVERYTHING back to the nand at the prebootloader level.
The I717 is pretty much just as open as a nexus as far as easily modified and rooted...
No locked bootloader even which nexus have though it's a single line in a terminal to unlock, that step isn't needed on this device.
Only thing that isn't as open is the hardware drivers.
You may have flashed an incompatible kernel for a DIFFERENT device... and that on any phone will brick you.
And ranger not sure if it's the circuits within the phones that vary from device to device, ands seem to require a more specific voltage across those pins to trigger download mode
Or, if It's the resistors that are the variable. They are only rated within a certain +/- tolerance the cheaper ones having a larger margin of error.
And lol yes I am a ninja, but I didn't do anything special to my jig at all, I got mine from mobiletechvideos, funny enough it's worked on 4 captivates, a vibrant, 2 note 1s, and an s3, but didn't work on an s2 I was fixing.
the one I got from Goomanager was probably for the i700 which shouldn't even be able to happen.
They have video proof of them fixing phones with dead black screens from exactly what happened to mine using the JTAG Method. As far as I am concerned this thread can be closed cause I got the answer to my question.
the JTAG rewrites basically everything anyways so it is being sent out later this week. Till then I'll use a blackberry or something...Take care guys hopefully next time you see me post it will be to help someone and not asking for help
You'll be up and running by next weekend. By then, lots of exciting development will be happening on the released rom.
I doubt it, I live in Canada and have to send it to the states. It probably be closer to the weekend. Unless I expedite everything.
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Fastbird said:
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Click to expand...
Click to collapse
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
mjones73 said:
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
Click to expand...
Click to collapse
I don't know yet. I think I've still got my OG Droid hiding somewhere too.
I'm going to wipe it all and do a full factory ruu reflash and see if that doesn't help things out. I want to swap the outer bezel out because I closed my toolbox on it and ended up with a nice dent in the black chrome bezel. The LCD is fine, but I don't know about the digitizer considering the soft keys are really REALLY slow to respond anymore. I was thinking of rebuilding it for the fun and then I don't know. By rebuild I mean new circuit board because I think mine is the root of the issue. Won't know until after a factory reset, but the crackly speakers doesn't give me high hopes.
I really loved this phone. My biggest complaint was always the horrendous battery life. I have three batteries and could easily kill them all in a day with it. Guess I'm not done tinkering with it yet.
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Fastbird said:
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Click to expand...
Click to collapse
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
I liking it so far. Not reboots or freezes. I think that is what finally got me. For the last few months, I could not get the red to run smoothly on any roms dating back to bean stock and maybe before. Gummy had worked great but for blacks screens that also happen on kitkat. I'm still keeping the red for roms as I am not going to root the N3.
Sent from my SM-N900V using Tapatalk
REV3NT3CH said:
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
Click to expand...
Click to collapse
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Holy crap. I left it sit all night, and just turned it on and it booted! However, I try to turn Wifi on, and it just sits at "Turning Wi-Fi on......" so looks like wifi is definitely buggered. As it bluetooth.....same thing.
Just went into Settings and under Wi-Fi is says Error. Yep.....that's fubar.
It's SlimRom 1.6, just checked.
But the good news is that I now have USB Debugging enabled, so I can use Fastboot and relock and put a factory RUU on it. One last try, lol.
Fastbird, I had bought a used Rezound for my daughter over Christmas and when we tried it the wifi said the same thing as you stated, "turning on wifi". It would stay like that forever. I then went and put on ViperRez rom and then the wifi was fine. Not saying this will work for you as well but just a thought I had when I saw your problem. Good luck, hope it all works out for you.
Bryon
Fastbird said:
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Click to expand...
Click to collapse
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Also, the "turning WiFi on" issue, if it just stays like that, is usually an issue of a kernel/module mismatch... Remember when flashing a ROM or restoring a Nandroid when S-On you must flash the boot.img manually.
Sent from my Nexus 4 using Tapatalk
REV3NT3CH said:
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Click to expand...
Click to collapse
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Fastbird said:
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Click to expand...
Click to collapse
all ruu.exe files and ota.zips require s-off for downgrading..... ie. say your on an older version like 3.14.605.12 you can be s-on and upgrade to higher if im not mistaken...going s-off and redoing the whole phone from first to finish on ruu and ota's would be your last chance for that board without having to spend cash....and no offense you can probably get a used perfectly working rezound alot cheaper than 70 as well...is there any chance you deleted the wrong system files....only factory ruu will it restore original files...some deletions can cause these issues as well
The getting stuck turning Wifi on started BEFORE I tried a restore.
Shouldn't be a kernel mismatch because I used the same kernel for the nandroid CleamRom 1.6 and the other version of CleanRom I was running (I believe 1.7).
Only wiped Data, Cache, and dalvik cache. Several times for each.
The phone is acting EXACTLY like it was prior to the nandroid restore which is why I'm so sure it's a hardware issue. And I do mean exactly. 85% of the time after rebooting it boot loops for a random amount of time. Once booted in it's fine, save for Wifi and Bluetooth not working.
I understand I could get a replacement phone for cheaper to slightly more than te $70, but that's not the point. I like to tinker. I learn by doing. Gives me something to do.
Ok, relocked and trying to upgrade to a higher RUU which by what I read is acceptable. I flashed one of the earliest ICS firmware's and rom's, and the last RUU I could find was about 3 months later so I'm hoping it's good.f
*Edit* RUU took, trying to boot, but it's boot looping like normal. I think it's safe to say hardware is jacked at this point. It's getting into the UI then dying again, just like before.
Nappyloxs said:
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
Click to expand...
Click to collapse
How were you able to keep unlimited? My contract is over with my Rezound and I want to purchase a Galaxy S4. The best Verizon would offer me to give up my unlimited data is 6gb of data for $30.
Sent from my ASUS Transformer Pad TF700T using XDA Premium 4 mobile app
Hi, all..
As is probably known, before fastboot commands on the Nexus 9 will work, two things are required...
First, this option, in Developer Options, needs to he checked box ticked...
** Enable OEM Unlock **
...followed by... (with the device booted into it's bootloader)...
Code:
fastboot oem unlock
------
UNDER ABSOLUTELY NO CIRCUMSTANCEs SHOULD THIS PROCEDURE BE REVERSED.... unless you're running 100% stock.
It will very likely cause your Nexus 9 to be become permanently semi-bricked.
The device will boot, and it will charge... However IF YOU CAN'T BOOT ANDROID, AND RE-ENABLE. the ** Enable OEM Unlock ** option in Developer Setting's, then...
Code:
fastboot oem unlock
...will fail.
And you won't even be able to fastboot flash back to factory stock.
You can't even remotely boot a recovery, with...
Code:
fastboot boot recovery
...as this too, also requires an unlocked bootloader.
I know; I've tried.
-----
And this is my current predicament... My Nexus 9 now constantly bootloops into TWRP, with this message, at the top of the screen...
This is a development device not intended for production use..
Bootloader is locked, and I can't unlock it because I can't boot Android in order to set ** Enable OEM Unlock ** in developer options.
Unless anybody has any suggestions, my Nexus 9 is now pretty much useless.
Rgrds,
Ged.
OK.. Anybody know what the setting **Enable OEM Unlock** in Developer Options actually sets.
What flag it sets?
In terms of the underlying operating system, this MUST JUST FLIP some binary state flag, such that...
Code:
fastboot oem unlock
...now works.
There's gotta be some ADB command that will re-enable this, in the absence of a bootable version of Android.
Or some terminal command like a (dd=if>of command).
----
I've been at this for now, for 12 f**king hours...
I've tried everything I know.
At one point, TWRP, didn't bootloop and booted properly. But it was a pyrrhic victory, 'cos I had nothing on the device to restore. That was four hours ago... since then TWRP just bootloops endlessly.
I suspect that when., via the bootloader, I select the FACTORY RESET option, it's looking for the stock recovery... and which of course it doesn't find.... because TWRP is installed.
Indeed, I also suspect because Lollipop now runs encrypted, there are issues with mounting the data partition.
----
Well, I guess, my Nexus 9 is pretty much screwed, I think...
It'll make a nice Christmas decoration though.. It actually lights up!!!))). It's not THAT bricked. It still lights up..
----
In conclusion..
...and for guidance for others...
***
After rooting, and fastboot flashing TWRP...
--do not relock the bootloader.--
--do not disable. ** Enable OEM Unlock ** in Developer Options--
***
If you do both, and Android won't boot, your Nexus 9 is f**cked!!
You won't be able to flash anything; not even with a a toolkit like Wugs. I've tried.
Rgrds,
Ged.
Wow, really sorry to hear about your device! Maybe somebody here can come up with a fix for you...
Thanks for giving the rest of us a heads up!
Sent from my XT1053 using Tapatalk
@GedBlake
If you have time I'm willing to help you out, I've been testing some things and may be able to help, just let me know
Don't worry! Will let demkantor help you. Have you tried fastboot erase recovery and flash stock?
MRobbo80 said:
Don't worry! Will let demkantor help you. Have you tried fastboot erase recovery and flash stock?
Click to expand...
Click to collapse
He can't fastboot because his boot loader is locked. He can't unlock boot loader because he can't check that box. I knew this was gonna be problems as soon as I saw this setting. I guess I get what google was going for, but I still don't like it.
A nexus device should be able to recover from anything short of a hand grenade, for something this simple to semi brick a nexus is ridiculous.
Op, i taje it you can get to an adb shell? Or can you not even access recovery?
di11igaf said:
He can't fastboot because his boot loader is locked. He can't unlock boot loader because he can't check that box. I knew this was gonna be problems as soon as I saw this setting. I guess I get what google was going for, but I still don't like it.
A nexus device should be able to recover from anything short of a hand grenade, for something this simple to semi brick a nexus is ridiculous.
Op, i taje it you can get to an adb shell? Or can you not even access recovery?
Click to expand...
Click to collapse
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
demkantor said:
@GedBlake
If you have time I'm willing to help you out, I've been testing some things and may be able to help, just let me know
Click to expand...
Click to collapse
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
GedBlake said:
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
Click to expand...
Click to collapse
As long as you don't make the same 'mistake' again,(admittedly a mistake google should have considered before implementing the 'unlockable' flag) rooting/flashing a nexus is perfectly safe. If you stay unlocked, you can recover from anything. Performance with kernels and roms will continue to get better as the nexus 9s shortcomings are discovered and figured out. (There is a lot of new things with the 9-----lollipop, 64 bit architecture, etc). Personally I need root and an unlocked boot loader, but not everybody does.
Realistically with your device having access to a # adb shell your device was probably recoverable at the very least with 'dd', but you're back up so thats good. You paid for the no questions asked warranty and used it as designed as you should have, as much as it sucks at least you're back up.
Glad everything worked out for you.
GedBlake said:
Hi, di11igaf...
Thanks for your response... And apologies for my late response. I took a few days off from Android; I just needed a break. (And I have a new Nexus 9).
Yep; whilst TWRP was bootlooping, ADB did work... certainly, ADB devices yielded a device serial number... but I had nothing to 'push'.
I had no Nandroid backups on my laptop, and no Custom ROM. zips to 'push'. (I don't even think there are any yet, for the Nexus 9).
And even if I did successfully ADB push something, TWRP was bootlooping.
TWRP was essentially just useless, other than acting as an ADB gateway.
***
Hi, demkantor...
Thanks for your offer of help... but I now have a new Nexus 9.
Still interested though, in what you have in mind, as I suspect this particular problem is going to rear it's ugly head again sometime in the future. As other Nexus 9 devices will likely befall a similar fate to my Nexus 9....
-----------------------------------------------------------------
Hi, guys...
Thanks for your input, help and advice.
First, apologies for my language in my posts above. It's not often that I resort to expletives, even if disguised with asterisks. It was unbecoming of me, and I hope I didn't cause any offence.
On to the matter in hand...
After three days, I would dearly love to report that 'I fought the good fight', and discovered some ingenious method by which I resolved the problem... but alas I didn't.
The device continued to bootloop TWRP, and fastboot oem unlock continued to fail.
The bootloader itself was still accessible (by pressing & holding vol-down, followed by power on). This button press sequence, interrupted the bootlooping TWRP, and forced a reboot into the bootboader.
But the only real use for this, was to shut down the Nexus 9, as accessing fastboot was a sheer waste of time. With a locked and unlockable bootloader, nothing could be fastboot flashed.
The device was stuck, and with no way out.
A resolution.. but not a solution.
The Nexus 9 in question was actually bought for me, by a very close friend, for my 49th birthday on the 18th November. When she recently enquired how I was doing with it... well, as you can imagine, I was somewhat reluctant to admit that I'd screwed it up.
But eventually, and to my embarrassment, I admitted I'd made a bit of a pig's ear of it.
After she'd given me 'the look', and a sigh of exasperation, she revealed she'd also bought with it, a two year extended, no-quibble, anything-can-happens warranty. I have a similar warranty on my old Nexus 7, though I've never had any cause to avail myself of it on that older device. It adds about £80 to the price of the device. So, this morning, we both headed out to the local PC World from whence she bought the Nexus 9, and got it replaced: no questions asked.
So, I'm currently midway through setting it up again.
Needless to say, I won't be repeating the same mistake!
As it stands, right now, my replacement Nexus 9 is working just fine. And indeed, if it can be said that 'every cloud has a silver lining', it's that the replacement unit is actually 'better'. The original unit had some minor light bleed issues, and the back cover flexed inwards marginally. This new one has no lightbleed at all, and it just feels more robust, with no flexing of the back. Google and HTC really need to get these build quality issues sorted, and quickly. It's really just not good enough on a tablet at this price point.
In conclusion..
After three years of tinkering with Android devices... rooting them, flashing Custom ROMs, etc, this is the first time I've ever rendered one unusable. Not technically hardbricked, in the classical sense, with a black unresponsive screen... but certainly unusable and very likely unrecoverable.
And it's caused me to reconsider the whole point of rooting Android, and unlocking bootloaders.
What are the benefits of doing so? And what are the attendant risks?
And is it worth it?
Of course, it you're rich, and you can afford to replace a bricked device, then maybe it is worth it. Or if you happen to have a no-quibble warranty, (at an additional price), as I did... then perhaps, also it might be worth it.
***
Android today, is a wholly different beast to what it was when I first came to it back in 2011...
...with GingerBread, HoneyComb and, later Ice Cream Sandwich. Then, there where very significant benefits to rooting and flashing Custom ROMs... but today, I'm not so sure it's really worth the hassle, or potential financial cost if things go wrong. And it's been my experience of technology, that things can sometimes go horribly wrong.
***
I rooted my Nexus 9, just so I could run Titanium... A great app, but I feel it's no longer as relevant as once was... and to run Greenify, the power saving app. But if Lollipop delivers on it's promise of improved battery performance, with the so called Project Volta, then maybe even Greenify will become less relevant. And the Greenify app devs. have made great strides forward in making Greenify work in non-rooted mode anyway... I know; I have it running on my unrooted HTC One M8.
Maybe, at some point in the future, I will unlock the bootloader again, and root my Nexus 9 again... but there is going to have to be a pretty compelling reason to do so... And right now, I can't think of one.
I'm just happy to have a Nexus 9 that works one again... and I'm not inclined to take any further chances with it.
Cheers all...
Rgrds,
Ged.
Click to expand...
Click to collapse
I think you simply got a good scare off this story, losing a tablet for a checkbox unchecked is quite annoying.
I like to have the bootloader unlocked/s-off as soon as I get a device, so that I can do whatever I like with it the future. I personally couldn't live without root and custom roms, but I guess that my opinion could differ from yours
Sent from my GT-I9100 using XDA Free mobile app
totalnoob34 said:
I think you simply got a good scare off this story, losing a tablet for a checkbox unchecked is quite annoying.
I like to have the bootloader unlocked/s-off as soon as I get a device, so that I can do whatever I like with it the future. I personally couldn't live without root and custom roms, but I guess that my opinion could differ from yours
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
A good 'scare off' story is perhaps sometimes a good thing. It helps keep perspective. A 'chilling' perspective...
Rooting, unlocking bootloaders, and/or flashing custom roms/kernels/recoveries, etc... should, I think, NEVER be considered routine.
We're not talking about installing Angry Birds here... there is always going to be some element of risk to the device.
However, with all that said... I've decided that some valid points have been made... And so I have decided to bite the bullet, and root my replacement Nexus 9.
Currently backing everything up to my laptop...
I'm going to use CF-Auto root... And stay clear of TWRP. I have some suspicions that the presence of TWRP (which endlessly bootlooped), played some part in the previous debacle.
Hope my female friend, who bought me this device, doesn't learn that I'm messing with it again. She'll give me all kinds of hell if I screw it up again!!
Anyhow, signing off for now... progress report later.
Rgrds,
Ged.
Yay!!!! My Nexus 9 bootloader is now unlocked, and successfully rooted... and without problems.
I can now rest easy... .
Thanks once again, for everybodies input, help, advice and guidance.
Kind Rgrds,
Ged.
GedBlake said:
A good 'scare off' story is perhaps sometimes a good thing. It helps keep perspective. A 'chilling' perspective...
Rooting, unlocking bootloaders, and/or flashing custom roms/kernels/recoveries, etc... should, I think, NEVER be considered routine.
We're not talking about installing Angry Birds here... there is always going to be some element of risk to the device.
However, with all that said... I've decided that some valid points have been made... And so I have decided to bite the bullet, and root my replacement Nexus 9.
Currently backing everything up to my laptop...
I'm going to use CF-Auto root... And stay clear of TWRP. I have some suspicions that the presence of TWRP (which endlessly bootlooped), played some part in the previous debacle.
Hope my female friend, who bought me this device, doesn't learn that I'm messing with it again. She'll give me all kinds of hell if I screw it up again!!
Anyhow, signing off for now... progress report later.
Rgrds,
Ged.
Yay!!!! My Nexus 9 bootloader is now unlocked, and successfully rooted... and without problems.
I can now rest easy... .
Thanks once again, for everybodies input, help, advice and guidance.
Kind Rgrds,
Ged.
Click to expand...
Click to collapse
In my opinion, unlocking the bootloader and rooting is routine, on mine and on my close friends' phones. But, as I said, everyone is free to do whatever he likes with their device
I've always had bad luck with TWRP on my devices. I always use ClockworkMod recovery, even if someone specifically recommends TWRP for some task.
But don't be scared by this episode. From your post, you definitely know what you're doing and eventually hit a brick wall. Yeah, **** happens. It's an inherent risk of modding your device.
Just don't give up.
I just relocked mine prior to sending it back, however, I was stock.
I did a full wipe, then did a fastboot oem lock, then booted back into android, re-enabled Developer Options, disabled OEM Unlock option and wiped again - booted into setup screen no problem.
Now packed up ready to send back to Google.
StuMcBill said:
I just relocked mine prior to sending it back, however, I was stock.
I did a full wipe, then did a fastboot oem lock, then booted back into android, re-enabled Developer Options, disabled OEM Unlock option and wiped again - booted into setup screen no problem.
Now packed up ready to send back to Google.
Click to expand...
Click to collapse
that sounds like the logical proper order to do it.
Sent from my Nexus 9 using Tapatalk
Thanks for the warning. So to sum it up, if we need to enable oem unlock, we should be in stock 100%. Right?
albsat said:
Thanks for the warning. So to sum it up, if we need to enable oem unlock, we should be in stock 100%. Right?
Click to expand...
Click to collapse
Hi, albsat...
Apologies it's taken me so long to respond, but with Christmas coming up, and helping out with family related stuff, I've not had much chance this past week to post stuff.
---
Anyhow, to try to answer to your question...
Having thought long and hard about this problem... the problem isn't so much re-locking the bootloader with fastboot oem lock. I suspect this alone, shouldn't cause any problems.
It's the **Enable OEM unlock** setting in Developer Options, that is potentially dangerous.
---
If Android (for whatever reason) won't boot, (bootlooping, for example), and if all other possible remedies fail... you would normally just (re)unlock the bootloader with fastboot oem unlock, and fastboot flash a factory image.
BUT THIS WILL NOT WORK, if the **Enable OEM unlock** setting in Developer Options has also been disabled.
If the device is soft-bricked at this point, and Android won't boot such that you cannot gain access to Developer Options (in order to re-enable that setting), then the device is permanently soft-bricked.
And there is nothing that can be done to rescue the device. And this was my earlier prediciment, as previously described.
---
Let me see of if I can explain why I think this...
In a previous post on this thread, I wrote the following...
GedBlake said:
...anybody know what the setting **Enable OEM Unlock** in Developer Options actually sets.
What flag it sets?
In terms of the underlying operating system, this MUST JUST FLIP some binary state flag, such that...
There's gotta be some ADB command that will re-enable this, in the absence of a bootable version of Android.
Or some terminal command like a (dd=if>of command).
Click to expand...
Click to collapse
This was largely just desperate optimism on my part, in the hope that somebody might know of some ADB or terminal command... but having recently read the OP in this thread, I now know that my attempts to unbrick my previous Nexus 9, was likely a hopeless cause.
If, and as I suspect, the **Enable OEM unlock** setting in Developer Options, is an additional layer of security, then it probably CANNOT be circumvented by some ADB or terminal command.
It wouldn't be much of a security measure if it was that easy!!
Consider the following hypothetical scenario...
"Let's suppose a guy, a regular non-techy kind of guy, buys a brand new Nexus 9 tomorrow. Now, this guy knows nothing about fastboot or factory stock images or any of that stuff. Developer Options, by default, is hidden to him, 'cos he doesn't know you need to tap 7 times on the build number... And so, consequently also, the **Enable OEM unlock** setting is also hidden and by default, it's disabled.
He doesn't know this, and from his point of view, he doesn't want or need to know this. He just wants a nice tablet for browsing the web, checking his emails, posting on Twitter or Facebook, and maybe playing the occasional game. So he takes his new purchase home, and sets it up... with WiFi key and Google Account details, etc. He installs some apps from PlayStore, and copies over his music/pics/documents and other stuff from his laptop.
**But he's a security minded guy, so he decides to set a LOCK PATTERN or PIN NUMBER on his lock screen.**
One day, whilst going to work, he absent mindedly leaves his Nexus 9 on the train... which is then subsequently found by somebody who is not entirely honest. Instead of turning it into the police or the train stations lost property office, this scurrilous individual decides to keep the tablet for himself. He sees the device is PIN or PATTERN locked, but being a bit of an Android expert, he's non too worried about this. All he has to do, is unlock the bootloader and fastboot flash a factory stock image, and the stolen device will be his...
...Or so he thinks!!!
His first stumbling block (and upon which successfully flashing a factory stock image depends), is first unlocking the bootloader... and which of course will fail, because the lawful owner NEVER enabled **Enable OEM unlock** in Developer Options. Indeed, he wasn't even aware that such a setting existed. And our opportunist thief cannot boot Android in order to enable this setting, because he is not in possession of the LOCK PATTERN or PIN CODE required to get past the lock screen.
He is in possession of a useless tablet."
So, in this scenario... the setting **Enable OEM unlock** in Developer Options, has served it's purpose, in rendering the Nexus 9 useless to somebody who has no lawful right to it, and why I think that there was no possible way of salvaging my original Nexus 9. Any such method would undermine the whole point of it.
---
So, in conclusion...
Re-locking the bootloader is probably safe... The danger is ALSO, AND AT THE SAME TIME disabling the **Enable OEM unlock** option in Developer Options... and is risky, as you're potentially disallowing the bootloader from EVER being unlocked again.
And if Android won't boot... FOR WHATEVER REASON, there is NO WAY of re-enabling that setting.
So, once you've enabled it, my advice is to NEVER disable it... regardless of what you do with the bootloader lock state.
---
Anyhow, I hope my lengthy post sheds some light on all of this... And is of assistence to whomever has the patience to read the whole damn thing.
Sorry, but I do tend to waffle on at times.
Kind Rgrds,
Ged.
My case is similar, the only difference is that I never changed the recovery. After a few days of it working ok, at the startup it just stays at the Google logo.
Tried a Factory Reset and Wipe and not yet a single change. Next step would be to just flash the stock ROM, but wait! Developer Options was never enabled nor was Enable OEM Unlock.
I bought this $450 tablet in the US and I live in Brazil and now I cannot even return it. This is how dumb the decision to add this toggle was. And I tought Google made the device for developers.
dirceucorsetti said:
My case is similar, the only difference is that I never changed the recovery. After a few days of it working ok, at the startup it just stays at the Google logo.
Tried a Factory Reset and Wipe and not yet a single change. Next step would be to just flash the stock ROM, but wait! Developer Options was never enabled nor was Enable OEM Unlock.
I bought this $450 tablet in the US and I live in Brazil and now I cannot even return it. This is how dumb the decision to add this toggle was. And I tought Google made the device for developers.
Click to expand...
Click to collapse
You're fine. Just find the factory update.zip and install it via factory recovery, along with a userdata wipe.
After a few tries the factory reset was well succeeded. Thanks for the info though. I had no knowledge that I could flash the stock version via factory recovery. I guess I'm back to the noob pack.
Same just happened to me and I'm stuck. Is there any way to even use TWRP? I can boot into it but it can't mount storage which makes it useless afaik. I was running stock rom and everything except recovery..
You still have no answer to your problem?
Edit: after trying factory reset through the bootloader the recovery won't boot anymore..
My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
henderjr said:
My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
Click to expand...
Click to collapse
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
henderjr said:
...I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader...
Click to expand...
Click to collapse
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's via fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
GedBlake said:
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make available factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's with Google's factory stock images, which can only be flashed with fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
Click to expand...
Click to collapse
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
henderjr said:
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
Click to expand...
Click to collapse
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
madbat99 said:
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
Click to expand...
Click to collapse
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
madbat99 said:
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
Click to expand...
Click to collapse
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
henderjr said:
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
Click to expand...
Click to collapse
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
I don't think I've ever used my N9 camera either. Regardless I'll take my time
Indeed. Once you've gone around all of the edges (I used my fingernail) to prise/detach the back, I would suggest some light finger pressure on the camera to 'pop' it out of its hole, before lifting the back away.
Sent from my moto g(6) using XDA Labs
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
I ordered mine from there and they sent a toolkit with it too.