Related
Hi guys, sorry to say I'm back with another problem.
I have a Desire Z, rooted and S-off. Rooted with the wiki method (downgrade version, adb, gfree).
Using clockworkmod recovery 3.0.2.4, and have made a backup of my first 1.32 boot.
However, I tried flashing a new rom, but recovery just won't take it. It will say Can't open /sdcard/rom.zip (Bad) installation aborted, with every rom I tried. And I've tried more than 10.
So I thought, no biggie, I have a nandroid backup. So I run the restore, which works fine. But upon booting the device, it gets stuck on the white HTC loading screen. I have tried this multiple times, deleting cache/data etc fully. Also I used the FULL-WIPE-VISION.zip for this purpose to no avail.
I have followed the semi-brick guide which said I had to go get a stock rom with root, so I did. But I can't load it through clockwork restore, because I get the same Bad rom error.
What's left to try?
Additional info I should give according to the semi-brick thread (http://forum.xda-developers.com/showthread.php?t=842495):
The last and only Rom I had was the stock 1.32.4xx to which I had to downgrade before I got perm root. This rom is my nandroid recovery.
The command adb devices recognizes my device.
adb remount is succesful
adb shell gives me root
I have /data and /system mounted when trying most roms (but I get the same error when I don't have it mounted)
After booting and waiting a minute when it's stuck in white screen, adb devices will not recognize my device anymore, adb remount and shell also say that the device is not found.
Thanks a lot for helping out!
TL;DR: Clockworkmod recovery does not load roms, nand restore gives WSOD. How come?
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.
Noboo said:
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.
Click to expand...
Click to collapse
This isn't spam, and no need to apologize. Your post may be of benefit to others. If somebody has a similar issue, they may find your post, and from it find out how to fix it.
If nothing else, you should add [SOLVED] to the thread title.
Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.
Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?
Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.
ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro
edit: re-ran superoneclick for run and it worked! I should be good from here
Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.
So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...
I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA
lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Tokie the dropbox links are not working
reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys
cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.
when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one
dd: can't open sdcard\boot.img : no such file or directory
i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image
I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.
If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol
Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol
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
Gday
I was wondering if it were possible to get some help. I have been playing around with my HTC one x and have unlocked the bootloader, placed the clockwork recovery on there and have flashed cyanogen 9 onto the device. It booted up just fine but when i tried to flash a different rom suddenly i couldnt see any of my files from within clockwork recovery. Now i can only get into fastboot and clockwork recovery and cant mount usb within clockwork as i get an an error saying um lunfile cant be found.
Since then i have tried everything i could do within clockwork recovery and fast boot, as well as using adb and quick adb pusher to try and get some files onto my device so i can get it back up and running. Nothing seems to be working. It seems as though I have lost the connection with my sd card somehow?
The closest i have gotten to getting things to work is within quick adb pusher where it will detect my device but when i browse to tell it where to put the files on my device there are no folders, just an error folder called '"/error: device not found/". In the information it says that it faled to mount as r/w.
I have also been trying out adb with commmands such as "fastboot erase cache" but just get a
"failed (command write failed (unknown error))".
Does anybody know what might be going on here? is this something ive done and can be fixed or has my sd card just failed? if so do you think HTC will fix it for me?
Many thanks in advance to any help i can get here!
... Camm
use the newest ClockworkMod (5.8.4.0), that bug (ums lunfile) has been fixed since June. You're likely on 5.8.3.1 or older.
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
I have same problem. When i turn on my phone there is a google screen and then "X" screen. After 30 seconds it reboots again and again. I tried everything that i found on xda forum. Pls help !
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
DR3W5K1 said:
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
Click to expand...
Click to collapse
Erk.... No wonder sometimes when in fastboot mode, when flashing the userdata.img, it will failed with "Read Only Mode" error.
:crying::crying::crying:
But, thanks bro for your information.