Hi guys,
I got a problem:
I rooted my Desire PVT4 with unrevoked and AmonRa-Recovery under Linux Mint Live CD. Everything went fine.
Next, I wanted to prepare for flashing a new rom. I did a Titanium Backup and downloaded Rom Manager. I proceeded to do a nand-backup, which it did, I guess. After that, however, my desire didn't recognize my sd card anymore.
Connecting to Windows 7 didn't work either. (It did work before)
So I went and bought a new sd card. I formatted it and put it in my device. Still, no sd card detected.
Along with the new sd card, I got an adapter, so I can now stick the sd card directly into my computer.
Surprise: I could now see both sd cards in Windows. Still, I formatted both after backing up the files on it.
The Desire wasn't able to boot anymore, though. So I went into recovery mode and partitioned the card manually with AmonRa recovery 2.0.1. This did work.
I can boot the Desire now, but it still won't detect the sd card.
Mounting it with AmonRa doesn't work either.
I read, that the problem might be caused by using RomManager on a PVT4 device.
Installing the HTC drivers didn't help and I can't install the google USB drivers. When I try to do so it says that there were no drivers found in the specified directory (""C:\android-sdk-windows\google-usb_driver")
In the device manager it shows 3 "Qualcomm CDMA Technologies MSM" (bought it in Germany, so shouldn't it read "GSM"?). All of them are marked with a yellow question mark. Upon trying to update the drivers I selected "Install software from a list or source" and specified ""C:\android-sdk-windows\google-usb_driver". I clicked "proceed" but Windows tells me that it couldn't find the drivers. Tried that on Win7 and on my WinXP laptop.
I desperately need help. I'm no pro. Actually I am a complete noob I searched on google but I couldn't find any solution so far.
Since I can't access my sd card (except partitioning in AmonRa, that did work somehow) I can't access any .zip on my sd card.
e. Additional information:
Upon trying to mount in Amonra recovery it says:
""Can't mount /sdcard"
Same, when trying to flash a .zip from sd.
hboot version is 0.93 I think.
I tried the following:
Just fixed it... i think the problem erupted because i have AmonRA recovery and used Rom manager (Clockwork mod recovery based) .. there were several reports
that this may cause a usb brick. ... any way... i searched for how to unbrick it.. and used a clone cd from modaco ((Tinycore.img)) which is linux based to boot from it (with phone connected to fastboot usb) .. and
entered the following commands :
Quote
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
and it enabled the sdcard... i checked the sdcard workability from the recovery (i hadn't format it yet) then thought : WTH, why not to try and restart the phone to see if it will log in normally .. and it did (naturally
because the sdcard block was the thing that prevented it from booting from the very start)...
Click to expand...
Click to collapse
Except that I used Linux Mint Live CD.
All I got was:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write/protected, mounting read-only
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: /dev/sr0 already mounted or /mnt/cdrom busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/cdrom
cd /mnt/cdrom/root
bash: cd: /mnt/cdrom/root: No such file or directory
Must I use TinyCore? I read somewhere that it only works for Hboot 0.8 and lower? What exactly is TinyCore anyways?
I almost know nothing about linux
No one?
Now I can't even get a signal anymore. I could cry...
Have you tried this procedure?
http://forum.xda-developers.com/showthread.php?t=691639
It worked for me when i bricked (pvt1 s-off). The problem seems to lie in the misc partition, which you have patch with the edited img file...
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
e. Also, my PC does not recognize the desire when pluggin into USB.
Eiskrem-Kaiser said:
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
Click to expand...
Click to collapse
You type that into cmd prompt window on your PC.
There are some instructions on SD card fix in this thread:
http://forum.xda-developers.com/showthread.php?t=691639
It happened to me when I partitioned the SD card in windows. Could you chech if your partitions on your SD are both set as primary and also uncheck "Take ownership of filesystem" (or something like that) when you are using the HD utility in linux.
Basically what happened was that the partitions were logical in stead of primary. Banged my had in the wall for two days before I figured this out. Hope it helps.
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Eiskrem-Kaiser said:
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Click to expand...
Click to collapse
I guess it means that sdcard can't be mounted...anyway, have you done the hexeditor thing already?
I just put the two files on the sd card and rebooted in fastmode. However, I'm not sure about my rom version. Where can I find out which one I have?
e. I just typed "cat /sdcard/flash_image > /data/flash_image" in ConnectBot, but it says "cannot create /data/flash_image: permission denied"
e.. When I type in "su" first, it still says "/sdcard/flash_image: No such file or directory"
Eiskrem-Kaiser said:
Where can I find out which one I have?
Click to expand...
Click to collapse
Oh sorry, i didn't read that...well i remember i was confused about that too at this point...too bad i can't remember how i found out.
Anyway, i found another solution on modaco:
"2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
3. Put THIS (attached) update.zip on your sdcard.
4. Reboot into recovery.
5. Apply sdcard:update.zip.
6. This will automatically fix your MISC partition with the correct CID. Reboot, and your done!"
Try this and tell me if it works in the while
I just booted into fastmode again and typed "fastboot oem enableqxdm 0" into the command prompt.
Now the Desire detects the sd card again :thumbsup:
Now I will try to use the cat command again.
e. I just did the thing with the "update.zip". Rebooting now.
e. I got my sd card back and a phone signal. That's great so far. Now what?
Still, when typing
"cat /sdcard/flash_image > /data/flash_image"
I get
"/sdcard/flash_image: No such file or directory"
I guess you're done if it worked...are you able to connect normally to your pc now? You should be :s
Also, those commands are meant to be used in a terminal emulator, not on your pc, i hope you didn't misread...anyway if you used the modaco tip you shouldn't need that anymore.
When you're done remember to copy your misc folder to a safe place, it will be enough to replace it via root explorer or similar if someday you'll brick again...
Nope, can't get it to connect to my PC quite yet. But I hope I will get that to work after rebooting the phone and/or windows or installing the htc drivers again.
I can not thank you enough right now. I was going crazy about this. Just bought my desire recently, upgrading from the Legend, with the little spare money I had. It would have been bad, if it was broken now.
So: THANK YOU VERY MUCH.
Also, someone tried to call me yesterday, while my phone signal didn't work. Now everytime I start the Phone, it shows me my missed call.
My girlfriend has a similar problem with a message I sent her. Everytime she boots her phone, she gets that message (fortunately it's "I love you" ).
So, I guess, it has something to do with the SIM?
Hmm, if you can't connect it might mean that the usb isn't fully restored...could you turn off the phone, plug it to pc, turn it back on and see if drivers get installed properly? Just to make sure...
I am stupid.
Hold on, it might work now. I had to switch to "local" in ConnectBot. Thought the app would remember that, but it didn't
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Eiskrem-Kaiser said:
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Click to expand...
Click to collapse
Sorry, i'm not sure i got ya. How would you run connectbot while you're in saftboot mode?? Because that's what i did, to make it clearer:
1. Downloaded image file "mtd0.img" and "flash_image" (from here http://forum.xda-developers.com/showthread.php?t=691639) and put them on sdcard (ofc i edited mtd0.img with my CID using some free hex editor before)
2. Installed Android Terminal Emulator app (from market), but connectbot should be the same.
3. Opened emulator, typed "su" command, accepted to give root permissions
executed this commands:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/misc.img > /data/misc.img
chmod 755 /data/flash_image
/data/flash_image misc /data/misc.img
4. Rebooted phone, connected to pc.
5. Success
Is this exactly what you did?
Yes. I typed exactly that. I just wanted to type it in again, but now it tells me again, that there is no such file or directory on /sdcard. But I can see the file with Astro being on the sdcard.
e. Maybe I used the wrong rom version number?
e.. Someone suggested to run in fastboot mode and type "fastboot oem eraseconfig". What exactly would this do? Which config would be erased?
What exactly is fastboot?
Eiskrem-Kaiser said:
Maybe I used the wrong rom version number?
What exactly is fastboot?
Click to expand...
Click to collapse
You just need the CID, not the rom version for this...
Anyway, please note that when i write misc.img i mean mtd0.img, that's what you typed right? Sorry if i confused you.
I guess there's no need to mess further with fasboot, i didn't need it, except for mounting sdcard.
If this still fails, you can always move mtd0.img and flash_image to /data manually via root explorer app, then go on from the chmod command.
My Galaxy Nexus system partition appears to be missing Is there anyway to recreate it?
Thanks
What makes you think it's missing? What you were doing to your phone when this happened? Got Nandroid backup? More details, please..
When I attempt to mount it CWM states that it is unable to mount and when you run the log it states that the volume does not exist.
I was attempting to install Bugless Beast from Rom Manager download and it looked to me that it was successful and I rebooted and I was stuck at the Google lock screen. I have a android backup but when I attempt to restore it CWM states that it is unable to mount and erase /system which is what leads me to believe its missing.
Have you tried to flash one of factory images? Which version of GN you have? GSM/CDMA?
Yeah I have tried all the images. I have a CDMA model.
Sorry, i'll give up here. Perhaps someone else can help you.
PS. Just a thought. What if you could find .PIT file and and flash factory images from ODIN with "Re-Partition" option ticked?
Just be warned, on SGSII forums i've seen few people crying about bricked phones after doing so.
Boot int CWM, connect the phone to your PC, then open a command prompt and run the following adb commands and post the results here.
Code:
adb shell ls -l /dev/block/mmcblk0*
adb shell dd if=/dev/block/mmcblk0p10 count=5
OK so when I type in adb backup -f C\Backups\gnexbackup.ab -all -nosystem
it looks like it does it's thing and backs up everything, but then when I go to the folder (Backups) I don't see that .ab file... what's up?
I am using takju 4.1.1 unlocked bootloader, but no root
same problem
works, but does not fix broken system apps
start cmd with admin
go to location of adb.exe
C:\>cd C:\adb
check adb
C:\adb>adb devices
List of devices attached
0123456789ABCDEF device
connect only one device!
if "adb devices" returns anything else, something is wrong, try '>adb kill-server' and retry and/or redownload newest adb at thanks Snoop05
C:\adb>adb backup -all
confirm at phone with password, no password leads to failure during restoring process, its a known bug (adb v1.0.32 and below)
file C:\backup.ab will be created
restore with
C:\adb>adb restore backup.ab
confirm at phone with password
wait till done
works for me, all user apps and data are restored, but it did not fix my broken google services and deleted calendar storage (accidents happen )
This function is not reliable. Some apps work, others dont. Only use this if you dont have any other options, e.g. broken phone or some malfunction.
Could someone run
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
and upload it? Flashing unbrick in a 'raw' fashion will allow you to hard brick most Qualcomm devices. Unfortunately I lost my backup and I can't boot my device. This file will allow me to recover. Thanks!
I can
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing
vincowoo said:
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing
Click to expand...
Click to collapse
I messed up, here's the correct command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
Thank you very much!
Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...
vincowoo said:
Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...
Click to expand...
Click to collapse
Make sure you're running as root, from adb shell or terminal emulator. Try this one instead
Code:
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/unbrick.img bs=512 count=31250
That command should have created 'unbrick.img' on your external SD card. I am extremely thankful for you doing this. My device is bricked and sitting in QHSUSB_BULK mode. You may want to save this file in case you ever need it! Thanks again, it is very much appreciated!
It is my pleasure. this forum helped me many times m trying to return something.That command completed successfully i am uploading it ?
https://docs.google.com/file/d/0B3i0YJU831QXUmViWGMyMGE1eHM/edit?usp=docslist_api
So I have been recently playing around with my S4 Mini Value Edition/Plus (I9195I) trying to port CyanogenMod to it. Then when it was really late I read about the `adb reboot nvbackup` (DO NOT EVER RUN THIS COMMAND ON THE S4 MINI VE), and now the phone is basically stuck in a bootloop. I think the problem is identical with http://forum.xda-developers.com/showthread.php?t=2657519 which points out that Samsung has simply messed up something there and now the FSG and BACKUP partitions are corrupt. According to the thread it is possible to recover if you get clean versions of the FSG and BACKUP partitions so I'm hoping someone with the S4 Mini Value Edition (i9195i) can help me by getting the clean versions from his device. It's not much to do and won't do anything to your device but will help me to continue (and actually have a working device again).
Can someone run these commands (either in a rooted shell (e.g. adb shell -> su -> change in the directory of your internal/external sdcard (not sure about the path), use TWRP way if in doubt), or from TWRP directly (Advanced -> Terminal Command -> then select e.g. your /external_sd or normal /sdcard) -> Select (bottom of the screen)), type the following 2 commands and send me the resulting files (e.g. by attaching it here to a post, or uploading it on AndroidFileHost or Dropbox, ... whatever):
Code:
dd if=/dev/block/mmcblk0p9 of=fsg.img
dd if=/dev/block/mmcblk0p19 of=backup.img
This will place the partition contents of FSG and BACKUP in the current dir (file names fsg.img and backup.img) and you can upload them from your PC e.g. by inserting your external SD card in your PC or simply booting into Android and connecting your phone to the PC. Unlike the names suggest they don't seem to contain a backup but actually files that are necessary for booting which is now corrupted after I run this stupid command... Thanks in advance, I hope someone can help me with getting my phone back working.
PS: I'm pretty sure there is no separate forum for the VE/Plus variant, so I guess this is correct here.
Solved with the help of @kariboo92 (thanks!), if someone ever makes the same mistake as me for this device, just PM me and I can help to fix it.