Related
Hi all,
yesterday my desire GSM running CM7.0 (running for many weeks/months) experienced some problems not showing some menu's, empty, no icons etc. So i rebooted, and.. got stuck on HTC/white bootscreen. After this I did the following:
- mount sd to pc, clear catch, factory reset in CWRM.
- put back a backup of android 2.2 (Defrost) works fine!
(but i want to go back to CM7).
- Trough RomManager tried to install CM7 --> stuck at boot
- In CWRM tried to install CM7 --> stuck at boot
- Wipe Davik, system, cach everyting, then installed CM7 --> stuck
- Installed android 2.2 rom --> works
- Installed android 2.3 rom --> stuck
Am I missing something stupid here? Forgot to do something?
Thanks in advance for all your help
HBOOT says:
BRAVO PV1 SHIP S-ON
HBOOT 0.93.0001
RADIO 5.11.05.27
(maybe something else:
When i install Rom of defrost this is the log:
Installing update
formatting cache
deleting files
coping files
formatting system
copying files
formatting boot
writting boot
installation complete
when i install CM7 it only tells me:
installing update
installation complete
of course formatting data and cache i did manually, but not formatting boot and system... but if i format boot, and something goes wrong starting up.. will this brick my phone? I Guess yes)
Hello.
Don't try anything else that ain't recommended. It is very hard to brick the phone, but if you bricked it, then he is gone.
Anyway I see that your Radio is not up-to-date. Usualy CM7 recommends any radio that is 2.2+ compatible. It will do you no harm if you try to upgrade your Radio to 5.17.05.08 (it's not the latest but the one before it; most people agreed this one performs better than the latest one, but this differes from phone to phone, also region, sim etc.).
How to flash Radio (CWM Recovery):
Code:
1. Go into recovery
2. Choose install zip from sd
3. Choose zip from sd
4. Confirm
5. Reboot
6. The phone will then reboot a couple of times. This is normal. Do not touch or move the phone during the process.
OR if you are used to fastboot commands:
Code:
fastboot flash radio c:\radio.img
After this Wipe everything again (User Data, Cache, Dalvik-Cache) and install CM7 again.
Hope this helps you.
I doubt it's radio, it would boot just fine even with old radio, do you have any partitions on SD?
Thanks for you reply's.
I managed to fix it, how ... and why everyting happend is not clear to me
I thought about the radio too since there are always warnings everywhere about having the correct one, but since i have no real clue what it precisely does, and my previous CM7.0.0 worked fine I had doubts.
I installed android 2.2 for the night (I needed a alarm in the morning) that worked fine. But next day when I tried to put on CM7 It failed (again). But now going back to android 2.2 failed too! And I got error clearing the extra partition (I didn't receive those before!) I though I wait to fix the ext3 partition till I managed to get CM7 working again.
Thanks you your tip, I paid more attention to the ext partition and got Gparted installed and recreated the partition. Now everything went smooth again, and got CM7 installed! Thanks!
(still couple of questions left:
- how can a rom force the phone on restart to suddenly go into a bootloop
- was this the whole-time related to the extra partition?
- why could Linux access the ext partition when I backedup my data trough CWRM, and later when CW gave me error, Linux did too!?
- Is this common error, or is this something new?
)
Thanks in advance for your patient help. I've searched forums for answers, w/o finding what I need.
I've owned my DInc (amoled) since release day, and for most of that time, been running on Nils' Business Sense (froyo). I later switched to Synergy RLS1, and then to Nils Business GingerSense 3.5. Switching ROMs has always been smooth and easy every time to this point. After running Nils Business GingerSense 3.5 for a few days, I wanted to re-flash the ROM, since things were running a little slow.
After a nandroid backup, I followed the steps listed here (http://forum.xda-developers.com/showthread.php?t=1267158): went into Recovery (CWM 5.0.2.0), factory reset, then format /system, then installed zip for stock gingerbread. After rebooting, the phone is stuck/frozen at the white 'htc incredible' screen. Since that point, I have been unable to get past the frozen white screen.
I have attempted to restore various nandroid backups, and tried installing a few different custom ROMs, also tried stock ROMs (2.1, 2.2, 2.3). Also tried flashing stock froyo through hboot flash, same result.
For any of these options, when loading the ROM or restoring the backup, it only takes a few seconds to complete (literally 5-10 seconds). I know this is very odd, since they normally are in the 150-300MB range. I believe it should take more like a few minutes, if not 5+ min to finish loading/restoring. This just isn't happening. Of course, before trying restore/new ROM I've done multiple wipes/factory reset, formatting all the options available in CWM recovery, etc.
At one point, I got what appeared to be the '5 vibs of death'. I definitely got 5 vibs, then black screen. But I haven't gotten that experience again.
Also at one point, I was able to connect via USB in the FASTBOOT USB mode, and could send adb commands to the phone. I did this in order to replace the nandroid.md5 in one of my nandroid backups, since recovery complained that the md5 mismatched (it didn't). Commands run in fastboot usb:
adb shell
# cd /sdcard/clockworkmod/backup/#date-of-backup#
# rm nandroid.md5
# md5sum *img > nandroid.md5
This adb command worked, and the md5 checksum passed, but still frozen at white screen after reboot.
Current status:
-I am able to flash any version of radio or recovery I want successfully
-Current hboot is 0.92, radio is 2.15.00.07.28.
-I can't connect via adb in the fastboot usb mode anymore, but I CAN connect via adb in the recovery mode (CWM), and Windows7 recognizes when phone is connected with android driver.
-All attempts to restore a backup or load a ROM zip completes in 5-10secs reporting success, but when rebooting I'm frozen at the white 'htc incredible' screen. (I've waited for 20-30min multiple times, eventually the battery runs out, since it won't charge on this screen.)
-Attempts to hboot flash the stock froyo rom originally completed successfully (resulting in frozen white screen), but currently the update is frozen on step [4] system. It unzips, then takes 1min or so to update (upper-right bar completes), but then unzips again on step 4, and freezes at 95% thru the 'updating' state.
Let me know if add'l info is needed, I tried to provide everything as accurately as I could. Appreciate any help the Android community provide. Thanks!
I would try the 5 vibes fix even though its not happening anymore. Also i would backup and then format your sdcard fat32, and then place your files back on it.
I am experiencing something similar. I have never been able to load a Sense 3.0 ROM on my phone. Everytime I format everything and install the ROM, I reboot and it just gets stuck at the splash screen. Everytime.
Any idea why?
Md5
Are you guys matching md5 sums from their original source?
Also, there may be errors on your sdcard. I recommend you back up the contents of your sdcard, reformat it, and then start all the way over by running unrevoked again.
Download whatever files you want to install and ensure that the md5 sums match.
This may take some time but its worth it.
Much love my friends.
EDIT: read this thread - http://forum.xda-developers.com/showthread.php?t=1128733
Tried wiping the whole device? And agreed about the erasing the SD Card. Found it can cause problems for some reason.
Tried Amon Ra recovery, that worked.
The whole time I had tried using CWM (various versions, mostly v5) to do factory reset and wipe everything. Only after I tried using Amon Ra was I able to load a new ROM afterwards. I'm sticking with Amon Ra for now...
I just wanted to throw this out there in the event someone else experiences what I did. I searched the forums and didn't find much out there.
I was trying to flash a new ROM with 3.0 kernal. I went through the routine. Backed up current (reloaded 1.1) ROM. Wiped Factory Rest|Cache|Dalvic Cache and System. When I tried to flash the new ROM I received a message E: cannot open zip file. The KF was stuck/frozen in TWRP so I did a hard shutdown and booted back into recovery. Tried to install the zip again and the same message appeared. Rebooted to recovery again and then mounted USB and put on a few other zip's I had. Each returning the same message that the zip couldn't be opened. I knew I couldn't have had bum downloads of all these ROM's. I restored to my Reloaded 1.1 and rebooted into recovery and this time I wiped everything but System. Installed new ROM without error.
I'm not sure what happened here but it appears that it didn't like when I wiped System. Hope this helps anyone who may find themselves in a similar situation.
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Hello there, hope someone can help me with my problem.
I softbricked my Find 7a while trying to reinstall ColorOS 2.1.5 stable. When I boot the phone up normally, it tells me that "SystemUI has stopped working" and that the Encryption was unsuccesful. no problem, I thought, lets just wipe everything and reinstall it via ColorOS Recovery.
But nothing works there - I can't wipe data, it always tells me I need 250 MB free space - and just reinstalling ColorOS 2.1.5 didn't help - it says the installation was succesful, but when I boot it up, its again "Encryption unsuccesful", just like before. Trying to wipe everything via fastboot didn't help either, (used 'fastboot erase xxx', whereas xxx stands for cache, system, userdate, recovery and so on), I always get the following message: FAILED: (remote: failed to erase partition)
I've also tried the unbrick tool from Irwenzhao but whenever I click on start a green bar is loading but after 5 seconds my phone just reboots, no matter how often I try.
I also have the feeling this has something to do with a failed unification (LVM), because I tried to switch back so it would maybe work... nothing.
Seems like I cant delete anything, even though I can boot up the phone, go into fastboot mode and go into recovery mode (which was useless so far since nothing works here)
Am I missing something here? Would be great If someone could help me out here..
Do you have LVM installed before per script? Try uninstalling it (Although ColorOS should work with LVM): http://community.oppo.com/en/forum.php?mod=viewthread&tid=46285
Or try this: https://www.youtube.com/watch?v=-HraWDrHve8