Related
Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app
monkeyass said:
Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.
Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app
monkeyass said:
Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
First -- In case you want to go full metal on P990, that means repartitioning, new BB and full flash, you need to flash. There is no other way than using NVFlash, as described in lovely thread in development by Stephan G.
Reasons - reformatting is not easily done from within phone which runs on these partitions, same goes for reflashing recovery from within recovery.
Second -- not sure why without USB?
Third -- there is CWM-possible way by using TonypAndHarsh's vlite V28E rom, yet this goes without new BB and with possibility of no call audio issue.
So, to repeat my answer to your main point, no. There is no way to fully install new system/BB without USB connection and PC. You have to flash it.
Hello. I think you can instal the new ICS without your usb cable.
1. you need to instal rom manager from PlayStore and flash from here the CWM recovery. I recomend you to instal the version 5.2.0
2. Make a nandroid backup before you do something to your actual rom.
3. Use titanium backup to backup all your apps and settings.
4. Put ICS rom from here http://forum.xda-developers.com/showthread.php?t=1959545 in your sd card (i think you have at leat a card reader and on adapter to put your microsd card) and follow the isntruction from the download page.
Good luck!
Cool thank you will try tomorrow.
Ant
Sent from my LG-P990 using xda app-developers app
ergosum said:
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.
Click to expand...
Click to collapse
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...
LarsPT said:
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...
Click to expand...
Click to collapse
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.
monkeyass said:
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.
Click to expand...
Click to collapse
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head
headshot21 said:
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head
Click to expand...
Click to collapse
Unfortunately not, it is running a version of gingerbread, can't remember which one.
monkeyass said:
Unfortunately not, it is running a version of gingerbread, can't remember which one.
Click to expand...
Click to collapse
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359
ocr66 said:
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359
Click to expand...
Click to collapse
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though
monkeyass said:
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though
Click to expand...
Click to collapse
Too bad to hear it didn't worked, do you mind if I ask, what exactly failed? I mean, it would be great to have some feedback of what you did and where you got stuck, so I might make some updates of the post, or upload another backup, or so
If you have any doubt about my post, I would be pleased to help you with that
thanks for giving it a try
cheers
Hi
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1
Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium
mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.
professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.
Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.
Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.
i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!
So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium
I had a TF701T tablet and dock I sold on ebay. It was neither rooted nor unlocked and worked fine. The buyer later complained saying it didnt work right, wouldn't read the SD nor an external drive. Now i know to read a external drive it needs to be rooted. But I advised it worked perfectly when it was sold. He filed a PP claim. It got here and guess what, it doesnt work right because he unloaded the bootloader flashed CWM on it. IDK what else was done but he lost the PP claim and rightfully so. But with that being said, the tablet would not turn off so eventually it will die. It will charge though. Where would I begin in flashing (I assume) the OEM software to make it usuable again?
Sounds like your buyer was a straight up dumbass.
The first thing I think you need to do is check the forum for the updated bootloader and recovery and go from there if you can install them. If you can't, idk.
You begin by determining which bootloader version you currently have: Boot holding Power and Volume Down until you see some small text. Let go, read the text and post it. Do not use the Wipe Data option from that page with CWM installed!!!!!!!!
Next you need to find the corresponding stock recovery (same firmware version) at Droidbasement and flash it in fastboot.
That done you download the Asus firmware for your SKU, unzip that file once resulting in another zip. If the tablet boots into Android, you can copy the second zip to the root of your internal storage. You should get a notification that an update is available. Confirm it and the stock recovery will flash it. That'll put you back onto stock. But there is no way to relock the bootloader - sorry.
If that does not work there's also a way to flash the stock firmware from a microSD. Let me know.
I wrote a pretty detailed guide on flashing a recovery and rom for the TF700. It's the first sticky in the TF700 General section.
Read that for the basics on getting fastboot to work.
The TF701 is very similar to the the TF700, but there are small but important differences and I wrote that guide for people trying to get AWAY from stock, so you're gonna have to extrapolate. But the basic steps are the same.
Ask here if not sure and flash only once you are clear on each step.
An easier option would be to flash one of sbdag's stock Asus roms. You still have to determine which bootloader you have now and if your CWM version is compatible. But if both are ok, you could just flash the rom and would be on pure Asus stock, but rooted with a custom recovery and could try to sell it as such.
There may be people who actually looking for a tablet all ready for flashing custom roms to it...
Lets face it: Nobody knows what that guy did to the tablet and you should disclose that to the next buyer. So I think you have a better chance to sell it to someone who wants to tinker with it. Swappa would be a good place for that.
Thanks guys. I finally got this back working.
weedahoe said:
Thanks guys. I finally got this back working.
Click to expand...
Click to collapse
Out of curiosity: How?
In the end, a data wipe though CWM that was installed by the buyer.
Thank God it was simple.
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...
hey guys hopefully ive gotthis in the right thread,
i have an amazon fire 7inch tablet i tryed to install cyno 12 onto it threw flashfire, everything went okay but then it restart and basically has got stuck on the logo of the cyno.. i have tryed getting intorecoverying by useing the power and down button .. seems to be no recovery screen there. i can tho get into boot screen, does anyone know how to get recovery screen on to it again to install stock rom etc.. its putting my head away lol
Without being able to boot into Amazon's recovery, your only option is to ask Amazon for a replacement if still under warranty.
If out of warranty and were on 5.0.x, you can try the unbrink with custom recovery but does not look promising.
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4.
There is a good chance when you flashed the new ROM, the order was not correct for the wipe. See:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
There are plenty of posts on this subject, you could search those and see if someone finally found a solution, but as far as I know, not yet.
shabuboy said:
Without being able to boot into Amazon's recovery, your only option is to ask Amazon for a replacement if still under warranty.
If out of warranty and were on 5.0.x, you can try the unbrink with custom recovery but does not look promising.
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4.
There is a good chance when you flashed the new ROM, the order was not correct for the wipe. See:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
There are plenty of posts on this subject, you could search those and see if someone finally found a solution, but as far as I know, not yet.
Click to expand...
Click to collapse
Concure - no unbrick solution that I'm aware of.