Related
So hopefully someone will respond as I'm a new member and can't post directly to the developer forum
I'm trying to install Virtuous Fusion 1.1.6 ROM for mytouch 4g. I'm coming from cyanomogenmod nightly. I followed the instructions on the dev page, but it keeps getting stuck. The steps I took:
1) Backup
2) Reboot to recovery mode
3) Wipe cache, wipe data/factory reset, wipe dalvik
4) Install zip
So it installs successfully, and then I reboot from the recovery menu.
It boots after a little bit to the phone main screen and I let it sit for a few more minutes as per the instructions. This is where the problem occurs.
When I let it sit, the screen goes blank (with the screen-off animation). It sits there for awhile not appearing to be doing anything so I click the trackball wake.. nothing. I click the power button.. nothing. I thought it froze so I battery pull and reboot. Same thing happens. I start over (wipe/reflash) and decide not to battery pull this time.
Same thing happens where it freezes after the screen times out. When I let it sit even longer, it eventually vibrates and reboots by itself, loads to the phone screen, but then sits there after the screen blanks again and appears to do nothing. I let it sit there for >20 minutes and it still seemed to be unresponsive. No response to any physical buttons pressed.
On another attempt, I also tried pulling the ring on the drawer before the screen times out and it goes to some setup screen, but when I click "Next" it just freezes every time.
Also, I tried the same thing with version 1.1.5 before 1.1.6 came out and the exact same thing occurs.
Is there something I am doing wrong? Thanks for the help in advance.
Not that anyone responded, but there is no need anymore. After reflashing to backup, everything started force closing. A soft reboot yielded a frozen mytouch 4g flash screen. In the end the phone bricked itself showing E: cannot mount errors and error formatting /system. Will obtain the eMMC serial later since I did use gfree method.
If your phone will boot to hboot or even recovery then your phone is not bricked. It appears that your recovery is broken. Try flashing a new recovery via fastboot or adb
Sent from my HTC Vision using XDA Premium App
I know there are a lot of posts out there and I've looked through most of them, and it seems that even if you can get into recovery or hboot, if you don't have engineering bootloader you can't fix the problem through adb. Or something like that. I don't have eng bootloader, i have the SHIP s-off. I could connect tried adb to fastboot another recovery and it did 'send' OK, but 'FAILED' (remote: not allowed). I've been reading and reading and frankly don't know what else to do but give up.
bochocinco23 said:
If your phone will boot to hboot or even recovery then your phone is not bricked. It appears that your recovery is broken. Try flashing a new recovery via fastboot or adb
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Wrong bochocinco. Your phone is bricked. Some of the MT4G's have a bad eMMc chip. I am assuming you rooted with the g-free method, because that is the only method that works with the bad chip.
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
I know this is going to sound like a really dumb question, but is it charged? The reason I ask is because you mentioned not turning it on for a while and the battery can drain even then.
If it does have a charge, the only thing I could think of would be (after wiping cache and dalvik and seeing if that works) to wipe data completely IF you have a backup/don't care about starting over.
It does have a charge. I even tried booting it with it plugged in. I just constantly sits on the animated CM7 logo, then goes black, then sits on the logo again.
When I boot to ClockWorkMod recovery, I see:
wipe cache partition
wipe Dalvik cache.
Can I do both of those without losing stuff? If someone can explain what those caches are actually used for, I would really appreciate it.
Well, I couldn't wait and cleared both. Still same problem.
The odd part is that I hadn't changed anything. I'm 99.9% sure it was working. I shut it down, left it plugged in, and then days later tried to boot it.
I can only imagine that an app is starting up on boot that's having issues. Is there a "safe" mode like windows has where I can boot with the minimum OS so I can somehow remove some apps from starting?
Thanks,
Mark
markdemich said:
I have a gtablet with CM7.03 on it. It's been working for a while. I hadn't booted it in a while and just tonight I tried to boot it. The cyanogenmod logo comes up and animates for a few minutes, then the screen goes black, the process repeats.
I'm hoping someone can give me some steps to follow to figure out what's wrong. I booted in recovery mode, but wasn't sure what to do first. Should I clear caches? Any expert advice would be appreciated. I'm a programmer, but I'm new to all this Android mod stuff.
Click to expand...
Click to collapse
What I find odd is the fact that it was running fine before you shut it down for the last time.. The only thing I can think of is there was some sort of low level data corruption before the last time you shut down..
Do you remember installing any new apps or flashing anything like a different kernel, modifying the Build.Prop or anything that may have an adverse effect to normal booting? If so, that may be the cause of your trouble. Since you have at the very least a boot sequence (with Bootloop) it doesn't appear to be a soft brick so that's some good news for you.
I can only suggest if you have a backup use it via recovery mode.
If not you could try and start over from scratch by installing a fresh copy of 7.0.3 (Be sure to Wipe Data and Cache AFTER Flashing) via recovery mode if you can get the zip file copied to your internal SDCard, I say if because with some versions of ClockworkMOD for the GTAB, it will only read from the internal SDCard and not the External SDCard.
The version of CWM I use is v.2.5.1.8 which I believe is also a play on Bekits v.8 but I'm not sure at the moment.
v.2.5.1.8 will mount the USB Storage (External SDCard)via recovery (Mounts & Storage> mount USB Storage) so you can copy the fresh zip file onto it and CWM will read from that card and not the internal SDCard.
If all else fails, you may need to try and NVFlash, which is used to restore the GTAB to its original Out of the Box Condition.. Which should only be used in the event of a Soft Brick...
Good Luck!
markdemich said:
I can only imagine that an app is starting up on boot that's having issues.
Click to expand...
Click to collapse
That and filesystem problems on /data are what I suspect.
Since you are a programmer, do this to find out what's wrong:
1. Switch off gTab.
2. Attach the USB cable to the gTab.
3. Run "adb logcat > logcat.txt" (or "adb logcat | tee logcat.txt" on Unix) on the host PC.
4. Power on gTab.
This will collect logs almost right from the beginning which might hold a clue as to what's wrong.
You might also want to read through these 2 posts:
gTab partitions
gTab SD cards
Hello,
I have a Nexus S that was encrypted because one of the Exchange servers I connect to requires it.
The unit has since failed to boot into CM9. It enters into the "Google" start screen, flashes once, and stays at the "Google" start screen with the soft buttons activated. I assume this is what is called "soft bricked". Recovery still works, and so does Download mode.
Mounting from recovery has failed. I've tried CWM and TWRP, but neither can mount, nor can they format the SD card. I've attempted load stock rom through flashboot, but of course that fails because it doesn't have access to the SDcard.
Attempting to mount Internal SDCard and Data through TWRP as hinted in Cyanogen forums have failed as well.
I can't seem to find Odin files for Nexus S either. I may be wrong, but there might not be Odin files for the vanilla non-4G Nexus S.
Can someone offer advice on what to try next?
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
amadaeus said:
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
Click to expand...
Click to collapse
I have the same problem. Can't do anything with my phone since it can't mount the internal sd... I'm currently searching for the files to restore the phone, so if I find anything, I'll post it here.
Hi,
I have refereed to earlier threads for same problem but could not resolve the issue. That's why I am initiating a new thread.
I was trying to unlock my htc one s and was trying to install a custom rom. But I don't know which step goes wrong. Now my phone is not starting and I am not even able to go to recovery mode by volume button. When I try to start the phone it stuck on 'this build is for development purpose only'.
Please help.
Regards,
Meher Chandan
It is kind of difficult to help since you are not telling what you have already done...
However, I'm just guessing that your phone may be in a reboot loop with fast reboot/poweroff enabled. This means it is never really powered off. Try to hold down the power button when you see the HTC screen, at least for 10 seconds (more may be required). That should force a hard shutdown. After that, you should be able to boot into fastboot, and so, into recovery.
FWIW, I've installed CM 12.1 and I still got the red warning message. It does not bother me, however.
I got similar case in the old day. Boot up the phone first to wakeup it and force it power off and immediately connect to PC when the screen goes blank.
Try "c:\>adb reboot bootloader" now, sometimes it will fail and report device not found(then unplug the usb cable, reboot it and power off and connect to PC again), you might be need to try many times to make it success(I'v tried like 10 times) and once you get it working, it will reboot into bootloader and now fastboot(c:\>fastboot devices) and recovery also working.
meherchandan said:
Hi,
I have refereed to earlier threads for same problem but could not resolve the issue. That's why I am initiating a new thread.
I was trying to unlock my htc one s and was trying to install a custom rom. But I don't know which step goes wrong. Now my phone is not starting and I am not even able to go to recovery mode by volume button. When I try to start the phone it stuck on 'this build is for development purpose only'.
Please help.
Regards,
Meher Chandan
Click to expand...
Click to collapse
There is boot.IMG file on your ROM.zip (you have installed) extract it in your fastboot folder and reboot your phone into boot loader and then goto your PC command promot and flash boot.IMG (fastboot flash boot boot.img) from fast boot folder.
Sent from my One S using Tapatalk