Related
I tried installing chainfire3d driver in jellybean( i didnt know then that it is not for JB). Now my nexus wont boot into os. it just stays at the unlocked bootloader logo.
1. I can get into recovery mode
2. I have wiped out the cache and factory reset
3. I dont have a update file in my phone.since nexus dont have an external sd card i cant put any file in it directly.
4. I have tried fastboot -it shows my serial ID and i am able to reboot my phone using it but whenever i try to flash recovery.img or update update.zip it shows "cannot load recovery.img" or "cannot update update.zip"
5. I have tried ADB - on using adb shell it shows "error:device not found"
6. on using Odin (not sure whether it is compatible with Nexus s) it detects my phone. when i tried to flash the stock fireware it fails and my device shows "verify image (radio) fail"
Plz help.Is my phone bricked???????
Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.
What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S
polobunny said:
Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
kwibis said:
What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
amvignesh said:
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
Click to expand...
Click to collapse
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Cascabreu said:
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
Click to expand...
Click to collapse
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.
amvignesh said:
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.
Click to expand...
Click to collapse
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)
Cascabreu said:
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)
Click to expand...
Click to collapse
Thanks a lot Cascabreu.it worked . i never knew one could drag and drop files in command prompt(wonder y it didnt work otherwise, I had specified the path correctly).Thanks again..will change the thread topic accordingly....
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
I just lolled xD
Sent from my Nexus S
kwibis said:
I just lolled xD
Sent from my Nexus S
Click to expand...
Click to collapse
helppp..im also facing the same prob...i dun know how to run adb shell and those stufff after that...:crying:
C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Good job.. I wouldn't have thought of that...
Sent from my Nexus S using XDA Premium 4 mobile app
C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance
tlangey said:
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance
Click to expand...
Click to collapse
either u can find onlien a way to flash back to stock.
or ur best bet is to go to the store and say u got an update but it failed and that now its not turning on. Warranty will cover that
ok so i have a htc sensation and i installed clockwork mod touch recovery.
i then flashed cm10.1 and wiped data and dalvik but it stayes at the spinning cyanogenmod boot animation
am i using the wrong kernal as i couldent find one on the jellybean post http://forum.xda-developers.com/showthread.php?t=2115520
SamzWorldOfMusic said:
ok so i have a htc sensation and i installed clockwork mod touch recovery.
i then flashed cm10.1 and wiped data and dalvik but it stayes at the spinning cyanogenmod boot animation
am i using the wrong kernal as i couldent find one on the jellybean post http://forum.xda-developers.com/showthread.php?t=2115520
Click to expand...
Click to collapse
why did you wipe data and dalvik after rom's installation?
follow these steps
full wipe from recovery
flash the rom
flash gapps
reboot
done
note:the initial boot takes a while
rzr86 said:
why did you wipe data and dalvik after rom's installation?
follow these steps
full wipe from recovery
flash the rom
flash gapps
reboot
done
note:the initial boot takes a while
Click to expand...
Click to collapse
ok will try now sorry for multiple post btw
edit nope still stuck spinning anything else i could have done wrong. i didnt root the stock os before installing cm10 could this be why
SamzWorldOfMusic said:
ok will try now sorry for multiple post btw
edit nope still stuck spinning anything else i could have done wrong. i didnt root the stock os before installing cm10 could this be why
Click to expand...
Click to collapse
no it doesn't matter if you didn't root the stock one
cm10 comes already pre-rooted
do this
connect your device in fastboot mode to pc(in bootloader must say fastboot usb)
extract the boot.img from the rom.zip and place it in your adb and fastboot folder(i assume you have installed sdk tools)
open in that folder a cmd window and do fastboot flash boot boot.img
then do fastboot reboot
rzr86 said:
no it doesn't matter if you didn't root the stock one
cm10 comes already pre-rooted
do this
connect your device in fastboot mode to pc(in bootloader must say fastboot usb)
extract the boot.img from the rom.zip and place it in your adb and fastboot folder(i assume you have installed sdk tools)
open in that folder a cmd window and do fastboot flash boot boot.img
then do fastboot reboot
Click to expand...
Click to collapse
i already have but the boot.img from the rom zip has no recovery if i press recovery it continues to boot cm10
SamzWorldOfMusic said:
i already have but the boot.img from the rom zip has no recovery if i press recovery it continues to boot cm10
Click to expand...
Click to collapse
actually you flash the boot.img from pc
you misunderstood me
edit:wait do you have a problem for booting to the recovery?
rzr86 said:
actually you flash the boot.img from pc
you misunderstood me
edit:wait do you have a problem for booting to the recovery?
Click to expand...
Click to collapse
i did flash from pc using (fastboot flash recovery boot.img) command it flashes sucsessfully but when i enter recovery via bootloader it just starts booting instead of entering recovery but itf i flash cwm recovery it enters recovery fine. if you want i can upload a video showing whats happening.
SamzWorldOfMusic said:
i did flash from pc using (fastboot flash recovery boot.img) command it flashes sucsessfully but when i enter recovery via bootloader it just starts booting instead of entering recovery but itf i flash cwm recovery it enters recovery fine. if you want i can upload a video showing whats happening.
Click to expand...
Click to collapse
let me put it simple
for flashing recovery ->fastboot flash recovery recovery.img
for flashing boot.img ->fastboot flash boot boot.img
do you see your mistake now?
rzr86 said:
let me put it simple
for flashing recovery ->fastboot flash recovery recovery.img
for flashing boot.img ->fastboot flash boot boot.img
do you see your mistake now?
Click to expand...
Click to collapse
OOOOhh okay i see now i feel dumb just did it and its booting well see what happens
edit still stuck at cm boot animation ;\ sorry if im really noobish i have never modified a htc before
SamzWorldOfMusic said:
OOOOhh okay i see now i feel dumb just did it and its booting well see what happens
edit still stuck at cm boot animation ;\ sorry if im really noobish i have never modified a htc before
Click to expand...
Click to collapse
still stuck at cm logo?
did you wait enough?
can you post again your bootloader details?
rzr86 said:
still stuck at cm logo?
did you wait enough?
can you post again your bootloader details?
Click to expand...
Click to collapse
its the se as the other post details nothing has changed
SamzWorldOfMusic said:
its the se as the other post details nothing has changed
Click to expand...
Click to collapse
what recovery do you have installed?
rzr86 said:
what recovery do you have installed?
Click to expand...
Click to collapse
cwm touch recovery
SamzWorldOfMusic said:
cwm touch recovery
Click to expand...
Click to collapse
change it to 4ext recovery
link in my signature
somewhere it says If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
click on download,extract the recovery.img and place it in your adb and fastboot folder
you know the rest
don't make any mistake while entering fastboot command hehe
after that flash again cm rom
rzr86 said:
change it to 4ext recovery
link in my signature
somewhere it says If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
click on download,extract the recovery.img and place it in your adb and fastboot folder
you know the rest
don't make any mistake while entering fastboot command hehe
after that flash again cm rom
Click to expand...
Click to collapse
ok will try
SamzWorldOfMusic said:
ok will try
Click to expand...
Click to collapse
OMG IT BOOTED THANK YOU SO MUCH I THOUGHT I WAS F*D.
i clicked the thanks button for you
SamzWorldOfMusic said:
OMG IT BOOTED THANK YOU SO MUCH I THOUGHT I WAS F*D.
i clicked the thanks button for you
Click to expand...
Click to collapse
but wifi dosent seem to work
SamzWorldOfMusic said:
but wifi dosent seem to work
Click to expand...
Click to collapse
and now it works
SamzWorldOfMusic said:
and now it works
Click to expand...
Click to collapse
just to know
if you ever face wifi error the first thing we are doing is flashing the boot.img via fastboot
glad for you mate:good:
Hey there!
I have the follwing problem:
I tried to install the Cyanogen mod on my htc explorer.
I followed the instructions posted here, but when it comes to the part where I have to go in the recovery mode.
And It seems, that I have not installed the Clockworkmod recovery correctly, so I cant get into it.
When I choose reset to factory settings in the bootloader mode, and when I try to start the phone,
there is only the "htc" symbol which stays there and the phone does not start.
Is there a possibility to save the phone or did I destroy it? =D
Thanks, and sorry for my bad explanations =D
FLo
rooooks said:
Hey there!
I have the follwing problem:
I tried to install the Cyanogen mod on my htc explorer.
I followed the instructions posted here, but when it comes to the part where I have to go in the recovery mode.
And It seems, that I have not installed the Clockworkmod recovery correctly, so I cant get into it.
When I choose reset to factory settings in the bootloader mode, and when I try to start the phone,
there is only the "htc" symbol which stays there and the phone does not start.
Is there a possibility to save the phone or did I destroy it? =D
Thanks, and sorry for my bad explanations =D
FLo
Click to expand...
Click to collapse
Try to flash a recovery through fastboot
It will work as you said recovery was not installed..
TYPE THIS COMMAND
fastboot flash recovery recovery.img (Rename the recovery to recovery.img)
Worked, thank you =)
shubhojit89 said:
Try to flash a recovery through fastboot
It will work as you said recovery was not installed..
TYPE THIS COMMAND
fastboot flash recovery recovery.img (Rename the recovery to recovery.img)
Click to expand...
Click to collapse
[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.
aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"
FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading
El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes
El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:
FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
it goes in the same folder on your computer as where fastboot is located. then fastboot flash recovery recovery.img
I have fastboot, adb and recovery image in the same folder on my desktop.
mgf8384 said:
I have fastboot, adb and recovery image in the same folder on my desktop.
Click to expand...
Click to collapse
the android laying on its back is the stock recovery btw. did you rename the recovery properly? is it still an img file?
mgf8384 said:
Each time i get failed remote error image is not a boot image....
Click to expand...
Click to collapse
Its not a boot image, Its a recovery image. You sure your typing the correct command?
Esit: Just done some googling and someone had the same problem. Was due to a bad download.
Edit 2: ah just read again and you said you tried 2 types of recovery. Scrap my 1st edit then?
Sent from my Nexus 5 using XDA mobile app
mgf8384 said:
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
Click to expand...
Click to collapse
You'll just be doing wrong and no, nothing needs to be in the same folder of you installed it properly. Click the link in my signature to the sticky thread and read my adb and fastboot thread.
Also ensure "hide known file extensions" is turned off in windows.
If you need more help, you should post screenshots of your cmd window.
Sent from my Nexus 5 using Tapatalk
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
the way it was renamed.
There's no need to rename it....for future flashes.
KJ said:
There's no need to rename it....for future flashes.
Click to expand...
Click to collapse
i rename it to simple 3-4 letter words, for ease of typing
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Just brought it up, cause in this case...he wouldn't have had an issue if he left it.
But yeah, I do that too. Lol
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
Because you had "hide file extensions" on in windows like I said.
File was called whatever.img but you can only was whatever because. .img is hidden. So when you rename it, it only let's you rename whatever (leaving .img hidden and unchanged) so you rename what's visible to recovery.img and results are obvious
(whatever).img > (recovery.img).img
So the quick lesson - turn off "hide known file extensions" in windows. Not just for this reason but for your own security. .exe files with word doc icons etc
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Or type first letter or two then press tab
Sent from my Nexus 5 using Tapatalk
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
siddjazz said:
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
Click to expand...
Click to collapse
Go to general and read the sticky thread about 5.0 roms and recovery