Related
I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
You said your phone is s-off and "rootly rooted". I assume you meant "permanently rooted"? Did you use the right version of superuser (2.3.6.3 or above) and clockwork recovery image (4.0.0.9)? You can ignore the "no image" message, I get them all the time and I can still boot into recovery no problem.
I have the right superhero version but i don't think I have the right clockwork. How could I fix it, without having to boot into recovery.
Sent from my myTouch_4G_Slide using XDA App
imjames said:
I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Sounds like you need to reflash your recovery. Since you can get into fastboot still, this is an easy fix.
Just download the recovery image from here -
http://android.modaco.com/topic/343...e-mytouch-4g-slide-unofficial-modaco-edition/
once downloaded, enter hboot and select fastboot. Once your phone says "fastboot usb" on it enter the following command into fastboot -
Fastboot flash recovery c:/android/tools/recovery.img
The "c:/android/tools/recovery" portion of that command will be variable based on where the downloaded recovery image is contained on your computer.
Id say that has a pretty good chance of fixing your prollem =). Keep me posted
Sent from my myTouch_4G_Slide using xda premium
do i have to have adb to do it, because thats learning in progress
imjames said:
do i have to have adb to do it, because thats learning in progress
Click to expand...
Click to collapse
um, yeah. Fastboot is like ADB, but a different tool included in the SDK. Do you have the SDK? It's relatively simple, let me just break it down to maximize simplicity.
1) If you don't have the SDK, download it (in zip format) here. If you do have the SDK,
2) for simplicity's sake, create a Directory on your computer (the hard drive root) entitled "Android" (so that it's c:\Android).
3) If you didn't previously have the SDK, once it is is downloaded, extract the files.
4) assuming you run windows, navigate to the SDK, there's a subdirectory called "tools". Move that folder into the Android folder you created.
5) Now. take that recovery.img that you downloaded... (if you haven't done so yet, look to the link I provided in my previous post) move IT to the Android folder as well
6) open a command prompt and change the directory to the tools subdirectory of the Android folder (type cd c:android\tools), You'll now see a command prompt beginning with C:\Android\tools
7) make sure your phone is connected to your computer and in fastboot mode (select "fastboot" from the Hboot screen, it'll then say "fastboot usb" on the screen). I"m assuming your drivers are already properly installed since you were able to root your phone.
8) type in the following command into the commmand prompt - "fastboot flash recovery c:\android\recovery.img
That should do it =)
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
imjames said:
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Because:
AndroidAutobot said:
... (type cd/c:android/tools) ...
Click to expand...
Click to collapse
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Blue6IX said:
Because:
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Click to expand...
Click to collapse
Oops lol. I cant believe i did that ha ha. Thanks for spotting that =)
I've corrected all the command lines in that particular post. Should be able to follow it step by step without any trouble now.
Sent from my HTC Doubleshot using xda premium
So i've done this many times on the samsung galaxy S3
i'm doing this for a friend
i've rooted the phone, everything required..
i use twrp and goo manager and installed several custom roms but they always get stuck when booting for the first time, it just spins for way over 30 minutes. i do wipe the system and cache.
i've read some pages i need to use a boot.img but i'm unsure on this..
am I missing a step here?
thanks
First this should be in th Q&A section.
If you phone has hboot 1.14 then yes you do need to flash the boot.ing for the Rom. Open the rom.zip and look for the boot.img. There are several places to get fastboot from on this forum, but download fastboot and copy the boot.img to the same folder you have fastboot in. Open command prompt and navigate to the fastboot folder. Boot phone into bootloader and select fastboot. Connect phone to pc and then type "fastboot flash boot boot.img" When its done reflash the rom and then reboot.
Sorry for being a little terse but I typed this on my phone.
Sent from my VenomXL using Xparent Red
you can grab adb/fastboot from this very forum, in the stickies.. "gunnymans quick and dirty adb/fastboot primer" download it and extract it, put it on your (c: ) drive... take the boot.img out of the rom. drop it inside of your adb folder... right click on the folder and choose open command prompt here.. follow imagios instructions after that
InflatedTitan said:
you can grab adb/fastboot from this very forum, in the stickies.. "gunnymans quick and dirty adb/fastboot primer" download it and extract it, put it on your (c drive... take the boot.img out of the rom. drop it inside of your adb folder... right click on the folder and choose open command prompt here.. follow imagios instructions after that
Click to expand...
Click to collapse
Thanks Titan for the link. Couldnt hardly find anything on my phone.
Sent from my VenomXL using Xparent Red
ImagioX1 said:
Thanks Titan for the link. Couldnt hardly find anything on my phone.
Sent from my VenomXL using Xparent Red
Click to expand...
Click to collapse
I was gonna link it... But I have to stop spoonfeeding them... This way I can get them to browse the sticky's lol
Sent from my One X using Tapatalk 2
I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.
After unsuccessfully attempt to flash identity crisis phone not able to flash any other rom seems to me bricked, any solution?
Sent from my MI PAD using XDA Free mobile app
Fastboot flash the XT1033 5.0.2 Firmware Image for your phone from here:
http://forum.xda-developers.com/mot...y-firmware-t3110795/post60792279#post60792279
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If you have problems, provide a full and complete fastboot log (copy and paste the fastboot screen)
I am on cm 12.1 now.
I wanted to use your rom.
Sent from my MI PAD using XDA Free mobile app
Nishblueweapon said:
I am on cm 12.1 now.
I wanted to use your rom.
Click to expand...
Click to collapse
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Will try buddie
Sent from my MI PAD using XDA Free mobile app
lost101 said:
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Click to expand...
Click to collapse
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Nishblueweapon said:
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Click to expand...
Click to collapse
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
sachoosaini said:
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
Click to expand...
Click to collapse
I am on win. 7. It first gave me an error adpwinal.DLL file is missing from your PC while I was trying to flash those commands in cmd window, so I installed that file on my PC. Whenever I am in fastboot mode now it doesn't recognise me device. & normally it does. I think the problem with fastboot files, it shows USB connected. Will try what u said.
Sent from my Moto G using XDA Free mobile app
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Nishblueweapon said:
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Click to expand...
Click to collapse
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
Got it to boot successfully. Thank u
What I did was flashed 1 more system I.e. 0 not mentioned in the op
Sent from my MI PAD using XDA Free mobile app
So I'm trying to install TWRP but I cannot find the appropriate folders because I cannot find the adb.exe or the fastboot.exe.
I used the adb installer successfully and I can use the CMD to boot my device to the bootloader.
The device is also unlocked.
You used the Minimal Adb fastboot installer?
Look for folder C:/minimal adb.
Could also be C:/adb depending which version you installed.
Use the search function in Explorer
Sent from my Nexus 5X using Tapatalk
berndblb said:
You used the Minimal Adb fastboot installer?
Look for folder C:/minimal adb.
Could also be C:/adb depending which version you installed.
Use the search function in Explorer
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Aha, I looked at two different guides. I used the 15 seconds ADB installer.
Thanks, found it in system
Yes.
You sure you are searching your C drive?
What Windows version do you have? Explorer's search function always stank. Less so in Win10 but still....
Took Windows to find my adb 3 minutes. Saladin needs 30 seconds...
FreeCommander is also a neat file explorer....
Look on C:\Program Files too
Sent from my Nexus 5X using Tapatalk