Related
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!
OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!
OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?
OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.
OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?
Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!
P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin
Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.
Check out the CDMA development thread
Whenever you get your phone back.....
Good luck
I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.
Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download
Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"
Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking
Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
AlphaJ23 said:
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
Click to expand...
Click to collapse
check that your cid and mid are now correct for T-Mo by doing a fastboot get var all.
Firmware you flashed is fine.
your phone is stuck in a bootloop which isn't un-common, due to the rom version and firmware version mis-maych I expect.
red triangle is stock recovery, so that's also normal.
at this point, rather than trying to reboot the phone, you should of just booted back to the bootloader fastboot usb mode and run the T-mo RUU, the first thing the RUU does anyway is boot your phone to the bootloader anyway, your just manually doing the first part yourself.
Thanks a lot for the help. A couple of follow-up questions for you. Adb/fastboot can't connect to the phone now. I've tried at the HTC white screen and the bootloader fastboot screen. It just says '< waiting for device >'.
I'm also having a problem with the RUU. When I accept the license agreement on the install it seems to crash. No errors but nothing else happens and the process isn't running. I'm going to try that on a different machine and see what happens. Thanks again.
Another update. The RUU install works fine on a different machine. I think that was a Windows 8.1 issue. The problem now is that the RUU can't see the phone either. So I can't get a PC to see the phone over USB at all. I assume that's because of the bootloop. Is there anything I can do from the bootloader to fix this?
Some progress. The RUU finally found the phone. I guess that was a timing issue. Now it seems to be stuck at 'Updating.... (1/7) Sending....'. It's been doing that for over an hour.
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
please help
AlphaJ23 said:
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
Click to expand...
Click to collapse
my phone has exactly the same problem but i really dont know what to do from here
So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
Hi All,
I know this is my first post and its asking for help already but I can usually find the answer to anything I need by just searching.
But this time i'm really stumped
I can see that a lot of other people are having this problem and have tried all the solutions to no avail.
I was rooted before and had the notification that update was available.
I followed this guide How to get OTA Updates on a rooted HTC One M8 by sakitech on youtube as I have done before.
I flashed the stock recovery and rebooted fine.
then I applied the update from the notification you get and now I am stuck with this brick...
I can get into boot loader using a combination of up and down buttons with the power button.
I am S-on
OS4.16.401.13
Ive tried putting various 0P6BIMG.zip on the sd card and have had the following results
Device halted due to large image update fail
that's the best I have so far.
If anyone could help me get my phone back that would be great
if there is anything else I need to tell you let me know
Thanks Loads
Toefudge
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
How to get OTA Updates on a rooted HTC One M8 is not applicable on lollipop
Install TWRP and restore non-rooted TWRP 4.16.401.10 backup and then install 4.16.401.10 stock recovery then redo the OTA.
You can restore only system if you want to keep your data or backup your data and restore later after the OTA successfully update your device.
Thanks for the reply
sorry I am in way too deep lol
would you be a super star and give me a little walk through of what to do as I have been trying for hours today already
Also if you could provide the links I need that would be most excellent
I need all the help I can get )
Read How-to and all the files needed are here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thanks again
but the phone is not recognised with adb now?
was before but now I open it up type adb devices and it lists nothing?
Help me Jesus lol
I'm having the exact same issue as the OP. Took an OTA and got bootlooped. S-On, Bootloader Unlocked, Bootloader 3.19.0.000, CID CWS_001. I flashed a GPE custom rom in TWRP to have a working OS, but now I can't figure out how to return to stock. I tried relocking the bootloader and then using the ATT RUU on HTC's website, but it failed because the system version was wrong or something like that. I have a backup of my data, but I can't figure out how to get this OTA so I can go back to stock and restore my data and not take an OTA again. Radio is [email protected] if that helps.
Toefudge1975 said:
Thanks again
but the phone is not recognised with adb now?
was before but now I open it up type adb devices and it lists nothing?
Help me Jesus lol
Click to expand...
Click to collapse
Why adb ? adb works only while in recovery or running system.
And the tutorial that I linked to you has nothing about adb, only fastboot
So what are you trying to do with "adb" ?
HI again day 3
How do I install TWRP without adb?
I can get into fastboot menu and have the TWRP .img on my SD card
How do I install it?
PLease Thanks
Toefudge
You don't need adb commands but fastboot commands !
so would you help me?
how and where do I use fastboot commands please?
as you can tell I haven't got a clue lol
so I type the fastboot commands in the same place but it just says waiting for device?
In your post #1, you mentioned you flashed stock recovery, how did you do that ?
It's the same fastboot command
after put your device in bootloader/fastboot mode and connect to PC, run this command:
fastboot flash recovery NameOfRecovery.img
If you don't have fastboot/adb properly installed, try this : http://forum.xda-developers.com/showthread.php?t=2317790
Yes I flashed the stock recovery to start when it was working
Then tried to do the update then it went into boot loop
I tried every thing including a factory reset.
Would this turn off the USB debugging? Stopping me from seeing the phone with fast boot/adb?
Many thanks for all that have helped me so far
No.. usb debugging on is needed for adb
fastboot doesn't need usb debugging on
Try the fastboot/adb link that I posted.
Also fastboot work when you put your device on bootloader/fastboot mode, most likely won't work while bootlooping
Ok cool thanks loads
I will try again I'm a bit
Just making my 3 boys dinner and then I'm back on it
Then I'll be back asking for help probably lol
What can i say ..
Thankyou so much for your help and patience
its all sorted now followed your instructions on the link after i reinstalled the fast boot software
You guys .