Hello! I was looking for some help with flashing ROMs. I have had my A700 flashed with other ROMs before like CM and IconiaN, but for some reason, now it will only boot the stock ROM. I had CM11 on it and decided to go back to IconiaN. Well, it wouldn't boot. To try and fix this, I went back to full stock ICS with a locked bootloader and stock recovery and started from scratch. I've tried about 4 or 5 times, unlcking the bootloader and flashing CWM, but every time I try to flash anything other than an official update.zip in CWM, it just hangs at the splash screen with the animated Acer logo. I did have TWRP for awhile too, but I had CWM originally and I have it now. Thanks!
Dark_Spark said:
Hello! I was looking for some help with flashing ROMs. I have had my A700 flashed with other ROMs before like CM and IconiaN, but for some reason, now it will only boot the stock ROM. I had CM11 on it and decided to go back to IconiaN. Well, it wouldn't boot. To try and fix this, I went back to full stock ICS with a locked bootloader and stock recovery and started from scratch. I've tried about 4 or 5 times, unlcking the bootloader and flashing CWM, but every time I try to flash anything other than an official update.zip in CWM, it just hangs at the splash screen with the animated Acer logo. I did have TWRP for awhile too, but I had CWM originally and I have it now. Thanks!
Click to expand...
Click to collapse
Hey guys! Nevermind! I went back to stock again and tried another ROM first before I tried IconiaN, and it booted! So I guess it was just the .zip of IconiaN I have. Weird too because I re-downloaded the .zip. Anyway, I'm good now!
Related
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
I finally fixed my old issue... (softbrick stuck at boot logo without access to fastboot)
now i have a new one.
Im using TWRP recovery right now, and it seems the only ROM i can install right now is Clean ROM.
I have tried Blackbean, CM10 nightly, and HYDRO.
None boot up.
Is there something that is unique to CleanROM that would let me install it and not others?
confuz said:
I finally fixed my old issue... (softbrick stuck at boot logo without access to fastboot)
now i have a new one.
Im using TWRP recovery right now, and it seems the only ROM i can install right now is Clean ROM.
I have tried Blackbean, CM10 nightly, and HYDRO.
None boot up.
Is there something that is unique to CleanROM that would let me install it and not others?
Click to expand...
Click to collapse
You are on JB, so the only Roms you can flash are [email protected], Clean and Hydro JB. Thats it. All other Roms are only flashable with ICS bootloader and you are not able to get back from JB:
I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?
This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2
I had to revert back to 4.2.1 stock rom, after bricking my tablet. I flashed twrp 2.8.7. And it boots to recovery fine. However when I try to install a new rom, it flashes an goes back to the team win splash screen without installing. Also tried super su without success.
This was happening befor flashing the Asus stock blob. I thought it would fix twrp recovery by reinstalling. The stock recovery also showed a dead android and wouldn't boot into recovery. Twrp seems to work until I try an install.
Any ideas on how to fix Twrp to install a custom rom and root.??
Any help would be much appreciated. Tablet is currently working with stock 4.2.1 rom.
Rgbrewser said:
I had to revert back to 4.2.1 stock rom, after bricking my tablet. I flashed twrp 2.8.7. And it boots to recovery fine. However when I try to install a new rom, it flashes an goes back to the team win splash screen without installing. Also tried super su without success.
This was happening befor flashing the Asus stock blob. I thought it would fix twrp recovery by reinstalling. The stock recovery also showed a dead android and wouldn't boot into recovery. Twrp seems to work until I try an install.
Any ideas on how to fix Twrp to install a custom rom and root.??
Any help would be much appreciated. Tablet is currently working with stock 4.2.1 rom.
Click to expand...
Click to collapse
I tried myself to get the latest TWRP 2.8.7 without getting it to install. I have heard to use 2.8.6.5. I can not even get that installed. Not sure what else to try.
Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please