Related
Hello,
Yes, I do sound noobish saying this but I might have bricked my phone. I was trying to flash an image using the bootloader on my phone(you know the method with the "VoguIMG.nbh" file).. Anyways... I was unsuccessful at this and now I cannot flash another image..
When I put a Voguimg.nbh file on my microsd card, the bootloader does not execute the image as it should.. It just flashes to some error message which I cannot see because it flashes too fast, but anyway it returns to the the
VOGU100 MFG
SPL-2.31.Coke
CPLD-3
message and I cannot do anything past this point..
Anyone have any pointers on how I could fix this issue...
Any help is much appreciated.. Thank you in advance..
Bricked mine once, this is what I did.
1- Soft rest phone, put phone in bootloader mode (press power button + record button + soft reset with stylus at the same time) before phone bricks.
2- Connect to PC, run a RUU to flash instead of the SD method this time.
3- Download a rom that flashes using an RUU (my last NFSFAN rom used one), remove the NBH that is already in the folder, place the NBH you want to flash into the folder.
4- Run the rom update utility, should flash.
Hope it helps, if not sorry, that is the best I can do. Good luck.
Quick Question; is the battery loaded to at least 50%?
Flashing to a stock rom also tends to solve the issue. Don't worry, this should not relock your device.
A phone being "bricked" means that there is no way in hell you can salvage it and you have a very expensive paperweight. Ok, so there's a 99% chance your phone is not bricked at all, but I hope this guide will help you figure that out. If you have any questions on terms, refer to the earlier Noob's Dictionary Guide in my sig. I am not responsible for anything you do to your phone.
PART ONE: Things You Should NEVER Do With Your Phone
Any of these things may cause your phone to be legitimately bricked.
1. Flash a radio for any other phone, even the IncS. Your phone will be bricked.
2. Pull the battery during a radio flash.
3. Flash a ROM for any other device.
4. Flash a kernel for any other device.
5. Do a Root/S-off method with no experience.
PART TWO: How To Tell If Your Phone is Actually Bricked
1. Does anything happen if you hold the power button down? If you even get to the splash screen, your phone can probably be salvaged.
2. Can you get into Hboot by holding Power and Vol Down? If yes, you can probably run a RUU and you'll be good.
3. Can you get into recovery? Then you are fine! Many newbies assume that "OMG mai fone wont turn on so its liek brik3d!!!111!"
4. Does your screen not turn on/ you get flashing LEDs? Your phone probably is bricked, with no way to salvage it.
5. Do partitions not mount? You probably have a hardware issue, so your phone needs to be replaced.
PART THREE: Fixing It (If Possible)
We will go from easiest fix to hardest.
1. If you can get into recovery, just restore a Nandroid and you're good.
2. If your phone is stuck at splash screen, just pull the battery, hold power + vol down until you are in Hboot. Then select recovery. Restore a Nandroid Backup. If it won't go into recovery, see Steps 3 and 4.
3. ***Especially for EXT4 Recovery Users*** If your boot image has been erased, recovery will not boot. Get the Android SDK working. Go to http://forum.xda-developers.com/showthread.php?t=1219246. Download the recovery image in the OP and put it in your android sdk tools folder. Hold Power and volume down until your phone is in Hboot. Plug your phone into your computer. Use this code:
Code:
cd C: \[insert path of android-sdk here]\tools
fastboot devices
fastboot flash recovery cwm-4.0.1.4-vivow.img
fastboot reboot recovery
Your phone should now be in CWM recovery. You can now restore a Nandroid. CWM will not restore any 4EXT backups, though, so be careful. You may also flash a zip.
4. If you can't get into recovery at all, follow these steps. http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
If anyone has any corrections, suggestions, or comments, feel free to leave them!
Hi, I read this after trying to flash a firmware to in order to flash Android Revolution ROM. I made a NANDroid backup and I tried restore my phone back by with the back up I made and it says:
"Restoring Data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring Cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore Complete!"
I reboot my phone and it is stuck in bootloop. I can still boot into CWM Recovery so I am not exactly "bricked" am I? Is there a way to fix this? If so, how can I fix this?
LOL, there is no Android Revolution rom for the Inc2. And also, just download any rom, plug phone into computer, wipe in recovery, go to mounts and storage, mount USB storage, copy the rom to your sd, flash it, reboot.
myst3ry23 said:
Hi, I read this after trying to flash a firmware to in order to flash Android Revolution ROM. I made a NANDroid backup and I tried restore my phone back by with the back up I made and it says:
"Restoring Data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring Cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore Complete!"
I reboot my phone and it is stuck in bootloop. I can still boot into CWM Recovery so I am not exactly "bricked" am I? Is there a way to fix this? If so, how can I fix this?
Click to expand...
Click to collapse
Did you try to restore a back up from a different phone? Or did you port arhd yourself?, if it's, just restoring data, it's not wonder you have a bootloops for a snack
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
In the process of trying to flash a new firmware to a GIO I somehow managed not to be able to acess the recovery menu anymore. Right now the Phone is rooted, booting fine into stock ROM, download mode is working but no recovery menu. While trying to boot with power and home button it just shows the Samsong logo for ages.
I tried to flash a new recovery several times due to the fact that the stock recovery is only able to apply update.zip and not able to select any custom filename. So I installed su and a new recovery this way. After realizing that there is no recovery anymore I did it using ODIN and download mode. I tried several recovery images from cwm to stock, but everytime the same.
What did I miss?
How to do a dalvik/cache reset outide revovery menu and not doing a full hard reset?
Would a hard reset help?
TiA,
longInt
Guess their are commands to do it with ADB, phone can still go on so thats fine
Download adb
Connect phone to pc
Open command prompt , cmd.bat
Type
Adb
Su
Reboot recovery
Try if it works...
You can also flash recovery with ODIN, cwm v5 can be flashed with odin
Sent from my GT-S5660 using xda premium
I did already
Flashed cwm-5.0.2.7-ext4+rfs-odin.tar.md5 using ODIN without problems, but as I said, no recovery menu available/accessible. BTW: Do I've todo anything after ODIN triggered the reboot? I just remove the phone and try to access recovery menu...
I do not have adb available at the moment, Sorry. Will try tommorow, but I guess this will not show something different!?
Thx!
Terminal emulator?
Code:
su
Reboot recovery
Sent from my HTC Sensation
OK; will try the Terminal emulation soon. But also when trying "Reboot to recovery" from inside ROM Manager it just hangs showing the SAMSUNG Logo. Did I flash the right recovery in terms of the ext4 thing?
TiA
voetbalremco said:
Adb
Su
Reboot recovery
Click to expand...
Click to collapse
This results in a black screen and the phone not booting anymore (just showing the Samsung logo). I'm pretty sure the stock rom is booting again after flashing cwm again (had this before). Doing this now...
Any other ideas, tipps?
TiA
OK, guys, time for new proposals. Whichever way I try to get into recovery it fails. Reflashing recovery brings the phone back, but how to go into recovery!? I even tried to boot recovery using my GS3 Toolkit with the same negative result just to prove there is no way to reach recovery.
Isn't there a need to flash cache and dalvik or something else after flashing recovery!? How?
TiA
Try flashing a full stock rom with odin, so everything is gone, kernel, su etc...
If still not, live with it or bring it to a service center
Sent from my GT-S5660 using xda premium
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
exact same problem
longint2 said:
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
Click to expand...
Click to collapse
I have the exact same problem as you. Same phone as you, phone rooted fine, tried installing CWM now can't get to recovery with the same symptoms as you. Holding Power+Home results in a hanging Samsung logo and no longer being able to boot at all. Removing the battery doesn't help. Reflashing allows me to boot normally but still not recovery mode (download mode accessible all the time). Rebooting from ROM manager usually results in "RAMDUMP mode arm9" instead of recovery (wtf).
Tried different CWM versions recommended for Gio, some older some newer, some with different filesystems.
Tried different methods for installing recoveries (from SD card in the original recovery mode the first time, and from ODIN)
Tried different methods of reaching recovery mode (key combination on boot, reboot from terminal, reboot from ROM manager).
Tried doing "firmware update" with (lol) Kies
Seriously no idea how to solve it, it's exactly the same as the problems in this thread. Advice from friends and these forums has so far not helped, but hopefully someone will discover an answer soon?
Things I don't think are related:
I have hardly any space left on the phone
My battery life has now been reduced to 2 hours average (woohoo!)
Have you tried installing stock rom via Odin? It installs stock recovery itself, and then you would be able to see what happens when you are trying to acces recovery
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
---------- Post added at 08:23 AM ---------- Previous post was at 08:17 AM ----------
Follow step by step:
Make sure you do it from a PC on which you haven't already installed Samsung USB drivers or KIES.
1. Install Samsung usb drivers.
2. Open Odin and boot phone into downloading mode.
3. Browse Gio.ops and xxxxxxxx.tar file and start flashing.
Sent from my GT-S5660 using Tapatalk 2
nope…
pakistanish said:
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
Click to expand...
Click to collapse
I doubt this is the problem because the first time I tried flashing CWM was not with Odin (I'm not a Windows user) but from the stock recovery as shown in the video tutorial on this forum. I think I'll try wojtek267's suggestions and reflash the stock rom when I get my USB cable back.
Tried a lot more things, none of them worked
Sorry for double-posting, but this is long.
Update:
I got a USB cable. I tried a lot of stuff that also doesn't work. That's what's covered in this post:
This doesn't work. Naturally the first part doesn't work because it says boot into recovery and I can't do that. Ignoring that and continuing from step 5 does just as little. At the bottom of this post I've written what Odin does.
This also doesn't work, it's basically the same thing.
Tried reinstalling stock ROM as suggested. No difference in results. List of ROMs I've tried at bottom of post.
Tried using Odin from a different PC, as suggested. More on this at bottom of post.
Tried flashing using flash_image in adb. More about that at bottom of the thread.
Tried to get fastboot to work. I get an infinite < waiting for device >. More on that at bottom of the post.
Tried to factory reset the phone using both the menu option in settings, and the dial code, both result in the phone turning off and then starting up with a blank black screen that stays there forever.
Tried taking the battery out a thousand times, seriously why is this suggested so often?
List of Recovery ROMs I've tried:
signed_cwm-5.0.2.7-flashablezip-ext4only.zip
cwm-5.0.2.7-ext4only-odin.tar.md5
cwm-5.0.2.7-ext4+rfs-odin.tar.md5
stockrecovery-DXKT4-odin.tar.md5
All coming from this thread.
Also one or two others from blog about clockworkmod etc.
The point is it has no effect because as far as I can tell it isn't even flashed anyway.
Flashing from fresh PC failed
What I mean by this is:
I took a different PC
did a fresh install of windows on it
installed the Samsung drivers using the Kies CD
put the phone in download mode (VolDown+Home+Power)
start Odin, select OPS and tar.md5 file
connect phone
run Odin
nothing special happens…
What Odin does:
copy image to phone → success
disconnect from COM port and wait for reboot
start countdown timer
at this point phone reboots normally (not recovery or anything) and nothing special happens, the Odin timer eventually time's out and the operation is finished
Update: added actual output from odin as an attachment.
I'm not sure but I don't think the above is what Odin is typically supposed to do.
The odin I'm using is 4.42 for Gio and comes from the threads linked to in the first 2 bullet points linked above.
How flash_image fails
I have tried using both adb and terminal emulator on phone. Root access is given to the emulator via superuser app. This is what I do:
Code:
su
cd system
flash_image recovery recovery.img
This is what I get:
Code:
error scanning partitions: No such file or directory
recovery.img is located in /system/recovery.img
flash_image is located in /system/bin/flash_image with proper chmod setting of 755.
It makes no difference if I mount the system as read/writeable or not.
The flash_image I'm using comes from CyanogenMod wiki, here.
My best guess here is that the reason flash_image finds no recovery partition is that there isn't one. I certainly don't see one. And this would also explain why the phone does nothing (black screen or samsung logo) when you try to boot to recovery.
Please dear God somebody tell me that one of you has seen this before and knows a solution for this?
According to this thread the partition where recovery.img resides is /dev/block/bml9, but how do I get my CWM recovery.img on that partition? Do I cat? dd? What? Is there any partition (e.g. that one, or /system or anything) that I should format to something strange before this will work?
Issues with fastboot
2 problems with this. First one is, how exactly do you get into "fastboot" mode on the phone? I don't even know if it can. I have uncovered the following startup key-combos:
recovery mode (Home+Power) does not work, so now just a blank screen
download mode (VolDown+Home+Power)
ramdump arm9 mode (VolUp+Home+Power)
emergency download mode (VolDown+VolUp+Home+Power)
LK Little Kernel Mode (VolUp+VolDown+Power)
blank screen (VolUp+Power)
blank screen (VolDown+Power)
regular boot (Power) doesn't work after attempting hard reset, only results in samsung logo and inability to boot
None of these seem to be fastboot mode, so I guess it's more complicated than that.
Other problem is I'm using Linux and I've read I'll need to configure Udev to detect the phone ID used when in fastboot mode.
I've read that some people who couldn't flash with flash_image in adb were able to flash using fastboot so I'm hoping for that.
Summary
As you guys can see I've really tried a lot of things. Everything I can think of, and everything I could find on XDA and the rest of the web. I have had no success. Like OP's topic title says, I still have a working phone. When Hard Reset fails and the phone becomes unbootable I can make it bootable again by using Odin to fail at flashing a recovery.
So the phone actually works fine. The problem is I can't get to recovery mode and therefore can not flash CyanogenMod (all CyanogenMod threads say to flash ClockworkMod Recovery before CyanogenMod).
Please can somebody help me with this, I don't know what else to try.
Edit: hey pakistanish, thanks for the suggestions, if I don't install the USB drivers from the Kies CD then where am I supposed to get them from?
Bump?
Nobody able to help with this?
Am I in the wrong sub-forum or something?
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Good luck,
Darkshado
very nice try, still no cigarre
Darkshado said:
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Click to expand...
Click to collapse
Hi thanks for the helpful advice! I tried that now. Backed up the current bml9 to sdcard with dd and then dd'd my recovery.img over it; it seemed successful. I restarted the phone to recovery mode and it just hangs at the Samsung logo like normal. This thread confirms that /dev/block/bml9 is indeed the recovery partition, however replacing it seems to have no effect.
I have never heard of ddms or logcat, what do they do and do you have download links?
I still have the same issue, thx for any advices.
Hi I want to format my drive and start with a completely clean system. The problem is I am not too good at using adb and fastboot.
So I used my wife's old sgs5 as a test device. I even had an SD card in there as backup. Somehow I dormated the dam SD card too.
I thought that if you sideload it would install it for you just like a twrp flash bit I can't seem to her it to work. Drivers are installed and it is detecting my device. I'm not sure what I'm doing wrong.
If someone could give me a step by step for setting this up I would forever be grateful.
I don't care about the s5 it's just a test device . But I want to root my.pixel
Thanks
First thing, the s5 is WAAAAYYY different than our pixel. That goes for partitions, flashing, adb/fastboot commands, etx. You could test and play with it all you want but as soon as you hop to the pixel it's a whole different game.
So your end goal is root on the stock rom?
If so you'll have to unlock the bootloader.
When you unlock the bootloader the device will factory reset (that takes care of your "clean" part).
After unlocking the bootloader, reboot to bootloader, fastboot boot twrp, install latest magisk, reboot.