Related
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
I'm trying to use Rom Manager to search for Rom updates.
When i click search for updates it says i must have Clockworkmod recovery installed and when i press install it says please confirm model but Xperia play isn't on the list.
I am on official CM7 android 2.3.7 thanks
Sent from my R800i using XDA Premium App
The Xperia play is not on the list, I think this is due to it still being in development and not "stable". As for now you must do the update with the CWM recovery and install or update from zip
Even if it was official, you can't update with ROM Manager alone, since the kernel has to be updated with Fastboot.
Logseman said:
Even if it was official, you can't update with ROM Manager alone, since the kernel has to be updated with Fastboot.
Click to expand...
Click to collapse
with the latest release you can flash a new rom with the update with out fastboot, I am now able to boot into recovery with out an issue.
And how do you flash the updated kernel? There is no recovery partition, it's embedded there. You can't access the kernel from the recovery because it's the same partition.
As logseman said, Rom manager will never work on the xperia play. Unlike other devices, the xperia range has no dedicated recovery partition. Recovery is held on the boot partition, the same partition as the kernel.
As you know when you flash a partition the said partition is formatted in the process. This means flashing a recovery image would format boot partition and erase the kernel. And flashing a kernel would do the same and erase recovery. This is why recovery needs to be embedded in the kernel
Sent from my R800i using Tapatalk
linkthanks go to mioze7Ae/brianlili/mchlbenner/J.Y.Daddy/fifalcon.
Please give feedback.
P.S. THIS SBF NOT MEANT TO BOOT.
download OR.rar and apply it first its your open recovery make sure you move your updates to it.
delete your present open recovery or move off main sdcard.
xt720mod sbf. it will not work on cm6.
this has up to 250 mb internal storage depending what rom your using. this sbf doest boot use it to get to open recovery.
how to get to recovery simple go to moto stock recovery and click update.zip it will take you to open recovery.
their a bootfix for cm7 ours.
their a bootfix for JY.Daddys cm7 and miui ics.
let me know if links don't work or any other problem.
DONT FLASH SBF FIRST.
yesterday i spent about 6 hour with bravo trying to get a sensor fix but did not I will trying to get a fix for all
I have been running this for a few weeks and it is great. The recovery is what the Milestone A853 people call a "vulnerable recovery". This means that the Motorola stock recovery in the sbf has a security vulnerability--it does *not* check that update.zip has been signed by Motorola before applying it (on all the others it does check that). Also like mchlbenner says, the /data partition is much larger (256mb)--actual amount free after boot will depend on the ROM's configuration. To reiterate the wonkyness:
You MUST prepare your sdcard with the OpenRecovery before flashing (or you will be forced to put your sdcard in a computer). You must have /sdcard/update.zip from OR.rar and an update or nandroid to apply.
After you flash the sbf, it will not boot anything except Motorola stock recovery until you get into OpenRecovery (from stock recovery) and flash a ROM.
The rotation sensor is somehow rotated by 90 degrees. mchlbenner's bootfixes fix that for Gingerbread ROMs. We don't have a fix for eclair or froyo (yet?).
Hi could you post link to xt720mod sbf mine will not work.
I flashed clockwork mod and it worked!
Sent from my XT720 using xda premium
mchlbenner said:
Hi could you post link to xt720mod sbf mine will not work.
Click to expand...
Click to collapse
http://www.multiupload.com/4I3FIFTD68
Mioze7Ae said:
I have been running this for a few weeks and it is great. The recovery is what the Milestone A853 people call a "vulnerable recovery". This means that the Motorola stock recovery in the sbf has a security vulnerability--it does *not* check that update.zip has been signed by Motorola before applying it (on all the others it does check that). Also like mchlbenner says, the /data partition is much larger (256mb)--actual amount free after boot will depend on the ROM's configuration. To reiterate the wonkyness:
You MUST prepare your sdcard with the OpenRecovery before flashing (or you will be forced to put your sdcard in a computer). You must have /sdcard/update.zip from OR.rar and an update or nandroid to apply.
After you flash the sbf, it will not boot anything except Motorola stock recovery until you get into OpenRecovery (from stock recovery) and flash a ROM.
The rotation sensor is somehow rotated by 90 degrees. mchlbenner's bootfixes fix that for Gingerbread ROMs. We don't have a fix for eclair or froyo (yet?).
Click to expand...
Click to collapse
So, I'm a bit confused on what all this means. I understand the part about the /data partition being larger, but is that at the expense of the /cache partition? Also, as I understand it the Clockwork Mod is the equivalent of AOR, is this correct? What is the benefit of CWM vs AOR?
thejaycan said:
So, I'm a bit confused on what all this means. I understand the part about the /data partition being larger, but is that at the expense of the /cache partition?
Click to expand...
Click to collapse
Both the /system and /cache partitions are slightly smaller (the partition layout is the same as the Motoroi 50R froyo sbf, but this uses a Milestone XT720 kernel instead of a Motoroi kernel). The other implication is that if you are running this sbf, you will always be able to enter OR (assuming you have a valid sdcard). With other sbf's if you do something to make your system unbootable and you can't re-enter OpenRecovery, your *only* option is to flash sbf. In other words, a bootstrap recovery is not needed with this sbf.
Also, as I understand it the Clockwork Mod is the equivalent of AOR, is this correct? What is the benefit of CWM vs AOR?
Click to expand...
Click to collapse
I have not tried the clockworkmod. Mostly because I haven't had time to study it, but I have studied AOR. So for me at least it's more of a devil-I-know sort of thing at the moment.
Hi
I'm using clockwork mod and I'm using minimod recovery I prefer are recovery.
Rom manager is oka but if you flash cm7 with it you only have edge not 3g I could not fix this issue yet.
I would recommend to stay with are open recovery for know.
Sent from my XT720 using xda premium
I Know this is prob a stupid question... But are there any performance increases with this? or just more space? and always be able to get into OR?
The answer is yes less on sdcard will help with performance that's my opion.
I personal have got better performance on this sbf.
Sent from my XT720 using xda premium
Are there plans for a froyo fix ? I saw MZ say (YET?) lol
The plan is it to get it work on cm6 and eclair but I have searching for this fix but I not found it yet their must be a fix will find it.
Sent from my XT720 using xda premium
HI.
First off all, thanx for this.
SBF is installed, and flashed with J.Y.Daddy CM 7.1.1 with bootfix.
I'm actually restoring all my apps, will let you know if it's good or not.
---------- Post added at 12:59 PM ---------- Previous post was at 12:06 PM ----------
Just for the fun, and because it's not really simple, here is the way to use this SBF.
Prepare you're SDCARD:
Copy the content of AO.rar from the first post to your sdcard
be sure to get a valid rom update in your sdcard/OpenRecovery/updates directory.
(I personnaly used CM 7.1.1 from J.Y.Daddy)
Flash your phone:
Boot your phone in flash mode (power + cam key)
Flash your phone using rsd lite and the xt720-2.1-mod.sbf file
After succesfull flash, restart your phone by pressing Power key + Camera Key + GalleryKey to bring up the recovery screen.
Don't wait for your phone to boot! This SBF can't!
When the Triangle/Exclamation point screen appears, press Volume Up + Gallery Key down and tap the camera key to show the recovery menu.
Apply the update.zip to get the OpenRecovery menu
Apply your ROM update
Apply the fix for your rom provided in the first post
Wipe data / cache / dalvik
Reboot
Enjoy.
I m flashing it for the third time and it don t boot after the rsdlite flash....
It stay with the motorola logo for a long long time (i m waiting for about 10minutes now...)
Anyone had this problem? I think i m gonna try to go to the moto recovery without waiting for the first boot
edit it works without waiting for the first boot... Sorry
B_e_n said:
I m flashing it for the third time and it don t boot after the rsdlite flash....
It stay with the motorola logo for a long long time (i m waiting for about 10minutes now...)
Anyone had this problem? I think i m gonna try to go to the moto recovery without waiting for the first boot
edit it works without waiting for the first boot... Sorry
Click to expand...
Click to collapse
thats whats supposed to happen isnt it? you have to go straight to moto recovery, select update.zip. and that will bring u to the custom AOR, and from there, u can flash the rom that u want, and apply the bootfix.
That's normal. This SBF can't boot!
You have to remove your battery and restart your phone by pressing Power key + Camera Key + GalleryKey to bring up the recovery screen.
Then you just need to follow my previous post.
Sorry I m so tired this days.....
Hi mchlbenner... nice to finally see something from you (not forgetting the help from the other devs). this modded sbf thing is really cool, hope to see more improvements, it would be awesome if there were fixes for the simpler roms (2.1 and 2.2)! keep the good work up!
I hope to find a fix cm6 and 2.1.
Not to long ago we did not have many choices at all and now we have a ton choices.
Sent from my XT720 using xda premium
can you post the kernel cmdline?
/proc/cmdline
trying to slide the above onscreen
peshovec said:
can you post the kernel cmdline?
/proc/cmdline
Click to expand...
Click to collapse
console=ttyS2,115200n8 console=ttyMTD10 rw [email protected] init=/init ip=off brdrev=P3_TABLET_SKT androidboot.bootloader=0x0000 mtdparts=omap2-nand.0:[email protected](pds),[email protected](cid),[email protected](logo),384k(misc),3584k(boot)ro,[email protected](recovery),8960k(cdrom),[email protected](system),[email protected](cache),265344k(userdata),1536k(cust),[email protected](kpanic)
The boot.img is identical to the one in the UK and Central Europe SBFs:
eff22955e8e91eb19545a3af39973934 xt720-2.1-mod/CG35.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
uname: Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
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.
@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot
Cool, what ROMs did you test this on ?
OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp
funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.
funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?
Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.