Related
My phone won't get passed the t-mobile mytouch 4g screen. This happened after I backed up my stock rom using rom manager and did a full wipe to start clean ut no after I went back and restored my backup, my phone is stuck on the mytouch screen and won't get pass that. Is my phone bricked? or can it be saved? can someone pls help me? I just got this phone yesterday and rooted it with no problem. All I did after the root was add a custom kernel. Everything was going great until I restored my backup. Pls help. Thanks in advance.
try going into the bootloader. press power& the volume down button at the same time. then let it load, select the option to boot into recovery. once u do that wipe all cache, data, and restore the backup u made. but if it doesn't boot up again then it might be a defective backup. might have to start fresh with flashing a new rom. but keep trying once u boot into the phone tho. goodluck!
I tried that and still not working. Is there away I can get a stock rom to flash?
Jaylito. said:
try going into the bootloader. press power& the volume down button at the same time. then let it load, select the option to boot into recovery. once u do that wipe all cache, data, and restore the backup u made. but if it doesn't boot up again then it might be a defective backup. might have to start fresh with flashing a new rom. but keep trying once u boot into the phone tho. goodluck!
Click to expand...
Click to collapse
Now I can't even boot into clockworkmod recovery. Now it boots me to the stock recovery. How can I get clockworkmod recovery back? I can't flash a rom without it.
ImABoss said:
Now I can't even boot into clockworkmod recovery. Now it boots me to the stock recovery. How can I get clockworkmod recovery back? I can't flash a rom without it.
Click to expand...
Click to collapse
The phone still says s-off so I don't know what is wrong and since I bought the phone yesterday I can take it back to t-mobile to get a new one but won't they notice the s-off and not exchange it?
Use Fastboot. It is like adb, but only uses the bootloader on the phone. If you don't have the SDK installed, you can get adb and Fastboot from TrueBlue_Drew's thread in the dev subforum.
HTC Glacier run ning CM7 #33
jggimi said:
Use Fastboot. It is like adb, but only uses the bootloader on the phone. If you don't have the SDK installed, you can get adb and Fastboot from TrueBlue_Drew's thread in the dev subforum.
HTC Glacier run ning CM7 #33
Click to expand...
Click to collapse
I'm using fastboot but nothing happens. AM I screwed? I'm sorry for all the questions but this has never happened before.
ImABoss said:
I'm using fastboot but nothing happens. May I screwed? I'm sorry for all the questions but this has never happened before.
Click to expand...
Click to collapse
Is there an official update.zip I can probably apply through the stock recovery?
Thanks Jaylito and Jggimi for your help, was able to get into cwm recovery and flash a new rom. It looks like I had a bad backup. Thanks again to you both.
i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,
Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?
http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home
Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250
Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.
i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)
jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(
Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:
I have a Motorola Razr M XT 907 on Verizon, which had been rooted for a long time. I wanted to update the software, hoping to get better reception and battery life. I made the mistake of installing the latest update, KDA20.62-15.1, which can't be rooted. I did, however, unlock the bootloader beforehand.
I have tried to flash a new recovery, hoping to downgrade the android build afterwards. Each time I try, I get confirmation of success in the command window, but I can never boot into recovery.
Any ideas? Or am I stuck staying unrooted?
Once you get recovery flashed, all you need to do is flash a SU.zip in recovery to gain root access. What recovery file are you trying to flash? Also, after recovery, immediately power off the phone and then boot straight into recovery so the update script can finish.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Once you get recovery flashed, all you need to do is flash a SU.zip in recovery to gain root access. What recovery file are you trying to flash? Also, after recovery, immediately power off the phone and then boot straight into recovery so the update script can finish.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks for answering. I tried to flash Clockwork recovery and clockwork touch. After flashing, I turned off and tried to boot into recovery, but the phone wouldn't boot into recovery mode.
joedp2 said:
Thanks for answering. I tried to flash Clockwork recovery and clockwork touch. After flashing, I turned off and tried to boot into recovery, but the phone wouldn't boot into recovery mode.
Click to expand...
Click to collapse
Ensure you are using the recovery built for our device this thread does have the proper recoveries for our device linked within the op...
We cannot teach people anything; we can only help them discover it within themselves.
It worked.
joedp2 said:
It worked.
Click to expand...
Click to collapse
Woot!
Sent from my HTC6525LVW using Tapatalk
issues
Okay so i pulled this phone out to mess with it.. Rooted, Bootloader unlocked and installed CWM Recovery because i cant seem to install any of the twrp versions.... I am able to backup and restore my system without issue but cant flash a custom rom in recovery. Is there something i am missing?
On stock kit Kat 4.4.2 and using cwm 6049razor-hd_m-kit Kat sorry left that out...
Which error?
Starts to flash then fails with droid on his back
I have same issu e!
Successfully flashed clockwork recovery...
But after boot into recovery mode is starting normally instead of recovery mode...
What can I do????
Don't let it reboot.. Hold down power and volume to go into recovery manually. If you allow it to restart it will load stock recovery back onto the device.
Hi all, I met a problem after flashing cm-11-20141028-NIGHTLY-mb52x.zip.
I cannot enter Custom Recovery (TWRP) any more. Other functions are OK, but I cannot upgrade to new ROM now.
Is there a simple way to restore Custom recovery in CM11?
Otherwise, I will have to use the method: "flashing stcok ROM (Android 2.3) -> root -> 2nd Init -> flashing Custom recovery", to restore it.
Thanks in advance.
hi, don't know if you still need an answer but you can try this:
http://forum.xda-developers.com/showthread.php?t=2708771
Hi jh20, thanks for the information.
I checked the post you provided. However, my problem is that I cannot enter the Custom Recovery anymore, let alone flashing another ROM.
jh20 said:
hi, don't know if you still need an answer but you can try this:
http://forum.xda-developers.com/showthread.php?t=2708771
Click to expand...
Click to collapse
perhaps i should explained a little more. these are based on memory as i haven't done these a while now.
cwm recovery had been permanently removed from cm11, and you can only flash cm10 and not anything earlier (cm7 or cm9) with cm11's twrp because of ext4 partition. so as long as you can still get into twrp, you can flash cm10 which still has both twrp "and" cwm recovery. cm10's cwm recovery allows you to repartition it back to ext3 and hence allows you to flash cm7.
i did a little google on how to revert from cm10, and here are the hits:
https://www.google.com.au/search?q=...hannel=sb&gfe_rd=cr&ei=rXBiVP7-GqGN8Qfiz4HYCw
and the first one on xda:
http://forum.xda-developers.com/showthread.php?t=2095518
if you need more just read the other posts. hope they help.
Thanks a lot, jh20.
I think I made a mistake in the post, that I was not use CWM recovery in CM11, it is TWRP recovery instead. I've update my post to reflect this.
So the problem is that I cannot enter TWRP recovery any more, and cannot flash another ROM or anything via TWRP recovery.
Is there a simple way to restore TWRP recovery, otherwise I have to start from scratch by flashing stock ROM, ...
I'm not trying to go back to CM7.2.
jh20 said:
perhaps i should explained a little more. these are based on memory as i haven't done these a while now.
...
if you need more just read the other posts. hope they help.
Click to expand...
Click to collapse
swest said:
So the problem is that I cannot enter TWRP recovery any more, and cannot flash another ROM or anything via TWRP recovery.
Is there a simple way to restore TWRP recovery, otherwise I have to start from scratch by flashing stock ROM, ...
Click to expand...
Click to collapse
Sorry, not with my knowledge. So unless some experts/developers here have any ideas, you might have to start from scratch.
No matter what ROM I flash, I keep getting to the ROM's boot logo, and it just loops until the battery drains. The only thing I could get to boot is Sailfish OS....
I've got 3.0.3.0 TWRP on there and I've tried LineageOS and Nitrogen OS, same result.
I would try and flash the factory images and start all over again
Nitin
nitin.chobhe said:
I would try and flash the factory images and start all over again
Nitin
Click to expand...
Click to collapse
Tried, no luck, same result.
RavenII said:
Tried, no luck, same result.
Click to expand...
Click to collapse
Are you sure you flashed the factory images? What process did you follow?
Nitin
Did u flash through twrp??
Flash the factory img using fastboot commands, backup data using adb commands. This will remove ur custom recovery though and you'll have to flash twrp through fastboot. Then u can go for custom rom.
nitin.chobhe said:
Are you sure you flashed the factory images? What process did you follow?
Nitin
Click to expand...
Click to collapse
TundraLK520 said:
Did u flash through twrp??
Flash the factory img using fastboot commands, backup data using adb commands. This will remove ur custom recovery though and you'll have to flash twrp through fastboot. Then u can go for custom rom.
Click to expand...
Click to collapse
I just followed https://developers.google.com/android/images#occam
The zip for the N4 has a .sh file with all the fastboot commands that automates the process.
RavenII said:
I just followed https://developers.google.com/android/images#occam
The zip for the N4 has a .sh file with all the fastboot commands that automates the process.
Click to expand...
Click to collapse
Lollipop takes a bit longer to boot, just wait it out like 20-30 mins.
Sorry just read ur first post again, don't know what to tell u, maybe someone else will figure it out.
RavenII said:
I just followed https://developers.google.com/android/images#occam
The zip for the N4 has a .sh file with all the fastboot commands that automates the process.
Click to expand...
Click to collapse
I got the 4.4.4 stock image to boot...flashed TWRP (latest) and then Nitrogen from there...boot loop. Weird.
Try flashing with old twrp, not the lastest one. I doubt twrp is the problem but u can give it a try.
Or just try with fastboot directly.
Or maybe try another rom PN , SAOSP, maybe u downloaded a problematic Nitrogen OS build.