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
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
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob
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
Hello everyone !
I have some questions about the installaton of superman rom.
I've tried to change the bootloader and the modem but when i tried to install it via Odin it doesn't want to reboot and stay on samsung logo.. That's my only problem because i've successfully installed twrp.
I've heard that my actual rom (stock rom APB2) is encrypted.. how to unencrypt it.. (sorry for my english).
Thanks you !
Did you follow the install instructions on the first page?
They are very clear
suprememaster said:
Did you follow the install instructions on the first page?
They are very clear
Click to expand...
Click to collapse
Of course, i've followed everything but like i said when i want to install bootloader and modem that allow to install rom, it never boot
Try to flash the stock rom ape9 i think instead of the modem only. Can you still go to twrp even when you got a bootloop? If so. Flash the rom in twrp
suprememaster said:
Try to flash the stock rom ape9 i think instead of the modem only. Can you still go to twrp even when you got a bootloop? If so. Flash the rom in twrp
Click to expand...
Click to collapse
Can you give me the link to download the ape9 stock rom please i didn't found it :/
Yes when it booloops i can go to twrp and i've tried to install the rom but when the installation with aroma finished, it bootloop again
I think you might've skip a step in this thread:
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Namely step 9. that should answer you decrypting question.
It does a few minutes for boot up. How long were you in the bootloop??
But the rom is pre-rooted no ? It means that i don't have to root the phone before if i've right understand ?
If i let this 3 hours i think it have bootloop during 3 hours
@p0m-walt
Yes the Rom is prerooted but that was not what I was referring to. You asked how to decrypt the phone so I provided a link to the dm-verity zip file that you need to flash through twrp before installing a Rom. If you missed that step that's probably what's causing you problems.
3 hours in a bootloop is a little excessive. You should figured something was was wrong after 15-20 mins.
Format data
I installed the rom successfuly. I had to install an APE9 stock rom and after that, the installation via twrp was a success, Thanks for your help guys