So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
The harder this phone is to mod, the more it seems worth it Thanks for trying!
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
It's the preinstall partition from the atrix. There's no integrity check there so it flashes A-OK. I suppose the preinstall from any phone would work though.
You're the second one to do that successfully. I think it was discussed at length as a potential source for root, but we couldn't get the permissions we wanted out of it for some reason. I think it came down to nosuid, but I'm not positive. The root thread talks more about it.
thingonaspring said:
@pplude
Can you give any more detail on the root file you flashed to your droid 3?
Is it really from an Atrix? Are there any downsides to running this root partition?
The reason I ask is - the Atrix has been rooted, so perhaps this would be a good way to attack the droid 3.
Here's the Atrix root hack. Care to give it a try if you're still feeling brave?
http://www.motorolaatrixforum.com/m...s-f15/how-to-root-motorola-atrix-4g-t318.html
Click to expand...
Click to collapse
I used that on my Atrix way back (a month ago , to enable sideloading, I believe.
You want me to give it a try on the D3 (i.e., flash the /preinstall partition?)
That's what I used to break out of fastboot. Can't help us because of nosuid and noxec built in at the kernel level.
pplude said:
So, I nearly **** myself earlier when I nearly bricked my D3, so I though I'd post how I ressurected it.
So, I flashed a bad /data partition, and the bootloader kicked me out. Fastboot rebooted with a line (Last Flash Failed) and would NOT let me out after waiting, battery pulls, wipes, the works.
So, I flashed the ATRIX root.img, and the message went away. A Battery pull later and I'm back in business!
Click to expand...
Click to collapse
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
rynosaur said:
I see you said you've reflashed a half-bricked D3 with an image from Atrix? You said it was root.img?? Did you mean boot.img? I have an Atrix too, and don't see this partition anywhere. Did you or someone pull it with dd? If you have it, could you send it to me and tell me what command you used to flash in moto-fastboot or fastboot?
I tried flashing from the OTA and I'm **** out of luck at the moment, after borking /system trying to make the OTA update in recovery. It's been one headache after another with this fine device
Click to expand...
Click to collapse
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
psouza4 said:
What the OP is describing only works with fastboot. It sounds like you're able to get into recovery, a completely different system. Start a new thread if this is the case and I'll try to help you out.
Click to expand...
Click to collapse
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
rynosaur said:
I have flashed a partition that failed the verification check and now I can't do anything but boot into BP menu. Really, my problem and his are/were pretty similar, I think.
Click to expand...
Click to collapse
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
rynosaur said:
Thanks. I haven't located the /preinstall you're talking about yet, but I believe you're talking about the the /preinstall that was used to unlock the bootloader, or are you talking about the initial power cord-recovery hack? Anywho, I've been able to successfully flash /system and /boot, but I'm looping into BP menu. The fight continues . . .
EDIT: There are some partitions that the phone will not let me flash in Fastboot, and I think least one of those is my problem (like BP, for example). I keep getting a permissions error, and I am using moto-fastboot in linux or windows.
Click to expand...
Click to collapse
My success was using the Android SDK fastboot binary on Windows using PowerShell. And yes, it was the preinstall used to unlock the bootloader. I don't have a copy of it anymore, I seem to remember Ben64 on the IRC Freenode Channel #KrazyK giving it to me.
Huh -- so, despite the fact that Atrix4g won't do squat with regular fastboot, you're recommending it for this problem on the Droid3? Interesting. I did find the preinstall you're speaking of -- I actually found two, just in case. Thanks for your help so far, I will report back.
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
pplude said:
That's why I recommend using PowerShell (free download from Microsoft.com), it's a fully POSIX compliant shell and ADB/Fastboot is a lot more useful with it!
Click to expand...
Click to collapse
Roger that -- I've been using it since I installed Win7 two years ago. The only thing that's better is bash, in my opinion, and I have already seen where flashing a failed phone/bootloader only works with powershell, for some reason.
pplude said:
that's exactly it. Find the hacked /preinstall image for the atrix, mine was named (root.img). Then use adb fastboot to flash it to /preinstall. Then it'll reboot as normal. Boot into recovery, then wipe /data and /cache
Click to expand...
Click to collapse
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
jchenny said:
Can you help me out with a step-to-step instruction?
I cannot boot into recovery mode, it switch to AP Fastboot mode and says "BOOT FAILURE".
Click to expand...
Click to collapse
Did you already do a factory reset? If you haven't do not!
rynosaur said:
Did you already do a factory reset? If you haven't do not!
Click to expand...
Click to collapse
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
jchenny said:
I did try to factory reset...but again it reboots to the AP Fastbook screen again, and wouldn't let me reset it...
The phone still works, just somehow the camera does not work, I have tried 3 or 4 different camera Apps, and none works...
Click to expand...
Click to collapse
I'm guessing your drivers are messed up. Did you already flash the OTA or copy parts of the OTA into your /system directory?
Related
ADDING THE LINK HERE NOW : https://www.dropbox.com/s/it4ji9mlohfgagf/NexusOne-rescue-tools.zip
And please, a THANKS would be great if this helped you.
For some reason the phone one day just didn't boot. Was stuck on X logo.
We have tried alot... can't get into recovery, so flashed custom recovery, both RA and CWM... can't get into any of them, just stuck on X.
The phone was stock, and unrooted.
We managed to unlock bootloader via fastboot and root it.
Tried the PASSIMG.ZIP method - not working.
Any ideas?
.... please? =(
EDIT: Problem solved! Send me a PM if you're in the same seat, and i could send you all the files you need.
Oh, all you need is your FASTBOOT to work, no need for ADB, since it didn't work for me either.
EDIT #2:
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far (2012-02-10) 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
*** PM ME FOR THE LINK TO THE *.ZIP ***
Unzip, open an command promt, and:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
do the commands in that order, and when you are done reboot the phone
and see if it boots.
if NOT: keep on flashing ONLY the boot.img again and again until it
boots. it seems like the boot partition is corrupted and may need alot
of flashing until it works.
i think i flashed like 100 times before it booted. =)
There is also another recovery in that zip... RA's recovery. You can also try that one, no harm done!
Once you get it to boot, you will have FroYo 2.2 installed.
If you got it to boot with recovery.img just let android update to latest (2.3.7?)
If you have RA's recovery, just flash back recovery.img or you wont be able to upgrade to 2.3.7 "the stock way"
Can you boot without sd card?
Maybe Hardware--
rugmankc said:
Can you boot without sd card?
Maybe Hardware--
Click to expand...
Click to collapse
Sorry, no. Not booting when i remove sdcard either.
:/
May be hardware
rugmankc said:
May be hardware
Click to expand...
Click to collapse
How do i find out?
When we searched yesterday (google), we found some ppl who had fixed it, now i can't find those pages again..
So anyone here who knows what to try?
I've been in a similar situation before and just kept fastboot flashing system, recovery, and boot, and eventually I recovered the phone...
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
bassmadrigal said:
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
Click to expand...
Click to collapse
Thanks!
But we have tried to fastboot system.img, boot.img and recovery.img
Still stuck on X.
Is that code any different perhaps?
I can't try that now, that's why i ask instead of try it =)
All the commands that I posted are supposed to do is install a custom recovery and then boot into it. From recovery, you need to wipe your device by wiping the /system partition and doing a Factory Reset/Data Wipe. Then install whatever ROM you want to.
I've never tried using fastboot to install the system image, so I can't comment on that at all.
O M G!!!
i actually got the phone up and running!! everything is working now, i'm just too awesome
If anyone is interested, i could find out what i did, and which files i flashed, etc etc.
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Woa, check your PM
Check you inbox buddy! Tack på förhand
mrBira said:
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Click to expand...
Click to collapse
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
NismoDrift240 said:
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
Click to expand...
Click to collapse
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
mrBira said:
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
Click to expand...
Click to collapse
That makes perfect sense, I'm the same way. Thanks for getting back to me, here's to hoping I make 15...
same prob.
I sent you a PM, bro. Get back to me as soon as you can! Thanks!
Nexus One recovery boot error
PM sent. Thank you for your assistance.
i would like to know how to you solve the problem
No recovery for unrooted fones
first root ur phone using passimg.img
and fastboot flash bootloard oem unlock etc
and then try to flash a recovery using
fastboot flash recovery recovery.img
then u r done
Thank if it helps u
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Youngunn2008 said:
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
penser said:
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
Click to expand...
Click to collapse
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Dude oh my god I had this same issue on a different device, I forgot what the fix was. If I come up with something I'll let you know.
Sent from my MB886 using xda app-developers app
I think he has to get the motorola factory programming cable to fix it, since it acts like a os for you to load a new os to your phone. Sorry I don't know a link on where to buy.
penser said:
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Click to expand...
Click to collapse
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img
fastboot reboot
Click to expand...
Click to collapse
if everything is done right, your device is now ok.
Silentwidow said:
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Click to expand...
Click to collapse
Flashed stock with Myth about 3 times, didn't work.
Aingaran said:
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
if everything is done right, your device is now ok.
Click to expand...
Click to collapse
I'll try that. Thanks!
EDIT: It worked!
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
Click to expand...
Click to collapse
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
EDIT: It worked!
Click to expand...
Click to collapse
nice to hear it worked :highfive:
Aingaran said:
nice to hear it worked :highfive:
Click to expand...
Click to collapse
I thanked ya cause he didn't
skeevydude said:
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
Click to expand...
Click to collapse
I always flash all partitions. Its just good practice
Sent from my MB886 using Tapatalk 4 Beta
My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Edit: I have a feeling its due to a driver issue... during the downgrade the required driver probably changed... and thus disconnected in the middle of flash. If this is the case, then I feel like an idiot
diabl0w said:
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Click to expand...
Click to collapse
Try setting up another computer. You should be able to go into bootlader mode by pressing power and volume down buttons at the same time. Hopefully you have enought battery. If that doesnt work someone should be able to help you out.
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
r3pwn said:
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
Click to expand...
Click to collapse
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
diabl0w said:
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
Click to expand...
Click to collapse
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
r3pwn said:
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
Click to expand...
Click to collapse
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
diabl0w said:
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
Click to expand...
Click to collapse
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
r3pwn said:
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
Click to expand...
Click to collapse
I realized that after I downloaded the file and took a look at it further... thanks for your help and for bearing with me. It worked!
Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.