Related
Edited May 16 2012
Hi all,
Due to confusion and scared people I have decided to post simple instructions on how to unlock the bootloader on GB 2.3.4. I just received my Bell Atrix 4G, unlocked it for rogers and then rooted and unlocked the bootloader. I was confused by the pudding instructions, so I decided to recreate them In my own wording.
I take no responsibility for anything that happens to your phone or your heart stopping while you wait for your phone to reboot or if it is stuck on moto screen etc...
Credit for original tutorials go to the2dcour, romracer, Nottach, Faux123 and the others for all of their hard work.
Requirements:
1.Create a folder on your desktop named motounlock
2.Go here: forum.xda-developers.com/showthread.php?t=1136261
Scroll down to where it says "RSDLite/Windows Drivers/Sbf_flash"
UPDATE: Download RSDLite from here : http://www.multiupload.com/T6NOEBKKLO . If you need x64 bit Drivers use the other link. thanks AnguishedEnd!
download the first two files for windows (RSDLite 5.5 link, x64 Windows drivers)
download the third file for linux/mac
3.Scroll until you see the big word "Unlock"
where it says "Unlocker only SBFs" download the second file UNLESS you are on ATT.
4. Scroll down to the word "Root" and download 'Fastboot' for your OS
5.unzip all of the files you just downloaded into the motounlock folder on your desktop
6. open the folder, install RSDLite, and afterwards install the Drivers.
Then follow these instructions
Power Down your atrix
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD. Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Navigate to your desktop and open the motounlock folder and select the file named intl-fix-try1.sbf ( IT WILL BE DIFFERENT IF U ARE DOING THIS FOR ATT)
Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!
Press the “Start” button. The Flash actually failed for me, wait for it to complete to 100% it may FAIL or PASS! just make sure it gets to 100% leave your phone sitting for about 10 minutes AFTER RSD SAYS FAIL/SUCCESS.
If nothing is happening after 10mins, perform a battery pull. Power the phone on while pressing vol-down. “Fastboot” Will show up on screen. DONT PLUG IT IN YET. Press volume up and let your phone sit. You will see “Starting Fastboot protocol support" LEAVE IT UNPLUGGED
press the windows key + R on your computer, type cmd and press enter
command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
Plug your device back into usb now
back in your command prompt window type "fastboot oem unlock" no quotes
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####
fastboot oem unlock ####
fastboot reboot
your moto will reboot. UNLCOKED!!!!!!!!!!!!!
Proper Recovery:
1. After your bootloader unlocked go to this link http://forum.xda-developers.com/showthread.php?t=1204500
2. Scroll down to where it says "ALL USERS" and download your favourite colour. (NOT THE ZIP VERSION) Place it in the motounlock folder that you have on your desktop.
3. Press the windows key + R on your computer, type cmd and press enter
4. A Command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
5. type "fastboot devices" Press Enter.
5b. type "fastboot erase recovery" Press Enter.
5c. type "fastboot flash recovery recovery-atrix5.img" Press Enter.
Wait for the command prompt to say : "writing 'recovery'... OKAY ['The amount of seconds it took here']"
5d.type "fastboot reboot"
DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'
You will be set 100% !
Installing a custom ROM (Any custom rom will work as long as it has unified kernel/Faux Kernel)
MOST ROMS WILL COME PRE-ROOTED! Just saying, to avoid confusion.
I will be using Nottach's Darkside ROM as an example, because Cyanogenmod does not have features included with original moto rom (this one is way more NOOB friendly) But this is COMMON PROCEDURE for almost every rom so be sure to follow this for whatever ROM you want to use.
1. Go here http://forum.xda-developers.com/showthread.php?t=1222108
2. Scroll down to where it says 'DOWNLOADS' and download the most current version.
3. When it is finished downloading you will have a ZIP file named something like "TheDarkSidev2.8.0-Wipe.zip"
4. Plug your phone in to your computer and transfer that file to your INTERNAL MEMORY.
5. MAKE SURE YOUR PHONE HAS DECENT CHARGE! I would say at least 50 percent. 70+ is recommended, I have done it with 40 + though.
6. Power Down your Phone.
7. Hold The POWER Button + VOL DOWN. DONT PRESS VOLUME UP WHEN YOU SEE FASTBOOT! Instead...
8. After fastboot shows up click volume down until " Android Recovery " shows up, about 7 down clicks. THEN press volume up.
9.
***FIRST TIME ROM FLASHERS ONLY!!!!!!***
WE ARE GOING TO BACKUP YOUR ORIGINAL ROM SO THAT IF YOU EVER DERP YOU WIL ALLWAYS HAVE A SOLID BACKUP
Press VOLUME DOWN and go to backup and restore. Press the POWER BUTTON
Press the POWER button on backup
Select where you want to put your backup (internal or external memory)
Backup INCLUDING WEBTOP! (if you ever think you will use it)
Wait for it to finish.
***********************************
10. Ok now that you are in android recovery you have to do a few things before flash.
a. Scroll down to "wipe data/factory reset" PRESS POWER. say yes to EVERYTHING until it goes back to the main screen.
b. scroll down to "wipe cache partition" PRESS POWER. say YES. Wait for return to main menu
c. Scroll down to"advanced", click "wipe dalvik cache" Go back to "advanced", "wipe battery stats
11. At the main menu, Scroll to "install Zip from SDcard" Press POWER.
12.scroll down to "choose zip from internal sdcard"
13. select the ZIP file that you saved to your INTERNAL memory. If you're using darkside the file name is "TheDarkSidev2.8.0-Wipe.zip"
14. Scroll down to "YES - install TheDarkSidev2.8.0-Wipe.zip" Press POWER
15. Let your phone work its magic!
16. When it is finished installing, you will be returned to the recovery main menu.
17. click "reboot system now"
18. Let it boot! This can take anywhere from 10 seconds to 5+ MINUTES! if you dont see it move from the "unlocked" screen after 10 minutes Perform a battery pull and power on again. If it hangs then all you have to do is go into recvoery click "backup and restore" and restore your original ROM. Or like me, have one of every kind of ROM on your storage in case I feel the need to change it on the go!
19. YOUR PHONE HAS BEEN SUCCESSFULLY TURNED INTO A FULLY OPEN DROID Pat yourself on the back and have a drink to your accomplishments . We on XDA knew you could do it!
Some solutions to issues:
As ar31791 said,
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Hope this helps it worked for me. I was afraid of a brick because nobody clarified the steps that were involved in RSDLite. It may be nerve racking, but it does work!! Enjoy and thanks again to the2dcour, romracer, Nottach, Faux123 and anybody else who has helped in the scene that I didnt have a chance to mention. PM me if I forgot you!
Oh, and just to let everybody know when your bootloader is successfully unlocked it will say unlocked at the top left of your screen everytime you turn it on. just wait, this is normal.
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
noobler said:
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
Click to expand...
Click to collapse
I understand your grief hahaha. Feel free to press the thank you button at the bottom of my post. I'm trying to get a good reputation around here as I am going to school for programming and I will probably be in these dev forums daily to get help cooking Roms!
Has anybody else had success with my simplified instructions? Results?
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
sanriver12 said:
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
Click to expand...
Click to collapse
Are you sure it works on a Bell/Int'l Atrix?
Thanks heaps for the instructions Just used them to unlock a Telstra Atrix which I updated to 2.3.4 this morning! Worked a treat.
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
timfoote said:
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
Click to expand...
Click to collapse
you would have expected this if you had informed yourself as you should, before performing this kind of procedure on your phone.
Worked perfectly for me. My phone wouldnt complete the flash, so I went into CMD and unlocked it.
I've been trying to do this before, and many failed attempts.
So thank you.
worked
Fantastic summary.
Worked like a charm.
Bell Atrix with retail updates.
Thanks a million!
...Damnit, still can't remove Kobo; wtf!
Super guide
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
xeidy said:
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
Click to expand...
Click to collapse
I also have an unlocked bell atrix 4g on rogers. If you dont have 2.3.4 you would have to update your phone with the bell original software. It wont take away your unlock as unlocks are permanent. after you upgrade follow this guide to unlock the Bootloader and feel free to use custom roms!
nabicat said:
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
Click to expand...
Click to collapse
well after I unlocked my bootloader I installed romracers CWM and DarkSide v2.1 to my phone. No issues with ram so far. I dont know if you intend on installing customs ( I assume so because what other reason would you have to unlock the bootloader? lol) but after the install my ram readouts seemed correct
Yes, you're correct. I checked available memory and its over 800 mb, so the fix must be in there.
Cheers
Working very well with Bell Atrix.
Thanks for big help.
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
MrJcc said:
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
Click to expand...
Click to collapse
I'm not sure if it works with hong kong version. If you check the link that I posted, it leads to a thread on here called international house of pudding. in that thread at the beginning it says that " China version ??: DANGER: Brick after OTA 2.2.2" So you would definitely have to ask someone around the forums or search to see if somebody has done it successfully
It is possible to remove the unlocked during the boot?
Sent from my MB860 using XDA App
My Nexus One is rooted (I forgot how I did it).
Last night suddenly my phone went off and could not reboot anymore. It stayed on "X" screen forever. I tried to hard reset (i.e. Pressing volume down and power button). Then I pressed "Recovery" and then it went restart and stayed on "X" screen forever again. What can U do?
Please help, I am a new root user. please teach me step by step to do so. thanks.
Turn it off. Hold the trackball while starting it up. If you have usb debugging on and working fastboot drivers, you can wipe your phone (fastboot -a in cmd) and flash an img file of like a stock ROM.
Sent from my Nexus One using Tapatalk
Thanks Theshawty, donno why my Nexus One can't even boot up now
wingod513 said:
Thanks Theshawty, donno why my Nexus One can't even boot up now
Click to expand...
Click to collapse
I had read some other members did some tricks to their phone by remove the SD card and reboot the phone. BTW, is the battery fully charged? Try to pull the battery and then put it back on.
wingod513 said:
My Nexus One is rooted (I forgot how I did it).
Last night suddenly my phone went off and could not reboot anymore. It stayed on "X" screen forever. I tried to hard reset (i.e. Pressing volume down and power button). Then I pressed "Recovery" and then it went restart and stayed on "X" screen forever again. What can U do?
Please help, I am a new root user. please teach me step by step to do so. thanks.
Click to expand...
Click to collapse
Step by step new ROM for nexus one and restoring....
ADDITIONAL information for people who don't know to use passim.zip and update.zip
1-passimg.zip
a-Download the Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ ROM.z
ip link ( 1st link)
b-Rename the file to passimg.zip ( in windows take care of renaming it passimg.zip.zip)
c-copy it into the root of your SD card
d-turn of your phone
e-Press and hold the power button + vol. down button until a white screen showing android buddies skating at the bottom appears
f- the phone will automatically read the passimg.zip ( will load and then check it) after it is check it will ask you to press volume up to confirm the updates
g-the device will reboot then go to the SD card and DELETE THE PASSIMG.IMG file
then it is done
2-update.zip
a- download the corresponding update file from the steps above
b- rename the file to update.zip( again in windows take care of the update.zip.zip rename problem)
c- copy the file to the root of your SD card
d- turn off the phone
e-Press and hold the power button + vol. down button until a white screen showing android buddies skating at the bottom appears
f-wait for 4 sec. the using the volume down and up buttons to go up and down go the RECOVERY and then press the power button to select
g-it will load the nexus logo then will show the android buddy with an exclamation mark .... press power button + volume up button
h-choose using the trackball the apply SD card:update.zip option
the phone will go through some process verifying package... verifying software version and the end the phone will restart to finish the update ( Notice: in some updates it doesn't restart automatically so just choose the "reboot system now" option)
i- AFTER THE PHONE RESTART ALWAYS REMEMBER TO DELETE THE OLD UPDATE.ZIP FILE TO PUT THE NEW ONE FOR THE NEXT UPDATE according to the above steps
Hope this post is helpful for some people and if there is any missing steps or mistakes i would like if someone help me with an advice
Download linksonly the link of the stock rom i had to upload it cause it isn't available anymore on the google servers)
-stock ROM "FRG33"==> http://www.multiupload.com/NTA9DANZGC
-from FRG33 to GRI40 ==> http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip (thanks to efrant)
-Update FRG33 to FRG83 ==>http://android.clients.google.com/p...01ae02c.signed-passion-ota-60505.766a101a.zip
-Update FRG83 to FRG83D ==> http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
-Update FRG83D to FRG83G ==> http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
-Update FRG83G to GRI40 ==>http://android.clients.google.com/p...signed-passion-GRI40-from-FRG83G.81304b2d.zip
taodan said:
I had read some other members did some tricks to their phone by remove the SD card and reboot the phone. BTW, is the battery fully charged? Try to pull the battery and then put it back on.
Click to expand...
Click to collapse
I tried this already but still not work, I had brought my phone to some third party mobile repair centre, they said my N1 is CPU broken and will cost around US$96 to replace with a new CPU (HTC need around US$190 for mother board). I paid US$96 anyways. not sure if it worth.
cnalbant said:
Step by step new ROM for nexus one and restoring....
ADDITIONAL information for people who don't know to use passim.zip and update.zip
1-passimg.zip
a-Download the Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ ROM.z
ip link ( 1st link)
b-Rename the file to passimg.zip ( in windows take care of renaming it passimg.zip.zip)
c-copy it into the root of your SD card
d-turn of your phone
e-Press and hold the power button + vol. down button until a white screen showing android buddies skating at the bottom appears
f- the phone will automatically read the passimg.zip ( will load and then check it) after it is check it will ask you to press volume up to confirm the updates
g-the device will reboot then go to the SD card and DELETE THE PASSIMG.IMG file
then it is done
2-update.zip
a- download the corresponding update file from the steps above
b- rename the file to update.zip( again in windows take care of the update.zip.zip rename problem)
c- copy the file to the root of your SD card
d- turn off the phone
e-Press and hold the power button + vol. down button until a white screen showing android buddies skating at the bottom appears
f-wait for 4 sec. the using the volume down and up buttons to go up and down go the RECOVERY and then press the power button to select
g-it will load the nexus logo then will show the android buddy with an exclamation mark .... press power button + volume up button
h-choose using the trackball the apply SD card:update.zip option
the phone will go through some process verifying package... verifying software version and the end the phone will restart to finish the update ( Notice: in some updates it doesn't restart automatically so just choose the "reboot system now" option)
i- AFTER THE PHONE RESTART ALWAYS REMEMBER TO DELETE THE OLD UPDATE.ZIP FILE TO PUT THE NEW ONE FOR THE NEXT UPDATE according to the above steps
Hope this post is helpful for some people and if there is any missing steps or mistakes i would like if someone help me with an advice
Download linksonly the link of the stock rom i had to upload it cause it isn't available anymore on the google servers)
-stock ROM "FRG33"==> http://www.multiupload.com/NTA9DANZGC
-from FRG33 to GRI40 ==> http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip (thanks to efrant)
-Update FRG33 to FRG83 ==>http://android.clients.google.com/p...01ae02c.signed-passion-ota-60505.766a101a.zip
-Update FRG83 to FRG83D ==> http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
-Update FRG83D to FRG83G ==> http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
-Update FRG83G to GRI40 ==>http://android.clients.google.com/p...signed-passion-GRI40-from-FRG83G.81304b2d.zip
Click to expand...
Click to collapse
Thanks, I will try this after my phone get fixed.
cnalbant said:
-stock ROM "FRG33"==> http://www.multiupload.com/NTA9DANZGC
-Update FRG33 to FRG83 ==>http://android.clients.google.com/p...01ae02c.signed-passion-ota-60505.766a101a.zip
Click to expand...
Click to collapse
These links not working, please help me update. thanks
are you sure you just didn't lose your recovery
rugmankc said:
are you sure you just didn't lose your recovery
Click to expand...
Click to collapse
Sorry, what do you mean?
Sent from my GT-N7000 using xda premium
wingod513 said:
Sorry, what do you mean?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
If your bootloader is unlocked, just flash a new recovery from fastboot Otherwise unlick it anyway.
Sent from my Hypersensed Nexus One using xda.
race55 said:
If your bootloader is unlocked, just flash a new recovery from fastboot Otherwise unlick it anyway.
Sent from my Hypersensed Nexus One using xda.
Click to expand...
Click to collapse
The bootloader of my N1 is unlocked, I am not familiar with fastboot thing. My friend helped mine root and he is out of my country now. Gotta follow cnalbant's steps and see.
Install ClockworkMod Recovery on Nexus One Manually
Step 1: Download ClockworkMod Recovery: recovery-clockwork-2.5.1.1-passion.img (there are more current, look at the xda)
Step 2: Set up ADB for Nexus One
Step 3: Put the downloaded recovery-clockwork-2.5.1.1-passion.img in C: drive
Step 4: Turn Nexus One off and connect it to PC via USB
Step 5: Hold the Power button + Trackball together to start Nexus One in fastboot mode
Step 6: Once in fastboot mode, open Terminal / Command Prompt and run following command:
fastboot devices
This command will check if your device is connected in fastboot mode or not.
Step 7: Now run following command (place the file recovery in the same folder where the fastboot):
fastboot flash recovery recovery-clockwork-2.5.1.1-passion.img
This will install Clockwork recovery on your Nexus One.
That’s it, enjoy!
You can either follow the above guide or this amon ra recovery guide
forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images
Amon ra is another recovery just like clock workmod
B4 using adb download the drivers of adb and fastboot
www.mediafire.com/?bhxmn903d6cz9eg
When you connect ur phone use device manager to locate the connection on win 7 and select install drivers frm folder and install frm the extracted folder of adb driver
Sent from my HTC Nexus One using XDA
Hi I've been an avid flasher for years without problems but today I have a huge problem!!
I flashed xenon s latest and flashed gapps via Cwm but it wouldn't boot so when I rebooted it just goes into a bootloop into recovery but it only loads the recovery slightly before rebooting again.
I've tried entering the bootloader by powering off etc and holding volume +&- and power but still can't enter
I've also tried pulling the battery and trying but still no luck
Please can anyone help
Sent from my GT-I9505 using Tapatalk
Solved
Sent from my GT-I9505 using Tapatalk
Can you share how you solved? I've been seeing this problem reported all over the forum and no one has yet posted any solution aside from replacing the main board or RMA.
I will post the solution tonight with step by step and images but out atm but I will post
Sent from my GT-I9505 using Tapatalk
1eyedmonster said:
I will post the solution tonight with step by step and images but out atm but I will post
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Here is my solution step by step.
1 install 'wugs root toolkit & skipsoft android toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2 install USB drivers from skipsoft as its easier - select option 1 after entering the main menu
3 you need to select the build of your custom ROM in wugsfresh toolkit 4.1/4.2/4.4 etc (this is important as if you choose the wrong build it won't work straight away and you will have to try each build individually).
4.in wugsfresh select "soft bricked" and select "launch advanced Utilities"
5.select (boot temporary _ custom Recovery) and execute
now connect your n7 with the usb
6 you will see prompts on the screen saying Rebooting into bootloader and at this point press the volume down button constantly if you get a prompt "device not found......" Just press OK and follow the procedure again until your bootloader starts( of it doesn't work try a different build
7 once you bootloader starts unplug your USB instantly and then scroll down using the volume keys and select "reboot bootloader"
8 close wugsfresh "Ctrl+alt &del and end process" and restart your computer
9 after pc reboot enter the skipsoft toolkit and you can connect your n7 (still in bootloader mode) via usb
10 select your build and download the recoveries when prompted
11 when in the main menu select option 6 "flash custom recovery" and select twrp only
12 flash away (if it doesn't detect your n7 (reboot bootloader on your n7) and try again
13 once you've flashed successfully (on your n7 scroll down and select reboot into recovery and twrp should load.
14 from here you can install your desired ROM with a otg cable or from a ROM on you devices storage but if you don't have a otg cable or a rom on your storage go to the next step
15 download your desired ROM and place it on your PCs hard drive. Open wugsfresh toolkit and select launch utilities again
16 select "flash zip -file is on the computer"and press OK when prompted and select your downloaded ROM /enable wipe selected partitions and select data cache and dalvic and then confirm operation
17 you will see a prompt stating "sending ROM.......to device" this will take sometime be patient once it's completed it will reboot your device back into twrp recovery and the file will be on your devices storage in a folder called "ready to flash" and the rest is up to you.
18 once your booted into your device os you can reflash your desired recovery with the toolkit of your choice
Hope this helps
Wow, did you just trial and error your way through that?
Interesting that you needed to use both toolkits, but whatever works...
Hopefully this will help some folks that were otherwise SOL with a bricked tablet. :good:
1eyedmonster said:
Here is my solution step by step.
1 install 'wugs root toolkit & skipsoft android toolkit
2 install USB drivers from skipsoft as its easier - select option 1 after entering the main menu
3 you need to select the build of your custom ROM in wugsfresh toolkit 4.1/4.2/4.4 etc (this is important as if you choose the wrong build it won't work straight away and you will have to try each build individually).
4.in wugsfresh select "soft bricked" and select "launch advanced Utilities"
5.select (boot temporary _ custom Recovery) and execute
now connect your n7 with the usb
6 you will see prompts on the screen saying Rebooting into bootloader and at this point press the volume down button constantly if you get a prompt "device not found......" Just press OK and follow the procedure again until your bootloader starts( of it doesn't work try a different build
7 once you bootloader starts unplug your USB instantly and then scroll down using the volume keys and select "reboot bootloader"
8 close wugsfresh "Ctrl+alt &del and end process" and restart your computer
9 after pc reboot enter the skipsoft toolkit and you can connect your n7 (still in bootloader mode) via usb
10 select your build and download the recoveries when prompted
11 when in the main menu select option 6 "flash custom recovery" and select twrp only
12 flash away (if it doesn't detect your n7 (reboot bootloader on your n7) and try again
13 once you've flashed successfully (on your n7 scroll down and select reboot into recovery and twrp should load.
14 from here you can install your desired ROM with a otg cable or from a ROM on you devices storage but if you don't have a otg cable or a rom on your storage go to the next step
15 download your desired ROM and place it on your PCs hard drive. Open wugsfresh toolkit and select launch utilities again
16 select "flash zip -file is on the computer"and press OK when prompted and select your downloaded ROM /enable wipe selected partitions and select data cache and dalvic and then confirm operation
17 you will see a prompt stating "sending ROM.......to device" this will take sometime be patient once it's completed it will reboot your device back into twrp recovery and the file will be on your devices storage in a folder called "ready to flash" and the rest is up to you.
18 once your booted into your device os you can reflash your desired recovery with the toolkit of your choice
Hope this helps
Click to expand...
Click to collapse
Will give it a try later today & post results...
Fingers crossed!
Thanks,
Shabby.
PrizmaticSmoke said:
Wow, did you just trial and error your way through that?
Interesting that you needed to use both toolkits, but whatever works...
Hopefully this will help some folks that were otherwise SOL with a bricked tablet. :good:
Click to expand...
Click to collapse
Yes had to use both toolkits as you can't flash recovery in bootloader mode in wugfresh but you can in the other
Sent from my GT-I9505 using Tapatalk
Recovery Bootloop Nexus 7
1eyedmonster said:
Yes had to use both toolkits as you can't flash recovery in bootloader mode in wugfresh but you can in the other
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Wow, I was hoping someone would find a solution to this unstoppable boot loop. Awesome work 1eyedmonster!
I gave this a try since I like many others flashed XenonHD with CWM as my recovery and fell into the boot loop too, but how were you able to get step 6? I been trying to get the tablet into the bootloader when the message appears in wugfresh while pressing volume down, but then fails to reboot into it and the status will then show checking fastboot and fails. So I try it again but still having trouble and it just keeps going from the google logo then to CWM and then back to the google logo. Checked the drivers and it shows as ADB in the device manager when CWM pops up so drivers seem good.
Since my build was 4.4.2 I tried custom rom KK and standard 4.4.2 when selecting the build, but not sure what I might be doing wrong.
Any help will be greatly appreciated.
xdarkstar13x said:
Wow, I was hoping someone would find a solution to this unstoppable boot loop. Awesome work 1eyedmonster!
I gave this a try since I like many others flashed XenonHD with CWM as my recovery and fell into the boot loop too, but how were you able to get step 6? I been trying to get the tablet into the bootloader when the message appears in wugfresh while pressing volume down, but then fails to reboot into it and the status will then show checking fastboot and fails. So I try it again but still having trouble and it just keeps going from the google logo then to CWM and then back to the google logo. Checked the drivers and it shows as ADB in the device manager when CWM pops up so drivers seem good.
Since my build was 4.4.2 I tried custom rom KK and standard 4.4.2 when selecting the build, but not sure what I might be doing wrong.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
once you clicked the 'Boot tempory custom recovery' button plug your n7 via the usb and press the volume down button erratically (do not hold down) before powering the n7 on
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
1eyedmonster said:
once you clicked the 'Boot tempory custom recovery' button plug your n7 via the usb and press the volume down button erratically (do not hold down) before powering the n7 on
Click to expand...
Click to collapse
once bootloader boots up you must unplug the usb immediately
another thing I forgot to add is once in wugfresh you need to go to options /custom recovery/utilize open recovery by team wi......
Sent from my Satellite Pro A300 using Tapatalk
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
Same prob as xdarkstar...
I know this might sound a bit stupid, but what is the best way to get the back off? [I'm asking this because all I'm doing at the moment is chewing in to the sides of the device with no results...]
TIA,
Shabby.
SHABBYLEA said:
Same prob as xdarkstar...
I know this might sound a bit stupid, but what is the best way to get the back off? [I'm asking this because all I'm doing at the moment is chewing in to the sides of the device with no results...]
TIA,
Shabby.
Click to expand...
Click to collapse
Hi, Shabby...
I've found the easiest way of removing the back, is to begin at the top (opposite end to the USB port)... slide a fingernail under the plastic back and gently prise it away. Then slowly work your way around both left and right edges with your fingernails. You shouldn't need to use any real force; once you've got the process started, the back should pretty much just 'pop' off.
To put it back on... reverse the process... begin at the bottom (USB end)... and apply gentle pressure, equally on both right and left hand sides... slowly working your way up to the top. You should 'feel' it begin to snap back into place.
-----------------------------------------------
Incidentally, I really hope this method discovered by @1eyedmonster works for you... and anybody else afflicted by the decidedly toxic combination of Xenon and CWM.
Rgrds,
Ged.
GedBlake said:
Hi, Shabby...
I've found the easiest way of removing the back, is to begin at the top (opposite end to the USB port)... slide a fingernail under the plastic back and gently prise it away. Then slowly work your way around both left and right edges with your fingernails. You shouldn't need to use any real force; once you've got the process started, the back should pretty much just 'pop' off.
To put it back on... reverse the process... begin at the bottom (USB end)... and apply gentle pressure, equally on both right and left hand sides... slowly working your way up to the top. You should 'feel' it begin to snap back into place.
-----------------------------------------------
Incidentally, I really hope this method discovered by @1eyedmonster works for you... and anybody else afflicted by the decidedly toxic combination of Xenon and CWM.
Rgrds,
Ged.
Click to expand...
Click to collapse
For future reference don't attempt to install xennon with philz recovery either as this causes the bootloop also
Sent from my GT-I9505 using Tapatalk
This isn't working for me. Maybe Im doing something wrong but I cant get it to work.
Found a fix to restore to stock!
timmytim said:
This isn't working for me. Maybe Im doing something wrong but I cant get it to work.
Click to expand...
Click to collapse
Warning! This method will restore your tablet to factory defaults. I did not try to flash a custom recovery while in Fastboot Mode though Im sure that will work too if you just want to write a Recovery (TWRP... hint hint) and reflash a different ROM.
I'm convinced. This tablet must truly be unbrickable!!
I have found another fix and it was as easy as pie! Here's what I did... results may vary. Please post here if you had success or not. Also, you will need working adb for this to work as well as the ADB drivers installed and working.
For starters, this is the Epic Fail after flashing a ROM with CWM or Philz Recovery
What I found is that while on this screen you can still run adb commands. Eureka I thought! Here's the simplest way to recover your tablet from this vicious cycle. Again, you will need either need the Android SDK installed on your PC or you will need the adb executable with libs at minimum....
1. Download the Nakasi Nexus Factory Image of your choice from HERE
2. Plug your tablet into your computer while it's bootlooping. You will have to have the ADB drivers installed for this to work.
3. Open a command prompt on your PC and type in adb reboot bootloader and press Enter on your keyboard.
4. If you happened to catch it at the right moment, which is between the Google splash screen and the f*cked Recovery screen seen above, congrats! If not, keep pressing the Up Arrow and Enter keys simultaneously on your keyboard starting at the Google splash screen until it reboots into Fastboot mode
5. Extract the Nakasi factory image that you downloaded and run flash-all.bat and wait for the script to finish. It will reboot your tablet into Fastboot Mode a few times while it executes. When done, it will boot the tablet and it will be factory restored
Win!
timmytim said:
Warning! This method will restore your tablet to factory defaults. I did not try to flash a custom recovery while in Fastboot Mode though Im sure that will work too if you just want to write a Recovery (TWRP... hint hint) and reflash a different ROM.
I'm convinced. This tablet must truly be unbrickable!!
I have found another fix and it was as easy as pie! Here's what I did... results may vary. Please post here if you had success or not. Also, you will need working adb for this to work as well as the ADB drivers installed and working.
For starters, this is the Epic Fail after flashing a ROM with CWM or Philz Recovery
What I found is that while on this screen you can still run adb commands. Eureka I thought! Here's the simplest way to recover your tablet from this vicious cycle. Again, you will need either need the Android SDK installed on your PC or you will need the adb executable with libs at minimum....
1. Download the Nakasi Nexus Factory Image of your choice from HERE
2. Plug your tablet into your computer while it's bootlooping. You will have to have the ADB drivers installed for this to work.
3. Open a command prompt on your PC and type in adb reboot bootloader and press Enter on your keyboard.
4. If you happened to catch it at the right moment, which is between the Google splash screen and the f*cked Recovery screen seen above, congrats! If not, keep pressing the Up Arrow and Enter keys simultaneously on your keyboard starting at the Google splash screen until it reboots into Fastboot mode
5. Extract the Nakasi factory image that you downloaded and run flash-all.bat and wait for the script to finish. It will reboot your tablet into Fastboot Mode a few times while it executes. When done, it will boot the tablet and it will be factory restored
Win!
Click to expand...
Click to collapse
Using this method, do you have to disconnect the battery?
Thanks,
Shabby.
No
Sent from my GT-I9505 using Tapatalk
MoFo will NOT work on 5.1 so do NOT upgrade to the 5.1 bootloader or partition table if you want to use MoFo.
This method involves purchasing a piece of software named mofo.exe that allows you to flash a modified, unsigned system image to your device despite its locked bootloader. The cost is $20. Links to the modified images for the XT1096 and XT1097 are found in the OP of the MoFo support thread:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
This Method Does Not Disable Write Protection. Please read the following post if you don't know what that means:
http://forum.xda-developers.com/showpost.php?p=60412113&postcount=292
This Method Trips the Root Checker and Your qe Will Convert to qe 1/1 Permanently! What this means is that if you boot your phone into recovery, you will see qe 1/1, which means you are currently running modified software. The qe will stay at 1/1 even if you flash back to stock.
1. Check Your Software Version and Enable USB Debugging
Go to Settings -> About Phone and read your Android Version – it should say 5.0 on the XT1096 and 5.0.2 on the XT1097. If not, and it says 4.4.4, you are still on 4.4.4 and as long as you have not modified your system by flashing using mofo.exe, you should still be stock and can take the 5.0 or 5.0.2 OTA.
If you haven’t already, go into Settings -> About Phone and click on Build Number repeatedly until you get the message you are developer now (or something like that). Then hit the back button and you will see that the Developer Options now appear. Click on Developer Options and check USB Debugging.
2. Install Motorola Device Manager (MDM) and Drivers to Your Computer
You can download MDM and the drivers here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Install MDM on your computer after you download it. MDM should install the drivers.
3. Download Copies of Adb and Fastboot
You can get these from the Adroid SDK but you don’t need the whole Android SDK. Root Junky has the files you need on his site here:
http://rootjunkysdl.com/?device=Adb Fastboot Files
I made a folder on my computer named c:\mx2014 and put the zip file in there. Then I unzipped it with 7-zip.
http://www.7-zip.org/
4. Download a Copy of the Official Firmware
Root Junky has a copy of the XT1096 5.0 official firmware here:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
and the XT1097 5.0.2 fxz is here:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
You should download it into a separate folder (I put mine in a folder named c:\mx2014\lollipop) and unzip it so if you have any problems you can flash back to stock. Place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll in the folder with the lollipop official firmware.
Also if you are planning on taking the 5.1 OTA when it is released, you would need to flash your system back to stock so it is a good to have it ready. And if you are planning to update to 5.1 via MDM I would still flash back to stock because if you don't, IME MDM will detect that you are running a modified software and will wipe your device when it upgrades you to 5.1. If you flash back to stock first, MDM will not wipe your data and sdcard when it upgrades you to 5.1.
5. Test the Drivers and Adb
Once you have completed Steps 1-3, you can test the drivers and adb. Power on your phone and after it boots, connect it to your computer via the data cable. Open a command prompt, and then navigate to the directory where you have adb and fastboot by typing:
cd c:\mx2014 (or wherever you have adb and fastboot stored)
and hitting enter. Then type:
adb devices
You should then see a prompt on your phone asking you to authorize your computer. Check always allow and click OK. Adb should show you the serial number (not the IMEI) of your device.
Now type:
adb reboot bootloader
to get into bootloader (BL) mode (aka fastboot mode).
6. Test the Drivers and Fastboot
Once you are in BL mode, double check that on your phone’s screen right above the first green line you see this:
Transfer Mode: USB Connected.
If it does not say that, go to Root Junky’s site and download the Motorola drivers and manually install them.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
Then type:
fastboot devices
and hit enter. Fastboot should return your device’s serial number.
7. Test Getting into Recovery and Wiping Cache
While in BL mode, scroll down to Recovery by pressing the vol dwn button to highlight Recovery. Then select Recovery by pressing vol up. You should see the dead android with a red triangle having an exclamation point in it coming out of its stomach. Then press the pwr button for a couple of seconds and then press and release the vol up button and then release the pwr button to get into the recovery menu. Use the vol dwn button to scroll to wipe cache partition and then press the pwr button to select it. You should see that the cache is being formatted.
When cache is done being wiped, the recovery menu should reappear and you should hit the pwr button to reboot into system.
8. Test That You Know How to Get Into Bootloader Mode Using Buttons
Disconnect your phone from your PC, power down your phone and then hold down volume down and then press and hold the power button. Hold both buttons simultaneously for about 4 seconds and then release the power button and then the volume down button. This should put you in Bootloader mode (aka fastboot flash mode). Alternatively, you can try pressing volume down + volume up + power and holding for about 4 seconds then releasing.
Once in BL mode, you can either hit the power button to boot back into Android or if you want to test that you know how to flash back to a stock system, complete the instructions in Step 9.
NOTE – flashing the system partition does NOT affect your apps/settings/text messages/call history, which are stored on the data partition, not the system partition. Updates to system apps since 5.0/5.0.2 was rolled out will be lost as well as any system app settings that are relevant to the updates or stored on the system partition.
NOTE – flashing the system partition does NOT affect your stored media (e.g, pictures, music, videos), which are stored on the sdcard partition, not the system partition.
9. Test That You Know How to Flash Stock System (Optional)
While in BL mode you can test that you know how to flash back to a stock system. This is optional but if you have never done it before, it is a good idea to do it IMO. When you flash a system.img, you do not lose your apps/data/texts or your media unless the app is a system app, then you will lose the updates since 5.0 was rolled out (but those can be re-downloaded from the Playstore). However, it is always a good idea to backup before you flash in case you do something wrong. I use SMS Backup and Restore to backup my texts and my photos are backed up to my Google account.
Put your device in BL mode and then connect it to your computer. Open a command prompt and navigate to where you have the stock 5.0/5.0.2 image stored on your computer. Type the following:
fastboot flash system system.img_sparsechunk1
and then hit enter to flash the first sparsechunk. Repeat for the other sparsechunks until you have flashed all 9 of them. Then boot into recovery, wipe cache and boot into system.
10. Purchase MoFo.exe
First you should go to:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
and read all of the information. And be sure to watch Root Junky’s video here:
https://www.youtube.com/watch?v=AXAYjbf76II&feature=youtu.be
The high level summary of what you will be doing is this:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
2. Using the link generated by MoVerify to navigate to where you can purchase mofo.exe; and
3. Purchasing and downloading mofo.exe.
11. Download, UnZip and Flash a Pre-rooted Ext4 Image
The OP of the MoFo thread has links to the pre-rooted images that are available for the XT1096 and XT1097. Once you download one of them, unzip it and move the image file to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofo.exe flash [Insert name of image file here]
then hit enter. Of course you do not put brackets around the name of the image file. Once the pre-rooted image has been flashed (about 25 minutes), boot into recovery and wipe the cache then boot into system.
It may take a few seconds for the boot animation to start so don’t panic. Once the system has booted, to check that you are rooted, download root checker basic from the Playstore and confirm that you are rooted. Your device will also bypass the subscription check when you turn on WiFi hotspot.
The copy of mofo.exe that you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it - unless you upgrade to a higher version of Android. If you upgrade to a higher version of Android, once that higher version of Android is supported by MoFo for your device, you can re-download mofo.exe for the higher Android version.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
Mofo will NEVER be updated to support 5.1 as the exploit was closed with the 5.1 bootloader.
Thank you for the guide and for the testing - its a great service to Moto X owners.
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
HTC-OH_SNAP said:
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
Click to expand...
Click to collapse
It is best to ask on the MoFo support thread where you are more likely to get maiko1's attention.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Adding this to the OP
This is from the MoFo support forum - there appears to be some confusion about mofo.exe being device specific. The copy of mofo.exe you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
JulesJam said:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
Click to expand...
Click to collapse
might want to expand the MoVerify process with little baby steps.... the Mofo site and the Mofo forum here are again very sparse on details.
1) download and unzip the MoVerify program
2) connect you phone to computer
3) open cmd window
4) navigate to c:\mx2014 (or wherever you have adb and fastboot stored)
5) type adb devices
6) type adb reboot bootloader
7) navigate to the MoVerify folder
8) go to the folder that represents your computer's OS; let's assume Windows here
9) in the Windows folder, double click on "mofoverify_gui.bat"
10) MoVerify will open a cmd window and return back that your devices was found and give a link that looks like
https://mofo.disekt.org/verify/ [big long alphanumeric string]
11) right click anywhere in the text that is in the MoVerify cmd window and select "Select All" and then hit enter
12) open Notepad or other text editor and past the text
13) cut and paste the https address into your browser
14) follow steps to purchase Mofo
i have purchased but have not gotten farther yet... may have some more suggestions later...
Nice job putting this together. And thanks for all of your testing during the process!
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill. if these two merhids are equivalent for this mofo process, maybe both options should be stated in the step by step.
is there any time when the button method MUST be used?
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
[email protected] said:
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
Click to expand...
Click to collapse
No.
[email protected] said:
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
Click to expand...
Click to collapse
I tend to use the buttons so that is why I wrote it up that way.
[email protected] said:
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
Click to expand...
Click to collapse
Yes, that would work.
[email protected] said:
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill.
Click to expand...
Click to collapse
True but if you soft brick your phone, the buttons are the only way to get into bootloader mode so best to be familiar with this way.
Did you try holding vol dwn/up and pwr simultaneously for 4 seconds and then releasing? After the lollipop update I swear that works the best for me. Let me know if that works more reliably for you - it does for me.
[email protected] said:
is there any time when the button method MUST be used?
Click to expand...
Click to collapse
If you get into a bootloop or your screen goes black and the phone is unresponsive.
[email protected] said:
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
Click to expand...
Click to collapse
Standard fastboot has a size limitation on how large of a file it can flash. So system images above that size limitation have to be broken down into smaller chunks. The version of the 5.0 Official firmware that is available to us is the one on Root Junky's site and that one is broken down into chunks.
Motorola made a modified version of fastboot, often referred to as mfastboot, that can flash larger files. However, I cannot find a version of mfastboot that can flash the 5.0 system.img (fxz) that we have available to us. If anyone has a version of mfastboot that can flash the 5.0 fxz system.img, then you could flash it. RSD Lite may be able to flash it, idk I didn't try it.
As for mofo.exe - mofo.exe has a way to avoid the size limitations of standard fastboot. Idk why standard fastboot has a size limitation in the first place. But it does and so large files have to be broken down into chunks when you use standard fastboot to flash. Mofo.exe doesn't have that same size limitation.
JulesJam said:
Once you download one of them, unzip it and move the image to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofoe.exe flash XT1096_5.0_22.21.11_rooted.img
then hit enter.
Click to expand...
Click to collapse
ok. so i attempted this today
1) powered off phone
2) booted in BL mode using power and volume buttons (yes it does work very well, esp after taking the phone OUT of the case so buttons are more fully accessible) - phone screen says "AP Fastboot Flash Mode (S)" at very top
3) plugged phone into computer
4) double clicked the mofo_gui.bat to open cmd window
5) copy and pasted your text exactly
6) after hitting enter, i got the following error
======================================
'mofoe.exe' is not recognized as an internal or external command,
operable program or batch file.
======================================
methinks you have a typo in your mofo command... extra "e" that should not be there??
taking out the "e" worked and it flashed
it then said
=====================
Flashing 'XT1096_5.0_22.21.11_rooted.img' to device. Do not interrupt.
Progress: 100%
Complete. Press power to start.
=====================
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
if i hit the power button again, it still showed the battery level screen
so i pressed and held BOTH the power and volume buttons, and it booted!
when i power down, it goes to the batter level screen. and i can't seem to get into BL mode using the power and volume buttons
however, i can get to BL, then Recovery using adb, and was able to wipe cache partition
i installed and ran Root Checker Basic ... make sure you click "Grant" when it asks for permission while checking root access, or it will return a "no root access" message.
i now have wifi tethering! yahoo!
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
i am running Nova Launcher... could that be the issue with the widget not working?
otherwise, i have to go into Settings to turn it on/off... which is better than NOT having hotspot at all!
[email protected] said:
methinks you have a typo in your mofo command... extra "e" that should not be there??
Click to expand...
Click to collapse
Oops! Thanks for catching that - I will edit!
[email protected] said:
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
Click to expand...
Click to collapse
Disconnect it from your PC and then press the power button to turn it on.
[email protected] said:
when i power down, it goes to the batter level screen.
Click to expand...
Click to collapse
That is b/c it is connected to your computer. The same thing will happen if you have it plugged into the wall.
[email protected] said:
i now have wifi tethering! yahoo!
Click to expand...
Click to collapse
Yay!!!! I am at over 50GB this month from all of the downloading of images I did to test them, lol! I have never used that much before.
[email protected] said:
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
Click to expand...
Click to collapse
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
[email protected] said:
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
you want a hotspot toggle then, but idk of any off hand.
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
might want to just add the words "disconnect the phone fromthe usb cable" somehwere in the OP directions, you know, just for all those noobs out there that might get panicked
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
mikeoswego said:
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
Click to expand...
Click to collapse
thanks! I suggest booting into recovery and wiping cache before you boot back into Android.
mikeoswego said:
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
Click to expand...
Click to collapse
yeah I noticed that last night, it is great!
[email protected] said:
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
There is a Hotspot toggle in quick settings. From your lock screen, just swipe down from the top of the screen to see it. From your home screen, swipe down with 2 fingers.
Anyone know whether the January security patch has started rolling out OTA on this thing yet?
I ask because up until this month I had been using custom ROMs. It was only a few weeks ago I decided to flash stock on the NP and focus my modding efforts on my phone, where I don't have to deal with OTG cables and Netflix's DRM. Now I'm starting to wonder whether my former tweaking is blocking me from updates somehow, or whether it always takes this long. I mean I'm back to stock recovery and I'm not even rooted, and four days for a critical security update seems like an awful long time.
I'm in the UK, stock 6.0.1 unrooted, and still no OTA yet
Sent from my iPad using Tapatalk
If you got tired waiting (as I was):
1. Get the January patch OTA for sidleloading (MMB29M to MMB29T)
2. Turn on Debugging on the NP
3. Connect the NP to your PC and run adb reboot bootloader
4. Using NP power button, select recovery (press once to change and then long press 2 sec to select)
5. Once "no command" appears, long press 2 sec to make the recovery menu appear
6. Select ADB sideload zip (press once to scroll and then long press 2 sec to select)
7. From your PC then run adb sideload file-downloaded-before.zip
The process will take 2-3 minutes and after that your NP will have Jan 2016 patch!
jeppo said:
If you got tired waiting (as I was):
1. Get the January patch OTA for sidleloading (MMB29M to MMB29T)
2. Turn on Debugging on the NP
3. Connect the NP to your PC and run adb reboot bootloader
4. Using NP power button, select recovery (press once to change and then long press 2 sec to select)
5. Once "no command" appears, long press 2 sec to make the recovery menu appear
6. Select ADB sideload zip (press once to scroll and then long press 2 sec to select)
7. From your PC then run adb sideload file-downloaded-before.zip
The process will take 2-3 minutes and after that your NP will have Jan 2016 patch!
Click to expand...
Click to collapse
Woah! I had no idea Google put out sideloadable zips. I figured my only option for stock was the fastboot images.
For future reference, where did you find that URL? I'm also wondering if these could be flashed with TWRP, or whether it would fail with anything other than stock recovery. I mean I already have an SSH app for easy file transfers, so it'd be amazing to install future updates without lugging my computer over to connect with the player. But stock recovery doesn't exactly have a file manager or anything.
Either way, thank you. This is awesome.
EDIT: Actually stock recovery surprisingly has an "apply update from SD card" option, but it throws me a "couldn't mount /sdcard" error every time. I guess I'll stick with ADB sideloading for now, unless I get some kind of indication a custom recovery would work with these patches. But I get the feeling it wouldn't.
Unfortunately there is no public listing of the OTA URLs. You have to wait for someone to posts it online (or on xda forums).
About custom recoveries, those zips will not work with them because the update process checks the integrity of the system and it fails if you have something different from clean stock.
Sent from my Nexus 5 using Tapatalk
Yup still waiting here, more curious to see how fast or slow it will come.
are there instructions to load this in TWRP? thanks
knives of ice said:
are there instructions to load this in TWRP? thanks
Click to expand...
Click to collapse
Unfortunately based on what jeppo is saying it wouldn't work with TWRP. Otherwise it would be the same process. TWRP has an "ADB sideload" option under "advanced" if I recall correctly.
I got my OTA update last night... (it says January 1, 2016 security patch) not sure if I see any difference in color though
if someone would make a flashable zip in twrp i'd even willing to paypal a few bucks
pretty please?!
Must have gotten the update sometime today.