i loaded 13.04 on my nexus 7 and i ran out of space and was like 'that doesn't seem right.' so i saw in gparted that i had tons of unformated room...so i went to format it and now the little dude won't turn on....i tried googling and didn't really see anything... btw i tried to boot into recovery with no avail. pressed the power button for like 5 minutes including various combinations with volume - the screen will not turn on. i also tried connecting via adb with no results.
any ideas?
Can you get into fastboot mode instead of recovery? And see if computer picks it up in fast boot mode?
Fastboot is where you need to be. When you flash the os in fastboot, make sure to use the commands given in flash all.sh. Otherwise, you could end up with only 16gb useable on a 32, or 8 on a 16, and so on.
http://forum.xda-developers.com/showthread.php?t=1776860 see post # 10
Sent from my Nexus 7 using xda premium
http://forum.xda-developers.com/showthread.php?p=31931117:thumbup:
Sent from my Nexus 7 using xda premium
esema1o said:
http://forum.xda-developers.com/showthread.php?p=31931117:thumbup:
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If the n7 is reporting incorrect space due to a bad previous flash, this will not help. It will still only read the formatted space available. Fastboot is the only way to correct the incorrect space issue.
Skyrocket on AOKP by R4ins
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
rebel1699 said:
If the n7 is reporting incorrect space due to a bad previous flash, this will not help. It will still only read the formatted space available. Fastboot is the only way to correct the incorrect space issue.
Sometimes, the wrong command can be used during a flash process, and can cause a larger capacity to be seen as a smaller one. There are no grouper releases for 32, 16, or 8 only. It is the same image for all. So, the flashall.sh commands help avoid it from being seen as the wrong size. That way, your 32 is not formatted and installed as a 16.
Skyrocket on AOKP by R4ins
Click to expand...
Click to collapse
Skyrocket on AOKP by R4ins
That's for your responses but I gave up (people on Ubuntu- arm irc told me there was no fixing.) and just had the wife exchange it. But I will definitely read those threads about using the whole memory
Sent from my Desire HD using xda app-developers app
qkall said:
That's for your responses but I gave up (people on Ubuntu- arm irc told me there was no fixing.) and just had the wife exchange it. But I will definitely read those threads about using the whole memory
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
So you broke it and exchanged it on the manufacturers dime right?
Sent from my Nexus 7 using Tapatalk HD
Wow, did they check to see if it was tampered with?
Good luck and will you uh block boot loader again ???
Sent from my Nexus 7 using xda app-developers app
When you formatted it, it probably also erased the boot loader. In which case, you're screwed.
Sent from my Nexus 7
veeman said:
When you formatted it, it probably also erased the boot loader. In which case, you're screwed.
Sent from my Nexus 7
Click to expand...
Click to collapse
exactly... the screen wouldn't turn on or anything...
and to those saying i'm ripping off the manufacture - get what your saying but i'm a broke dude. not the best excuse but i wasn't about to throw away 200 bucks...
Related
http://imgur.com/a/motAI
Coworkers bought his 32gb unit from Office Deport which was delivered today. It has ICS 4.0.3 and a bunch of test apps loaded. Also the screen DPI made it think it was a normal 10" tablet. He was really confused by the strange interface of it and lack of setup wizard and everything.
I would have just loaded the new firmware onto it but this unit has the screen lift issue pretty badly on the right side -- so he's going to return it. Can't believe they haven't sorted that issue out already.....
ICS,Tablet mode..
You have dev tablet
Try make Backup and send to forum
adrianblack said:
http://imgur.com/a/motAI
Coworkers bought his 32gb unit from Office Deport which was delivered today. It has ICS 4.0.3 and a bunch of test apps loaded. Also the screen DPI made it think it was a normal 10" tablet. He was really confused by the strange interface of it and lack of setup wizard and everything.
I would have just loaded the new firmware onto it but this unit has the screen lift issue pretty badly on the right side -- so he's going to return it. Can't believe they haven't sorted that issue out already.....
Click to expand...
Click to collapse
Seems pretty cool
Sent from my Nexus 7 using Tapatalk 2
Those apps could be fun to play with.. Possibly the binaries too for anyone who wants to get all retro and downgrade Android.
Sadly he wants a working tablet so is returning it -- meaning I didn't get any time with it. If I had more time I would have tried rooting it and TiBacking up all the various test apps. Funny they let stuff like this get released to the world.
adrianblack said:
...Funny they let stuff like this get released to the world.
Click to expand...
Click to collapse
They probably just "accidentally" install it on very few tablets, in hopes a developer gets a hold of it and does some cool stuff
Reminds me of how a person got a CR-48 test Chromebook with a BIOS on it (CR-48's had EFI on them), and that person uploaded the BIOS somewhere, and then anyone with a CR-48 could flash that BIOS, and then install any OS they wanted
espionage724 said:
They probably just "accidentally" install it on very few tablets, in hopes a developer gets a hold of it and does some cool stuff
Reminds me of how a person got a CR-48 test Chromebook with a BIOS on it (CR-48's had EFI on them), and that person uploaded the BIOS somewhere, and then anyone with a CR-48 could flash that BIOS, and then install any OS they wanted
Click to expand...
Click to collapse
Haha, ya, you would think. Of course, since the N7 is so open already, nothing really needs to be leaked. (Look at the recent full Ubuntu for N7)
those test apps are available. i have them all on my acer a500. There also is a version for jelly bean . but i cant find them They are on my computer here somewhere . grrr i need to do a fall cleaning .
Funny to see that there has been a 32GB with ICS from the beginning!
Sent from my Nexus 7 using xda app-developers app
erica_renee said:
those test apps are available. i have them all on my acer a500. There also is a version for jelly bean . but i cant find them They are on my computer here somewhere . grrr i need to do a fall cleaning .
Click to expand...
Click to collapse
Where are these test apps available at? My accelerometer is off a bit and would like to try and re-calibrate it.
Sent from my Nexus 7 using xda app-developers app
I had a set that worked with i think most or all ics devices.For some reason i cant find it. This might work im not sure. I have not tried installing this on 4.1 . USE AT YOUR OWN RISK...
If i remember where the others are i will post them. I have only installed on a500 and on my old ics phone. no longer have .
Have fun ..
espionage724 said:
They probably just "accidentally" install it on very few tablets, in hopes a developer gets a hold of it and does some cool stuff
Reminds me of how a person got a CR-48 test Chromebook with a BIOS on it (CR-48's had EFI on them), and that person uploaded the BIOS somewhere, and then anyone with a CR-48 could flash that BIOS, and then install any OS they wanted
Click to expand...
Click to collapse
Couple of things. First, Win8 RT relies pretty heavily on the UEFI BIOS API set. While not absolutely required, it would make writing the shim a pain. Secondly, trust me when I say that Google did not "accidentally" release the CR-48 UEFI BIOS into the wild. Things happen on the assembly line.
erica_renee said:
I had a set that worked with i think most or all ics devices.For some reason i cant find it. This might work im not sure. I have not tried installing this on 4.1 . USE AT YOUR OWN RISK...
If i remember where the others are i will post them. I have only installed on a500 and on my old ics phone. no longer have .
Have fun ..
Click to expand...
Click to collapse
Alright thanks. I'll give this a go sometime tonight and I'll let you know if it works or not.
Sent from my Rezound using xda app-developers app
No dice. Put it /system/app, rebooted, and it didn't show in the app drawer.
Sent from my Rezound using xda app-developers app
zZDave_Stud said:
No dice. Put it /system/app, rebooted, and it didn't show in the app drawer.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Set the permissions right?
Sent from my Nexus 7 using xda premium
I think to install that ..
Connect your computer to tablet thru usb..
cmd to the directory you unzipped the run the install.xxxx xxx x x ? .bat..
The above is from memory only. USE AT YOUR OWN RISK.. if i had the tab here i could be sure my son has my a500 right now.. Gonna have to confiscate it back i think he is trying to take ownership . Kids go figure.. ..
Yea no doubt. If a 32gb was just updated recently it wouldn't of had ICS. So this suggests that Asus had 32gbs back during original production of the 8s and 16s.
O relly!
Sent from my Nexus 7 using XDA Premium HD app
player911 said:
Yea no doubt. If a 32gb was just updated recently it wouldn't of had ICS. So this suggests that Asus had 32gbs back during original production of the 8s and 16s.
O relly!
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
They've gotta get rid of all them old 8gb chips lying around somehow!
Dear all,
I have recently rooted my Samsung galaxy note using this method:www .cursed4eva.com/root-galaxy-note/ which worked very well and i had no issues.
I then installed Beats audio pro from the play store and thats when i started to get issues like crashes and such so i uninstalled the app, then thats when i started to get a error message saying "Process system not responding" which would result in me losing control of my keyboard and i completely lost service and was unable to make calls etc(O2 UK).
I then performed a factory wipe and cleared the cache but this has made matters worse now when i reboot it only shows up for a couple of minutes then shows the "process system not responding" error message then goes to a blank screen with only the two lights at the bottom showing and i cant use my phone at all.
Please Help ill paypal anyone who can get my phone to work again.
Oh and Hi im Nathan nice to meet you all
Put the phone in download mode. Use pc odin to flash latest ICS rom.
Please PayPal Nokia model n91 10 million dollars or 5 million euros. Whatever is easier for u
Sent from my GT-N7000000000 using Tapastalker 2
Not sure what the point of the last thread was. It's possible that the hot fixed had a virus? Be careful about the sites you choose for Android tweaks, it's incredibly susceptible to viruses. I could be way off here.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Not sure what the point of the last thread was. It's possible that the hot fixed had a virus? Be careful about the sites you choose for Android tweaks, it's incredibly susceptible to viruses. I could be way off here.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
nope your right, they add loggers often. Happens with apps as well.
Jinksey, for a how to go to development section of n7000 section. Read stickies from dr Ketan. You will find step by step directions on how to follow nokias advice, as well as a proven safe method to root
here http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-N7000 using Tapatalk 2
SpyderTracks said:
Not sure what the point of the last thread was. It's possible that the hot fixed had a virus? Be careful about the sites you choose for Android tweaks, it's incredibly susceptible to viruses. I could be way off here.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Am I missing something here. Where did the virus come from?
It's not difficult to add things into an app. They're saying that someone could have embedded a virus in what he used for root, to hijack his phone.
Sent from my SGH-I777 using xda app-developers app
It's the supersu . zip from xda forums.
He did do what looks like a factory rs from stock ICS rooted.
Sent from my GT-N7000000000 using Tapastalker 2
As above poster said, try flashing stock gb.
Sent from my GT-N7000 using xda premium
No reward
Sent from my Amazon Kindle Fire using Tapatalk 2
asf58967 said:
No reward
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
lol, you did deserve one.
Lol
Sent from my Amazon Kindle Fire using Tapatalk 2
problem solved?
what Rom that you use?? what kernel??
I just got the 4.3 OTA upgrade and it fixed the low volume problem. Yay!!!
nastypup said:
I just got the 4.3 OTA upgrade and it fixed the low volume problem. Yay!!!
Click to expand...
Click to collapse
It also enables the fstrim feature by default so there should be no more slow downs.
Sent from my SGH-T999 using Tapatalk 4 Beta
I noticed that too.
Sent from my Nexus 7 using xda premium
TheLastSidekick said:
It also enables the fstrim feature by default so there should be no more slow downs.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm confused. I thought support for trim commands has been in since 4.2 or even earlier. I'm positive that the file systems were mounted with the -discard option before this most recent update. My understanding is that this causes trim commands to be sent to the flash whenever files are deleted. The tradeoff is that this involves a near constant but consistent performance hit, but keeps write amplification from getting out of hand. Is my understanding wrong? If so, how? If not, what has actually changed in 4.3?
---------- Post added at 12:44 AM ---------- Previous post was at 12:22 AM ----------
I checked the mount options for /data and /cache and I no longer see -discard. Did 4.3 remove the -discard option from mount in favor of running trim opportunistically when the device is idle?
Sent from my Nexus 7 using Tapatalk 4 Beta
thomase00 said:
I'm confused. I thought support for trim commands has been in since 4.2 or even earlier. I'm positive that the file systems were mounted with the -discard option before this most recent update. My understanding is that this causes trim commands to be sent to the flash whenever files are deleted. The tradeoff is that this involves a near constant but consistent performance hit, but keeps write amplification from getting out of hand. Is my understanding wrong? If so, how? If not, what has actually changed in 4.3?
---------- Post added at 12:44 AM ---------- Previous post was at 12:22 AM ----------
I checked the mount options for /data and /cache and I no longer see -discard. Did 4.3 remove the -discard option from mount in favor of running trim opportunistically when the device is idle?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
All I know is fstrim was introduced in 4.2 but wasn't enabled by default. It now is in 4.3.
bluecarbon said:
I noticed that too.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Sent from my SGH-T999 using Tapatalk 4 Beta
Thing is still sluggish when updating apps. Whats with that? It's a quad core right? Isn't multi core optimized for handling multiple tasks? My Nexus 4 doesn't skip a beat when it's updating
Sent from my Nexus 4 using Tapatalk 4 Beta
Why so many 4.3 threads?
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Cor-master said:
Thing is still sluggish when updating apps. Whats with that? It's a quad core right? Isn't multi core optimized for handling multiple tasks? My Nexus 4 doesn't skip a beat when it's updating
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
N7 has a companion core. It only switches to the quad core when needed. I think it thinks it doesn't need to.
Sent from my Nexus 7 using xda app-developers app
I think I know the answer, I was a bit tipsy when I posted that, trying to get my tablet back to 4.3 with a vodka buzz, so Nevermind lol. Lesson learned, don't drink and flash
Sent from my Nexus 4 using Tapatalk 4 Beta
Cor-master said:
I think I know the answer, I was a bit tipsy when I posted that, trying to get my tablet back to 4.3 with a vodka buzz, so Nevermind lol. Lesson learned, don't drink and flash
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
somehow i think that is a lesson for life in general.
I don't feel that 4.3 helped the audio on my N7 whatsoever. Some Youtube videos for me even at max volume are hard to hear with the sink running gently a few feet away.
Ok, please forgive me but if it's not enabled then how did one go about and enables this then.....
TheLastSidekick said:
All I know is fstrim was introduced in 4.2 but wasn't enabled by default. It now is in 4.3.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Cor-master said:
Thing is still sluggish when updating apps. Whats with that? It's a quad core right? Isn't multi core optimized for handling multiple tasks? My Nexus 4 doesn't skip a beat when it's updating
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Most likely the I/O try using ROW
As for the audio it seems the exact same as before, was an audio fix even mentioned by Google?
rastlin said:
Ok, please forgive me but if it's not enabled then how did one go about and enables this then.....
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
You don't. You run a script while rooted on anything below 4.3,and 4.3and above already have it enabled.
Sent from my SGH-T999 using Tapatalk 4 Beta
thomase00 said:
I'm confused. I thought support for trim commands has been in since 4.2 or even earlier. I'm positive that the file systems were mounted with the -discard option before this most recent update. My understanding is that this causes trim commands to be sent to the flash whenever files are deleted. The tradeoff is that this involves a near constant but consistent performance hit, but keeps write amplification from getting out of hand. Is my understanding wrong? If so, how? If not, what has actually changed in 4.3?
---------- Post added at 12:44 AM ---------- Previous post was at 12:22 AM ----------
I checked the mount options for /data and /cache and I no longer see -discard. Did 4.3 remove the -discard option from mount in favor of running trim opportunistically when the device is idle?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This is actually the correct answer.
myepicyear said:
This is actually the correct answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2384493
It would have been nice if Anandtech articulated this to begin with.
Didn't fix volume problem on mine
nastypup said:
I just got the 4.3 OTA upgrade and it fixed the low volume problem. Yay!!!
Click to expand...
Click to collapse
Is there anything you need to enable to see the increased volume? Mine has no change at all.
It actually made mine worse. Now the sound comes out all grainy and low.
Sent from my Nexus 7 using XDA Premium HD app
natoe33 said:
It actually made mine worse. Now the sound comes out all grainy and low.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It is louder for me, but I also never used any previous stock ROM, I went straight to custom. I could barely hear it without headphones, until the update.
Sent from my Nexus 7 using xda premium
TheLastSidekick said:
It also enables the fstrim feature by default so there should be no more slow downs.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well as I was reading in other threads in this forum and also being told there are no slow downs and its any app I have installed. So this fstrim is for something else
but i got lucky as hell,my a100 was locked up..and the nexus 7 toolkit saved my bacon..
You used a Nexus 7 toolkit on an A100?
Lol...he prolly used it to flash recovery since he didn't know how to set up fastboot/adb
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Lol...he prolly used it to flash recovery since he didn't know how to set up fastboot/adb
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
more than likely i had my kids running thru(and clicked something else),i may not be so widely versed that i know all the intricacies..of this or that..ive had some luck for the most part with understanding all the instructions (2 a100s,1 n7) and before i had tablets i had ipods,palms etc..so im not a total noob..just happy as hell that i turned it around is all..
mordeith said:
more than likely i had my kids running thru(and clicked something else),i may not be so widely versed that i know all the intricacies..of this or that..ive had some luck for the most part with understanding all the instructions (2 a100s,1 n7) and before i had tablets i had ipods,palms etc..so im not a total noob..just happy as hell that i turned it around is all..
Click to expand...
Click to collapse
Whatever works bro lol...I sorta figure that's how you pulled it off. You took a risk and this time it paid off. Get some practice with fastboot/adb now....its not really that bad (sounds like you already have the drivers installed and working )
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Whatever works bro lol...I sorta figure that's how you pulled it off. You took a risk and this time it paid off. Get some practice with fastboot/adb now....its not really that bad (sounds like you already have the drivers installed and working )
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
im scared to try again,couldn't root it ,so i was redoing everything(unlock,root,etc)...my nexus has a cracked screen so im using this in the meantime..course tomorrow i might decide that i cant stand the screen laggy quote...what luck though,considering many who had the same issue had no recourse but to send it back.
My tp was left uncharged for about a week and now I've got the dreaded white battery. I've tried everything. I cant get my tp to boot into download mode. It stays like that til it does, I plug it and try every button combo trying to boot back and just get white battery. Any feedback welcome. I'll pay $25 in amazon credit for something if someone wants to personally fix it. It's not worth it but I love my little touchpad.
havikx said:
My tp was left uncharged for about a week and now I've got the dreaded white battery. I've tried everything. I cant get my tp to boot into download mode. It stays like that til it does, I plug it and try every button combo trying to boot back and just get white battery. Any feedback welcome. I'll pay $25 in amazon credit for something if someone wants to personally fix it. It's not worth it but I love my little touchpad.
Click to expand...
Click to collapse
What is download mode? Moboot? Bootie? So you have something on your screen then? If so what.
Sent from my Nexus 6 with Pixel XL build.prop
bryantjopplin said:
What is download mode? Moboot? Bootie? So you have something on your screen then? If so what.
Sent from my Nexus 6 with Pixel XL build.prop
Click to expand...
Click to collapse
It's just a white battery symbol with am exclamation.
Have you tried tpdebrick_v004
Sent from my Nexus 6 with Pixel XL build.prop
---------- Post added at 11:39 PM ---------- Previous post was at 11:38 PM ----------
havikx said:
It's just a white battery symbol with am exclamation.
Click to expand...
Click to collapse
Wait exclamation or question mark?
Sent from my Nexus 6 with Pixel XL build.prop
---------- Post added at 11:45 PM ---------- Previous post was at 11:39 PM ----------
havikx said:
It's just a white battery symbol with am exclamation.
Click to expand...
Click to collapse
This should fix it unless you can get to the USB symbol. Try power+home+volume up for 30 seconds.
http://rootzwiki.com/index.php?/topic/38786-TPDebrick-v004
Sent from my Nexus 6 with Pixel XL build.prop
bryantjopplin said:
Have you tried tpdebrick_v004
Sent from my Nexus 6 with Pixel XL build.prop
---------- Post added at 11:39 PM ---------- Previous post was at 11:38 PM ----------
Wait exclamation or question mark?
Sent from my Nexus 6 with Pixel XL build.prop
---------- Post added at 11:45 PM ---------- Previous post was at 11:39 PM ----------
This should fix it unless you can get to the USB symbol. Try power+home+volume up for 30 seconds.
http://rootzwiki.com/index.php?/topic/38786-TPDebrick-v004
Sent from my Nexus 6 with Pixel XL build.prop
Click to expand...
Click to collapse
Power volume home doesn't get me to usb. It just sits at the exclimation.
havikx said:
Power volume home doesn't get me to usb. It just sits at the exclimation.
Click to expand...
Click to collapse
Ok then I would follow that first post word for word. If you have a question on a step ask.
Sent from my Nexus 6 with Pixel XL build.prop
What about a touchpad thats been dead for a year? I gave it to my daugter in law after i had updated to android with webos. I have two other touchpads i saved from death and they are doing well. I would like to resurrect the third one for my wife. I've got it on the touch stone with a charger plugged in also. So far nothing.
Sent from my Touchpad using XDA-Developers Legacy app
Rolfsted said:
What about a touchpad thats been dead for a year? I gave it to my daugter in law after i had updated to android with webos. I have two other touchpads i saved from death and they are doing well. I would like to resurrect the third one for my wife. I've got it on the touch stone with a charger plugged in also. So far nothing.
Sent from my Touchpad using XDA-Developers Legacy app
Click to expand...
Click to collapse
You need a PC, thumb drive, and all the files in the OP. It's really easy to use and should get you going.
Sent from my Nexus 6 with Pixel XL build.prop
Rootzwiki link not working to download TPdebrick
Rolfsted said:
Rootzwiki link not working to download TPdebrick
Click to expand...
Click to collapse
Well here is one with lots of files
http://downloads.codefi.re/jcsullins
And another
https://www.androidfilehost.com/?a=show&w=files&flid=5459
Sent from my Nexus 6 with Pixel XL build.prop
---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------
Rolfsted said:
Rootzwiki link not working to download TPdebrick
Click to expand...
Click to collapse
Let me know if there is anything missing, I might have it.
Sent from my Nexus 6 with Pixel XL build.prop
Well, maybe a sign of hope. I connected to my laptop and pressed home, volume up and power and the pc said it didn't recognize device. so that means something is there.
Rolfsted said:
Well, maybe a sign of hope. I connected to my laptop and pressed home, volume up and power and the pc said it didn't recognize device. so that means something is there.
Click to expand...
Click to collapse
Yeah tpdebrick is what you need. That is probably qdl mode. Be sure to follow the instructions. I think there is some videos on YouTube.
Sent from my Nexus 6 with Pixel XL build.prop
Ok....I can't believe I'm doing this. I have Ubuntu installed on a 128gb usb. Now what do I do? I'm pretty intimidated
Sent from my SM-N920V using XDA-Developers Legacy app
Rolfsted said:
Ok....I can't believe I'm doing this. I have Ubuntu installed on a 128gb usb. Now what do I do? I'm pretty intimidated
Sent from my SM-N920V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sorry just seen this. Did you download everything mentioned here https://forum.xda-developers.com/showthread.php?p=71584026
If so the step by step instructions is pretty easy to follow. With that said if you need help with a step let me know.
Sent from my Pixel XL using Tapatalk
I'm not doing something right in the terminal window. I have Ubuntu running on an external hard drive and TPDebrick in the download folder. I'm not typing the commands correctly or something. It's been a few days since I mesed with it. I'll try to get a screen shot to show what is going on.
Sent from my Touchpad using XDA-Developers Legacy app
Rolfsted said:
I'm not doing something right in the terminal window. I have Ubuntu running on an external hard drive and TPDebrick in the download folder. I'm not typing the commands correctly or something. It's been a few days since I mesed with it. I'll try to get a screen shot to show what is going on.
Sent from my Touchpad using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did you download the right Ubuntu listed in the codfi.re downloads?
Sent from my Pixel XL using Tapatalk
bryantjopplin said:
Did you download the right Ubuntu listed in the codfi.re downloads?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ok....my son is a computer genius....been in IT for 25 years. I video chatted and he could see my screen. He talked me through all the commands and got tpdebrick running. But so far nada....connect touchpad push power+home+volumedown for 30 seconds and nothing. I bet i've done it a hundred times. I'll keep trying.
Sent from my Touchpad using XDA-Developers Legacy app
Rolfsted said:
Ok....my son is a computer genius....been in IT for 25 years. I video chatted and he could see my screen. He talked me through all the commands and got tpdebrick running. But so far nada....connect touchpad push power+home+volumedown for 30 seconds and nothing. I bet i've done it a hundred times. I'll keep trying.
Sent from my Touchpad using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well that is not good news. Wonder if a new battery would help.
Sent from my Pixel XL using Tapatalk
bryantjopplin said:
Well that is not good news. Wonder if a new battery would help.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I bought 3 touchpads several years ago. I was able to get 2 into usb mode and install android. This one had android and webOS and my daughter in law let it go dead. So I have a couple of options.....keep trying tpdebrick, buy a battery off amazon or just keep it for parts.
Sent from my Touchpad using XDA-Developers Legacy app
Oh an additional post....after holding down all the buttons for 30 secs plus, the terminal window finally says:
QDL mode not found
Aborting
Sent from my SM-N920V using XDA-Developers Legacy app