Related
Since the Evo just got NAND protection removed, I figured I'd share the persistent version of ClockworkMod recovery
Currently ROM Manager is using a recovery hot replace to give you a custom recovery. But I'll eventually be packaging this into ROM Manager's flashing process like the other phones it supports. I'll wait a week or so to switch, while everyone switches over to the new root.
For those that want to make ClockworkMod their default recovery on recovery boot, use this image:
These step assume you have already unlocked your NAND using the "Part 2" thread in the forums.
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-supersonic.img
http://www.droidaftermarket.com/koush//recoveries/flash_image
Place these files on the root of your SD card.
Then run this from a root Android shell.
cd /data/local
cat /sdcard/flash_image > flash_image
chmod 755 flash_image
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Done!
For insurance stuff, will we need to flash stock recovery img to get rid of everything?
<3
Will we be able to update this with ROM Manager?
Re: Permanently replacing your recovery with ClockworkMod Recovery Image
You are a God!
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
<3
Will we be able to update this with ROM Manager?
Click to expand...
Click to collapse
Yes, in a week, when everyone has done their NAND unlock, ROM Manager will start flashing and replacing your recovery for you, so you don't need to do this manually. I do not want to switch right now, because that will leave people who haven't unlocked out in the cold.
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
no, it means when you choose reboot to recovery in any application, ROM manager, quickboot or thru adb it will reboot to the phone's recovery partition but instead of loading the stock recovery, it will load this custom recovery!
this is basically a permanent or "sticky" recovery where as before we had to load the custom recovery every time as a temporary or "non-sticky" recovery. the days of temporary or non sticky recoveries are OVER ... at least until the next update from HTC/Sprint!
Koush, I m still a completely rookie on root part, EVO4G is my first androind phone, and 0 experience on root. Besides, i haven't done anything about rooting evo4g yet (still kinda struggle here, worrying to brick such a$$kicking phone, anyway). So please forgive if my question sounds ridiculous and stupid.
lets say if i decide do root like next months, so i should follow the 1st part root my phone by "PC36IMG.zip", then what's next step? should I use adb shell complete flash recovery, and 2nd part to remove NAND protection, at last run ROM Manager flash recovery permanently? or I can just directly use ROM Manager after root'd phone, like the instruction "[TUTORIAL] IDIOT-PROOF Root Guide! No ADB, no fuss!" by theBiles, to flash recovery permanently?
Koush said:
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
Click to expand...
Click to collapse
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
Hrm, let me double check on mine
phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
I get the android with the white triangle as well when using reboot into recovery from rom manager. However the normal recovery is now clockwork great job and thx K!
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
jeremydk said:
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
Click to expand...
Click to collapse
Found the problem Fix is being uploaded!
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Koush said:
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Click to expand...
Click to collapse
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
So what exactly does this do or look like? I'm a bit confused on that one.
phinnaeus said:
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
Click to expand...
Click to collapse
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Koush said:
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Click to expand...
Click to collapse
Oh gotcha. So thats what that progress bar is before it loads up? And this won't happen with the updated ROM Manager coming in a week. I guess thats not really a question, but if I'm wrong feel free to correct me
Koush said:
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Click to expand...
Click to collapse
Worked great but it might help to change that to
./flash_image recovery /sdcard/recovery-clockwork-1.8.2.2-supersonic.img
Took me a second to figure out why it said directory or file doesn't exist
Thank You for all your work
Hey Everyone,
Im sorry in advance if I'm about to ask the dumbest questions of the day/week, but I'm brand new to this, and I haven't found any answers in any of these threads, so go easy...
Up until now I customized the heck out of my mt4g. Tonight however, I followed HTC's instructions and unlock the boot loader -- as I thought based on what their site said, that I'd be able to flash custom roms to the phone once unlocked.
I was successful in unlocking the Bootloader, but (S=on) still exists. I'm kinda stuck now because I don't know what to do next? Is it possible to go from here to Root, if so, how? I've tried the HTC Super Tool for over an hour and it's not working... not giving me perm S=off. Maybe I'm doing something wrong?
If the phone isn't rooted, then how am I supposed to be able to flash a rom??... Do I do it from the HBOOT menu? Because I can't seem to do that either. If I opt for "recovery" while in HBOOT, I come to a red triangle, and have to do a battery pull.
The stock rom that's loaded now has GB 2.3.4 running.
My goal is simply to get CyanogenMod running on this phone. I just don't know what the next step is. I've already factory reset the phone so all my customizations and apps are gone therefore I don't really care what I have to do to get where I want to go. If it's possible to root from here, what's the next step? If root isn't possible, then how do I flash a new rom, like HTC claims I can do now that the BL is unlocked??
If someone could offer some help, I would be super appreciative!!
T40
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
headcreepz said:
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
Click to expand...
Click to collapse
Follow that guide and get off the official HTC unlock. You should have read the thread on this forum about it.
Sent from my mytouch 4g using xda premium
okay... I followed the guide and I achieved "perm-root", I believe.
If I go into terminal emulator, and type SU, I get a # returned. I do notice however that when I boot into HBOOT, it still says s=on. Not sure what the difference is between 'perm root' and 's=on' but...
I have rom manager downloaded. I also have titanium backup downloaded and did a full backup.
PROBLEM:
In rom manager, I Flashed ClockworkMod Recovery, and then downloaded the nightly CyanogenMod, no problem, but every time the phone reboots (into recovery mode), I stop at the red triangle?!?!?!
What's going wrong?
Open rom manager and art the top is an option to install recovery-install it, then you should be good to go
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
track40 said:
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
That's the stock android recovery.
Sent from my Infernalized Glacier!
-Team Inferno
If you had your device s-off and rooted, why HTC unlock? You just went backwards.
i started with HTC Unlock, then achieved perm-root, but (s=on)
Recovery
Hello,
I had the same issue, I had to flash the recovery with adb
1) If you dont already have it download flash_image and place it in your adb tools folder
2) Download the recovery you need and unzip, then rename to recovery.img and place in the root of your sdcard
3) open terminal and use the following commands
adb push flash_image /system/bin
adb shell
su
cd /system/bin
chmod 777 flash_image*
flash_image recovery /sdcard/recovery.img
4)wait for it to finish
5) type exit
adb reboot recovery
this should solve the issue
You can find the recovery here...including the new touchscreen version
http://clockworkmod.com/rommanager
You can download flash_image here
http://forum.xda-developers.com/showthread.php?t=902493
Thanks to Raichison for all the above
okay #furydude39, im all ready to run through your steps... when i issued the first command "adb push flash_image /system/bin", the handset responded with
"failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system"
Any idea where to go now? This is obviously why every time i boot into recovery that the processes initiated by RomManager isn't sticking.
an hour later...
I was able to execute the commands correctly that 'furydude39' recommended, and still nothing.
Here's a video I shot of the phone [still] giving me a headache
http://youtu.be/2Hr-7CosDQc
Someone's gotta have an idea on how to get past this?
Have you turned off fastboot?
Sent from my HTC Glacier using xda premium
yes, just checked... fastboot is off
We need to find out why it is not flashing the cw recovery. Are you able to to mount /system partition and copy files to it? I'm thinking a downgrade might be necessary so you can do gfree and eng bootloader.
Sent from my HTC Glacier using xda premium
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
track40 said:
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
Click to expand...
Click to collapse
You should manually wipe and flash. Doing it from the app seems to screw up some of the time. Make sure you wipe system data cache and dalvik before flash. It even helps to reboot recovery after doing wipe before you flash a rom.
Sent from my HTC Glacier using xda premium
i hate to ask another [stupid] question... but how do i manually do that?
track40 said:
i hate to ask another [stupid] question... but how do i manually do that?
Click to expand...
Click to collapse
In recovery, using the volume rockers, look for factory data reset/wipe. I'm not to positive on the exact names, since I have touch recovery. When you find it select wipe data an wipe cache. after those are wiped, go back then find advance, wipe dalvik cache. When that finished, go back. Select install from sdcard, find your files an install them. Everything should work then.
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader
Thanks all for your suggestions. I finally was able to get Cyanogen to stick. Had to wind up flashing the boot.img manually using fastboot via Windows while in HBOOT screen.
I tried to use the search and google but didn't really find anything helpful. Almost 2 years ago, I unlocked the bootloader back on honeycomb and did custom recovery, root, and custom rom. Then a little while after ICS came out, I did the OTA update.
Today, I reset the xoom back to stock ICS and tried to unlock the bootloader again...thinking nothing of it. The process was taking a few minutes so I decided to get a snack and when I came back it was rebooting.
I assumed that it worked and continued to try and fastboot a recovery image. The recovery image installed and I did another reboot but was greeted with the android welcome screen. Anyways I went through the menus and then tried to enter recovery and it gave me an android laying on its back with and exclamation point above his open chest.
I hard rebooted and can still get into my device, but adb cannot seem to find my xoom anymore. I have tried it on a 64bit desktop and laptop with no luck.
Have I messed up? Or is there a simple fix that I am missing? Thanks in advance for any help!
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
dfib1 said:
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
Click to expand...
Click to collapse
Yes, I can get into fastboot by holding the volume down key and the power button. That's fastboot, right?
Yes, I had to go through the menus the second time I unlocked.
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
dfib1 said:
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
Click to expand...
Click to collapse
I want to flash this ROM
http://forum.xda-developers.com/showthread.php?t=1997434
With whichever recovery is best. I tried flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1074979
I am on a 4G xoom on 4.0.4 but I don't use my data plan. I would like to be on a nice stable build of 4.2.
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
I think it is fine just the 3g/4g won't work.
I can get you going again but you are going to be starting with a locked honeycomb device. You will then have to either let it update to ICS or JB or unlock, root, install custom recovery and flash a rom. What xoom do you have 3g or 4g?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Okay I restored it again but this time i did a factory reset and wipe dalvick before flashing the rom and gapps. It works! Thank you for your help!
However, could I ask how to root this thing?
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
dfib1 said:
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
Click to expand...
Click to collapse
Thanks! Got it!
g;lad to hear it.
SL101 with CWM 1 click root v.1 which i understand is basically the same as the TF101
Tried rooting and seemed to be a success but bricked when trying to install cy mod.
Tried factory reset in recovery mode and still bricked.
Won't mount to SD card.
Can't seem to find any guides to reset firmware back to stock...
Any ideas? links to a guide i haven't found? (I have looked) or am I bushwacked?
Thanks.
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Did you use ROM Manager to install CWM?
That does not play nice with the Asus tablets.
You can try using PERI to push a new recovery via ADB when in recovery.
I would use ADB to push the TWRP 2.3.2.3 blob myself.
*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
chchas said:
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
Click to expand...
Click to collapse
Follow freds instructions above
*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
ALSO. Might note that I do not have access to my tablets home screen AT ALL. Not through cold boot or anything (unless it takes more than 30 minutes to cold boot)
chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
*Detection* said:
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
Click to expand...
Click to collapse
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
chchas said:
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
Click to expand...
Click to collapse
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
*Detection* said:
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
Click to expand...
Click to collapse
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
chchas said:
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
Click to expand...
Click to collapse
Been there done that. I had to use adb commands to push a new recovery blob. What version of cwm are you using again?
I have always had to use this one. After having this exact same issue.
D
DatDude123 said:
I have always had to use this one. After having this exact same issue.
D
Click to expand...
Click to collapse
v6.0.1.3
Do you have instruction on how you fixed yours? or a link ?
http://forum.xda-developers.com/showthread.php?p=16557195
This is what saved me. Alk I flash now is arhd and revolver. I do not attempt jellybean any longer......it was me, a laptop, and the tablet connected via usb and using adb commands. You are about to learn a lot.
D
So are there any handy links to a step by step of this? i found one for a Prime but i don't think it's the same thing....
So I followed this guide for adb http://forum.xda-developers.com/showthread.php?t=1071584 and got all the way to the end'. Now i'm stuck, where do I go from here? I don't want to screw anything up so any pointers will help!
Also, i can do this adb stuff while in recovery mode right?
Thanks!
Hello,
Yesterday there was an update for the Moto G, I confirmed to do the update. Since then the phone is in a reboot loop. I mean it doesn't matter what ever I do,the phone restart itself in every 2-3 minutes. The phone is rooted.
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
I've got a tip that I should remove the update file from the /chace directory,however I don't know how to do so,as the phone keeps reboot itself.
The only place,where the phone is not restarts is in the bootloader.
Is there any way to somehow solve this problem without flash a stock rom ?
Thanks for your help!
Regards,
Péter
The same here. Help!
Tussky said:
Hello,
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
Click to expand...
Click to collapse
You have to press volume up instead of power to choose something in fastboot menu.
Unroot and if used custom recovery go back to stock recovery.
mokkami said:
Unroot and stock recovery.
Click to expand...
Click to collapse
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Yes I know I have to press volume up,however if I chose recovery it's reboot itself,so I'am not able to select Recovery from the bootloader.
Tussky said:
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Click to expand...
Click to collapse
My is rooted and cwm 6.0.4.6
May be we must do something with fastboot command
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
Here is the forum link to install CWM Recovery for your Moto G:
http://forum.xda-developers.com/showthread.php?t=2563599
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Recovery menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
Click to expand...
Click to collapse
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
You mean this.
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
if you used the modified recovery method:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tussky said:
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
Click to expand...
Click to collapse
Thats strange.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
The general command to install a custom recovery in Fastboot is:
fastboot flash recovery your_recovery_image.img
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
Click to expand...
Click to collapse
Thanks MAN! It works perfect!
mokkami said:
You mean this[/URL].
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
if you used the modified recovery method:
Thats strange.
Click to expand...
Click to collapse
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
Tussky said:
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
Click to expand...
Click to collapse
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
mokkami said:
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
Click to expand...
Click to collapse
I used the method to root the phone what is on that site,I followed that description and it worked. I'am not an expert in it,so I just followed PaulOBrien guide,so I can't answer for it for sure.
At this point I'am really desperate as the phone is completely useless, so I don't care even if I had data loss,as I can't access it anymore,nor save it to my PC.
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
mokkami said:
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
Click to expand...
Click to collapse
Thanks! However I can try it out only after 20 UTC.
However I have an idea,but maybe I'am wrong.
What happens if I try the chace wipe via in command line, I mean:
mfastboot erase cache
This should delete the cache right ? Shouldn't this command remove the problematic update file ?
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I want to give it a try. Yes,however I don't have to install the update. But I think I will flash a stock rom,make the update and then re-root the phone.
Thank you guys, I was going crazy with this rebooting problem. So now it is fixed, but how can I get the update? Noway?
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I was able to enable the usb debugging,and then to start the bootloader. However If I connected the phone and tried to execute the adb reboot-bootloader command it didn't worked. So I restarted the phone and entered into the bootloader,then I've done the following:
fastboot reboot-bootloader
fastboot erase cache
After the first command,the phone rebooted into bootloader,then the second command finally cleared the chace. Now my uptime is more then 8 minutes,so the phone is working great now
However I will do the complete process on the weekend,but not now as I'am really tired,but I will flash a stock rom at the weekend.
Possible solution...
Just started a thread with a possible solution
http://forum.xda-developers.com/showthread.php?t=2663205
Hope it helps...