Hi,
I have followed the tutorial given here.
With the only exception of this part:
On the computer, open terminal and run the following commands:
Code:
Code:
adb shell
su
cp -R /sdcard/bootmenu /data/bootmenu
For some reason the bootmenu directory was not present in the sdcard directory, so I created the directory myself and pushed the files for the bootloader 1 at a time (individually).
Everything goes well, until, after the installation, I reboot the phone. It stays on the Google logo. I have tried with and without the Google-Apps pack, but the result is still the same.
To get the phone back on track, I use the sbf file presented in this tutorial, but, although the phone does boot, nothing in it works. I tried flashing to other sbf files, but the phone then won't turn on.
Any idea on what is happening?
I have tried clearing the cache and factory settings, but to no avail as well.
I have also tried a nightly build, but this time it gets stuck on the Motorola logo... tired clearing cache and factory settings... no use.
Any information on this would be appreciated
Thanks.
Which sbf did you use?
Just install 2nd init for defy. It's much easier.
Sent from my MB526 using XDA App
I tried a lot of methods, none of which did not work. At the moment I am either installing the CM mod and getting my phone stuck at the logo page, or else, I am usin an SBF and the phone is simply not turning on.
The main problem I think that I installed full SBF's so downgrading the phone seems to be not possible. Is there some way in which I can get my Defy back to it's stock OS?
I followed the guide here. With that I managed to get a stable OS. I then was able to follow the guide on the Cyanogen website and install Cyanogen 7.
so you installed "leaked" gingerbread on your phone?
It's not easy to downgrade to froyo but i think it is not necessary, bacause it's a good starter platform.
If you did:
install shadow_2.3.4-134_DFP-10.sbf via rsd lite.
root with root4defy134.zip( install from stock recovery)
Install 2ndinit 2.0
After that there are 2 routes: install zipped rom(like WajkIUI_multilang_1.12.16_ICS.zip)
or
Restore rom from a nandroid backup( like MS2Ginger2.1-Defy.zip)
You will find tutorials on XDA.
Related
I downloaded the Fresh 2.0d Rom and all essential pieces. Followed the download and install instructions. Got past the fresh "htc quietly brialliant" screen and it froze on the htc screen with shining letters. Then I wiped data, and dalvik-cache but it wouldn't let me wipe the sd card. It kept saying that I must wipe it via adb. I looked up the issue and downloaded Fresh Pre-kitchen 0.2 and clicked auto root but that didn't work. The link on the website for the add on for pre-kitchen is dead. I tried again to wipe and nothing.
*On a side note, yes I made two different backups before wiping and before flashing.
I'm thinking I may not be using Pre-kitchen properly or I'm missing something. Any help would be appreciated.
The Fresh Pre-Kitchen has been replaced well over a month ago with Fresh Kitchen. A link to it is in the CDMA Hero ROMs.
Well I rooted the phone through Fresh kitchen successfully but the wipe still didn't work. Am I missing a step? Is there something else besides just rooting that needs to be done in order to be able to wipe SD: ext? I'm still getting the same message saying to wipe ext via adb.
Also, is it okay to do a nandroid restore after I wipe?
Which recovery are you running? If it's Amon_ra's update to 1.6.2.
It says Build: RA-heroc-v1.6.2
anything? I'm poking around but still can't out the issue
I have never flashed a "Fresh" ROM before, but I would suggest reflash.
I tried flashing again and same thing happened. It just gets stuck on the htc screen after thinking or awhile. This feels like it should be easier lol
try this restore your nandroid and reboot it will take awhile since to cleared delvick then when its booted open a cmd prompt and cd to your sdk then type
Code:
adb shell
reboot recovery
I have found that when I get an error like that that if you use adb to boot into recovery that it will usealy work after that
i can't figure out how to get into the sdk. When i tried awhile ago it was c:\android-sdk or somethin but now since it's my f drive. do i just enter these commands from the f: ?
For anyone who hasn't yet and is in ADB ever.
It makes life a lot easier if you
"add a global path to the android SDK tools. Right-click My Computer > Properties, click on Advanced, then click on Environment Variables. Doubleclick on PATH, then at the end of the Variable value, add a semi colon ";" and then c:\AndroidSDK\tools" - this is ripped of from a post in the Eris threads.
This makes things easier instead of having to CD C:\AndroidSDK\Tools
ever time, you can now just type "adb" at any Prompt path.
and Windows recognizes it.
FINALLY!
I finally got it to work and didn't have to wipe the sd. It was because I kept doing a nandroid recover after the wipes. But now, it's asking me if i want to run /system/bin/sh as root:root. Not sure what to do there
Ok, here's the quick and the dirty: rooted Dx with bloatware removed. Read that the update won't work if I removed bloatware, so...
1. Downloaded 928droid's back to stock .zip file. Put on SDCARD root
2. Downloaded ROM manager /clockwork to install the ROM. Did not work. Phone rebooted and nothing changed.
3. Tried the update install just in case and it also (still) didn't work.
4. Tried bootstrap, mount and storage, go to format system, mount system = nothing. Phone stuck on M screen after restart.
5. Go into android recovery mode. Try to install 340update.zip (renamed to update,zip), won't work. Phone still stuck on M screen.
6. Tried wipe data cache in recovery mode. Still stuck on M screen
7. Tried restoring factory data. Still stuck on M screen.
Right now, I don't care about the update. I just want my phone working again.
Can someone please help me???
I'm not a super techie but can get through good instructions.
You have to flash an SBF, rdslite 4.8 and the gift 2 or newer... lame bootloader
Sent from my DROIDX using XDA App
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
Hey, on the Defy+, is it crucial to re-create the /tmp directory after wiping? I'm going off this link, which says that /tmp is symlnked and actually resides at /data/tmp, which means you have to re-create the directory. Otherwise, any attempt to flash something will result in this message
E:Can't make /tmp/update_binary
My question is, is this mandatory? I see lots of flashing tutorials, but nothing mentioning this /tmp directory hack. If you don't make it in adb shell, how do you do it?
.
Actually, I should clarify that i'm not too lazy to just try it.
My problem is I can't seem to get back to the initial recovery screen where I can choose to start adb daemon. But if I try to reboot system, I never get a blue LED to go into recovery; if from the CWM menu I try to restart recovery, I get taken to the screen with the knocked-out Android, from where I can only go to stock recovery.
Sent from my MB526 using xda app-developers app
Never mind. I stumbled on a couple posts warning to use Sndinit version 2 and to not flash stable, and that that would get me past the /tmp directory problem. That worked. But then I flashed Slimbean and lost my IMEI.
So I went back to square one, and then this time followed the instructions on the basic beginner's guide to flash the two-part sbf to root a BL7 stock rom. Then did Sndinit v.2, and now I'm back up with Slimbean.
Word of caution, if anyone's reading: I saw on that first boot of SB that I had my IMEI back, which I saw was restored going back to stock SBF. But then I changed the baseband for this region -- it was set to somewhere in Europe, and I'm in Southeast Asia. Then rebooted after that and saw my IMEI was missing again. I don't know why, but I rebooted again, and when it came back I had my IMEI. Strange.
Yes, this is a known bug.
Sent from my MB526 using xda app-developers app
I have just installed quarx' experimental 3.0 nightly on a defy+, which is working, but I can't access recovery any more. Entering recovery from the red screen by using the menu button causes the phone to restart. Resetting using stock recovery doesn't help.
Is there a way to replace the recovery from either adb, the terminal, or by using some app? Is it a matter of dd'ing an image from either update_recovery.zip or the rom over /dev/block/mmcblk1boot1 (or some other device)? If so which file - ramdisk-recovery from update_recovery looks promising.
Is there a better way to recover from a failed recovery? I did install update_recovery.zip, and reboot to it before flashing - I could have done something wrong there.
Of course, if this isn't possible, then there is always .sdf-ing it back to a stock and trying again.
Just replace the bootmenu folder in system with the one from the zip. Don't dd any images, because our custom kernel runs via kexec, not by regular booting
Sent from my Nexus 5 using Tapatalk
Thanks for that. I tried that, and found something interesting - the files at /system/bootmenu/2ndboot don't seem to be used - the firmware does not have a bootmenu folder - everything is in /system/bootstrap. I installed on this phone by flashing the sbf, rooting and installing 2ndInit, installing cm10, then update-recovery, then cm11, if it helps.
I am certainly loading the files in /system/bootstrap. I put '$BB_STATIC echo 64 > /sys/class/leds/[red,green,blue]/brightness' commands into bootstrap/scripts/recovery.sh, and the light cam on and changed color as it should, until it reached the line "./hbootuser ./hboot_recovery.cfg". It did not get past that.
Any assistance would be a help. As you can see, I like digging into things like this.
Edit: Fixed! I downloaded one of the other, older files, extracted the zImage and ramdisk-recovery, and put them into /system/bootstrap/2nd-boot as zImage-recovery and ramdisk-recovery. Then I edited hboot_recovery.cfg to make sure it was pointing at these files, and recovery now works.
Mind you, i might have just messed it up with flashing gapps......