Okay, so I finally decided that ICS wasn't enough for me any more, and that I needed to go with a custom ROM. Unfortunately, it seems most tutorials for the A500 were created over a year ago, and they were full of broken links and information that wasn't relevant. So, I combined a few different tutorials and was pumped when I got Cyanogenmod up and running, and then heartbroken when it started giving me some message about cyanogenmod.account stopping working. Threads on XDA suggested a reflash, and I did so, and now I have even worse problems.
The same ROM when flashed takes me to the Cyanogenmod load screen and stays there for seemingly forever (left it for 20 min before moving on). I tried flashing another Cyanogenmod ROM and it won't go past the custom bootloader's startup screen.
Now, I am very new to this, and if I've been a total noob, let me know where I went wrong.
-I rooted my tab months ago, using an .exe I downloaded that did most of the work for me.
-I installed a custom recovery/unlocked bootloader (V8-Thor 1.7.3) which works wonderfully, lots of nice features.
-Then flashed an unofficial Cyanogenmod 10.2 ROM with some GApps according to instructions from this guide (http://forum.xda-developers.com/showthread.php?t=1622425)
-tried just about everything I can think of short of asking for help, so that's why I'm here.
Please let me know if I've missed something, or if you need any more information, I'm looking to get this working, and just generally much around with my tab (maybe try and run ubuntu, or other roms, but I'd REALLY like to CM 10.2 running first).
I'm putting my tabs future in your hands, please help me!
Related
My son and his girlfriend have a vega each, however they seem to be both rather unwell after a hasty attempted flash by him, (I know we'd all have stopped at one ). However that's my situation.
I have all the tools and drivers and roms, when they initially both them they were flashed with r8 custom rom from modaco.
He has attempted to flash them both with the new vegacomb rom using the rom manager app, all seemed fine I'm told all prgress bars 100%, on re-boot though they failed into a blank screen.
I have attempted to re-flash (with nvflash) them but I get diferent errors each time from bootloader fails to recovery fails (yes i tried the stock rom from the vega home page, along with many other roms). Any help would be most gratefully accepted
More Info
http://android.modaco.com/topic/345...icked-vegas/page__gopid__1782997#entry1782997
Just to keep a tidy thread I have linked the responses from modaco
Hi there, taken a quick look through the responses over at modaco. I would start totally from scratch. Re-install the usb drivers from the advent webstite. Re-download the stock rom from the advent site (to make sure yours is not corrupt) and flash it. Looks like you have the procedure sorted, so it must be down to the drivers or the rom image. To have the only 2 bricked vegas in existence would be the worst luck ever!
Good Luck
make sure they are charged, it won't do an nv flash if it's not charged past 60%, something I stumbled with for a few days till i left it to charge overnight before flashing
and a slap at the back of your son's head will work well as well.
Edit - should of read the modaco thread first - fixed with a new lead
the newest honeycomb roms need a modified base rom:
http://tabletroms.com/forums/vega-r...ddedstock_1-10-v2-updated-stock-rom-base.html
Then you can apply latest vegacomb using clockwork mod recovery (factory reset and clear dalvik cache in cwm before applying the roms just to be belt and braces):
http://tabletroms.com/forums/vega-rom-development/1923-[rom]-[3-2]-vegacomb-3-2-build-6-a.html
As above make sure USB drivers are installed correctly and Vega has mains plugged in while doing all the flash work.
Not heard of a bricked Vega only physical breakages.
Good luck
Hey.
I'm having difficulties with new cyanogenmod 7.1
I Followed different tutorials and none of them helped me.
I started with stock 2.1 rom and did all the unlocking bootlader stuff , then installed custom kernel and managed to install cyanogenmod 7.1 but then occurred a funny thing . There was only FreeXperia logo showing up, nothing else, and it rebooted all the time. Then I flashed stock rom again and tried to understand what's wrong and tried to use different kernels and nothing.
So my question is. Is there anything I'm missing here?
Henri.
Full wipe after you install rom.
Dot forget to make backups first.
about that...
i always do full wipe after installing roms, so it has to be something else.
Thnks anyway..
But after browsing several topics in XDA forum I saw that I'm not only one with the problem.
If anybody has had the problems like I do and got the solutions, every kind of tips are welcome.
Thread closed
I got it all working, but I don't know what was the reason, because, I just did the whole thing again about three or four times, and then it just booted and worked.
I never could install Cyanogenmod in my phone... could you?
Hey!!!
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Does wifi and/or 3G work for you longer then 15 minutes?
No, but at the moment I'm using RC1 flawlessly.
Sent from my E15i using XDA App
coffee-break said:
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Click to expand...
Click to collapse
umm..why not post it publicly man ? It will be useful for everyone including myself.
Would also like that tutorial
ok,
i'm gonna post it here after finishing it.
So, the wanted tutorial is here!
Firstly it's for xperia x8(E15i) to be superclear.
I'm gonna put that tutorial into steps.
STEP 1
You need to have stock 2.1 rom with baseband XXX015 , if you don't have it, then go to Sony Ericsson's webpage and download the upload service and flash it back into your phone.
STEP 2
You phone has to be rooted. Easieset way is using Superoneclick(sorry, i'm not gonna provide the link, because it's just google-ing thing to you who need rooting program)
STEP 3
Now, everything comes to the unlocking process for bootloader. there is also tutorial how to succeed when using s1tool and msm7227 (if you have problem, then I don't know). Try to undestand the tutorial of doing it.
S1tool is for identifying if your phone is unlocked or not.
and msm7227 is for unlocking
tut is here - LINK
I wish luck, don't brick your phone, but it's not so hard to understand tutorials if you have right phone and right tutorial.
STEP 4
I totally suggest to install stable rom. The reason is that released 7.1 has bugs and incompatibility with some phones and i haven't got wifi and 3g working , but tried different roms and kernels.
I provide links i got from deani77, big thanks to him.
You can try this link for FXP028 ROM - http://www.multiupload.com/IIWIPG1ALH
For FXP030 kernel try this link - http://hotfile.com/dl/132650338/7b17...USTOM.ftf.html
(that release is RC1 of Cyanogenmod 7.1 but I think it's the best at the moment!)
and you download all the files as usual. Rom zip package should be in the SD card's root folder, so you can easily install it after flashing kernel
STEP 5
installing is quite simple actually. You need to use flashtool that is provided with rom(link in step 3)
firstly you flash kernel. Kernel file is the one you downloaded .ftf file. You have to put that file(X8_custom.ftf) into firmware folder which is inside of flashtool folder.
Then you open flash tool and you click FLASH, then appears little window and you click ok and then you need to plug in your phone into usb while holding down back button. Your phone has to be off when you are doing that. Then flashtool identifies your phone and will flash the kernel into your phone. when everything comes smooth then you now have fxp custom kernel. it has clockworkmod recovery and you need to click several times back button when FreeXperia logo appears.
STEP 6
You have to do factory reset and format, also i suggest from advanced menu using format system.
Then you select from the recovery menu install custom zip... and you browse your rom .zip file and if everything is OK then it should display "installing update or smth" if it's done then good for you, you reboot and it should work.
IF YOU WANT GOOGLE APPS , then google the link and install it same way you did with the rom. You can do it any time.
..
So if anything is not understandable then ask. I'm not an expert or anything, I just did things like I described.
Best,
Henri.
i have still had problems with bootloop and passing md5 checksum any idea on how to fix this?
mm.. at the moment I don't know but what that md5 checksum means?
I fixed my bootloop issue when I flashed back to stock rom, then I just did all the steps I describe again (not unlocking bootloader because it was unlocked already) .. but I don't know what's really does the bootlooping thing. I just got lucky. It took me like billion hours until I got it working...
Hello...
I've spent about a good week and a half trying to root and install ICS on the A500 at where I work. My goal is to get ICS or higher on this device so that it can be used for testing purposes. I was able to root and install CWM but have not been able to flash ICS or JB. Am hoping you guys can point me in the right direction.
I have tried to flash cm-10-20121027-UNOFFICIAL-a500.zip and cm-9-20121221-NIGHTLY-a500.zip but what I get in both cases is my device hanging on the Acer logo. My last attempt I left the device like that over the weekend and this morning it was still displaying the logo.
The CM9 nightly wouldn't install at first until I came across a post that said to remove the first line of the install script, which I did, and the install seemed to happen but as I mentioned the device hung up at the Acer logo.
No idea how to move forward here... there are hundreds of posts and updates on the topic but quite frankly there are terms that I've never heard of, all sorts of caveats, specific recoveries that need to be used, dead links, etc... am making no progress.
I do have a backup up of HC, so am able to revert easily via CWM.
Current Android is 3.2.1, build is Acer_A500_7.014.02_COM_GEN2
@eyepoker..... I honestly don't see where your problem is provided you are prepared to load a custom ICS rom from any of the Developers in thread #3. Without picking out a favorite I would suggest any of "Civatos" FLEXxxxx ..... SHELLshock..... roms will give you a highly customized ICS Rom.
Be aware that you will have to load first an ICS Bootloader..... you cannot run these custom roms on a HC Bootloader, but in "Civatos" posts there are links to tutorials on how to do this.
The issue is that i can't flash a rom, it doesn't work. The device hangs with the Acer logo displayed and advances no farther after a flash and reboot.
Should my take away be that the latest CM nightly and the unofficial don't work? Should i not bother with CM? Is ClockworkMod old now - is there something else I should be looking for?
I'll look at the bootloader stuff you mentioned.
@eyepoker..... With respect you know your tab better than I, however unless you have bricked it (you don't say it is nor does anything you say about it suggest that is the case) then there is no earthly reason why you cannot load a ICS rom onto it. Now I am not going to say that there is a problem with the NIGHTLY updates of CM roms but is it possible that an app that you have previously installed is causing a problem with CM?
To prove to yourself that your tab can run ICS why don't you try the following.....
1) Follow the instructions in Civato's thread to load an unlocked ICS Bootloader..... I would recommend "v.8"
2) Download one of his ShellShock or Flex roms and put the zip file onto your External SD card - DON'T unzip the file leave it in it's zipped state.
3) Boot into CWM Recovery - do the necessary "wipes"
4) From within CWM install the zip from your SD Card
I am quite certain that the rom will install.
If the above doesn't work then I think there is far more wrong with your tab than it being unable to flash a rom.
I'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...
Sooo, I'm new to rooting a note 4. I have the the international version, rooting is no issue now... I can do that quite quickly.
My issue is flashing a new from via TWRP. No matter what I do it fails everything, last night I managed to load CM12 but it just stayed in a bootloop for over 30minutes. I just restored it to factory. I thought maybe I'm not destined to have cyanageonmod
Anyways I found another decent room called Beanstalk, it seems like a pretty solid room (thoughts?) but when I go to flash the zip file it just says it can't mouth the file from what ever drive.
What am I doing wrong? I wiping the four things I'm meant to delete before I flash and still nothing
My phone: N910F running on 5.0.1
Baseband:n910fxxuibob4
Ive looked at ever forum possible but can't see what's wrong? I've also tried 3 different versions of Cm12 from different developers that are meant to work...
So again where am I going wrong?
If this is in the wrong place I am sorry! Could I be pointed in the right direction
did you follow instructions for installing and what to do after installing the roms?
xdm9mm said:
did you follow instructions for installing and what to do after installing the roms?
Click to expand...
Click to collapse
Yes followed the instructions like I was doing brain surgery! After... With CM12 it booted up and just kept going around in circles or about an hour, I left it because I thought I needed to, I have up an reverted back. With beanstalk I just got a message in TWRP saying failed to mount on e:/ or something like that.
Anyone have a clue what in doing wrong? I'm going crazy not being able to flash anything. Even a stable build of something. I'm 100% sure what I've downloaded is compatible but still nothing. Either bootlooping or having mount issues.
(bumps are probably not allowed but I've been trying this for 3 days and I'm not where)