Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
EDIT: In case anyone has this issue searching threads, I just used Wug Toolkit to flash everything back to stock and then used the same Toolkit to unlock and root. TWRP isn't going to recognize a backup from a different phone. To my understanding, there is a way around that, but I didn't look into it. Oh, and apparently, don't flash the EFS partition lol
New Jer-Z said:
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
Click to expand...
Click to collapse
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
mpalomba3 said:
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
Click to expand...
Click to collapse
Oh, that reminds me, TWRP wasn't able to mount any of the directories, it seems. I think it can, now, but I remember seeing those errors in the log before I wiped everything. Thanks for that suggestion, i'll give it a shot.
No problem, report back if it works
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Odin is for Samsung devices
sent from my HAMMERHEAD neXus
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
El Daddy said:
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
OK!
So, I used the Wug toolkit to basically flash everything to stock, and then root it. I installed TWRP using the app and I tried using the app to restore from my earlier back up. So, it boots into recovery but nothing happened. Looking at the log, it says the TWRP isn't able to locate the files. Trying to just restore from recovery isn't helpful because when I hit "Restore" nothing pops up. As if the SDCard partition isn't being accessed. I can't see any of the files in any directory. Anyone have any ideas?
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I realize that now lol. Well, I fixed that, but now have a new issue. Any ideas for me?
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I had a copy saved on my desktop, so I transferred it back.
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Sorry about that, I have a gs4 so I thought Odin was for all devices
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
New Jer-Z said:
I had a copy saved on my desktop, so I transferred it back.
Click to expand...
Click to collapse
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
housry23 said:
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Someone explained to me TWRP won't recognize a backup with a serial number from a different phone. So essentially, I will just have to forego it. I used Wug Toolkit to fix this issue and just flashed everything to stock and had the same toolkit unlock and root. Using ADB was a fail and cost me a whole afternoon lol
Related
I installed a wrong program through CWM and after that there is a yellow watermark on the phone. (attached show the screen).
Pleaaaase help me to fix the phone. I tried many roms but no results.
My tablet is GT-N8000.
Can you provide more information. Like what you flashed how you done it.and what you can and can't do with the tab as it is.Like do you have cwm can you get Odin Joe's to work.
Kies has a emergency recocery try that first if no go try flashing a stock rom with Odin.just guessing with the partial info you provided
Be careful and good luck
erica_renee said:
Can you provide more information. Like what you flashed how you done it.and what you can and can't do with the tab as it is.Like do you have cwm can you get Odin Joe's to work.
Kies has a emergency recocery try that first if no go try flashing a stock rom with Odin.just guessing with the partial info you provided
Be careful and good luck
Click to expand...
Click to collapse
I accidentally installed busybox by CWM but it was designed for galaxy tab 10.1 instead of galaxy note 10.1. Now, the device has some problems like it does not detect the sim cart and so on. I can install new frameworks and I have CWM but nothing happens when I install new framework or wipe the device. Also, I tried a stock rom but .... .
I really need help.
sorry for bad english.
Never would have guessed busybox that is usually pretty generic and doesn't have much to do with nonroot apps would cause issues like what you seem to be experiencing.. crazy stuff but good luck!
If nothing else Odin back to newest stock using the stock Odin package that is usually found among your device "stickied" threads. I don't have a gnote but I have had many galaxy devices and Odin is the cure for all ills
Sent from my Galaxy Nexus using Tapatalk 2
How can I reset the device to first time run state. Like it asked me about personal info and gmail account at start up?
each time I install new framework it begins to the OS without asking about these info.
Could always try to install busybox from the market.. Exactly what zip did you use and where did it come from please I would like to look inside it
Sent from my Galaxy Nexus using Tapatalk 2
wizayne said:
Could always try to install busybox from the market.. Exactly what zip did you use and where did it come from please I would like to look inside it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here is the zip file, I tried to install ubuntu and I followed an instruction in youtube but it was for galaxy tab 10.1 instead of galaxy note. I acted like a stupid. I'm totally messed up.
here is the link and file:
mirror20.downloadandroidrom.com/download/GalaxyTab10.1/tools/su_busybox_misc-sam_tab_10.1-061611.zip?token=162686692
stulker said:
Here is the zip file, I tried to install ubuntu and I followed an instruction in youtube but it was for galaxy tab 10.1 instead of galaxy note. I acted like a stupid. I'm totally messed up.
here is the link and file:
mirror20.downloadandroidrom.com/download/GalaxyTab10.1/tools/su_busybox_misc-sam_tab_10.1-061611.zip?token=162686692
Click to expand...
Click to collapse
FLASH STOCK IN ODIN.
Sent from my GT-N7100 using XDA Premium HD app
Mister_Mxyzptlk said:
FLASH STOCK IN ODIN.
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
NOT WORKED!!
GOD DAMMIT. I wonder why the device run into the OS and not asked me about my personal info like the first time that I started the phone. can you tell me how to delete all data in the device even the download counter?
stulker said:
NOT WORKED!!
GOD DAMMIT. I wonder why the device run into the OS and not asked me about my personal info like the first time that I started the phone. can you tell me how to delete all data in the device even the download counter?
Click to expand...
Click to collapse
Flash stock in ODIN. Wipe data/factory reset in stock recovery. Reboot. Enjoy.
Check Triangle Away thread for flash counter. You didn't do your homework. You should learn how to recover your device BEFORE you frak it up. Good luck.
Sent from my GT-N7100 using XDA Premium HD app
There is point when I start in system recovery it shows:
E: failed to mount /efs (Invalid argument)
is it ok?
also the yellow hint in the screen that I showed in the first comment indicates a software error.
Mister_Mxyzptlk said:
Flash stock in ODIN. Wipe data/factory reset in stock recovery. Reboot. Enjoy.
Check Triangle Away thread for flash counter. You didn't do your homework. You should learn how to recover your device BEFORE you frak it up. Good luck.
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
I think language barrier is keeping open from understanding
OK go here follow instructions for flashing Tom with Odin.download stock rom. You do not have to flash cwm flash stock rom instead boot your tablet
Never flash your device or install software until you know how to revert back
I do not recommend new to android people to tinker with this device. Stay stock for now
http://forum.xda-developers.com/showthread.php?t=1831152
Off topic hi Mister prp area here. I love Louisville
erica_renee said:
I think language barrier is keeping open from understanding
OK go here follow instructions for flashing Tom with Odin.download stock rom. You do not have to flash cwm flash stock rom instead boot your tablet
Never flash your device or install software until you know how to revert back
I do not recommend new to android people to tinker with this device. Stay stock for now
http://forum.xda-developers.com/showthread.php?t=1831152
Off topic hi Mister prp area here. I love Louisville
Click to expand...
Click to collapse
Thank you for your help. But I think I have a different problem. I flashed stock rom (several big roms about 1GB) but nothing happened. When I try to wipe data/factory reset it shows E; failed to mount /efs (Invalid argument). I think I need to mount /efs and format it.
I think I missed some files in the efs folder. the phone status shows that some basic info are missed from the phone. check the attached.
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337
Hi all, I'm pretty new to the forums, so please forgive my noob-ousity.
I have got a Nexus S it's a I9020A, I Rooted and unlocked my phone a long time ago, and all was well and good for a while, then I started getting major slow downs, So I started doing a regular format to try and get rid of clutter, and it helped for a while, then last night I got tired of it always bogging down, so I did something very stupid, I went to recovery and formatted/wiped everything that had the option to do so.
Now my phone reboots directly to bootloader, I can go into recovery and I have the clockworkmod v5.8.0.2,
I have tried;
- Updating to the newest clockwork (6.0.3.1), it just makes it so my pc no longer recognizes my phone and I can't copy anything to the sdcard. So I had to revert.
- Using the Sabra One Click Root Tool! to recover things to a normal state, (a google search on my troubles prompted me to try this). It doesn't seem to change anything. When this finishes, just before getting the "congrats ur device is now rooted blah blah blah" I get a few errors that flash on the screen saying;
can't remove recovery-from-boot.p
can't remove install-recovery.sh
postrecoveryboot.sh not found.
- Freeboot and adb, neither seem to want to pick up my device even though everything else seems too.
- Copying update.zip and running it from the clockworkmod interface, it doesnt seem to change anything.
I'm sure I'm just missing something, but when I google my issue I get a lot of people stuck in bootloader unable to do any of the stuff I tried. Nothing that really has my exact problem for my phone.
Try Nexus Root Toolkit. Works flawlessly if you read the instructions carefully.
ej8989 said:
Try Nexus Root Toolkit. Works flawlessly if you read the instructions carefully.
Click to expand...
Click to collapse
I did exactly that, when doing a search, all the different tools one can use, the options can be kind of intimidating, especially when you don't know really what your issue is, the Nexus Root Toolkit does pretty much everything. As you said, it works flawlessly.
I flashed back to stock, and it works again.
Thanks so much for your help
Mr.M.Grey said:
I did exactly that, when doing a search, all the different tools one can use, the options can be kind of intimidating, especially when you don't know really what your issue is, the Nexus Root Toolkit does pretty much everything. As you said, it works flawlessly.
I flashed back to stock, and it works again.
Thanks so much for your help
Click to expand...
Click to collapse
awhere do I find a original Firmware for nexus s, pleace?
dark'em said:
awhere do I find a original Firmware for nexus s, pleace?
Click to expand...
Click to collapse
When I downloaded the Nexus toolkit, it asks you what device you are using and what version, just tell it the newest one, in my case it was android 4.1.2 JZO54K and it will automatically download the original firmware for you, at least that was my understanding.
Mr.M.Grey said:
When I downloaded the Nexus toolkit, it asks you what device you are using and what version, just tell it the newest one, in my case it was android 4.1.2 JZO54K and it will automatically download the original firmware for you, at least that was my understanding.
Click to expand...
Click to collapse
Ooo I see now, thank you
dark'em said:
Ooo I see now, thank you
Click to expand...
Click to collapse
Not a problem, good luck!
Edit: Nevermind!
Sent from my GT-N8013 using xda app-developers app
Hey everyone,
I am new to the android phone arena and would appreciate some help.
I bought the nexus 5, rooted it and was attempting to flash CyanogenMod 11. I didnt realize I need a windows computer to do and was trying to do it through the phone itself. (i know, i know...terrible, like I said, I'm new)
The phone froze and will not even restore from a factory reset. It is like it is trying to reset from the CyanogenMod ROM (which wasnt installed properly in the first place). I have tried restoring from a backup, but none exists. I tried mounting a flash drive with the stock hammerhead ROM on it, but it will not mount. I am using ClockwordMod Recovery v6.0.4.4.
Can anyone help me?
Fastboot flash the factory images
Sent from my Nexus 5
Pirateghost said:
Fastboot flash the factory images
Sent from my Nexus 5
Click to expand...
Click to collapse
can you walk me through how to do that? I honestly have no idea. sorry.
kdmylin said:
Hey everyone,
I am new to the android phone arena and would appreciate some help.
I bought the nexus 5, rooted it and was attempting to flash CyanogenMod 11. I didnt realize I need a windows computer to do and was trying to do it through the phone itself. (i know, i know...terrible, like I said, I'm new)
The phone froze and will not even restore from a factory reset. It is like it is trying to reset from the CyanogenMod ROM (which wasnt installed properly in the first place). I have tried restoring from a backup, but none exists. I tried mounting a flash drive with the stock hammerhead ROM on it, but it will not mount. I am using ClockwordMod Recovery v6.0.4.4.
Can anyone help me?
Click to expand...
Click to collapse
Ok lets try decrypting this first.
It sounds like you got through the rooting process,and got yourself a custom recovery. Ok
You flashed CM11, but it started to boot loop on you.You tried to revert back to stock, but you failed to make a backup. Now you are stuck since you cant mount the phone as a disk from recovery and restore a working rom.
Is this what is going on?
If so, you still have hope. You can use adb from the boot loader and push the stock firmware back on.
Follow this thread and start over from the beginning.
http://forum.xda-developers.com/showthread.php?t=2513701
Yes, Un-root, go back to stock and try this again. Next time, make a backup before Flashing like mad.
kdmylin said:
can you walk me through how to do that? I honestly have no idea. sorry.
Click to expand...
Click to collapse
Google provides the factory images and the instructions on how to do it. The onus is on you.
Sent from my Nexus 5
Wow haven't seen pirateghost since the HTC vivid days.
Sent from my Nexus 5 using XDA Premium 4 mobile app
devoureddreams said:
Wow haven't seen pirateghost since the HTC vivid days.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Been hanging out in the nexus devices
Sent from my Nexus 5
Follow egofreak's guide. Good rule of thumb: if it boots, you can fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Wasup fellas?
Pardon my crappy grammar, im writing on a french keyboard and its not familliar.
I was trying to do the HTC one m8 verizon to full t mobile compatibility change but something went wrong. Im stuck in the white screen and the only thing that works is recovery. I thought i backed it all up but when i went to restore, lo and behold, no file. So here I am. Stuck with the "no image wrong image!" message. It seems that my computer recognizes the phone because when i write "fastboot" in cmd a long list of stuff pops up.
This guy had the same issue; http://forum.xda-developers.com/showthread.php?t=2789965
Somebody said "Flash stock rom and its recovery from this thread http://forum.xda-developers.com/show....php?t=2701376 "
But the thread is huge and I dont know what im looking for nor how to install it since my phone doesnt show up in my computer in the way that a USB key does, so i cannot put files in it.
There seem to be other threads on this issue out there but to be honest i cant understand the technical mumbo jumbo. Im not completely computer illiterate but i am new to this whole phone hacking thing. So, in layman terms, what am I to do?
john805 said:
Wasup fellas?
Pardon my crappy grammar, im writing on a french keyboard and its not familliar.
I was trying to do the HTC one m8 verizon to full t mobile compatibility change but something went wrong. Im stuck in the white screen and the only thing that works is recovery. I thought i backed it all up but when i went to restore, lo and behold, no file. So here I am. Stuck with the "no image wrong image!" message. It seems that my computer recognizes the phone because when i write "fastboot" in cmd a long list of stuff pops up.
This guy had the same issue; http://forum.xda-developers.com/showthread.php?t=2789965
Somebody said "Flash stock rom and its recovery from this thread http://forum.xda-developers.com/show....php?t=2701376 "
But the thread is huge and I dont know what im looking for nor how to install it since my phone doesnt show up in my computer in the way that a USB key does, so i cannot put files in it.
There seem to be other threads on this issue out there but to be honest i cant understand the technical mumbo jumbo. Im not completely computer illiterate but i am new to this whole phone hacking thing. So, in layman terms, what am I to do?
Click to expand...
Click to collapse
No image wronge image is not your problem. That simply means you don't have an RUU file on your SD card. The bootloaderr checks each time you enter it looking for an RUU file because that's how it flashes them.
fastboot flash TWRP. Boot the phone into TWRP (recovery). Copy the rom you intended to use to your SD card/internal storage. Flash that rom in TWRP.
dottat said:
No image wronge image is not your problem. That simply means you don't have an RUU file on your SD card. The bootloaderr checks each time you enter it looking for an RUU file because that's how it flashes them.
fastboot flash TWRP. Boot the phone into TWRP (recovery). Copy the rom you intended to use to your SD card/internal storage. Flash that rom in TWRP.
Click to expand...
Click to collapse
Hey,
thanks for the assistance. I'm not quite sure what I should do. I'm in recovery / install and I have two files in there, Android_revolution_HD_one_M8_43.0.zip
and ElementalX-m8-0.4-Sense.zip
I've tried installing both (flash=install, no?) but I run into the same issue.
Edit: I was basically trying to follow this guide http://forum.xda-developers.com/showthread.php?t=2710720
What should I flash?
Thanks
john805 said:
Hey,
thanks for the assistance. I'm not quite sure what I should do. I'm in recovery / install and I have two files in there, Android_revolution_HD_one_M8_43.0.zip
and ElementalX-m8-0.4-Sense.zip
I've tried installing both (flash=install, no?) but I run into the same issue.
Click to expand...
Click to collapse
Did you do a factory reset in twrp before flashing?
Sent from my Nexus 6 using Tapatalk
dottat said:
Did you do a factory reset in twrp before flashing?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I did not. I shall try that now. Spanx.
Nevermind I found it
dottat said:
Did you do a factory reset in twrp before flashing?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK I tried it, didn't work. Still the same error message.
john805 said:
OK I tried it, didn't work. Still the same error message.
Click to expand...
Click to collapse
Now just try flashing ahrd rom and not the kernel
Sent from my Nexus 6 using Tapatalk
dottat said:
Now just try flashing neos rom and not the kernel
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Not really sure what that means.
I googled it and this came up:
https://www.youtube.com/watch?v=i2Y-xaVAGkQ
john805 said:
Not really sure what that means.
I googled it and this came up:
https://www.youtube.com/watch?v=i2Y-xaVAGkQ
Click to expand...
Click to collapse
I mean just flash ahrd. Don't flash elemental
Sent from my Nexus 6 using Tapatalk
dottat said:
I mean just flash ahrd. Don't flash elemental
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried flashing "Android_revolution_HD_one_M8_43.0.zip"
but I get the same end result. If that's what you mean. I'm not really sure. If not, how do I flash anything if the phone doesn't seem to show up on my computer where all my hard drives are. Can I do it through the command prompt?
I'm totally lost, I tried googling what you said but a whole bunch of super complicated stuff shows up. I'm gonna need to take some baby steps here. What file exactly am I flashing and how?