I have a GEN1 Blade running SS (previously JJ), and I now want to try a 2.3 based ROM, probably Ginger Stir Fry as per recommendations (looking to speed and stability). However, I can't seem to boot into CWR - either but holding volume- during boot (that just show the green Android logo for a few seconds and reboots over and over until I let go), or via the Reboot into Recovery option in ROM Manager. As per ROM Manager I have the latest version 3.0.2.7 installed.
My plan was to to follow this guide to first convert to Gen 2, and then flash GSF.
Any ideas how I can get CWR to work again?
Recovery 3. 0. 2. 7 is Gen 2 only.
You should flash 3. 0. 1. 4 in ROM Manager.... works for Gen 1 Blades.
In RM scroll to bottom of screen... All ClockworkMod Recoveries..... go there..... you may have to clear cache to see old recoveries..... hope this helps
You could also TPT... GSF has tpt images in MoDaCo...... big thread there. Will also give you latest CMR.
Sent from my ZTE-BLADE using Tapatalk
That did it, thanks. 3.0.1.4 allowed me to boot into recovery.
Flashed to GSF and am playing with it now. Seems nice but the Market apps do not download, though I can browse Market content and choose install as usual. Peh, always something...
Related
So i'm trying to install KaosGingerbread and cannot get Google apps installed.
I've tried the 12/18 one and it causes a boot loop. Then I tried the 12/28 ones and it flashes, loads, but the google apps dont show up. not even the setup wizard runs. anyone got any suggestions?
I've tried an older version of KGB, i've tried formatting my sdcard, deleted the /sdcard/android-secure folder. but to NO avail. i've looked at the celb thread because i saw a few posts about that a week ago but none of the solutions there worked.
the latest Gapps 12/28 doesnt even flash over celb but the 12/18 one does. anyone have an idea why this is happening?
EDIT: at the advice of someone from the CELB thread i installed clockwork via rom manager booted to recovery from the end button it boots to amon-ra, went into rom manager it boots to clockwork, rebooted because i accidentally went from wipe(because of the damned 9 no's before a yes) and double clicked to reboot and just battery pulled and it booted to ra again.....so i somehow have 2 recovery's installed.....
EDIT 2: okay when i clicked boot to recovery from rom manager again it went into ra, unpacked clockwork and then booted into clockwork.....(after saying it replaced the stock recovery)
EDIT 3: still didnt work going to try to find a different version of the 12/28 package and compare md5's
FWIW, what you are experiencing with Clockwork is the way it is supposed to work: you launch it from within ROM Manager. If you cold-boot the recovery partition, you will get Amon_RA. It didn't work that way in the distant past, but that's the way it works now.
Part of the confusion results from the fact that the program which manages the on-screen menus is /sbin/recovery - when Rom Manager says "replace the recovery", it means that program, not the entire recovery partition. That's why you see the Amon_RA menu appear briefly - and then it disappears and gets replaced by the ClockworkMod (/sbin/recovery) menu.
All of this happens in the booted ramdisk - so the the recovery partition is untouched, and ClockworkMod only lasts for that boot.
Try doing this :
1. flash KGB and before rebooting flash the gapps pack from recovery
2. reboot
3. enjoy kaos goodness (i also recommend having setcpu clocked to 710 to get the lag down)
jrozga said:
Try doing this :
1. flash KGB and before rebooting flash the gapps pack from recovery
2. reboot
3. enjoy kaos goodness (i also recommend having setcpu clocked to 710 to get the lag down)
Click to expand...
Click to collapse
flashing gapps before reboot causes a bootloop
hi guys
my defy firmware is on version 5
anyway i downgraded to froyo now i want to install SndInit cuz i want to flash cm7 on my phone
so now on froyo rooted it then rebooted it after the root
now every time i install Sndinit it gives me success then i reboot my phone and my phone just get stock at motorola logo and keeps rebooting
what is wrong ??
i want to flash cm7 and every time i install SndInit i reboot to get to recovery mode it stocks at motorola sign
please help i tried all the versions of SndInit and i always gets stock at motorola sign
please help me i really want to flash cm7 and that SndInit aint working for me
any other way ?
waiting for ur help guys thanks alot in advance
on bootmenu set default 2nd-init and after this wipe cache partiton and dalvik cache. if doesn't work reinstall froyo, root it; install SndInitDefy_2.0.apk (last 2ndInit) and Bootmenu 1.0.4 and CWM 5.0.3.1
thanks for ur replay but i did set it as default also tried the beta
my phone after i install (SndInitDefy 2.0 or 1.4 or 1.5 or 1.9 i tried alots of version )then reboot i just get stock at motorola logo i cant get into recovery and my phone just stays at motorola sign so i flash spf again to make it work
i have tried 2 versions of froyo its the same
what do i have to do what is wrong ?
thanks in advance
dude can you explain more please im having the same problem i cant install 2endint i did install bBootmenu 1.0.4 and CWM 5.0.3.1 but what do i do now? i go to stock recovery ?? please explain a little bit more thank man .
i also had met the same situation as you mentioned. and i found if i unpluged the usb from my computer, sndinit will take effect after rebooted. maybe this could be helpful to you.
Sent from my Nexus S using XDA App
read this, if don't understand search in forum
zyxwvut said:
Monzer, when you install bootmenu are you installing the .apk and then opening the app and then clicking to install 2nd init? This is the right procedure! after you do this reboot your phone and watch for blue led to flash during boot, hit volume down once it flashes blue.
What 2nd init version are you installing? here is the latest http://forum.xda-developers.com/attachment.php?attachmentid=792601&d=1322064151
Are you trying to flash CM7?
There is a very old version of CWM that should be suitable if all else fails you. It should work just fine to flash CM7 but not so sure about CM9. However if you want to flash CM9 You could use this old version of CWM to flash CM7 which will in turn install a new version of 2nd init which is definitely suitable for flashing CM9. This old CWM "might" work for flashing CM9 but I dunno if I would try or not! Download in my attachment below!
You MUST enable USB debugging to install.
copy the apk to your sdcard and use a file manager to install it then open the app in your app drawer and choose to install the custom recovery (with USB dubugging ON)
THIS STEP IS VERY IMPORTANT!!!
AFTER INSTALLING THE CUSTOM RECOVERY DISABLE USB DEBUGGING.
You enter CWM by again opening the app and choosing reboot to recovery (with USB debuggind OFF)
Click to expand...
Click to collapse
Hi all,
I have a Nexus 7, rooted, running stock 4.1.1 rom, and just installed TWRP 2.1.1
I have been reading this thread, http://forum.xda-developers.com/showthread.php?t=1779092 , however I cannot post on the thread due to being a new/low post count member.
I read that, and it does happen, that each time I reboot, the stock recovery reinstalls itself.
I attempted to follow this....
NOTE: The stock ROM may automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced -> File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Click to expand...
Click to collapse
but it doesn't seem to work.
Firstly, when I go to the "Mount" menu, there is only 3 entries.....1 large button which says "Mount USB Storage", and 2 boxes which are selected with a cross in the box, "Unmount Data", and "Unmount Cache". If I do press Mount USB Storage I can only Unmount it to return to menu.
So regardless of that part, if I then go to the file manager, and browse to the system folder, the folder shows up empty, and the only thing showing is a Bin subfolder (also empty)
any ideas whats wrong?
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
TheBiles said:
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
Click to expand...
Click to collapse
hi,
yeah I did use the tool, all is rooted fine. If you install TWRP from GooManager, and then press to reset to recovery, TWRP loads fine. Once you reboot again however, the stock roms overwriting the TWRP so it no longer works each time. The steps there were supposedly to stop this from happening, from within TWRP, however the options aren't even there. Sadly, I can't post in the TWRP thread due to having less than 10 posts
How r u booting into recovery? Do u power off then use button combo? I use quickboot from market. Its free and boots u into recovery without having to manually turn off the device. I had the same exact issue u drescribe when attempting to follow op instructions. I couldn't do it so I said what the hell, let me see if I boot into recovery using quickboot it overwrites. I was happy to discover that it didn't.
Sent from my EVO using Tapatalk 2
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Midnight Tboy said:
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Click to expand...
Click to collapse
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
pathtologos said:
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yup....just installed Quick Boot (Reboot),
chose Recovery, and again its rebooting back to the original recovery instead of the TWRP.
Guess I'll have to flash to a custom rom to get around it if want it sorting now....or wait till I have the minimum post count to post on the main TWRP thread
Not end of the world to reinstall apps and games I guess when the custom roms are more mature, so long as I remember to use Titanium Backup to save my games progress
you need to rename the recovery-restore.sh file in /system/etc/ (I forget the name offhand - if you look at the filenames there you'll figure it out). It restores the stock recovery at every reboot unless deleted or renamed. Then flash your 3rd party recovery.
Hi,
thats the trouble.....I use the file manager in TWRP, and I can't see that file anywhere.
The TWRP page says to go to /system......but when I go there its empty, only one subfolder, /system/bin, which also shows up empty
I have been upgrading a friend's Blade but I've run into trouble. I rooted the froyo firmware and flashed CWM. Now if I try to boot into recovery via "adb reboot recovery" it somewhat works but if I try to get into the recovery via Vol - + Power it doesn't. It just gets stuck at splash screen and won't bulge. But if I have flashed a stock recovery I can boot into FMT. This is not the end of it though.
I went on to flash CM9 KonstaKANG release but wanted to do a reflash after doing TPT conversion, the TPT part went fine but now I later realised that I can't get into CWM. So...I got stuck. I flashed a Gen 2 stock via Windows and flashed a TPT image.bin I found that contained a stock 2.3.5 firmware. Brilliant, life saved...no? Turns out I can't root it, so I can't flash a custom recovery to it and boot into it in order to flash CM9. So....I did a bunch of other stuff and at this point the blade has a CWM recovery which I can't boot into, empty system partition and pretty much a boned status. I thought I'll flash a stock 2.2 TPT which I found at: http://amphoras.co.uk/downloads/blade-tpts but the one with a ROM are in some other format than TPT and I can't figure out how to flash them. Can anyone help me here?
Install rom manager (available in google play as a freeware) then flash clockwork mod recovery.
Now u can enter recovery with just 1 tap ie "reboot into recovery"
NOTE USB debugging should be enabled at all times
Add on:
You can root ur phone using an app named z4root.
To permanently root it search google and click the android modaco link
Sent from my Blade using xda app-developers app
Dragooon123 said:
I have been upgrading a friend's Blade but I've run into trouble. I rooted the froyo firmware and flashed CWM. Now if I try to boot into recovery via "adb reboot recovery" it somewhat works but if I try to get into the recovery via Vol - + Power it doesn't. It just gets stuck at splash screen and won't bulge. But if I have flashed a stock recovery I can boot into FMT. This is not the end of it though.
I went on to flash CM9 KonstaKANG release but wanted to do a reflash after doing TPT conversion, the TPT part went fine but now I later realised that I can't get into CWM. So...I got stuck. I flashed a Gen 2 stock via Windows and flashed a TPT image.bin I found that contained a stock 2.3.5 firmware. Brilliant, life saved...no? Turns out I can't root it, so I can't flash a custom recovery to it and boot into it in order to flash CM9. So....I did a bunch of other stuff and at this point the blade has a CWM recovery which I can't boot into, empty system partition and pretty much a boned status. I thought I'll flash a stock 2.2 TPT which I found at: http://amphoras.co.uk/downloads/blade-tpts but the one with a ROM are in some other format than TPT and I can't figure out how to flash them. Can anyone help me here?
Click to expand...
Click to collapse
Heh, not only have you screwed up CWM, you also converted your phone into a GEN3 phone in the process (by flashing that 2.3.5 TPT).
Easiest way to fix it:
1, download: http://bit.ly/yUi4Nu (stock partition layout, if you want a 160MB system layout use: http://bit.ly/wEO8Im )
2. unpack it to your sdcard (/image/image.bin)
3. flash it like you would any TPT
You should have CWM installed at this point (just press and hold vol- during bootup) and now you can flash whatever ROM you want to.
I've been trying to find instructions for installling CM11 (or 10.x for that matter) on my Bravo. The only guides/tutorials I find assume that I know a lot that I don't. Can anyone verify if these instructions are correct? I've included links to where I found each step.
Step 1: Install Drivers
Download and install Bravo drivers from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
From link in this thread by josuearisty: http://forum.xda-developers.com/showthread.php?t=1559109
Step 2: Root and bootmenu and recovery
Follow the instructions from http://forum.xda-developers.com/showthread.php?t=1817842 also by josuearisty.
This roots, installs bootmenu (2nd init) and a recovery image.
Just running runme.bat you will have a Bravo ready to use new roms in less than a minute.
Instructions:
1. Download: http://www.mediafire.com/?yfgvds9a1w8sbds
2. Extract files whenever you want.
3. Enable USB debugging (menu > Settings > Applications > Development) and connect your phone to the PC.
4. Run runme.bat, in folder Root+Boot-AIO.
5. Press Enter when script ask you to do it and READY!
Click to expand...
Click to collapse
Step 3: Install GApps and ROM
Get the CM11 Bravo ROM from http://forum.xda-developers.com/showthread.php?t=2515036 by Quarx.
This also has a recovery (or an updated recovery?), is this needed? If so, how do you install this?
For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
Click to expand...
Click to collapse
Google Apps are available here http://forum.xda-developers.com/showthread.php?t=2012857 by BaNkS. Is this step optional?
If you have problems and brick phone the recovery or here: http://forum.xda-developers.com/showthread.php?t=1559109 by josuearisty.
Finally, instructions for using bootmenu from: http://motodefynbravoromguide.blogspot.com/
INSTALLATION INSTRUCTIONS
NOTE: You must be on a froyo rom or higher to install this.
Copy the gapps and the cm zip to your sd card.
Boot into 2nd init(voldown on blue LED).
Use volume buttons to navigate and the power button to select an option.
Select Recovery.
Select Custom Recovery.
Wipe cache, data and dalvik cache.
Go to install zip from sd card and then select choose zip from sd card.
First select the cm zip and install it.
Clear cache and data again.
Now install the gapps zip.
Hit reboot and set up CM!
Click to expand...
Click to collapse
Does that sound right? Thanks!
Actually I had to install CM10.1 first, then install CM10.2 and last was to update the recovery.
After the recovery update I was able to install CM11.
So far so good. the only issue had been the crazy battery drain because the default clock have far to much voltage.
A little tweak and the battery is been drain like before (hardly a day of battery).
Any how It nice to see the latest version of android in this ol phone and see it work as my daily driver
balamacab said:
Actually I had to install CM10.1 first, then install CM10.2 and last was to update the recovery.
After the recovery update I was able to install CM11.
So far so good. the only issue had been the crazy battery drain because the default clock have far to much voltage.
A little tweak and the battery is been drain like before (hardly a day of battery).
Any how It nice to see the latest version of android in this ol phone and see it work as my daily driver
Click to expand...
Click to collapse
Other than that, are these the steps you used?
balamacab said:
Actually I had to install CM10.1 first, then install CM10.2 and last was to update the recovery.
After the recovery update I was able to install CM11.
So far so good. the only issue had been the crazy battery drain because the default clock have far to much voltage.
A little tweak and the battery is been drain like before (hardly a day of battery).
Any how It nice to see the latest version of android in this ol phone and see it work as my daily driver
Click to expand...
Click to collapse
One more question, how do you update the recovery?
Here's steps I took from stock.
Root and boot
Flash CM7
Boot and then recovery
Flash CM10.2
Boot and then recovery
Flash recovery update for bravo
Boot and then recovery
Flash CM11 and gapps
Bravo recovery
http://quarx2k.ru/cm11.0-nightly-kobe/update-kobe-recovery.zip
CM11 gapps, must use these
http://goo.im/devs/BaNkS/GApps/4.4.2//1-16_GApps_Core_4.4.2_signed.zip
ilmcgee, that's the sort of instructions I'm trying to understand. There's too many assumptions in what the user knows how to do and very little to no way to gain sufficient understanding to understand that abbreviated explanation.
For example, how does one install a new recovery image? It sounds like with the recovery from the (probably out of date CM11 build) that you don't need to progress through the other CM versions.
The Bravo's bootloader isn't unlocked so you must progress through newer roms to update the recovery. As far as I know, the recovery update must be flashed on twrp 2.6.3 and is not a standalone recovery. I do not pretend to understand how all this works, I just try to read and follow the guidance of others before me that know a lot more.
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
bravo root and boot
http://forum.xda-developers.com/showthread.php?t=1817842
thanks to josuearisty for this
Not able to install ANY custom roms?
This seems recent thread seem to be the closest to my issue.
I have followed the same information as noted on this thread but have not been able to install ANY custom roms. I have tried to install 4 different versions ParanoidAndroid and CM7.2 Kang (and CM10.2 though I understand that it would not work directly from rooted stock). For PA, it seem to install but does not and boot back into rooted stock. For CM7.2 Kang, I get the euroskank bootloop. Which I had to use RSD Lite & *.sbf to reinstall stock, re-root, etc. Spent half the day at it and am lost.
I have had half a dozen Android phones which I have rooted and install custom roms on and I have no idea why this is not taking. Tried TWRP and CWM and same effect. Have even used the Bravo Recovery app as well but also the same.
Bought this phone for my parents and am planning to change it to a seniors phone. Thought I update it to the newest fast stable rom beforehand.
Any help would be appreciated.
Cheers!
From stock you just need to do the root and boot and then get into your new recovery, volume down at the blue led. Once in recovery make sure to wipe battery, dalvik, cache and do factory reset. Battery and dalvik wipe are in advanced options in cwm. Then install your rom. Always be careful flashing sbf, most dangerous part, I prefer to use linux when flashing sbf.
And as far as new and stable, the cm7 roms are really your best bet for this phone, imo.