Database Info

Unlocked, now can't install kexec roms?

I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\

confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems

Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.

lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?

confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?

PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)

confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.

lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?

confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.

confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.

droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?

PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.

newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.

If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question

synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?

after unlocking phone wont boot

after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?

flameinthefire said:
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
Click to expand...
Click to collapse
Sounds like an bootloop, just odin back to stock and try again.

If you remove the battery and turn it back on, will it boot into recovery?

power+vol up+home button

Karl said:
power+vol up+home button
Click to expand...
Click to collapse
yes it turns back on but i have unlocked it and its on twp recovery which rom would work with it?

i tried flashing mr beans rom that didnt work beacuse i am on twp recovery and i tried flashing synergy rom that didnt work either so wat should i do. since i unlocked the phone can i still do odin? or will that brick my phone

guys please help!

flameinthefire said:
guys please help!
Click to expand...
Click to collapse
is there any rom that i can use for my unlocked s3

flameinthefire said:
guys please help!
Click to expand...
Click to collapse
Someone already told you what to do. Find a stock ROM, boot up Odin and flash.

the roms you tried work with TWRP... ive used TWRP since release

Karl said:
the roms you tried work with TWRP... ive used TWRP since release
Click to expand...
Click to collapse
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.

Locked or unlocked phone shouldn't matter as far as the Rom is concerned, it's been stated many times that the kexec kernels will boot fine on an unlocked phone. I would suggest starting fresh, stock ODIN, root, unlock, then flash CWM 6.0.1.0 with ez recovery and go from there.
Some people are not having any issues with the touch recoveries and others are, in my experience the CWM recovery has been the most stable and I could really care less about "touching" my recovery, buttons do the same thing. Just my 0.02
Sent from my Galaxy S III using Xda Premium

feel like an old man hearing these stories......we all know them...when we first started out flashing and **** went wrong....freak outs..panics....sweating..pacing..anger....regret.........BUT then you work through them and look back and say "**** that was easier than I thought"....and we come across them again without panic or hesitation........................dude relax........
1-grab a stock image...chose anyone you want in these forums..some are even prerooted.....i personally got competely back to stock
2-i use the one click root method..so root
3-flash cmw...any version you want as long as it is made for your model phone.....you can use e-z recovery app from market
4-MAKE A ****ING BACKUP!!! very important...
5-download e-z unlock from the play market..use...and done..now you are stock, rooted, unlock bootloader......if you plan on flashing cm10 or aokp or aosp....please make sure to read the thread "how to backup your imei" before flashing any of those roms.............boom goes the dynamite:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:.............................

King_tee said:
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Click to expand...
Click to collapse
Kexec roms don't but synergy should have. I use twrp and Synergy no problem. There isn't anything special that has to be setup for an unlocked bootloader.
Op you should be able to flash any non kexec rom. Did you do a wipe factory reset? If not you may want to give that a try

[Q] ROM Problem : Stuck on boot logo

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

[Q] Can't change ROM, reboot loop

I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated

krusty_da said:
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
Click to expand...
Click to collapse
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh

If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...

lj50036 said:
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
Click to expand...
Click to collapse
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
dgcruzing said:
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
Click to expand...
Click to collapse
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!

krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh

krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
Yes, dont worry too much as I was in the same boat.. lost the recovery a few times.. and or couldn't get recovery to mount any partitions..
If you have still got ADB connection then use Busters wipe... multiple times.. as it cleaned mine out..
Then I used the easyflasher to flash the CWM kitkat Version and used this to flash Tims Kitkat off the external SDcard..
booted in to Kitkat with out loading Gapps.. let it settle then booted in to the recovery then booted to Bootloader..
and reflashed TWRP 2.8.. flashed Gapps with this and its all settled in..
One thing that I made sure off was to boot the device after flashing a recovery.. somewhere in all the instructions it says to to this.. So I made sure I did it..
otherwise I kept getting that password screen in TWRP...and if i got that then I knew it was not mounting anything..
K.. keep at it.. if there is will there is a way and as said if you have an unlocked bootloader and ADB you are half way there already..
Good luck..

lj50036 said:
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
Click to expand...
Click to collapse
Thanks! I'm loading Lollipop for the fisrt time now!
I found a tutorial here to change the bootloader:
http://forum.xda-developers.com/showthread.php?t=2187982
And downloaded the latest firmware from here:
http://www.service.asus.com/#!downloads/c1wax
Thanks again

Custom ROM Issue... Stuck Booting...

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