CM7***new BETA Release*** - Atrix 4G General

I figured I would make this thread to consolidate ALL CM7 info for the Atrix instead of a thousand threads about the different releases. If a mod could sticky this for me that way we can keep people from starting a thousand threads, I'd really appreciate it. Anywho, here are the links.
***UPDATE***09/13/11 9:00 p.m. EST. ***The beta release is UP! Download here https://code.google.com/p/atrix-dev-team/downloads/list
Also, for all those who DON'T know, make sure you flash the ROMMANAGER version of CWM on your phone before attempting to flash this. It needs it for the ext-4 support that only that provides. If you don't or can't, flash this recovery image with fastboot. https://atrix-dev-team.googlecode.com/files/recovery-cwm-ext4.img
use this command:
fastboot flash recovery recovery-cwm-ext4.img
GAPPS---latest version for CM7--scroll down a little and the download link is there, figured I would link to the page containing instructions
http://android.modaco.com/topic/335141-addoncm7-updated-more-google-apps-2011-08-15/
**NEW update 11:20 P.M. 9/8/11** The kernel I had posted here people are saying is not compatible with this prebeta of CM7, so I took the link out. I'll just post the 1.9 version, the 1.3ghz overclock which is what I'm flashing right now. http://rootzwiki.com/showthread.php?1873-Kernel-Stock-FR-GB-CM7-2.6.32.xx-(Unified-v0.1.9)OC-1.3GHz-SLQB-BFQ-EXT4-Aug-27

**update**
Also, for those who don't know how to use fastboot, you can use moto-fastboot and it's easier if you don't quite get how to setup Fastboot or just don't want to bother. You can download moto-fastboot and unzip it to the root of your hard drive *so for windows users, the C: drive* and use that instead of fastboot. Download links for moto-fastboot on this page http://forum.xda-developers.com/showthread.php?t=1138092
**update**
For those having trouble with Google Apps--second way to do it is install CM7, go into ROM Manger and flash the latest CWM. Then click on Download ROM, and go to the bottom where it says "Google". Download the latest Google Apps version from August, and it will save it to your EXTERNAL SD card. Go into a file explorer (i use Root Explorer) and move it to the root of your INTERNAL sd card, then you can flash it with ROM Manager's CWM version.
**Update 9/9/11 8:25 AM** We now have a second choice when it comes to cameras! The MIUI camera app works GREAT on this prebeta build, you can download it from here http://forum.xda-developers.com/showthread.php?t=1244829
And also we have a working camcorder APP I tested myself, it does indeed record and save the video. It's a market app, check it out here
https://market.android.com/details?id=com.androidillusion.videocamillusion&feature=search_result

**update** 09/13/11 8:00 AM.** here's a link to get into the beta for Swype, thanks to Darkamikaze for posting the link on page 30 of this thread. http://beta.swype.com/

**Reserved**

ROM Manager's Recovery (5.0.2.0 - latest version as of this posting) was not properly wiping the system and boot partitions when installing new versions of the CM7 pre-betas. This gave me issues with FCs and random reboots, most of which were fixed by running "fix permissions" after installing a newer pre-beta over an old one. The issue was also present in the recovery you linked - which is actually ROM Manager's Recovery version 4.0.1.5.
There is an easy workaround though, manually wipe your phone with fastboot before installing a new ROM. This will ensure that your phone is clean and ready for a new ROM.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot reboot
This will wipe the system, boot, data, cache, and preinstall partitions, giving you a "clean slate" to start from.
After running these commands you can boot into recovery and flash a ROM.
EDIT: I suck at grammar this early in the morning.
DK

DeathKoil said:
ROM Manager's Recovery (5.0.2.0 - latest version as of this posting) was not properly wiping the system and boot partitions when installing new versions of the CM7 pre-betas. This gave me issues with FCs and random reboots, most of which were fixed by running "fix permissions" after installing a newer pre-beta over an old one. The issue was also present in the recovery you linked - which is actually ROM Manager's Recovery version 4.0.1.5.
There is an easy workaround though, manually wipe your phone with fastboot before installing a new ROM. This will ensure that your phone is clean and ready for a new ROM.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot reboot
This will wipe the system, boot, data, cache, and preinstall partitions, giving you a "clean slate" to start from.
After running these commands you can boot into recovery and flash a ROM.
EDIT: I suck at grammar this early in the morning.
DK
Click to expand...
Click to collapse
I did:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
and wiped cache & dalwik after installing the rom.
(Yours + webtop, just to make sure)
Installation was flawless.

I was running Alien #4 and RomRacer CWM. I did a fastboot -w twice, then factory reset through romracer, then wiped cache and dalvik, installed pre4, factory reset, wiped cache and dalvik and everything seems to be working great. I installed the old version of gapps by accident and then installed the new version through rom manager (which I had to flash the cwm from there first). Everything is working flawlessly so far.
Camcorder is coming.

Just a quick suggestion which may help keep everything in this thread. Maybe put the current Pre Beta build number in the thread title so those just hawking for the latest version know when it is released?
Thanks again to everyone working on this.

enomai said:
Just a quick suggestion which may help keep everything in this thread. Maybe put the current Pre Beta build number in the thread title so those just hawking for the latest version know when it is released?
Thanks again to everyone working on this.
Click to expand...
Click to collapse
Thread renamed. Thanks for the suggestion

Phalanx7621 said:
Thread renamed. Thanks for the suggestion
Click to expand...
Click to collapse
NP
I'm just gonna cross post this in here while this all gets organized:
Just flashed prebeta 4. Did factory reset, cache wipe, Dalvik wipe. No fastboot commands. Used Romracer's recovery. Booted fine. Flashed Faux123 v1.9 ~1.3 GHz CM7 kernel with no problems, tegrapart=1100 if that matters. Romracer's recovery still not detected by Rom Manager, not a big deal. Camera still works after kernel change.
Thanks again, devs.
Oh, and 4165 on first Quadrant, 4218 on second, 4277 on third.

Couldn't find the answer in the older threads...
Has anyone found a way to get the Motorola Entertainment Center working with CM7? Is it part of Webtop? If I install webtop from the other threads will it get this working?

CanEpia said:
Couldn't find the answer in the older threads...
Has anyone found a way to get the Motorola Entertainment Center working with CM7? Is it part of Webtop? If I install webtop from the other threads will it get this working?
Click to expand...
Click to collapse
I don't know. Wanna take a stab at it and let us know?

I was on pb3, wiped cache and dalvik then applied pb4.zip
Everything is perfect. Then updated to 1.9 kernel and everything is still perfect. Love it.
Sent from my MB860 using Tapatalk

enomai said:
NP
I'm just gonna cross post this in here while this all gets organized:
Just flashed prebeta 4. Did factory reset, cache wipe, Dalvik wipe. No fastboot commands. Used Romracer's recovery. Booted fine. Flashed Faux123 v1.9 ~1.3 GHz CM7 kernel with no problems, tegrapart=1100 if that matters. Romracer's recovery still not detected by Rom Manager, not a big deal. Camera still works after kernel change.
Thanks again, devs.
Oh, and 4165 on first Quadrant, 4218 on second, 4277 on third.
Click to expand...
Click to collapse
But the dock will not
Sent from my MB860 using XDA App

Figures, I switched from CM7 PB3 to Alien 4 yesterday and now CM7 PB4 comes out with working camera, which is why I flashed back to Alien 4 in the first place!! Ughhhh

after flashing..
My phone has been stuck on flashing stormgr partition: SOS for about 5 minutes? I'm not exactly sure what I'm supposed to do. its been awhile since I've had to use fastboot!

Can the first post be updated with a link to the kernel that comes packed with pb4? Thanks!

i just installed cm7, and titanium backup and rom manager are acting weird about the internal sd card not being mounted. anyway to fix it?

Joelesprod said:
i just installed cm7, and titanium backup and rom manager are acting weird about the internal sd card not being mounted. anyway to fix it?
Click to expand...
Click to collapse
Is your phone still plugged in to the USB on your computer? If so, unplug it

is not plugged into the computer, the internal sd appears on the file manager as emmc but for some reason some programs wont detect it
EDIT: Fix: settings>cyanogenmod settings>application settings> use internal storage

Related

Phone hangs on Dual core logo, need help

I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?
did you make a backup before installing the beta?
It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?
I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta
I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App
Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...
im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...

Solved:I guess I'm stuck in boot loop....now what?

Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!
Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.
1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium
Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!

[DEV/LEAK] ICS for A501

Got hands on an update for A501, but it's update only not a full package.
If someone is interested to build and then dump the full system (sorry don't have time to do it) :
1. Download this files :
http://cdn.acer.futuredial.com/Acer_A501_4.015.15_4.031.24_COM_GEN1_1315884879002_1b385af8.zip
http://cdn.acer.futuredial.com/Acer_A501_4.031.24_4.066.24_COM_GEN1_1323422721450_50889c0e.zip
http://cdn.acer.futuredial.com/Acer_A501_4.066.24_4.066.29_COM_GEN1_1323422673354_fb18aaff.zip
http://cdn.acer.futuredial.com/Acer_A501_4.066.29_041.126.01_COM_GEN1_1334565825911_78adda1e.zip
(You will have to decrypt packge to extract update.zip from them)
2. Wipe all with recovery
3. Install all packages in this order. (don't wipe between installs)
I may be able to provide a full dump this week-end if nobody did it.
Edit : Flashable (full) update : http://forum.xda-developers.com/showpost.php?p=25050248&postcount=38
Thanks Vache!
Thanks, I'll try to take the time to flash all this...
This implies that those of us who are on 4.066.24 need only force up to 4.066.29 and from there to the final version? It also implies that the software is out there for updating to the "real world" instead of just being leaks. Is this your understanding as well?
yeaaaa tnxxxx
vache said:
Got hands on an update for A501, but it's update only not a full package.
If someone is interested to build and then dump the full system (sorry don't have time to do it) :
1. Download this files :
http://cdn.acer.futuredial.com/Acer_A501_4.015.15_4.031.24_COM_GEN1_1315884879002_1b385af8.zip
http://cdn.acer.futuredial.com/Acer_A501_4.031.24_4.066.24_COM_GEN1_1323422721450_50889c0e.zip
http://cdn.acer.futuredial.com/Acer_A501_4.066.24_4.066.29_COM_GEN1_1323422673354_fb18aaff.zip
http://cdn.acer.futuredial.com/Acer_A501_4.066.29_041.126.01_COM_GEN1_1334565825911_78adda1e.zip
(You will have to decrypt packge to extract update.zip from them)
2. Wipe all with recovery
3. Install all packages in this order. (don't wipe between installs)
I may be able to provide a full dump this week-end if nobody did it.
Click to expand...
Click to collapse
Sweet! Will have to find a way to do this.
Thanks vache for the leak! Glad to see Acer has been working on ics for us a501 users.
Lets hope I get the 4g speeds.
Sent from my A501 using Tapatalk 2
Install OK.
Android 4.0.3
Acer_AV041_A501_0.001.00_WW_GEN1
3G works, SMS works.
This build number indicate it's a very early build but it works great, seems on par with the latest A500 leak.
Glad to see that Acer is finally working an our A501 !
installed all 4 OK after reboot it updates EBT and reboots again wiping out boot loader and recovery image.
Shows
Android Version 4.0.3
Baseband: Cust.R3C01 Config:R3S/3 Conf:R3C01 Protocol:R3B01 App:R3C01
Kernel: 2.6.39.4+
Image Version: Acer_AV041_A501_RV26RB01_WW_GEN1
Build Number: Acer_AV041_A501_0.001.00_WW_GEN1
3g initially did not work. I had to delete and recreate my APN for data to work.
Thanks Vache!
Now, I hope all of you are copying down your UID numbers before running the updates.
Will make things a whole lot easier if you need to roll back
What I also found is that if you try to go into recovery (vol down) it restores you back to Stock 3.2 HC Beware!
Also make sure you make a backup of all your stuff on internal SD card. the process will wipe it!!!!!
Thank you! Good)
There also apears to be something fishy with the update as well with the bootloader.
If you try to flash the custom bootloader with the thor recovery img each time it boots it appears to wipe the recovery image out and it wont go into recovery anymore after the first reboot and has to be flashed again? (shows dead android on its back with door open with red triangle)
http://forum.xda-developers.com/showthread.php?t=1594873
Not sure whats happening there however it does come up in RED after the PASS shows.
Secure Boot: Image LNX checksum fail.
Is there some funnyness locking happening with this update?
What am I doing wrong?
Update: I went back to back up of my prior ROM "DEV][AOSP] ICS sources and build instruction for A501" and it doesn't wipe out the recovery image. Is this because the boot-loader is specific to this ROM as it is for 4.0.4? Any ideas?
Wombat
wornbat said:
There also apears to be something fishy with the update as well with the bootloader.
If you try to flash the custom bootloader with the thor recovery img each time it boots it appears to wipe the recovery image out and it wont go into recovery anymore after the first reboot and has to be flashed again? (shows dead android on its back with door open with red triangle)
http://forum.xda-developers.com/showthread.php?t=1594873
Not sure whats happening there however it does come up in RED after the PASS shows.
Secure Boot: Image LNX checksum fail.
Is there some funnyness locking happening with this update?
What am I doing wrong?
Update: I went back to back up of my prior ROM "DEV][AOSP] ICS sources and build instruction for A501" and it doesn't wipe out the recovery image. Is this because the boot-loader is specific to this ROM as it is for 4.0.4? Any ideas?
Wombat
Click to expand...
Click to collapse
You have to root and remove /system/recovery-from-boot.p or it will reflash the recovery at every boot (assuming it's the same as the A500)
---------- Post added at 07:49 AM ---------- Previous post was at 07:48 AM ----------
Could anybody tell me if my ICS Root tool works with this leak? I don't have access to an A501 and I have no idea what version of the kernel this is running etc.
Thanks!
blackthund3r : ICS ROOT 5.1 works on this version. I chose to run it for the latest A500 leak and everything went just fine.
Mounting /system works too.
I tried wifi no work. Reflashing again :|
WiFi works for me, if you had a custom ROM you may have forgot to wipe something.
paugustin said:
WiFi works for me, if you had a custom ROM you may have forgot to wipe something.
Click to expand...
Click to collapse
1. install stock 3.0.1 rom
2. update to 3.2.1
3. make factory reset
4. go to recovery and flash this
5. wifi power on but no visible all wifi routers....
sometimes there are network. enter the password. all. again does not work.
OK it should work the way you did. One thing you can try is to install CWM, use it to wipe everything (factory, data, dalvik) and install from there. I know it can be done, I tested this.
Hope it will work for you too.
paugustin said:
OK it should work the way you did. One thing you can try is to install CWM, use it to wipe everything (factory, data, dalvik) and install from there. I know it can be done, I tested this.
Hope it will work for you too.
Click to expand...
Click to collapse
Tried same.
Damn sorry it doesn't work for you
Have you flashed 3.x using nvflash ? it usually does a good job of reseting everything. You can try this one : http://vache-android.com/v1/index.php?site=files&file=99

[Q] A500 hangs at booting primary kernel image

My Acer Iconia A500 was frozen, I turned it off by holding the power button, since then, I can not reboot the tab, it hangs at booting primary kernel image.
I have Skrilax_CZ V8 bootloader, CWM recovery 1.7.3, and the Flex-Resurrection_Rev1-Aroma-Public Rom.
-----------------------
I searched here, tried the methods by Moscow Desire
"Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media."
------------------------
And tried method by Skrilax_CZ
"You can also wipe userdata from fastboot: "fastboot erase userdata".
-----------------------
I did it several times, after installed the Flex Rom, ( I also tried the Lightspeed_4.8,) it still stuck on the booting primary kernel image, What should be my next step?
I saw somewhere Dibb_nz mentioned that re-flash the BL, recovery.img, not sure if I should try. I do have the CPUID and SBK numbers.
Thanks for your help, anyone out there.
I'm having the exact same problem. I tried what you did, and it still didn't work. This is my first time flashing, so I'm not sure what to try next. I do have one idea - I thought the ROM did have a kernal, so I didn't flash one. I'm going to search for one and try that.
I switched to Skrilax's V9 bootloader thinking that might help but it didn't. When I do a recovery with the back up of my normal rom I made before flashing then and only then can I get past the bootloader. The backup says there's an error when recovering my data though, so I'm going to have to start over from fresh either way.
Any help would be greatly appreciated. I've been at this for over 7 hours now.
Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4
dibb_nz said:
Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for replying. I went back to the normal ota rom from Acer, but will keep this in my notes if I try it again.

[Q] Can't remove multirom

I have a Nexus 7 WiFi 16GB running stock rooted and 2 custom roms via multiboot.
The custom roms stoped booting and now if you select any rom in multiboot it just boots the stock.
I tried to remove multirom (by reflashing boot.img to the device) and there were no errors but multirom remains.
I then thought I would reflash everything, bootloader, recovery, system the works. All of these processes reported 0 errors but the systems remains exactly the same.
I have also noticed that if I make any changes to the stock rom (install an app or change a setting) when the device restarts it's not there. It's as if the system isn't persistent.
Can anyone help???
Almost sounds like something in the file system got switched to read only.
What are you using to flash the device?
When I was playing with Multirom I think all I had to flash using Wug's was the stock kernel found under advanced options in order to remove multiboot.
The whole thing about making changes to the system that fail to persist is almost like root is borked or the bootloader is locked.
Does anyone know if its even possible to lock the bootloader once rooted?
KMDDesign said:
I have a Nexus 7 WiFi 16GB running stock rooted and 2 custom roms via multiboot.
The custom roms stoped booting and now if you select any rom in multiboot it just boots the stock.
I tried to remove multirom (by reflashing boot.img to the device) and there were no errors but multirom remains.
I then thought I would reflash everything, bootloader, recovery, system the works. All of these processes reported 0 errors but the systems remains exactly the same.
I have also noticed that if I make any changes to the stock rom (install an app or change a setting) when the device restarts it's not there. It's as if the system isn't persistent.
Can anyone help???
Click to expand...
Click to collapse
Did you read the OP?????
4. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Could've sworn there was an Q&A section
WooHooGuy said:
Almost sounds like something in the file system got switched to read only.
What are you using to flash the device?
When I was playing with Multirom I think all I had to flash using Wug's was the stock kernel found under advanced options in order to remove multiboot.
The whole thing about making changes to the system that fail to persist is almost like root is borked or the bootloader is locked.
Does anyone know if its even possible to lock the bootloader once rooted?
Click to expand...
Click to collapse
I have tryed flashing from commandline with fastboot as well as using both Wug's and Nexus7 Toolkit. I have tried flashing the stock kernel with Wug's and no change. The bootloader certainly says unlocked.
bonzer2u said:
Did you read the OP?????
4. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Click to expand...
Click to collapse
Tried that first
-PiLoT- said:
Could've sworn there was an Q&A section
Click to expand...
Click to collapse
Apologies, it was late, I was flustrated and I didn't see... if I knew how to move it I would.
I had the same problem trying to remove multirom, it just wouldn't budge!! I found the best way was to just erase everything on the tablet with fastboot commands and then just re-flash a stock image of Jellybean.
There's nothing like dusting off the old cobwebs once in a while to get that out of the box feel again!
Sent from my all singing and dancing Nexus 7 using xda app-developers app
mr_tris said:
I had the same problem trying to remove multirom, it just wouldn't budge!! I found the best way was to just erase everything on the tablet with fastboot commands and then just re-flash a stock image of Jellybean.
There's nothing like dusting off the old cobwebs once in a while to get that out of the box feel again!
Sent from my all singing and dancing Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Exactly what im trying to do.
I have ran:
fastboot erase system
fastboot erase userdata
fastboot erase cache
all with no errors but nothing was actually erased?!?
Start again but follow it in this order. But you also need to flash a stock ROM too. Your only doing half a job.
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update stockromfilename.zip
Sent from my Nexus 7 using xda app-developers app

Categories

Resources