[Q] Bricked phone? PLEASE HELP. - myTouch 4G Q&A, Help & Troubleshooting

I was using my mytouch 4g rooted and everything running the virtuous fusion rom when it shut off. When I tried to reboot the phone but it just went to the mytouch 4g screen and froze. I took the battery out and tried again several times but the same result was the phone being stuck at the mytouch 4g logo. I can get into the recovery but when I try to boot the rom up again it just says installation aborted. I also tried to run another rom (RoyalGinger) but it still froze at the mytouch 4g logo. I am very nervous, is my phone bricked?
Thank you for any answers possible,
Justin

Are you getting cache errors in recovery? Try wiping the cache partition for example, and see if that completes successfully. If you get the typical cache errors, that means your eMMC has failed and unfortunately the phone is indeed bricked.

Post your bootloader info please, that might help solve this
Sent from my Acer Iconia Tab A500 using XDA Premium App

GLACIER PVT ENG S-OFF
HBOOT- 0.85.2007 - (PD1510000)
MICROP-0429
RADIO-26.09.04.26_M
eMMC-boot

Lol so who is having the problem mohammed? You or holiday? Need to know what's going on with you phone?
Sent from my Acer Iconia Tab A500 using XDA Premium App

I have the same problem with the phone.

mohamed_moscow said:
I have the same problem with the phone.
Click to expand...
Click to collapse
TeeJay3800 said:
Are you getting cache errors in recovery? Try wiping the cache partition for example, and see if that completes successfully. If you get the typical cache errors, that means your eMMC has failed and unfortunately the phone is indeed bricked.
Click to expand...
Click to collapse
Cache errors?

I too am having cache errors....any solution to fix the issue? I cant flash anything, but I can get into fastboot just fine.

Teejay - question for you since I have read alot of your posts concerning cache errors....in mohammeds case, since he does have the engineering bootloader, cant he use fastboot to flash the stock pd15img.zip and get rid of cache errors? As long as he does not have fail pu? I believe I read of members successfully doing that in the emmc thread....It seems logical to be able to do that, reroot, and reflash cwm recovery but i could be wrong...
Sent from my Acer Iconia Tab A500 using XDA Premium App

bochocinco23 said:
Teejay - question for you since I have read alot of your posts concerning cache errors....in mohammeds case, since he does have the engineering bootloader, cant he use fastboot to flash the stock pd15img.zip and get rid of cache errors? As long as he does not have fail pu? I believe I read of members successfully doing that in the emmc thread....It seems logical to be able to do that, reroot, and reflash cwm recovery but i could be wrong...
Click to expand...
Click to collapse
That's the only solution, but unfortunately in most cases it has not worked. Sometimes they get the "Fail-PU" error when flashing PD15IMG, and sometimes even though it seems to flash successfully, the phone still bootloops and produces cache errors in recovery. I think I've read only one or two accounts of the phone becoming usable again once those cache errors appear in recovery. However, I've read probably a dozen or more accounts of nothing working.

I have PU-failed

mohamed_moscow said:
I have PU-failed
Click to expand...
Click to collapse
Yeah sorry man, but there's no hope at that point.

I am having the same issue. I loaded Beast Version 4 on mine. It was working fine and then it froze. I pulled the battery put it back in powered it on and it booted to the loading screen for the ROM (Green Android guy) I then pulled the battery again. Booted and it froze at the MT4G screen. So I botted into the Hboot. I run the wipe data/factory reset, wipe cache partition. Which both say success (Data Wife Complete,Cache Wipe Complete) and then its like it is trying to run recovery but it says:
E:Can't mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
Is this the cache errors you were talking about? Also when I tried to re-inatll the ROM it gives me an error but when I try re-loading Royal Ginger it loads it fine no errors.. Until I try to go back to previous screen to reboot then I get the error as seen above. I reboot and then it stops again at the MT4G splash screen. Am I bricked.. or is there fix for this. And if so is it the one listed above or is my issue slightly different.
Please help - Crossed Fingers.

I'm sorry, I know it sucks, but the phone is bricked. You can try restoring back to stock using this thread. Rename that file to PD15IMG.zip, put it in the root of your SD, and boot into the bootloader. If the file flashes successfully, there might be hope, but if you get the Fail-PU error, then it's definitely done.

OK thank you for your help. Crossing fingers but betting I am finicio :-(

I am very sorry to be bothersome. I clicked the link and it took me to a place to download the file (File Factory), but the file to download isnt there. Has it been move and by chance will you post the link to it. Again I am sorry.

I'm fairly sure that the file in this thread is the same file, and appears to be still available for download. Give that one a try.

Thank you again I am downloading now. Also it is highly appreciative how quickly you have responded. Again thank you so much.

tommyz182 said:
Thank you again I am downloading now. Also it is highly appreciative how quickly you have responded. Again thank you so much.
Click to expand...
Click to collapse
Sure thing, I hope it works for you. If not and you have T-Mobile insurance, most people have had no problem exchanging their phones for a new one when this happens. Also, don't forget to hit the thanks button if I've been helpful.

Yeah did any of you use the Gfree method of rooting? Because that's the one
I used.

Related

[Q] recovery isnt working

i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
lanceydavid said:
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
Click to expand...
Click to collapse
What exactly did u do to get that error??? Did u wipe data,cache,delvik & format system,i always format sd card also in case the sd card has a currupt file... did it automatically give the errors once u flashed?? Did u check the mdsum on the file to make sure u had a full zip file??? What recovery did u use 3.0.2.4 or 3.0.0.6??Sorry need to ask questions in order to help lol.... Ive heard of people fixin their phones with the part7backup-xxxxx.bin file & the pd15 file....just stick those to the root of the sd card go into recovery & let the phone to its thimg..
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
lanceydavid said:
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
Click to expand...
Click to collapse
Royalginger requires recovery 3.0.0.6 or 3.0.2.4....3.0.0.5 was mainly for cm7 but clockwork updated to flash froyo & gingerbread now... I believe u can dwnload a cm7 rom to the sd card frm the pc then try to flash that if that dnt wrk then if u rooted by using gfree method & have the 0.85.2007 bootloader it should of created a part7xxxx.bin file & that will help unrootin the phne & startin frm scratch again...
Theres a couple threads on here that could help u out,ur not fully bricked tho... I had this issue about 3 months ago when there barely was a fix now at least u have a chance..
i have the 0.86.0000 bootloader, will that be a problem? if not if i google how to unroot i should be able to find it easily?
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
I believe u need to have that 0.85.2007 bootloader but look around the Q&A threads & look for the subjects that says bricked or I think im bricked,those would help u out,im headin to wrk so cnt helo u now sorry...
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
darinmc said:
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
Click to expand...
Click to collapse
Doesnt he need the eng 0.85.2007??
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
Nope. I'm on 86 and have rooted and unrooted this phone about 30 times helping people and trying stuff.
Sent from my HTC Glacier using XDA App
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
darinmc said:
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
Click to expand...
Click to collapse
Thanks good to knw,i just thought u needed it since everyone talks about it...
cmdmilitia13 said:
Thanks good to knw,i just thought u needed it since everyone talks about it...
Click to expand...
Click to collapse
The reason we talk about is pretty simple. .85 allows you to use ADB commands and flash stuff via the HBoot engine. Where .86 does not allow you to. So if you get in "semi-brick" mode you can 9/10 times get your self up and rocking.
had it happen earlier today as a matter of fact.
http://forum.xda-developers.com/showthread.php?t=1040463
and this one rings a bell....
http://forum.xda-developers.com/showthread.php?t=1035413
They were both what most people would call bricked, but since they had the .85 engineering screen we could get them up and running.

[Q] cant mount /system cwm

I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
gamershadow said:
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
Click to expand...
Click to collapse
This issue has cropped up a lot recently. I'm sorry to say it but you might have bricked it. There is a chance though. 2 questions:
1. did you use gfree to root?
2. do you have the engineering Hboot? (.85.2007?)
I did use gfree to root. and i dont have the engineering Hboot.
gamershadow said:
I did use gfree to root. and i dont have the engineering Hboot.
Click to expand...
Click to collapse
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
mark manning said:
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
Click to expand...
Click to collapse
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
gamershadow said:
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
Click to expand...
Click to collapse
Ya you shouldn't have a prob
Yeah, they should give you a brand new in the box, depending on which state you're in, you have either 14 days or 30 to return the phone
Sent from my HTC Glacier using XDA App
I'm stuck as well.
Don't know WTF happened. Was running Iced Glacier for a couple of months, then decided to try one of the new ROMs, so took CM7 for a spin, then went to RoyalGinger for a day or two. Things were working, but RG started freezing up, etc. so tried going back to CM7. Once I started through the flash process I hit an error when trying to format /system.
Now when I even attempt a wipe (or most anything) via CWM I continuously get errors like:
E:\Can't mount /cache/recovery/log
E:\Can't open /cache/recovery/log
E:\Can't mount /cache/recovery/last_log
E:\Can't open /cache/recovery/last_log
...and this latest time, I now got this as well:
E:\Can't mount /cache/recovery/command
I had CWM 3.0.2.4 through all of this, so should be able to flash 2.2 and 2.3 ROMs, as I understand. I can only get into CWMR and HBOOT.
I used gfree to root & have engineering HBOOT (.85.2007).
I can't get device listed in ADB, but can under fastboot. Tried flash command using fastboot to try and re-flash CWM (no idea if it would do any good), but it says cannot open the .img file.
The ONLY thing I got to work was mounting SD to USB in CWM and putting PD15IMG.zip in the root of the SD card, then rebooting and letting it run an auto update as it looks for this by default. That worked and took me back to stock...nothing else I tried would work.
Now I'm afraid of doing anything else or risk creating an expensive @ss paperweight.
Any help or suggestions appreciated as to HOW this happened, and next steps.

[Q] Unable to boot/restore/write recovery: E: Can't mount /cache/recovery/command

Hey guys,
I have a MT4G here, i was running CM7 on it. Latest nightly, all was running smooth until somehow i started getting a bunch of FCs and i had to reboot to supposedly fix that. However, when i rebooted the phone was stuck on a bootloop, so i rebooted to recovery instead.
I tried restoring a nand from stock ROM, and i tried restoring a CM7 backup I had made a while ago, but recovery reads the following: E: Can't mount /cache/recovery/command.
I then said, ok, maybe the recovery is borked. So i tried to redownload the recovery img from the official website, and i "fastboot flash recovery recovery.img" - please note i had renamed the recovery file to recovery.img for the ease of typing things. Flashing that was a no-go, i get the following error: "remote: image update error".
So i kept on reading forums, and i came across the PD15IMG.zip, i placed on the root of my SDcard, rebooted to HBOOT, it checks for the update but fails to initiate installation, error says: "Fail - PU"
Do you guys have any ideas as to what can i try? I have the Eng Bootloader.
Hate to be the bearer of bad news, but you're bricked. The emmc chip died.
Sent from my HTC Glacier using XDA App
kimbernator said:
Hate to be the bearer of bad news, but you're bricked. The emmc chip died.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Appreciate the support, but i've seen hard bricks before. I am sure -and hopeful- that i'll be able to get out of this one.
If it serves any purpose, I tried erasing the recovery, rather than overwriting it, and i get the same Remote error. Unable to delete.
EDIT: Ok, so i spent the night reading, and it is not a user-driven failure, but rather a Manufacturer problem. Some eMMCs (labeled: "M4G2DE") may die all of the sudden, and not even necessarily during a ROM change, and/or during a restore. It can also fail inadvertently during day to day usage.
I am moving all my interested to the linked thread, in case anyone is interested.
http://forum.xda-developers.com/showthread.php?t=1079025
edit: whatever
JDV28 said:
This is stupid. You obviously have no idea what you are talking about. The only actual confirmation of a dead eMMC is the fail-pu error.
get the original pd15img.zip, put it on the root out your sd card,.then boot into hboot and follow the on screen instructions to flash it. THEN if you get the fail-pu error,.you know your emmc chip is dead.
Click to expand...
Click to collapse
I did try the PD15IMG.zip and i received the "Fail -PU" while installing.
I have the bad eMMC (tested according to the thread i linked to on my previous post)
I'll try to squeeze a replacement from T-Mo but not sure how lucky I'll be :sadpanda:
Sent from my LG-P999 using XDA Premium App
JDV28 said:
This is stupid. You obviously have no idea what you are talking about. The only actual confirmation of a dead eMMC is the fail-pu error.
get the original pd15img.zip, put it on the root out your sd card,.then boot into hboot and follow the on screen instructions to flash it. THEN if you get the fail-pu error,.you know your emmc chip is dead.
Click to expand...
Click to collapse
Dude, he said in the OP that he got the Fail-PU error.
TeeJay3800 said:
Dude, he said in the OP that he got the Fail-PU error.
Click to expand...
Click to collapse
weird, I lose interest in these long posts. I've answered at least 50 threads about these emmcs
fix this problem in my touch 4g
is the way to fixit i fixit my self is not brick if you can get to bootloader,make sure ti format your sdcard in fat 32 ,and put pd15img in sd card and it will find and update,i hade the sAME PROBLEM AND FIXIT FINALY
duka25 said:
is the way to fixit i fixit my self is not brick if you can get to bootloader,make sure ti format your sdcard in fat 32 ,and put pd15img in sd card and it will find and update,i hade the sAME PROBLEM AND FIXIT FINALY
Click to expand...
Click to collapse
Read the OP man, i tried, and i got "Fail -Pu". The sd card being formatted would not be necessary, i know the card works well.
Thanks for trying though
Sent from my LG-P999 using XDA Premium App

[q] please help

Hey guys my MyTouch 4g froze while updating flash lastnight
I was runnung the stock deodexd bloatware removed updated rom that is in
the dev section (Icannot remember who it belongs to)
I rebooted the phone and it frove on the splash screen
I rebooted into the bootloader
It wont let me do a factory wipe, and 4ext touch will not finish
installing any of the 4 backups I have on the sd card
I was finally able to flash CWM Recovery 2.5.0.7 but cannot get anywhere
To top it off my phone will not connect to my computer so I can
use adb. All I can do is place files on the sd card and try to push them from recovery
When I boot into recovery I get the following error
booting into safemode...
please format all partitions
after 7 minutes it says
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/log
E:Cant open /cashe/recovery/last_log
E:Cant open /cashe/recovery/last_log
cannot mount system, sdext, sd card, or MISC
can't mount /dev/block/mmcblk0 or mmcblk0p1
Would someone mind helping me out. I also tried to flash the
PD15IMG.IMG...nothing.I dont know if the partitions are jacked or what
S-OFF
HBOOT-0.85.2007
emmc-samsung 2151mb
rooted
Hi,
I guess in your frustrated mood, like many before you, you also need a dedicated, special confirmation that you're not an exception to the rule, and just reading "if this and that - your phone is screwed" doesn't work for you. So I'll honor your feelings by writing it 10000th time again.
Look at Glacier Wiki, section "Troubleshooting". Or at the topmost sticky in General section. Or in Q&A. Or search for any part of the error message you're getting. You'll receive the same reply:
If you flash PD15IMG and it either doesn't complete or shows you Fail-PU on one of the partitions - YOUR PHONE IS DEAD, AND THERE IS NO WAY BACK.
Have you tried wiping dalvik and cache and rebooting recovery? Make sure you unmount cache also. My phone did this before too, and that's what I did to fix.
Sent from my HTC Glacier using xda premium
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
saranhai said:
did you even read before posting?
if you did, you would've found this...
http://forum.xda-developers.com/showthread.php?t=1394238
Click to expand...
Click to collapse
Yes, yes I did along with a lot of other posts re the same topic.
BTW your link for the PD15IMG.zip is dead due to our wonderful government
and must I refer you to your post about you being mean to others ;p j/k
If I could get my phone to connect to my computer I could use adb no problem. But something with the driver is stopping it from connecting.
Ok thanks to PCLiteratesJax I was able to dl a good PD15IMG.zip. Phone is now stock and running good

[Q] Help! Nexus 10 Stuck at Google Logo, tried all solutions nothing works

Please help me, this is really frustrating .
I have a rooted nexus 10 running the latest CM10 with Clockwork Recovery. One day it ran out of battery and when I charged and booted it up, it got stuck at the Google logo. I went into CW Recovery and wiped everything, but I realized it wouldn't mount anything. I got messages saying:
"E: Can't mount /cache/recovery/command
E:failed closing /dev/block/platform/dw_mmc.0/by-name/missc
(I/O error)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/last_log
E:failed closing /dev/block/platform/dw_mmc.0/by-name/misc
(I/O Error)"
I tried Wug's toolkit, I tried nexus root toolkit, and tried downloading adb to my pc with fastboot commands.
Someone please help !
If I were you, I'd try to flash the stock recovery using Wug's Toolkit (somewhere in the advanced tools menu). Then, unbrick it and install everything custom from the scratch. However, always remember to be careful with advice from pingguo! I'm not a dev, but I have quite some experience in softbricking devices and finding a way to get them running again. :silly:
All you need to do is download the fastboot files, use the flash all file and then go into the stock recovery and wipe data/factory reset. It will boot after that.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
All you need to do is download the fastboot files, use the flash all file and then go into the stock recovery and wipe data/factory reset. It will boot after that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the reply!
I have tried that. It doesn't seem to work :crying:.
I get messages like
"archive doesn't have boot.sig
archive doesnt have recovery.sig.."
Any other ideas?
Try to download the stock 4.2.0 image manually from goo.im
I remember having that issue with some automatically fetched image...
Those two errors are fine, they always happen.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Those two errors are fine, they always happen.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yep, I agree.
I have seen this problem a few times recently, I think this can help: http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
I think the problem you are having is relating to fastboot.exes interaction w/ your specific device. Good luck!
Edit: But one thing I'm unsure of in your case is - I think I remember reading on these forums about if you do a full wipe off both /all areas and one other condition, you could have a real bad situation. Perhaps a pro knows on that?
bigmatty said:
Yep, I agree.
I have seen this problem a few times recently, I think this can help: http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
I think the problem you are having is relating to fastboot.exes interaction w/ your specific device. Good luck!
Edit: But one thing I'm unsure of in your case is - I think I remember reading on these forums about if you do a full wipe off both /all areas and one other condition, you could have a real bad situation. Perhaps a pro knows on that?
Click to expand...
Click to collapse
Thanks for the reply. Do you know how I am having problems relating to the fastboot.exes?
I was able to run flash-all.bat, but it reboots and i'm still stuck at the Google logo.
brianiswu said:
Thanks for the reply. Do you know how I am having problems relating to the fastboot.exes?
I was able to run flash-all.bat, but it reboots and i'm still stuck at the Google logo.
Click to expand...
Click to collapse
If you are able to get into the stock recovery do the factory reset option and it should boot up
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
If you are able to get into the stock recovery do the factory reset option and it should boot up
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
when I boot into recovery, it's still clockwork. When I use wug's toolkit to flash stock recovery or stock kernel, it temporarily boots into the Sentinel Rom (I said CM10 before but I got the roms mixed up), but all messed up. Once I hard reset that it goes back to being stuck at the Google logo.
brianiswu said:
when I boot into recovery, it's still clockwork. When I use wug's toolkit to flash stock recovery or stock kernel, it temporarily boots into the Sentinel Rom (I said CM10 before but I got the roms mixed up), but all messed up. Once I hard reset that it goes back to being stuck at the Google logo.
Click to expand...
Click to collapse
Well, usually when someone reports "stuck at Google (nexus) logo" the fix is just "factory wipe". And it gets reported a lot because it seems to happen after fastboot oem unlock (at least on 4.2.1) almost always.
The behavior you describe is certainly weird. But even if its not stock recovery, can you use any of them to do a "factory wipe"?
Im pretty new to all of this myself, but everyone always touts the "flash-all back to stock" as a way to fix everything. If you poke around in those threads I linked to you will find one of the vets here walks someone through something similar to what you are describing... but not 100% exact same...
I think it is possible to re-flash just the stock recovery, if flash-all is not getting you to that point. I'd look into that (I think that's even talked about on the links I did above.) If you could flash JUST the stock recovery first, then maybe you could use flash-all to completion?
You need to flash the stock recovery to get it to work
Sent from my Nexus 10 using Tapatalk HD

Categories

Resources