I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck
Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.
mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.
Related
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
If you've familiar with this problem and can direct me to regaining factory settings I'd greatly appreciate.
Used Nexus Toolkit to root, an had Twrp recovery. Had no backup w/Toolkit but did have a Nandroid backup....to no avail. Can't access it..
I still can get to bootloader and recovery of course but have a "NO OS" sign on the device.
A step by step from anyone in the community greatly appreciated.
Thanks
You could flash the system image through the root toolkit
I used wugs. And as long as you are boot loader unlocked and can access boot loader you are good. I somehow magaed to delete my OS, and my recovery so nothing worked! Used wigs, clicked flash stock and unroot. Checked the box for soft bricked or bootloop and it downloaded everything and flashed it onto my phone and it was fixed in 5 mins!
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
Additionally if you plug your phone into a comp while in recovery it should mount the storage on your PC so you could always dl a ROM on PC and move it over then flash.
Yea use wugs toolkit to flash back to stock. Easy fix
See this thread:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Wow the wugs toolkit is amazing. Thanks
This is exactly why I dislike toolkits... They're written by others, and you can never be 100% certain what's going on under the hood. I personally find it easier to simply run the fastboot and adb commands, and be done with it... If you make a command line mistake, the image simply won't flash, in which case, your system is left untouched. If you make a mistake with a toolkit, you could end up with a very expensive brick on your hands.
I'm in no way trying to denigrate toolkit devs or users; I'm simply giving my opinion on what I find to be the easiest, most risk-free method for flashing factory images and boot images. Recoveries are fine for day-to-day zip flashing, but when I need to do a bit more, I find fastboot and adb are the way to go. ?
jjhiza said:
This is exactly why I dislike toolkits... They're written by others, and you can never be 100% certain what's going on under the hood. I personally find it easier to simply run the fastboot and adb commands, and be done with it... If you make a command line mistake, the image simply won't flash, in which case, your system is left untouched. If you make a mistake with a toolkit, you could end up with a very expensive brick on your hands.
I'm in no way trying to denigrate toolkit devs or users; I'm simply giving my opinion on what I find to be the easiest, most risk-free method for flashing factory images and boot images. Recoveries are fine for day-to-day zip flashing, but when I need to do a bit more, I find fastboot and adb are the way to go. ?
Click to expand...
Click to collapse
To elaborate more on this, http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
I completely agree with jihiza here 100%
Its essential learning how to use adb/fastboot. Its not difficult to do and pays off in the long run.
how did you get your computer to recognize the device? Everything I've tried to this point says "no adb device"
edit: I got everything to flash manually.
papi5120 said:
You could flash the system image through the root toolkit
Click to expand...
Click to collapse
Or you could just fastboot it Root Toolkits make zero sense to me. Takes longer to Download the toolkit than it does to just fastboot the device.
Toolkits are great for phones that are good for phones with out fastboot but a nexus I feel that people never learn how or why they work stuff like this happens people don't know what to do.
I have wiped the System partition before, usually on purpose when flashing a ROM. There have been a few times that I either thought I had a backup which turns out I didn't, or the ROM I downloaded is in a mysterious "0" folder that twrp refuses to see. It's inconvenient yet but easy fix.
Use twrp to adbsideload if you have a ROM saved to your computer of I can fastboot factory image. No need to panic worst case scenario I don't have a phone for a day I do this with no computer and am gone for extended period of time
Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!
Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb
Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
or fastboot wipe user data and cache.
nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.
simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.
simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......
paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....
FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!
BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk
So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help
I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.