Hey guys. I'm a bit of a newbie at androids. I bought a Moto G, and I decided to root it.
I realized that the android was not unlocked, so I went through a small progress to try get it unlocked so I could install a custom recovery. I chose CWM.
I went through a tutorial on how to install CWM, and I installed it. I used the MotoTool to push Superuser to my android, and was able to install the zip.
It all went wrong when I tried to exit out of CWM.
I selected "Reboot" and it loaded the screen up to CWM again...a bit odd. So I'm trying to reboot so I can use my phone properly, and nothing is working.
What I've tried :
-----> Clearing dalvik cache and cache with CWM -
I tried this and it still didn't work.
-----> Loading into my AP Fastboot with CWM and trying to power off and on from there
Still didn't work and loaded into CWM.
----->Flashing my bootloader
Made it worse. I can't even power up my phone anymore.
In conclusion, my phone is hard-bricked, and I can't even power it up. If anyone has any solutions, it would be extremely helpful. Please feel free to comment or reply if you need more info about my device.
Related
So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.
Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..
Are you able to get into bootloader?
Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?
same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.
I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.
You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader
So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.
I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
i am currently using twrp and ive had no problems flashing roms including sky ics which those directions are from also a recovery isnt compatible with odin if you want to odin back to stock or flash anew recovery image you just go into download mode and procedd from there
RAVEN6 said:
I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
Click to expand...
Click to collapse
To reboot into recovery you hold power, volume up and down and when you see the first samsung logo let go of the power or it will keep rebooting.
As for being compatible with odin, I'm not sure what you mean. You can flash TWRP through odin, you can get into download mode with twrp installed also.
Have you tried reinstalling TWRP?
I been lurking on XDA for a long time just have made any posts, lots of great info has been found here and I usually find my answers without having to ask, that is till now. This might be a long post but I want to give the best information possible to get the best help. I recently updated my tf300t to jb4.2 and that's when the bottom fell out. First I thought I was bricked, flashed the update and it booted fine, flashed twrp and it booted fine, tried flashing Energy rom and that's when it started. Twrp would not mount cache, sd, nothing. Then after rebooting it would give the Asus screen with unlocked bootloader in the top then go straight to twrp, where I could not flash anything. I finally got it to reboot to fastboot where I can reboot to jb but if turned off it will still load straight to twrp and I have to adb fastboot reboot to the RCK android wipe screen and load jb from there using the android. I have tried wiping from that screen, wiping from twrp and even adb push the rom again to wipe with no success. When adb pushing any recovery or rom/software it seems to take but have to manually reboot with power button after to get it to reboot. I tried adb pushing different recoveries with no success along with Energy rom, no success. To me its like I have a dual partition on the storage. Is there any way to wipe everything completely clean and start fresh? Without using recovery since it is not working.
Sounds like you have bricked like a lot of other people. There is a guide in General. Which version of TWRP did you use on the latest bootloader. If it was not TEWRP 2.4.40 or the patched version then you have bricked unfortuntely.....
sbdags said:
Sounds like you have bricked like a lot of other people. There is a guide in General. Which version of TWRP did you use on the latest bootloader. If it was not TEWRP 2.4.40 or the patched version then you have bricked unfortuntely.....
Click to expand...
Click to collapse
I haven't bricked yet, it still works. I just have to adb reboot to bootloader if I power it down and restart it. I just cant wipe it and reinstall anything. I dont remember right off which version of TWRP I did use, but it wont mount anything to allow me to wipe or install from it though.
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.