Can anybody help me i think i just bricked my phone and all i did was:
1. install beans 50 gb rom
2. start a titanium backup
3. iterupte it and unistall for the pro version
4. try again and now it won't let me go nowhere but in recovery mode or download mode
5. tried odin back but it keeps failing at system.img Ext 4 and in recovery i can't mount anything
Please if anybody knows how to help it would be greatly appreciated
I had the ODIN issue with EXT happen to me too. Once I ran ODIN on another PC it worked perfectly.
Sent from my Galaxy Nexus using Tapatalk 2
That doesn't seem like a full brick to me either...
Sent from my SCH-I535 using xda premium
Yea this has never happend to me I'll try to use a different computer but i think it's a problem with the cwm recovery it simply won't let me boot into anything else after some trouble shooting i've realized i can flash through my external sd just not my internal one but i still come back to the recovery.
Marcismo55 said:
I had the ODIN issue with EXT happen to me too. Once I ran ODIN on another PC it worked perfectly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just tried this and im still getting the same error system.img Ex 4 Fail! anybody else that can help me
You might want to add specifics like what version Odin and what drives you're using too.
Sent from my SCH-I535 using xda premium
I used Odin 1.85 to get myself out of a jam like this.
Used root66 and Odin 1.85. Worth a shot
Sent from my SCH-I535 using xda premium
sorry im using for drivers Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0 and odin 3.07
-update i just tried odin 1.85 and i'm still failing at the same place
boot.img
NAND Write Start!
recovery.img
system.img.ex4
Complete(Write) operation failed.
All threads completed. (succeed 0/ failed 1)
I don't think that you bricked, so take a deep breath and go to:
http://forums.androidcentral.com/ve...5-guide-restore-back-clean-factory-stock.html
Odin the stock kernel 1st which will take you through a factory boot. Then Odin the stock rom and you should be back and working again.
I've pushed mine to probably as close to a brick as possible and have used this every time to get back. Let me know how you make out....
jcool13 said:
I don't think that you bricked, so take a deep breath and go to:
http://forums.androidcentral.com/ve...5-guide-restore-back-clean-factory-stock.html
Odin the stock kernel 1st which will take you through a factory boot. Then Odin the stock rom and you should be back and working again.
I've pushed mine to probably as close to a brick as possible and have used this every time to get back. Let me know how you make out....
Click to expand...
Click to collapse
The problem is he can't Odin anything. It almost sounds like something happened to his file system and he needs to format it. Do we have a pit file for this phone?
piiman said:
The problem is he can't Odin anything. It almost sounds like something happened to his file system and he needs to format it. Do we have a pit file for this phone?
Click to expand...
Click to collapse
I think you're likely right. Hopefully this phone does not have the emmc glitch the last galaxy s ii had.
Sent from my SCH-I535 using xda premium
that's what it seems like I can't use odin since it fails and in recovery i get the E: Can't mount /cache/recovery/command as an error at te bottom. I have been googling this up and down but since the people who actually solved it have different phones and files it looks like I'm stuck. Just tried fastboot, odin using samsungs stock, and trying to use adb just delete the recovery altogether but i can't do anything. if anybody doesn't mind and you've recently flashed or don't mind erasing your phone can you type the commands in:
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/mmcblk0p14_system.img bs=4096
RECOVERY
Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/mmcblk0p18_recovery.img bs=4096
USER DATA
Code:
dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/mmcblk0p15_userdata.img bs=4096
CDMA MODEM
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/mmcblk0p1_modem.img bs=4096
LTE_MODEM
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/mmcblk0p12_modemst1.img bs=4096
LTE_MODEM2
Code:
dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/mmcblk0p13_modemst2.img bs=4096
CACHE
Code:
dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/mmcblk0p17_cache.img bs=4096
BOOT
Code:
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/mmcblk0p7_boot.img bs=4096
At least this way i think we'll have the files needed but at this point i don't think none of them will help me or anybody with this problem. Either i have a corrupted recovery or the cache folder has been corrupted.
can you reformat the internal sd in recovery?
nope not thru the recovery won't mount but if i have an external sd its able to read it
sorry mods for bumping this again and this will be my last time can anybody help me in my situation either my cache is corrupted or it my recovery but due to that i am unable to boot normally anywhere except recovery and download mode. The other reason is because I believe my phone is not a complete brick and that it's fixable but of course since i really don't know alot about android I have no clue what to do now. I have tried odin but it fails are their any suggestions please?
Check pm.
Sent from my SCH-I535 using xda premium
joka10 said:
sorry mods for bumping this again and this will be my last time can anybody help me in my situation either my cache is corrupted or it my recovery but due to that i am unable to boot normally anywhere except recovery and download mode. The other reason is because I believe my phone is not a complete brick and that it's fixable but of course since i really don't know alot about android I have no clue what to do now. I have tried odin but it fails are their any suggestions please?
Click to expand...
Click to collapse
You may want to start thinking of restoring stock recovery (you could dd it with ADB) and resetting your flash counter and giving VZW customer service a call. It really sounds like you nand got toasted somehow and since it happened after you rebooted I don't feel it is the ROOM that did it so I'd see if they would replace it over the phone.
Did you try the older Odin someone suggested?
You may also want to ask in the IRC channel #verizons3, someone there may have some ideas.
---------- Post added at 01:20 PM ---------- Previous post was at 01:19 PM ----------
joka10 said:
that's what it seems like I can't use odin since it fails and in recovery i get the E: Can't mount /cache/recovery/command as an error at te bottom. I have been googling this up and down but since the people who actually solved it have different phones and files it looks like I'm stuck. Just tried fastboot, odin using samsungs stock, and trying to use adb just delete the recovery altogether but i can't do anything. if anybody doesn't mind and you've recently flashed or don't mind erasing your phone can you type the commands in:
dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/mmcblk0p14_system.img bs=4096
RECOVERY
Code:
dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/mmcblk0p18_recovery.img bs=4096
USER DATA
Code:
dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/mmcblk0p15_userdata.img bs=4096
CDMA MODEM
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/mmcblk0p1_modem.img bs=4096
LTE_MODEM
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/mmcblk0p12_modemst1.img bs=4096
LTE_MODEM2
Code:
dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/mmcblk0p13_modemst2.img bs=4096
CACHE
Code:
dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/mmcblk0p17_cache.img bs=4096
BOOT
Code:
dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/mmcblk0p7_boot.img bs=4096
At least this way i think we'll have the files needed but at this point i don't think none of them will help me or anybody with this problem. Either i have a corrupted recovery or the cache folder has been corrupted.
Click to expand...
Click to collapse
Have you tried doing this yourself just to see what you get?
are you talking about just shelling it hmm no i haven't
and as for the older odin yes i have no avail, and with adb the problem i was coming into is since I'm in recovery i can't use the command "su" making alot of the commands i found useless but of course i have very limited knowledge on android so maybe i just did something wrong. Do you have any commands you can recommend.
Did you look at anything in this post?
http://forum.xda-developers.com/showthread.php?p=29961927
Sent from my SCH-I535 using xda premium
Just trying to help with clues, don't know if it'll help.
I don't have an s3 but i had an infuse so maybe heimdiall works, that is what fixed my infuse's brick
Sent from my A501 using xda app-developers app
Related
Please delete this thread.
The updated version is here
http://forum.xda-developers.com/showthread.php?t=1167819
you could always post the links as text and then after 10 posts then you can convert to urls again
www.filefactory.com/file/cb882b4/n/Flash_Recovery.zip
www.filefactory.com/file/cb88370/n/Full_recovery.zip
filefactory.com/file/cb882b4/n/Flash_Recovery.zip link 1
filefactory.com/file/cb88370/n/Full_recovery.zip link 2
PM Sent.....
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
cloo24 said:
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
Click to expand...
Click to collapse
Your welcome and so everyone else knows you have to hold ctrl and shift in the folder and then click on open command prompt.
ok i made it simpiler to follow. I decided to do this because the ota is coming and many people want stock back.
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Thanks I really needed these instructions.
Sent from my Nexus S 4G using XDA Premium App
raiderep said:
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Click to expand...
Click to collapse
When I was on stock (when I first got the phone) I remember not having a recovery at all ( just the triangle) .
Sent from my Nexus S 4G using XDA Premium App
ok i used odin put those files in the right spot but its not doing anything. It says all threads comp succeed 0 failed 0 any ideas
ok will i treid this method and it dosent work i follow the directions just like it says put the tar files in the right spot hit start and nothing happens. it gives me the mess suceed 0 failed 0. put it download more and it just sits there. i do have adb set up for the device
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
mikeyinid said:
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
Click to expand...
Click to collapse
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
info[]box1 said:
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK. You obviously have fastboot drivers installed cus your rooted. Download THESE, courtesy of Pete. Extract that zip to a folder on your desktop. Open that folder, hold shift and right click in the folder and choose open command window here. Then run these commands, hitting enter at the end of each line:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
That is all, takes like a minute or 2 and your back to stock. I can do it with my eyes closed
Thanks Mike
Sent from my Nexus S 4G using XDA Premium App
windows can not recognize my phone can someone help me !
damnn said:
windows can not recognize my phone can someone help me !
Click to expand...
Click to collapse
can't recognize it at all, or can't recognize it in fasboot mode?
cant recognize it in fast boot mood.. my phone is on like normally and usb debugging is on and when i type in the cmd it doesnt go through it says "adb" is not regnozied as an internal or external command operable program or batch file
gonna try this since ive got a replacement phone on the way, what would happen if it sent the phone back unlocked and rooted anyway?
So, apparently, there is now a touch version of the CWM recovery.
There even is a version for our O3D
http://www.clockworkmod.com/rommanager
I tried to install that thing today and unfortunately it didn't work. I bought it through the latest ROM Manager, it installed and after a reboot I was stuck at the LG Logo. I tried it two times, both the same.
Does anyone have an idea why that happens? I was using the CM7 nightly (don't remember the exact build) for the P925 with the FroYo Baseband, could that be a problem? I'm now back to the P920 CM7 latest nightly with Gingerbread BB but I don't want to reflash everything again, so I'm afraid to try again
Same problem, reflashing everything again, maybe its buggy the touch recovery
What's the point?
Sent from my LG-P920 using Tapatalk
Point is to find out if there is anything wrong and if more people are having this problem. Maybe someone knows a fix.
Edit: arcee just posted on his Google+ account why that happens:
The image is in standard Android format instead of u-boot (which the p920 requires)
https://plus.google.com/115049428938715274412/posts/hd7ZDpaUAok
No, i thought what's the point of touch for cwm
Sent from my LG-P920 using Tapatalk
Oh, then I got you wrong, sorry
I would say it makes the use of the recovery a little bit easier by using the touchscreen to control it.
I think it's interesting so I wanted to try it.
It's ok ;-)
Oh, ok, I get it.
Sent from my LG-P920 using Tapatalk
how to install
paris07121978 said:
how to install
Click to expand...
Click to collapse
You can use the latest ROM Manager (there is an extra menu point for that now), but then you have to pay or you can download the img file from http://www.clockworkmod.com/rommanager amd flash it yourself.
But I don't know if there is working version available yet, the last one was broken. So you should wait.
When I have any news or confirmation, I will post here
thanks zwoggel
The new version of touch recovery is working 5.8.1.5.
Sent from my LG-P920
roxito said:
The new version of touch recovery is working 5.8.1.5.
Sent from my LG-P920
Click to expand...
Click to collapse
I can confirm that. Just flashed it
Sent from my LG-P920 using XDA App
how to flash it?
pimppu said:
how to flash it?
Click to expand...
Click to collapse
Download recovery image from CWM site:DOWNLOAD p920 Optimus 3d recovery image
Download terminal emulator or another from android market
Rename you recovery image to "recovery.img"
Using Terminal enter:
Code:
su <press enter>
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 <enter>
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096 <enter>
If you put recovery image to external sd
dd if=/sdcard/_ExternalSD/recovery.img of=/dev/block/mmcblk0p6 bs=4096 <enter>
Go to recovery: Turn off device. Click vol down + 3d button + power, and when LG Logo shows, release all buttons.
And screenshot:
thank You very much,works fine
adixtra said:
Download recovery image from CWM site:DOWNLOAD p920 Optimus 3d recovery image
Download terminal emulator or another from android market
Rename you recovery image to "recovery.img"
Using Terminal enter:
Code:
su <press enter>
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 <enter>
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096 <enter>
If you put recovery image to external sd
dd if=/sdcard/_ExternalSD/recovery.img of=/dev/block/mmcblk0p6 bs=4096 <enter>
Go to recovery: Turn off device. Click vol down + 3d button + power, and when LG Logo shows, release all buttons.
And screenshot:
Click to expand...
Click to collapse
you only have to click power + vol down
Indeed, I see many people saying 3d button is needed to enter recovery, but power + vol down is enough.
By the way, I had to go for the dd route to flash this recovery too, but it´s a scary procedure. A mistake here may ruin the phone. I would like to know why "flash_image recovery recovery.img" doesn´t work in the O3D. It´s much cleaner and fool proof than messing with blocks directly.
Hey guy's I haven't had time to pick up and fix my transformer since the whole recovery flashing issue I've finally come back to it but none of the guides to get the new recovery to stick work I've tried a few different methods I can cold-boot Linux and boot into android and drop back into recovery but I can't get anything to stick.
If I run this command: adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
All i get is a message saying no space left on device even thought I got 12GB left on the internal storage.
and I also tried this command: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
But I get a syntax error in adb saying that dd is not a recognized command.
Am I missing something big here as it's really annoying I can't even use my tablet properly.
Thanks in advance!
Bump
I really need help on this does no one know?!
APX is your best option to flash a new recovery
Sent from my Galaxy Nexus using Tapatalk 2
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
newshook said:
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
Click to expand...
Click to collapse
This belongs in Q & A but just flash the firmware from Asus and it will get rid of recovery and root.
Yup what ^ said. And this does belong in Q&A.
Sent from my Transformer Pad TF300T using XDA Premium HD app
duuude!!
newshook said:
I've been looking around for way to remove it but no avails. Can this be done or reversible? Please help.
Click to expand...
Click to collapse
i'm still lost for the answer to this EXACT question ... and this is the only searchable thread that come up with anything near like what I want.
I want to remove TWRP because it doesn't work .. i can't factory reset ... i can't do anything that involves mounting ... so how do i REFLASH over TWRP and go back NOT unlocked ...
interslicer said:
i'm still lost for the answer to this EXACT question ... and this is the only searchable thread that come up with anything near like what I want.
I want to remove TWRP because it doesn't work .. i can't factory reset ... i can't do anything that involves mounting ... so how do i REFLASH over TWRP and go back NOT unlocked ...
Click to expand...
Click to collapse
In Android Terminal, type
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
The "recovery.blob should be the blob of the new recovery u want to install.
Also you can't go back from "unlocked" A lot have people have tried and failed.
If you are more comfortable with fastboot, then maybe try using the fastboot command lines:
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase cache <------not sure if optional or not, but doesn't hurt
fastboot -i 0x0b05 flash recovery <filename>.blob
Or, last but not least, flash the stock rom. It will overwrite the recovery, and you must reroot. Not advising you to do this as a first resort, but just throwing the option out there.
Sounds like you semi bricked the device to me if you can't mount anything in recovery. Search for and follow Buster's guide to fix that issue.
Hi, I just updated to the latest firmware and well at first it tells me I have the latest number on the OS part and then after flashing a ROM or something or maybe even rebooting into it it says what the threads name states. It doesn't effect anything but I like having everything perfect and would like to know why its happening, any ideas?
& Yes I do have a ROM and everything loaded working perfectly.
S1L3nTShaDoWz said:
Hi, I just updated to the latest firmware and well at first it tells me I have the latest number on the OS part and then after flashing a ROM or something or maybe even rebooting into it it says what the threads name states. It doesn't effect anything but I like having everything perfect and would like to know why its happening, any ideas?
& Yes I do have a ROM and everything loaded working perfectly.
Click to expand...
Click to collapse
Happened on the M7 too...like you said, it doesn't affect anything. As long as you're not staring at the information on your bootlader screen you won't even notice.
brholt6 said:
Happened on the M7 too...like you said, it doesn't affect anything. As long as you're not staring at the information on your bootlader screen you won't even notice.
Click to expand...
Click to collapse
But I am... bootloader is life, life is bootloader, must stare! Lol well anyways no fix I guess then? As a perfectionist every little flaw makes me crave a solution.... and if there isn't one well I turn into Darth Vader and force choke someone... no one wants that!
S1L3nTShaDoWz said:
But I am... bootloader is life, life is bootloader, must stare! Lol well anyways no fix I guess then? As a perfectionist every little flaw makes me crave a solution.... and if there isn't one well I turn into Darth Vader and force choke someone... no one wants that!
Click to expand...
Click to collapse
It's a Twrp bug.
Update your recovery and reflash the firmware.
(Assuming we have a fixed version...)
santod040 said:
It's a Twrp bug.
Update your recovery and reflash the firmware.
(Assuming we have a fixed version...)
Click to expand...
Click to collapse
I didnt flash it with TWRP, used RUU mode. Could it still be related?
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
alibhatti said:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
I'm still fairly new to HTC, but I'm going to try...You're showing S-on and locked. I would assume locked means your boot loader is locked. You probably won't be able to flash a recovery if you're locked. I'm not even sure what "security warning" means.
Sent from my HTC6525LVW using Tapatalk
OS keeps saying OS-
They could have written that to the data rather than the actual OS name/number, seen it before in an unofficial ROM.
Sent from my SM-T210
---------- Post added at 04:57 AM ---------- Previous post was at 04:45 AM ----------
alibhatti said:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.
All i have done is run following command and now i am not able to do anything.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot bootloader
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Tampered : fastboot oem writesecureflag - you've triggered this because you are S-ON.
S-ON : You cannot flash anything other than Recovery if I remember rightly, due to 'Locked'
Locked : Bootloader is locked, meaning hboot is locked so no flashing, this also locks any other partitions they include which can be almost the whole devices partitions, a Custom Recovery can be installed though (or you'd have a brick with nearly zero access)
Unlocking Bootloader : if I'm not mistaken usually done through HTC with an unlock token (some devices can be done without going through htc), if you're stuck with it booting to hboot you'll have to check the devices forums for a solution :what:
Sent from my SM-T210
S1L3nTShaDoWz said:
I didnt flash it with TWRP, used RUU mode. Could it still be related?
Click to expand...
Click to collapse
I realize that, as you can't flash firmware in recovery.
Yes I'm certain it's a Twrp bug that has effected multiple HTC devices.
Flashing a version that has been fixed(we don't have one yet) and then flashing the firmware again fixes the blank OS version.
The problem is that once you use twrp again after updating firmware, it's wiping your /misc partition, which wipes out that info.
Once we get an updated version with the fix for that included, this will no longer be an issue.
I was never implying that using Twrp to flash the firmware was the problem, just the fact that you are using that recovery is enough to wipe the info.
Here is a working version: http://forum.xda-developers.com/verizon-htc-one-m8/general/twrp-blank-os-fix-t2879306