Related
hello all,
Just flashed this ROM using clockwork, only problem I ran into was clockwork will not reboot into recovery. Instead it reboots into samsung recovery.I would like to re-flash ROM. I am new to this, I was an iPhone user and it was pretty simple to reinstall operating system.
I use a macbook with snow leopard, what is going to be my best option to re-flash with the macbook. I have read about Odin, and ADB. But not really sure which to use or how to use them for just flashing a custom ROM.
Any help would be great!!!!1
RAMROD
Search "boot into recovery"....using buttons.
Power off
Hold vol+/vol- (keep holding)
Hold power (keep holding all three buttons)
Wait vibrant screen...wait for black...wait for second vibrant screen and release power button ONLY.
Should be set.
OR
Search for OS X...you can use Terminal to manually flash/reboot/etc. through utilities. Be careful though, the commands are slightly different.
I'm running OS X 10.4 (tiger) and never have to use the computer (outside of TGA_Gunman's one click root program)...everything can be done through the phone in most cases.
I have no problem getting it in this mode. I am trying to get it to boot into clockwork recovery, and the only thing that is loading is the stock kernal recovery menu.. So I am looking for a method that I can do it with my macbook. I have searched in google, and found other tutorials for other phones, but not the vibrant. If you know of one please let me know..
thanks
in sammy recovery hit 'reinstall packages' (may need to do this more than once) and it will reboot you to clockwork. then flash through clockwork like normal. this is why you need to leave the update.zip file on your sdcard after installing clockwork.
funeralthirst said:
in sammy recovery hit 'reinstall packages' (may need to do this more than once) and it will reboot you to clockwork. then flash through clockwork like normal. this is why you need to leave the update.zip file on your sdcard after installing clockwork.
Click to expand...
Click to collapse
I never removed the zip file from sd card, in fact while looking at the files contained in clockwork mod file. It contains the same files as my other Vibrant that is running fine. Just doesn't have Bionics Obsidian 2.2 running on it..
I tried what you said about clicking on re-install and did that 5-6 times. That didn't improve the problem.
thanks for the idea,
Back to the original Question, what is the easiest way to load different rom on my phone with my macbook?
Does the phone still boot up normally? If so, open Rom Manager and select "Flash ClockworkMod Recovery". Then select your device. Reboot into recovery and if you are still in the stock recovery, hit "Reinstall Packages". If that doesn't work, then I have no idea...
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10
deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse
Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse
Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2
Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app
Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
miapjp said:
Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
Click to expand...
Click to collapse
I think you're trying to use the wrong recovery file. Try downloading CWM or TWRP from the links listed in the first post of this thread -- I've used both with no problems on my NT.
Saludos,
Steve
Removing CM9
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Mauler85 said:
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Click to expand...
Click to collapse
You don't need to go back to stock to downgrade from CM9 to CM7. All you need to do is boot into recovery and flash the new ROM. With that being said, it would be well worth your time to start by installing Titanium Backup and backing up your system before you do anything else... That will let you restore any apps you've downloaded and want to keep (along with their settings and data), which will eliminate one headache after you flash the new ROM...
Review this thread from Lavero.Burgos about installing a customer recovery on your tablet. You've already got one installed if you're running CM9, but the thread has got lots of really good info, and if you have the Clockwork Mod 6.x recovery installed, you need to replace that with Clockwork Mod 5.x to flash CM7.
Next, check this thread from Celtic Web Solutions. The link to the internal CM7 ROM is in the first thread, along with the instructions for installing this ROM to your emmc (internal) storage.
Now, when you start you tablet, instead of holding Power + n to boot into recovery, wait for the Cyanoboot splash screen to open (the one that says CYANOBOOT, not the animated CM9 splash screen), then press and hold the n button until the boot menu appears. From here you can select to boot normally into CM9, into your internal recovery, or into a recovery.img loaded on your SD card. Select one of the recovery options, and you should be able to do a nandroid backup of your device, then install CM7. Since you're changing to a completely new ROM, I strongly recommend that you do a factory wipe/reset as well as wiping the cache partition and Dalvik cache.
NOTE: There's a big difference between an Titanium Backup backup and a Nandroid backup! You'll want to do both as you go through this. Titanium Backup will take a snapshot of your apps (including the settings and data associated with them) that you can restore after installing the new ROM. Super helpful, since you don't have to re-install everything from the Play Store, nor do you lose data like savegames, etc. Nandroid runs from recovery mode, and will do a complete image of your system, including the ROM. It protects you in case you run into a major problem while flashing a new ROM -- it's saved my life a couple of times...