Bravo's bootloader - Bravo General

Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7

Enigmavision said:
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Click to expand...
Click to collapse
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.

skeevy420 said:
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
Click to expand...
Click to collapse
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?

Dr. Orange said:
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Click to expand...
Click to collapse
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base

skeevy420 said:
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
Click to expand...
Click to collapse
Yep that makes sense. Thanks for the help as always skeevy.
*edit* Same issue.
Restoring system...
Error while restoring /system!
Problem while restoring system!
Maybe I didn't reboot correctly...bad backup maybe? I've restored this backup before with no problems. : \
*edit again* I goofed. Your instructions worked fine.

Related

[TUT] Flashing your first A500 custom ROM

Well, flashing a custom ROM on our beloved Iconias became quite easy now thanks to developers on xda. Most of you are quite familiar with the procedure but there are still people that ask basic things all over the ROM developement threads. This is just a beginner's guide, an attempt to collect all the procedures and tools in one thread. Nothing of this is my work and I would like to say THANK YOU to sc2k, thor2002ro, Euclid's Brother, Chainfire, monki-magic, drellisdee, ezterry, Skrilax_CZ, gersma and all A500 developers for making this possible.
You will need the following: external SD card, root rights, unlocked bootloader (if you're on stock ICS), custom recovery and a custom ROM of your choice.
Well lets start by placing an SD card in the SD card expansion slot. Its file system should be FAT32!
*This is optional: To be sure it is recognized later in CWM, format it first with SD Formatter - a tool that can be downloaded from here. Use your home computer / notebook with a card reader for this procedure. Alternatively you can do this using an ANDROID phone.
1.ROOT
Root for Honeycomb 3.0.1 by monki-magic
original thread by Slowie911 here
1. Make sure usb debugging is turned on and unknown sources is selected in Applications settings.
2. Have a micro sd card inserted and turn the tablet on portrait mode and lock it with the switch to fix it in portrait.
3. Download and execute the attached apk. (i had to download from my comp and transfer to the tablet for it to work).
4. Once the apk is installed run the root procedure within the app which was installed
5. Wait and you will receive full root access.
Download Gingerbreak 1.20
Root for Honeycomb 3.1 by sc2k thread here
1. Goto Settings->Applications and enable "Unkown sources"
2. Download the attached APK file
3. Copy the file to your Iconia
4. Install the APK & start the tool
5. Click "root"
6. Enjoy
/IconiaRoot should work on both 3.0.x and 3.1/
Download Iconiaroot 1.3
Root for Honeycomb 3.2.x OTA
Unfortunately there's no dedicated rooting app yet developed for HC3.2. It also comes with a new bootloader. In order to get root you need to revert to an older version of Honeycomb first where Iconiaroot works. How to do that is explained in details in this thread
UPDATE: if you're on OTA HC 3.2.x then you can just update to ICS and use the method for rooting ICS - links posted below
Root for ICS 4.x.x OTA
Stock ICS Leak One-Click Root Tool by blackthund3r
or
Full root for A500 ICS 4.0.3 - Simple method, posted by ZeroNull
2. Bootloader
Since there are many new ICS custom ROMs and custom recoveries, please read in their dedicated threads if they require ICS bootloader. Some of the ROMs can recognize the version of your bootloader and load the proper boot.img during boot. In general - if you're on Honeycomb - you have HC bootloader. If you've updated OTA to ICS, then you have stock ICS bootloader, that is unusable for flashing custom ROMs and therefore you need the unlocked bootloader. A guide on how to install it read here - thanks civato. This thread links to a nice little piece of software (option 1) by gersma that can automatically do all the job for you - install ICS unlocked bootloader and custom recovery. Read and download here - AfterOTA by gersma
3.Custom recovery
original thread with clockworkmod recovery by thor2002ro here
1. Open Market app with your tablet and search for Acer Recovery Installer.
Acer recovery installer
2. Install it and then open it. It has ClockworkMod Recovery by thor2002ro rev1.3.4 built-in.
3. Select "ClockworkMod Recovery rev.1.3.4 by thor2002ro". Tap on install Recovery Image. A popup offering to backup current recovery image will appear. Surely, buckup! Thus you can restore your original recovery image in case of need. Then CWM will be installed. Once it is installed you can remove Acer Recovery Installer tool from your system if you want.
thor2002ro updated CWM to 1.7.3. You can download the zip from tegraowners.com. Later versions of his recovery does not meet GPL because of the "mini" kernel of his - sources not being released. It supports flashing both from internal memory and the external SD card. In order to update your CWM to this latest version, place the downloaded ZIP on your external sd card and update from your CWM by choosing install zip from sd card. Alternatively you can extract the recovery.img from the zip, place it on your external sd card and install it through Acer Recovery Installer by choosing Custom or Stock recovery.img from micro sdcard.
GPL compliant recoveries
RA Revamped for Iconia
TeamWin Recovery Project (twrp) - needs ICS bootloader
A500 Public Recovery
Since the creation of AfterOTA by gersma, you can use his software to install both the bootloader and CWM before flashing the ROM. Get it HERE
4. Flashing custom ROM
Download the ROM of your choice which should be a zip file. Place the zip on your EXTERNAL SD card. Power off your device. Now hold volume down and power buttons together until you see text appearing on the top left corner of the screen - you can release both buttons now. Wait until CWM loads. Volume keys (Up and Down) are used to navigate the CWM menu. Power button is uded as "Enter" i.e. to proceed with your selection. Before going on to install your ROM do a full backup of your system first. Navigate to "backup and restore" and then select Full Backup. Wait untill the operation completes.
Now do the following:
Wipe menu:
- wipe data/factory reset -> navigate to "Yes - delete all user data"
this should format you data partition and cache partition (dalvik cache is gone as well)
Mounts and storage menu
- Format System
this should format your system partition
The above commands are presented in thor's CWM. There are slightly different menus and sub-menus in the other custom recoveries but if you dig a little you'll find that they do the same things and you'll get the idea of what you're doing.
Now you're ready to install your ROM. Get back to the main CWM menu and select
- Install zip from sdcard -> choose zip from sdcard.
Navigate to your zip on the SD card and install it - choose "Yes" again to install. Wait untill installation is complete, return to the main CWM menu and choose "reboot system now".
You're done, enjoy your first custom ROM. Take time for its initial configuration.
5. Flashing custom KERNEL
Flashing custom kernel is as same as custom ROM. You place the zip (Kernels come in zip files as well) on your external SD card and:
- Install zip from sdcard -> choose zip from sdcard.
It is recommended before flashing a new kernel to wipe cache partition and dalvik cache. And of course first you flash the ROM and then the desired Kernel
6. UNBRICKING by flashing a stock ROM
thanks to vache we have full packages shared in his topic
vache said:
Once the desired file downloaded, you have to use Acer Update Decryter by thor2002ro to decrypt them.
After decrypting the file, you have to extract the update.zip from it, put it on an external SDCard (does not work on internal memory) and boot your tablet with Vol- & Power. The update will launch automatically.
Click to expand...
Click to collapse
p.s. Feel free to add stuff to this tutorial - video, pistures or anything you find useful or to correct me if I've made a mistake.
This is fantastic. Thank you. I have had my iconia for a month now and been looking at flashing a custom rom but kept backing out. Just a couple of questions for clarification:
(1). Does wiping data erase the internal sd?
(2). If by some stroke of bad luck a flash is unsuccessful and a boot loop or similar occurs, am I right in my understanding that you can just go straight back into recovery and re-flash?
(3). What are the chances of bricking the tablet?
Sorry for noon questions, please just wanna certain because my gf bought me this tablet under the condition I don't do anything risky like on my x10 that I flash almost daily haha
Thanks for replies
Sent from my A500 using XDA Premium App
kylec said:
This is fantastic. Thank you. I have had my iconia for a month now and been looking at flashing a custom rom but kept backing out. Just a couple of questions for clarification:
(1). Does wiping data erase the internal sd?
(2). If by some stroke of bad luck a flash is unsuccessful and a boot loop or similar occurs, am I right in my understanding that you can just go straight back into recovery and re-flash?
(3). What are the chances of bricking the tablet?
Sorry for noon questions, please just wanna certain because my gf bought me this tablet under the condition I don't do anything risky like on my x10 that I flash almost daily haha
Thanks for replies
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
1. No, it doesn't.
2. Yes. You can do that. There's another option in mounts and storage -> format system - that will format even your system partition and leave your device bare with no ROM files on it. That would be a really clean install I guess
EDIT: I just saw that system is formatted during ROM installation. So no need to do that
3. Always read first what option you've selected and be sure you understand what it does. If you have CWM successfully installed, you have a powerfull tool to restore reflash, wipe, format etc. I've flashed my HD2 hundreds of times and now my Iconia is on the run Never ever had a boot failiure.
drkalo said:
1. No, it doesn't.
2. Yes. You can do that. There's another option in mounts and storage -> format system - that will format even your system partition and leave your device bare with no ROM files on it. That would be a really clean install I guess
3. Always read first what option you've selected and be sure you understand what it does. If you have CWM successfully installed, you have a powerfull tool to restore reflash, wipe, format etc. I've flashed my HD2 hundreds of times and now my Iconia is on the run Never ever had a boot failiure.
Click to expand...
Click to collapse
Thank you very much. I will click thanks when I'm on my computer :-D
Sent from my A500 using XDA Premium App
VERY good information here. Thank you very much for taking the time.
I've flashed ROMS on my last two "chinatabs" but haven't gotten into it with my A500 yet. (To be frank, I'm still thrilled with the prospect of OTA updates from a manufacturer after my last experiences.)
It looks like the process is very similar to my Rena3 tablet.
strider_mt2k said:
VERY good information here. Thank you very much for taking the time.
I've flashed ROMS on my last two "chinatabs" but haven't gotten into it with my A500 yet. (To be frank, I'm still thrilled with the prospect of OTA updates from a manufacturer after my last experiences.)
It looks like the process is very similar to my Rena3 tablet.
Click to expand...
Click to collapse
Thank you, that lays it out all nice and precise for us all. Like strider_mt2k, I have been holdng off on the custom ROMs, because my first tablet was a Gtab, and while it became a pretty awesome tablet, it had to be flashed with a custom ROM to be really usable. The OTA thing was holding me back. But I think that I may try to flash the thing this weekend if I get the chance.
Thanks. Glad it could be of use.
nice tutorial dude! thanks!!
could you please make another tutorial to return back to stock?
specially to return back to stock te kernel.
thanks!!!
As mentioned, best case is if you've backed up your device before flashing any ROM or Kernel. Thus you can restore to your country specific version.
Otherwise its pretty simple - its just like flashing any other ROM following the steps described.
Download the stock one that dr1337 shared from here:
http://forum.xda-developers.com/showthread.php?t=1154492
or choose the right full package - shared by vache:
decript it with Acer update decripter by thor2002ro
Of course they come with stock kernel
I am new in this with flashing and that kind of stuff.
Now is my question, how is it with updates from acer?
Greetz
distructor said:
How is it with updates from acer?
Click to expand...
Click to collapse
I'm not sure I understand your question. Could you be more specific?
if i put a custom rom on the device could i still use the build in update program of acer?
distructor said:
if i put a custom rom on the device could i still use the build in update program of acer?
Click to expand...
Click to collapse
Unfortunately I can not tell you for sure. I haven't tried all of the custom ROMs but in most cases - no you won't be able. I've tried Tabooney, Honeyvillain, Virtuous Picasso, Virtuous Galaxy. ROM developers usually update their ROMs to the latest base available. I think it depends on many things - base, kernel, stock apps removed etc.
Maybe someone who have succeeded with custom ROM updating would share his experience.
Can anyone tell me if there is a version of ROM manager that supports the version of CWM that there is for the Iconia. I would love to be able to simplify my ability to backup my ROM's before flashing.
synapses11 said:
Can anyone tell me if there is a version of ROM manager that supports the version of CWM that there is for the Iconia. I would love to be able to simplify my ability to backup my ROM's before flashing.
Click to expand...
Click to collapse
You can install a clockworkmod for Iconia no matter of the version of ROM manager. But it is much much easier to use Acer Recovery Installer. I recommend you using it instead of playing with recovery img files. It is a one time procedure after all
Anyway - here's what you need to do if you don't want to use Acer recovery installer, or you don't want to use ADB:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
instead of CWM 3.x you will need to get CWM from thor2002ro In this guide you substitute the recovery that ROM Manager is about to flash with thor's CWM. I haven't tried this method myself but it should work.
With Acer Recovery Installer you can flash custom recovery as well. As long as you have it in IMG format you can be flashed from within the app - "install custom or stock recovery image from sd card".
great thread.
thanks!!!
Great Tutorial!!!
Just a couple of doubts:
First question: Backup files.
3. Flashing custom ROM
"...Before going on to install your ROM do a full backup of your system first. Navigate to "backup and restore" and then select Full Backup. Wait untill the operation completes. "
Where do the backup files go in the system? On internal or external SD card? Is it an *.img file extension?
Should i move it to my computer to keep it save, or just leave it where ever they are?
Second question: Kernel.
4. Flashing custom KERNEL
"Flashing custom kernel is as same as custom ROM. You place the zip (Kernels come in zip files as well) on your external SD card and:
- Install zip from sdcard -> choose zip from sdcard.
It is recommended before flashing a new kernel to wipe cache partition and dalvik cache. And of course first you flash the ROM and then the desired Kernel"
I am on Stock 3.1 ROM with original Kernel, if i want to try Virtuos Picasso, do i have to flash a new Kernel? And if yes, shouldn't i do it before flashing the ROM? Or just flash the ROM and then the Kernel? What happens if i just flash the Rom and use the stock kernel?
Thank you..
Your backup goes to your external SD card in a folder named clockworkmod\backup\2011-XX-XX.HH.MM.SS
As you can guess the name of the backup corresponds to the time it is created. This backup can be used to restore your system through CWM in case of need.
CWM does not backup /data/media folder. Additionally: you should also delete .android_secure.img from your backup set or a full restore will fail before it restores flexrom.
The last is an issue described by Euclid's brother:
http://forum.xda-developers.com/showpost.php?p=16467191&postcount=3
I am on Stock 3.1 ROM with original Kernel, if i want to try Virtuos Picasso, do i have to flash a new Kernel?
Click to expand...
Click to collapse
No, of course! Your custom ROM (Virtuous Picasso in your example) and any ROM comes with its Kernel. Its up to you to decide wheather to change it or not after that by flashing another Kernel. Follow every Kernel developer's notes for ROM compatibility. So, that answers the last part of your question - you cannot flash Virtuous Picasso and still think you're on stock kernel
drkalo said:
No, of course! Your custom ROM (Virtuous Picasso in your example) and any ROM comes with its Kernel. Its up to you to decide wheather to change it or not after that by flashing another Kernel. Follow every Kernel developer's notes for ROM compatibility. So, that answers the last part of your question - you cannot flash Virtuous Picasso and still think you're on stock kernel
Click to expand...
Click to collapse
Oh, i see...i thought that the flashing ROM procedure of a custom ROM, would just flash the ROM and not the Kernel...so in this case i just have to choose the ROM that i want to flash and do not have to pay attention about the Kernel compatibility...unless i flash a Kernel only. Right?
Thank you very much!!
That is correct

[Q] Help with Defy (green lens) and custom ROMS

I am currently on a stock Android 2.1-update1 TMobile US ROM on my Defy (green lens) ROM. I would like to try out CyanogenMod 7.1 (or 7.2 RC) and need help confirming my understanding of the process. I am already rooted and have installed the GoAPK recovery.
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade).
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
I've searched and read as much as I can, I feel like I "got it" but I just wanted a little confirmation before I start hacking this phone apart =)
Thanks for any help you can give me =)
Here is the explanation from all that I know:
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade). Ya, that is true. But after flashing fixed SBF you also need Nandroid backup to be restored.(This is not your nandroid backup. Its the nandroid backup supplied with the fixed sbf)
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
Yes Nandroid backup is always recommended. Superoneclick is a software needed to root your phone. That answers the rest.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
Yes, however its not update.zip but its <ROM NAME>.zip Your contacts,calender can be backed up in your google account and if you use gapps(google apps. Needs to be installed separately by install .zip in CM) in your CM those will come again. Your installed apps and data yes can be restored from TB. You can backup SMS using SMS backup+
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
Yes either that or you can even directly flash CM9 for Froyo kernel.
Hope that helps...

[Q] Some help for a nub and ICS + Flashing ROM

Got ICS, OTA (download) installed that no problem, downloaded the acer usb drivers and used ICS Root (blackthund3r). Now i want to install LightSpeed 4.4 (i know theres a newer version) I renamed it update.zip and did the power button + V- button but it says invalid image.
Now im a bit confused cause all this android stuff is new to me, I have the acer recovery installed but im not sure what to do with it. Tried renaming it to recovery.img it says it is flashing but nothing happens.
Kinda lost at what to do or how to get this rom working.... if someone could point me in the right direction it would be sweet
Fox
foxorroxors said:
I renamed it update.zip and did the power button + V- button but it says invalid image.
Fox
Click to expand...
Click to collapse
Yep. That was pretty n00b of ya (that little trick only works on signed official roms, and even then, only ify-ify)
Check this thread. It has the tools you need.
http://forum.xda-developers.com/showthread.php?t=1622425
You can skip the part about installing an ICS rom and rooting. You already did that. You need to do steps 1, 2, (partial 4) 5 or 6 basically.
Note after you rooted. Look at step 4 and delete the required file like it says, before going to steps 5 or 6. You have an option on which package to use. Personally, I like the exe package. But your choice.
This installs patched b-loader and CWM recovery so you can flash ICS only Roms.
Easy
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
urbie47 said:
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
Click to expand...
Click to collapse
Acer recovery is fine if it'll install the patched Bootloader.
However, it doesn't make a user get his UID number, which is essential in case something happens in the future. Without your UID, you're basically toasted Or you're in for the long haul in figuring out how to unbrick a tab.
help
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
ores992 said:
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Moscow Desire said:
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Click to expand...
Click to collapse
Thanks, but that link is dead
ores992 said:
Thanks, but that link is dead
Click to expand...
Click to collapse
Yeah, XDA did some cleaning up overnight. Try it now;
http://forum.xda-developers.com/showthread.php?t=1622425
MD

[q] is there twrp recovery for mortorola bravo?

in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries

Huawei Ideos ROM Help

Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.
Bump for @Blefish
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Thanks for answering. You are the foremost expert on the u8800 that I know of.
Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.
Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery
I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.
After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.

Categories

Resources