Related
I rooted and flash my nexus one with a rom that was based on the cm7 nightly. It installed completely and I rebooted. It gets past the static x but loops in the moving x. I've tried so many things over the past 8 hours I need help to get a rom working on this. I tried going through the fastboot. Tried using recovery to update from sdcard and I'm having no luck getting this to work again. Hopefully someone on here knows how to fix my problem so I can get a working rom on my phone. Thanks everyone.
Did u install recovery (amon or clockworkmod?? If you did just dload another rom, wipe and flash again
N1
When I originally did the install I installed clockwork and did a back up. When I go into recovery all I can do is either wipe data, update from sdcard and wipe cache. I'm about ready to pull my hair out. I have no clue what went wrong. I've installed new roms on my old phones and no problems, I follow all the instructions.
nandroid, wipe all, retry flashing.
or restore your nandroid backup.
Looking at "adb logcat" while its booting will pinpoint the error.
I've tried to go through fastboot to use my recovery image but I get failed (remote: signature verify fail). I don't know how to get into nandroid and my computer I can only use the fastboot not adb to use logcat. Is there a way to use the fastboot that doesn't come up with the signature fail. I really don't know what happened. What other ways can I use my recovery image if I can't do it from the physical phone?
Sounds like a bad backup. DId you verify MD5?
If you want to start over..
Download AmonRa Recovery 2.2.1. From thread below...
http://forum.xda-developers.com/showthread.php?t=611829
With phone in fastboot mode and connected to PC via usb:
1. Command Prompt: fastboot devices (make sure device is connected)
2. Make sure recovery image file is in your SDK/tools folder
3. Make sure your working directory is SDK/tools folder
4. Command Prompt: fastboot flash recovery recovery-RA-passion-v2.2.1.img
5. After flash is done, reboot to recovery.
6. Wipe everything.
7. Re-flash your ROM.
You can always go back to Clockworkmod if you want. Just re-flash clockwork recovery.
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Your getting this error when flashing what?
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Did you unlock your phone (fastboot oem unlock) or did you just root it?
If you haven't unlocked your phone, perhaps try that then use the previous instructions to flash clockwork or amon recovery image.
link for reference
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Make sure you add to his "Thanks" meter! BTW. That would have been my next suggestion...
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Make sure you add to his "Thanks" meter! BTW, that would have been my next suggestion...
Sorry for the Double Post
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Glad to help. I think we've all had those "OMFG HOW DO I FIX THIS" moments.
So I tried rooting my girlfriend's G1 and it didn't workout so well, so now I'm trying to fix it for her (I feel terrible, my poor android friend.. I mean my poor girlfriend!) . I rooted it and it was working find, but I wanted to flash a ROM on there. I tried flashing CM5 following the directions on the wiki. I made sure I installed Amon_Ra's recovery and did a nandroid backup. Then I flashed the DangerSPL. 2 things then happened, when I tried starting up the phone it would just hang on the "G1" startup screen until I pulled the battery, and when I went back into recover it switched back to the old recovery I had after root (JFv1.42). So I can't go back. But when I go into Fastboot, the HBOOT is at 1.33-2005, which indicated the DangerSPL was flashed correctly. So should I flash CM5( or 6 or 7) now? I just don't wanna get the phone to a point where it's unusable (unless it is already) =/ Can you guys help me out?
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Your girlfriend G1 still fine.
The CM5 that you have flashed is not compatible with the SPL(HBOOT)/radio combination. (to my understanding) That is why it gets stuck at G1 screen (that had happens to me).
For G1, you can only flash up to CM 6.1 (to my knowledge), Cyanogenmod 7 will not (according to the DEV) works on G1.
You can try other ROM, recommending ezGengerbread, or Gingerbread Yoshi, and also my favorite (I am currently using it.) SuperAosp DM 2.8.2.
You will need to use 2708 SP and 13d radio for the newer ROM.
First load the radio, then the SPL. After both have been flashed (you can check it in the fastboot mode) then flash the ROM that you want.
AndDiSa said:
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Click to expand...
Click to collapse
Where do I put in these commands?
Vulf said:
Where do I put in these commands?
Click to expand...
Click to collapse
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
BeenAndroidized said:
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
Click to expand...
Click to collapse
No, it's not adb, it's fastboot, a different program, but you are right, it's a program that runs on your PC. You have to make sure to have fastboot installed. Then open a command window and enter the commands above having your G1 connected to your PC and beeing in fastboot mode (boot with back + power).
@ AndDiSa - Sorry for the short explaination, I should have explain in more detail.
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Vulf said:
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Click to expand...
Click to collapse
Have fun.
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Vulf said:
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Click to expand...
Click to collapse
Hmm, someone post an instruction in one of the forum that I saw yesterday. Not sure which one. It would fix the problem you are having with not see your G1 on ubuntu..
You can solved your problem with unroot like me.even my g1 lost function home & call button.
Sent from my T-Mobile G1 using XDA App
I've had my phone rooted since August, you all might know me from the 2.3 thread. Anyways, I've been wanting to go S-OFF to change that infuriating white splash screen.
However, I'm on HBOOT 1.47, the bad one that doesn't work with darch's ENG-SPL. It flashes, but doesn't change to 1.46 S-OFF. I can use Regaw's S-OFF method, but I don't want a permanent S-OFF, just in case.
How do I get to 1.46, preferably without RUUing? I will do it if I need to, but I'd rather not take all that time:
1. Backing up
2. Running the RUU
3. Re-rooting
4. Installing ROM Manager
5. Re-doing Firerats
6. Restoring the nandroid.
So, can I get the ENG-SPL without running a RUU?
Have you tried flashing the zip I posted on darchs eng-spl thread???
Root/Hack-Mod_Always *
laie1472 said:
Have you tried flashing the zip I posted on darchs eng-spl thread???
Root/Hack-Mod_Always *
Click to expand...
Click to collapse
I thought that was a RUU? One second.
Nope the ruu in zip format is on thedarknights thread. If that zip dosent work then I think you can just flash the .27 radio and then try flashing darchs eng-spl. " I think" Also that zip is for Ra if your on the newest cwm you will have to chang the scripting. That you will have to pm duce or jm for they know about converting zips from Ra to cwm. Or you can just flash Ra temporarily and try it. Then flash back to your current recovery.
Root/Hack-Mod_Always *
Sorry, different link that I thought was posted.
I am using cwm 2.5, that's still amend though. Does that matter?
I also have .29 right now, I'll try .27, since I just flashed this and I'm still 1.47 S-ON.
Your good as far as the recovery. And yea try the .27 radio because darch-spl doesn't work with .29 and then reflash the eng-spl zip. Its a long shot but it might work.
Root/Hack-Mod_Always *
Huh, that wasn't said in the thread at ALL. Thanks! Let me try.
Flash radio then eng-spl, or radio->reboot->spl?
Hummm. Id say flash radio first. Then reboot. Let it settle in. Then flash the eng-spl. After flashing the spl reboot back into recovery then power down. Then press and hold volume down and power to see if it took.
Root/Hack-Mod_Always *
Sounds good. I'll let you know how it goes.
EDIT: Radio is booting up.
I can't get the radio to flash... Odd. Do you have a downgrade zip?
Try this it's flashable from recovery
Link temp removed
Let me know when you get it so I can remove the link
Edit let me know when your back on line and I'll repost it
I'm back, and have tons of free time to spare.
Radio? Or I could get on the IRC, where it's quicker.
Well if your on there check there. If your on here I'll post it now let me know.
Root/Hack-Mod_Always*
laie1472 said:
Your good as far as the recovery. And yea try the .27 radio because darch-spl doesn't work with .29 and then reflash the eng-spl zip. Its a long shot but it might work.
Root/Hack-Mod_Always *
Click to expand...
Click to collapse
I have the .29 radio and flashed darch's file from the OP on his thread using CW 2.5.0.7.
It didn't take the first time though. To get it to take, I booted into HBOOT while I was S-ON. Then hit Home to go to recovery. I then flashed the zip. Then I rebooted recovery. This is when it updated the HBOOT. Maybe I just got lucky because I have seen others having issues with flashing with the .29 radio.
EDIT: Thought I should clarify, you can reboot recovery from the advanced menu.
@poashil
Yea you got lucky "imo" because it was a know problem with the .29 radio. If I'm not mistaken he already tried and it didn't update it. But I don't use cwm so your way might work for him. And I myself had to down grade my radio to flash it. And did you flash the zip from the op?? Or the one I posted???
Root/Hack-Mod_Always*
laie1472 said:
@poashil
Yea you got lucky "imo" because it was a know problem with the .29 radio. If I'm not mistaken he already tried and it didn't update it. But I don't use cwm so your way might work for him. And I myself had to down grade my radio to flash it. And did you flash the zip from the op?? Or the one I posted???
Root/Hack-Mod_Always*
Click to expand...
Click to collapse
Zip from the OP.
I am tempted to flash back the 1.47 HBOOT just to try it again. I know it didn't take the first time I did the flash, but I rebooted the phone that time. So I tried it with rebooting recovery and then it took.
If you don't mind me asking When did you dl it???
Root/Hack-Mod_Always*
laie1472 said:
If you don't mind me asking When did you dl it???
Root/Hack-Mod_Always*
Click to expand...
Click to collapse
I just click on the link on the OP and it downloads it. Just tested the link.
UPDATE:
So I went ahead and flashed 1.47 HBOOT and I am now back at S-ON. Now the 1.46 won't hold.
I got it once so I am going to try again and record the EXACT steps when I get it.
First, this is way more steps than the initial time I loaded this, so I think laie1472 is correct that I got lucky the first time.
To flash 1.46 Eng-SPL with the .29 radio I had to use adb/fastboot. So first I plugged the phone to USB.
1. Load the CW 2.5.0.7 image file to the root of your SD card. (Can be found here)
2. Reboot to recovery and Nand your phone.
3. Wipe data
4. Wipe cache
5. At cmd prompt:
Code:
adb shell
flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
reboot recovery
6. flash the heroc.hboot-1.46.2000.zip
7. reboot (Choose reboot system now)
From here the phone should show that it is updating the image. Then it will boot to FASTBOOT USB.
At the cmd prompt type
Code:
fastboot reboot-bootloader
It will restart and you will now see you are S-OFF and the HBOOT will be 1.46.2000.
Press vol down to get to HBOOT (you will be in fastboot). Press HOME to get to recovery.
If you use firerat's, you'll have to reset it back up. Restore your NAND and reboot.
poashll said:
I just click on the link on the OP and it downloads it. Just tested the link.
UPDATE:
So I went ahead and flashed 1.47 HBOOT and I am now back at S-ON. Now the 1.46 won't hold.
I got it once so I am going to try again and record the EXACT steps when I get it.
Click to expand...
Click to collapse
You mean the one the first page??? As in which link in the op????
Root/Hack-Mod_Always*
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
mymonkeyballs said:
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
There will be a cash reward for the person to help me get this working. (paypal)
Click to expand...
Click to collapse
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
That sucks balls MyMonkeyBalls..
Yeah, has happened to me too, I had to send in to get fixed, been 3 weeks so far.
Have a read over the forums for mine and others same issue, there are tips on how to fix but this is becoming very common at the moment, I can not offer any suggestions because everything i did did not work
Good luck
Tw1tchy said:
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
Click to expand...
Click to collapse
Sorry bro , just freaking out. Agreed.
twerg said:
That sucks balls MyMonkeyBalls..
Click to expand...
Click to collapse
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Tw1tchy said:
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Click to expand...
Click to collapse
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
I believe it all started going crazy when i tried to go back to stock and wipe the data (i did a factory reset from hboot as well as cwm)
mymonkeyballs said:
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
Click to expand...
Click to collapse
Before LC's CM10.2 were you running a 4.1.2 rom?
Tw1tchy said:
Before LC's CM10.2 were you running a 4.1.2 rom?
Click to expand...
Click to collapse
No. 4.2.2
mymonkeyballs said:
No. 4.2.2
Click to expand...
Click to collapse
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Tw1tchy said:
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Click to expand...
Click to collapse
Yes. Fastboot commands work but doesnt resolve my issue.
thejosh86 said:
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what do I have to do sorry
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Click to expand...
Click to collapse
I would highly appreciate that. Thanks bro
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
Thanks ! Testing it now. Will update.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
HALLELUJAH !! She is working ! Words cannot describe how happy i am ! i thought i was done! THANK YOU!
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
We saved mymonkeyballs =D
Sent from my One using xda app-developers app
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
thejosh86 said:
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
Click to expand...
Click to collapse
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
mymonkeyballs said:
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
Click to expand...
Click to collapse
Hey dude, don't forget to put [Resolved] in the thread title.