Kwongger's NVIDIA SHIELD All-In-One- Toolkit
An All-In-One Kit for our beloved Nvidia Shields.
Provides Unock, Recovery, Root, and Relock!
{
"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"
}
SORRY NO DL...
THE TOOL IS DISCONTINUED!
CHANGELOG
...
And this is mine!
Videos will come in the future!
HAHA. I LOVE the disclaimer! "Unless your device starts shooting lasers. Then that's all me".
I seriously got a good laugh out of that!
red triangle in recovery
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..
brian13206 said:
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..
Click to expand...
Click to collapse
Make sure you're booted into android... All it does is adb push the supersu.zip And walk you through the rest.
to be fair
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again
brian13206 said:
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again
Click to expand...
Click to collapse
Did you try booted into android?
In the kit you start everything in android
It put the SuperSU zip in my download folder.
I saw that screen.. when I hit :"install" it went to red triangle...
brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
NO BOOTLOADER!!!
A post above confirmed that it is working!
If you still have issues, copy and paste the file and go from there
sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors
brian13206 said:
sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors
Click to expand...
Click to collapse
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
You're instructions CLEARLY say to be booted into Android...
wwjoshdew said:
You're instructions CLEARLY say to be booted into Android...
Click to expand...
Click to collapse
Thanks for the back up
I was getting kind of frustrated, I'll check his past posts... May be a sad attempt at a Troll.
wwjoshdew said:
It put the SuperSU zip in my download folder.
Click to expand...
Click to collapse
brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.
chevyowner said:
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.
Click to expand...
Click to collapse
I adb push the file, so you have to be in Android.
Kwongger said:
I adb push the file, so you have to be in Android.
Click to expand...
Click to collapse
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.
chevyowner said:
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.
Click to expand...
Click to collapse
hmm... Never thought of that. I'll just stick with my method, IMO it is simpler and I have already plastered ALL OVER to start booted into android, thanks so much for the feedback!
If you have any other suggestions don't hesitate to let me know
hmmm never been accused of being a troll. i realize I should have never posted this. Just to be clear. I wasn't in bootloader when it happened.I was in android. I did step 4..(install su.) when it was finished I went into recovery to check and got the red triangle I stated that it reverted and restarted by itself and I just went and rooted via a different method.( github joshdew vid ) I tried to say that I didn't blame the Op or his 1 click... that I was posting just what happened to ME and that it probably wouldn't happen to anyone else. I even apologized if I was snide in my first post. I have had many smartphones and have never had an issue rooting. Shield was my only hiccup and I started all of this asking for help.
Let me know how the kit is working!!!
PM me any suggestions you have, for new features or for a new Supported device!!!!!!!!!!!
Thanks,
Kwongger
Related
thread outdated ! please user romracer's http://forum.xda-developers.com/showthread.php?t=1204500
Hi ALL,
This is the recovery.img build for Unlocked AT&T Atrix 4G.
You can flash this direct to the recovery partition for a unlocked device, no more AC charger!
Thanks Koush and other devs who are working on the original cwm recovery.
enjoy porting CM7!
this is under developmet ,please use at your own risk! but every release will be tested first.if you like my work. buy me a beer
have fun.
Updated:GMT+8:00 06-30 11:20am
filename: recovery-en-goapk-0630-1029.zip
add backup and restore pds( backup tested,restore didnt test.)
add Internal SD card Support (nandroid and choose zip from internal sdcard)
should add a restart adb server int the menu in next version.
Latest Download:
View attachment recovery-en-goapk-0630-1029.zip
{
"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"
}
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.
GMT+8:00 2011-06-25-22:25 Update again:
Important Update!recovery-en-goapk-0625-2034.zip
fix wipe format and backup restore
latest: View attachment recovery-en-goapk-0625-2034.zip
GMT+8:00 2011-06-25 03:38 Update:
fix format data and cache
please update to latest build.
another fixed!
please update.
and every other thing should work as it should。
how to install:
Windows:
unzip recovery-en-goapk.zip to D:\
open a CMD in windows.
fastboot flash recovery D:\recovery-en-goapk.img
Linux:
unzip recovery-en-goapk.zip to you home
mot-fastboot flash recovery ~/recovery-en-goapk.img
mot-fastboot reboot
pics:
Downloads:
2011-06-24-16:10 GMT +8:00
View attachment recovery-en-goapk.zip
2011-06-25 03:38 GMT +8:00
View attachment recovery-en-goapk-0313.zip
HERE IS THE EASY GUIDE:thanks Paschalis !
I had the prev version of CWM, and i wanted to update to the latest, using moto-fastboot instead of fastboot..
It's very easy.. So i wrote a little guide.. Dont blame me.. Its for new guys like me!
Btw will any future update of CWM, have adb enabled?
eg If we messed up with framework or anything else can cause a soft-brick, then recover using backup files..
Step-by-Step
How to install on Windows with moto-fastboot
1) With Root-Explorer go to: /system/etc/ and remove: "install_recovery.sh" file
2) Download moto-fastboot.rar, and latest recovery recovery-en-goapk-0630-1029.zip
3) Extract contents of moto-fastboot.rar in C:\Windows,
and content of recovery-en-goapk-0630-1029.zip in C (for example).
4) Get your Atrix in FastBoot:
................................ a) Turn it off
................................ b) While turning it on, press VolumeDown key
................................ c) Press VolumeUp key
................................ d) Connect your Atrix to your PC using usb data cable
5) Open a cmd (Command Prompt)
6) Enter following cmd commands:
............. a) cd C:\
............. b) moto-fastboot flash recovery C:\recovery-en-goapk-0630-1029.img
............. c) moto-fastboot reboot
7) Thank Paschalis for this guide!
Click to expand...
Click to collapse
original post on http://bbs.goapk.com/thread-2874929-1-1.html
please include this info when you post this on other forums.
Holy freakin Hell!!! Thanks!!! Good to hear from ya!!!! Its like xmas around here in june!! LOL
Great to see this so soon. I cannot wait for a fully functional version! Glad to see you still lurking around here tenfar, thankyou for this, as well as koush and all the others (if any) involved in making this happen!
How To: Get into CWM Recovery
Using ADB:
- adb reboot recovery
Using buttons:
- Hold down power, downward volume buttons until you see "Fastboot"
- Use downward volume button to click multiple times until you see Android Recovery
- Then, press the upward volume button
Thanks! Tenfar excited to put it to good use!
omg today is going nuts! only if i could get gingerbread lol
Any chance for the source? Or at least say how you got it working?
could i unlock simlock my phone with flashing ur file?
lechicuong said:
could i unlock simlock my phone with flashing ur file?
Click to expand...
Click to collapse
No... 10char
i flashed this recovery via fastboot but any idea how to get in to recovery?
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Daniel_GB said:
i flashed this recovery via fastboot but any idea how to get in to recovery?
Click to expand...
Click to collapse
hold vol down while powering on. press vol down to scroll the choices and vol up to select android recovery
rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)
lol...positive..
Just to let you know I flashed the 1.8.3 sbf after unlocking and then tried to flash this and met with failure.
I then ran the unlock sbf again (only) and it flashed successfully. Perhaps flashing a previous sbf does "re lock" (at least partially) the phone?
rickriego said:
Not working for me.. keep getting "Failed to process command flash :recovery error (0x180002)....?
Click to expand...
Click to collapse
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol
Bakano said:
Don't shoot me if i'm wrong, but are you SURE you unlocked the bootloader?
I unlocked mine, but screwed a lot up, so i had to SBF flash... tried to run this and got the same error.... forgot to RE-unlock. Mine is rooted too (had to re-root), but idk if that is significant
hope this helps! =)
Click to expand...
Click to collapse
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..
rickriego said:
i thought i read that we should still be unlocked after sbf flash..and i did flash back to 1.83..and rooted btw..
EDIT: just came up with "BATTERY TOO LOW TO FLASH"..maybe thats the issue..
Click to expand...
Click to collapse
No I did the same thing and got the same error. you gotta reflash the unlock sbf to fix it. everyone is right.
You can enter recovery mode with "adb reboot recovery" too!
jruweaver said:
reflash the pudding sbf. I'm guessing you have flashed a different sbf since you unlocked
edit: NM slow typer lol
Click to expand...
Click to collapse
yep...flashed to 1.83 like you. i'm gonna charge up and try the steps u took..thanks..
Hi,
I downloaded CWM unofficial 6.0.32 from this forum, but I'm new and I have no idea what to do with it. I did successfully root my phone that's all I've done to it.
Thanks!
You use fastboot commands. There's a tutorial skeevy just made in general.
Sent from my PACMAN MATRIX HD MAXX
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Do you have the lastest motorola usb driver installed?
hungrymr2 said:
Do you have the lastest motorola usb driver installed?
Click to expand...
Click to collapse
Yes, Sir
Rick1488 said:
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Click to expand...
Click to collapse
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
No idea, but here's what I did to install cwm. download safestrap apk, boot to safestrap recovery, hit fix permission, go back to cmd prompt, fastboot flash it,
edit: try enabling "usb developer/debugging mode" before booting it into fastboot?
skeevydude said:
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
Click to expand...
Click to collapse
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
{
"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"
}
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Rick1488 said:
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Click to expand...
Click to collapse
You might have a picky motherboard. Some front-side ubs ports won't work for some odd reason for some users. Use a usb port on the back of your pc.
Out of curiousity, did you try flashing a fastboot with rsd before you started doing this? And if yes, did it finish completely?
Also attached is a zip to flash CWM from SSR (maybe...SSR might block the command) and a fastboot modified to only flash CWM. Both are untested but worth a shot.
EDIT: Any one of you windows users care to chime in? Ya'll know I don't run it. I'm kinda runnin outta ideas here....gettin down to the just use linux reply...
unlocked bootloader
I saw that you rooted but did you unlock the boot loader?
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
You're right...can't believe I missed that...never once is that mentioned...,
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
Um, I kinda forgot that part.. my fault. I just unlocked the bootloader and I'm gonna give it another try.
UPDATE: Success!
I'm sorry guys thanks for all your help.
:victory::victory:
hello, I'm kinda desperate on installing recoveries on my phone
I'm following this guide over here
USB debugging mode is turned on, but it is not detected on the shell/command window
when I checked my device manager, my device driver is not found, I tried installing flash tool drivers, but I dunno where to search for these drivers, so I followed the way in this thread
and I found 4 drivers in the list:
- Android ADB interface
- Sony ADB interface
- Sony Composite ADB interface
- Sony Fastboot Interface
tried all the ADB interface but still give same result so I uninstalled the driver back to the way it was
Please help me as I'm really newbie at this and I wanna try Stryflex ROM, thanks
Note:
1. I already unlocked my bootloader, but someone in here said to unlock bootloader first so I assume that it will end the same way as LB
2. The error I received from the command window is "device not found"
3. Phone version C3502
4. currently still using stock ROM with 12.1.A.1.207 firmware, rooted with towelroot
5. I unlock the bootloader using the step on sony site
Bump, pls help anyone?
Sent from my C5302 using Tapatalk
Please explain to me what you are actually wanting to do?
TechnoSparks said:
Please explain to me what you are actually wanting to do?
Click to expand...
Click to collapse
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
daryula said:
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
Click to expand...
Click to collapse
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
TechnoSparks said:
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
Click to expand...
Click to collapse
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
daryula said:
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
TechnoSparks said:
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
Click to expand...
Click to collapse
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
daryula said:
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
So you're on stock ROM, i believe?
TechnoSparks said:
So you're on stock ROM, i believe?
Click to expand...
Click to collapse
yes I'm on stock rom, but I have root access and unlocked bootloader
daryula said:
yes I'm on stock rom, but I have root access and unlocked bootloader
Click to expand...
Click to collapse
Alright then my link before would definitely help you out
TechnoSparks said:
Alright then my link before would definitely help you out
Click to expand...
Click to collapse
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
daryula said:
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
Click to expand...
Click to collapse
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
TechnoSparks said:
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
Click to expand...
Click to collapse
I got this notification
{
"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"
}
should be an okay I guess?
thanks for the help
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
daryula said:
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
Click to expand...
Click to collapse
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
TechnoSparks said:
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
Click to expand...
Click to collapse
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
daryula said:
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
Click to expand...
Click to collapse
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
TechnoSparks said:
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
Click to expand...
Click to collapse
I forgot to put the rom to my SD card and I don't have card reader
what to do with the files?
oh nvm, I somehow managed to learn how to move my files via adb command
thanks again for your help
Guys, I get it. The atrix HD is an old phone and by making this thread I am digging up the past, but I've searched everywhere on this site and still don't have an answer. First of all before you read this, please note that I am very new to this flashing business and don't understand a lot of the tech lingo you guys use all over this forum. Excuse me for being stupid.
The problem I am having is that every time I try to reboot into cwm recovery, it takes me to a screen that I will include a screenshot of down below.
Before I started any of this, I rooted my phone using towelroot, unlocked my boatloader (I think) using motopocalypse's file.
I then downloaded CWM 6.0.4.4. Recovery for the Atrix HD . I then used the app Flashify (yes I know. I'm dumb) to backup my stuff such as my kernel and all that and then tried to install the .IMG file from my SD card. It downloaded and then asked me if I wanted to reboot. I clicked yes and then it went on this screen that said something about recovery failure and it gave me status code 0. I'll post the picture don't worry. I tried using the ROM manager app to install cwm but it did the exact same thing
Guys I know I'm not very good at this, but could someone please explain to me how to flash a custom recovery without a computer on the Atrix HD? And please include simple small steps, because I'm not the smartest at this crap. Also if you could not use so much tech lingo that would be greatly appreciated.
Thanks guys
{
"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"
}
Sinlesstitan said:
Guys, I get it. The atrix HD is an old phone and by making this thread I am digging up the past, but I've searched everywhere on this site and still don't have an answer. First of all before you read this, please note that I am very new to this flashing business and don't understand a lot of the tech lingo you guys use all over this forum. Excuse me for being stupid.
The problem I am having is that every time I try to reboot into cwm recovery, it takes me to a screen that I will include a screenshot of down below.
Click to expand...
Click to collapse
Hi
First of all, I can't see the screenshot that you posted for some reason. Could you upload it again?
Also, about your problem, if you already unlocked the bootloader, this is what you need to do:
First of all, make sure you have correctly installed the Motorola drivers. You can get them on the motorola site. You will need a computer to do this, preferably one with Windows on it.
Then, if everything is right with the drivers, turn off the phone. Then you need to press and mantain the volume-down button and then press and mantain the power button. Mantain both buttons pressed until you see a dark screen with some letters on it. Make sure it reads somewhere "Bootloader UNLOCKED". If it does, you are doing great.
Next, check the file that I uploaded. As you can see, it has your name on it and it's a .zip file. You will need to extract the content, preferably on a new folder on the root of your drive (Assuming you are using Windows, that would be C:/nameofthefolder/).
Next, you will need to open a console window. There are many ways to do it, but you can search for it on Windows. When you find the icon (a black one), right clic and use "Run as administrator". Then you need to navigate to the folder in which you saved the files. In the console, type "cd .." and press enter until you get to the root of the drive, then "cd nameofthefolder" to get there.
Now, to the good part. If your phone is still in fastboot mode (the black screen with white letters), you will type the following in the console and press enter: "fastboot flash recovery philz_touch_6.43.4-moto_msm8960.img" without the "". What this will do is send a flash command to your phone and it will flash the recovery indicated. It will show some message and then in about 4 seconds it will be done. And that's it. If it doesn't works or it says that it can't find "fastboot" or something, make sure you are in the right folder.
To enter the recovery, turn off the phone, press volume-up button and power button, mantain both until you see a purple screen with some options. That's the recovery. And from there, you can install a zip, a new ROM, and do some nice things, but be careful.
If you have any other inquiry, let me know.
mauchito said:
Hi
First of all, I can't see the screenshot that you posted for some reason. Could you upload it again?
Also, about your problem, if you already unlocked the bootloader, this is what you need to do:
First of all, make sure you have correctly installed the Motorola drivers. You can get them on the motorola site. You will need a computer to do this, preferably one with Windows on it.
Then, if everything is right with the drivers, turn off the phone. Then you need to press and mantain the volume-down button and then press and mantain the power button. Mantain both buttons pressed until you see a dark screen with some letters on it. Make sure it reads somewhere "Bootloader UNLOCKED". If it does, you are doing great.
Next, check the file that I uploaded. As you can see, it has your name on it and it's a .zip file. You will need to extract the content, preferably on a new folder on the root of your drive (Assuming you are using Windows, that would be C:/nameofthefolder/).
Next, you will need to open a console window. There are many ways to do it, but you can search for it on Windows. When you find the icon (a black one), right clic and use "Run as administrator". Then you need to navigate to the folder in which you saved the files. In the console, type "cd .." and press enter until you get to the root of the drive, then "cd nameofthefolder" to get there.
Now, to the good part. If your phone is still in fastboot mode (the black screen with white letters), you will type the following in the console and press enter: "fastboot flash recovery philz_touch_6.43.4-moto_msm8960.img" without the "". What this will do is send a flash command to your phone and it will flash the recovery indicated. It will show some message and then in about 4 seconds it will be done. And that's it. If it doesn't works or it says that it can't find "fastboot" or something, make sure you are in the right folder.
To enter the recovery, turn off the phone, press volume-up button and power button, mantain both until you see a purple screen with some options. That's the recovery. And from there, you can install a zip, a new ROM, and do some nice things, but be careful.
If you have any other inquiry, let me know.
Click to expand...
Click to collapse
Thanks for replying man it really means a lot. I will definitely try this later today and I'll let you know if I run into any problems. Also, I sent you a private message with a link to the picture on it, due to the fact I'm new here, xda developers won't let me post pictures on a thread yet.
Sinlesstitan said:
Thanks for replying man it really means a lot. I will definitely try this later today and I'll let you know if I run into any problems. Also, I sent you a private message with a link to the picture on it, due to the fact I'm new here, xda developers won't let me post pictures on a thread yet.
Click to expand...
Click to collapse
I just saw your screenshot. It looks like your bootloader is still locked. It must say "UNLOCKED" for you to install a custom recovery. There is a thread around here to do that, I honestly don't remember how to do it since I did it like 2 years ago, but search on this forum and you will find it. In case you can't unlock your bootloader, let me know and we'll see what we can do.
Look the image that I just uploaded. This is what you are looking for. This is how it should say. Note that it says "Device is UNLOCKED. Status Code: 3". Yours says "LOCKED".
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
{
"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"
}
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Try power button + Volume down for up to 10 seconds.....should shutdown and reboot after a few seconds of shutdown
(Meaning, it will shutdown and appear to just be off.....but it will actually start to reboot after a few seconds of nothing.....so be prepared/ready to do the button mash to boot to recovery......it will vibrate once as it begins to boot again....
*****edit.....
Sorry I'm in the wrong thread (different phone), but its possible you need to press and hold power plus volume up/or volume down.
Best of luck
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for the suggestion, but sadly for me it doesn't work. My phone doesn't shutdown at all and is just in this perpetual charging state even after holding the power button for 30 seconds.
Hanzor said:
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Click to expand...
Click to collapse
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
reg66 said:
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
Click to expand...
Click to collapse
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Hanzor said:
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Click to expand...
Click to collapse
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
reg66 said:
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
Click to expand...
Click to collapse
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
reg66 said:
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
Click to expand...
Click to collapse
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Hanzor said:
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Click to expand...
Click to collapse
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
That's alright, I'm fine with later or tommorow as well. Rest well, and thanks!
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Hanzor said:
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Click to expand...
Click to collapse
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
reg66 said:
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
Click to expand...
Click to collapse
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Hanzor said:
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Click to expand...
Click to collapse
Excellent. Glad it's all good again :good: