I used the easy rooting process from and once i was rooted i used ROM manager to download Liquid Gingersense 1.0 and saw there was no access to radio. So i went to download a new radio and was told to rename PG05IMG.ZIP. I went to put on SD card and saw that from the rooting process there was already a file with that name. I figured it was just the radio files needed for the rooting, so i replaced with the new .ZIP file. I then loaded the bootloader (down, and power) and tried to load the new .ZIP but to no avail it did not work. I don't remember exactly what i did from then to know but to problem........I truly believe my phone is bricked and I cant find anything that describes my problem.............
I cant power down while plugged in. It automatically loads the bootloader giving the four options bootloader, reboot(which still works properly, and loads up the phone without any problems), reboot bootloader, and power down. If I choose bootloader it automatically tries to read if i have anything on the card. Then i have the option of fastboot, recovery, factory reset, simlock, hboot usb, and image crc. If I choose recovery or factory reset it instantly changes to the white HTC screen and reloads the bootloader. Also to make matters worse, I had read that if you do the system update through the phone that it would erase the rooting done to your phone, I downloaded the newest update and tried to install. Now every time I turn the phone on it, on it's own, shuts down my phone to update the software but instead of updating the software it just opens the bootloader.
As of now I'm rooted with s=on
If my battery is low enough it wont try to upgrade with the new software.
I reformatted my SD card and that didn't work either.
I used Titanium Backup to load clockworkmod. When tried to use that, it would still load in the bootloader with the 3 androids on the bottom.
and the top of the bootloader there is white text with pink background that says *** Security Warning ***
So to sum up, I cant recover or factory reset(through my phone settings, or hard boot), I cant access clockworkmod to recover anything, and bootloader doesn't work.
I've only had this phone for a few days, so please help me fix it.
Thanks,
Bryce Morgan
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??
Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
I have the US 32gb unlocked version. Tried to do the downgrade to install CM using the method mentioned several times that changes the version from a command put in twrp.
First I unlocked bootloader, then installed twrp, then did the command line thing to lower the fw version, then put the v1.12 firmware on zip then rebooted to install.
Well, the install failed so I decided to stop there and try to put everything back to stock by using the latest ruu exe from HTC. The exe started sending a file to phone, then locked up and threw an error. I restarted the exe and it finally passed. I got everything set up and went to bed while it was updating apps.
This morning, shut off phone to put in SD, and when turning on it was optimizing apps then when done, would reboot and optimize again. The phone was stuck in this loop until I let the battery die. I couldn't do anything with it.
Battery finally died and tried to run the ruu exe again. This time it would not pass at all, no matter how many tries. I wanted to try to run the zip from SD but the latest firmware I can only find as exe.
Finally decided to just do a factory reset from recovery mode. This let the phone boot normally and I could do set up again. I tried doing a soft reboot, and it booted fine. Then I disabled apps I don't use, and did a full power down, now the phone is back to doing the 'optimizing apps' bootloop.
Right now I'm waiting for it to run its battery down again so I can at least get to download mode/recovery. Maybe I will try a full power off and app disabling separately, to see which is causing the loop.
Anyone have an idea what's going on? A link to the latest ruu in zip form? I really need a sure fire way to get this thing full clean stock (remember the exe is failing for me) to eliminate if thats the cause. Is it because I edited the version number?
Edit: just realized I put this in the wrong section
Update: Once battery died, I did factory reset again from recovery. Went through setup, and I then immediately shut the phone completely off and turned back on. It booted up fine. I then went to disable the same apps as before, EXCEPT for the "Google App". Phone still powers up fine, so I left it there and phone is working fine. I didn't want to see if disabling the Google App was causing the phone to boot loop. I had that app disabled the entire time I've had the phone, but don't think I've ever completely shut the phone down, so maybe that's why I never had the problem.
Still don't know why the ruu exe didn't work. Hopefully it was the computer, and I can still take updates.
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
hmedved said:
I have the same problem, can't disable apps without phone going into bootloop on restart. Can you tell me what apps did you disable? Facebook, Instagram, Google docs, HTC apps etc,etc...
Click to expand...
Click to collapse
I think what caused my problem was disabling the app called "Google App". No problem disabling all the Facebook and Instagram apps.
What about Google docs, slides and news apps? Can those be disabled?
Same problem with my A9 bought a week ago. Like Rouyal, I recall disabling the Google App and then came the OTA update and the bootloop. Tried alll permutations of buttons and even when I could get to RECOVERY MODE, all the options looped as well, returning to the same screen: no bootloader, no recovery. The only alternative screen was the "Enter your code to decrypt your drive" after leaving RECOVERY MODE. It looped as well. Copied the stock RUU to an external SD card; did nothing (with HTC Sync).
SOLUTION: Enter wrong codes for the "decrypt your drive" screen 30 times; that is the limit before the drive gets a factory reset. After the 30th it was factory reset. On restarting, the systems asks for the SAME email that was used previously.
The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?