I was using TNT 4.2 with some bugs, but nothing major. I have the VS G Tablet I tried flashing the 3588 ROM. That failed. I then used the NV Flash process. It worked. I used the old ROM update with it but then got the 3588 from Viewsonic. That worked fine. Installed Clockwork Mod 08 and that went well. But when I tried the update zip I get this error:
E:unknown command [Bootloader]
E:unkwown command [/tmp/bootloader.bin]
TNT reports the install completed successfully.
Now I'm stuck at the VS birds splash screen. Can't enter recovery. It recognizes recovery was started but nothing but birds. I have tried this four times today. Cleared all caches, including Dalvik, tried formating everything. Many different attempts but the same result. I also redownloaded the TNT 5.0 again to be sure the file wasn't corrupt. Same results. I don't know where to go from here. I've googled and searched XDA. I like to try everything I can think of before asking. I can follow instructions well, or any ideas you may have, I'm willing to try. Thanks in advance XDA members.
Can't use CWM with 5.0
If you read the TNTlite instructions, you will see that it needs stock recovery to flash 5.0 properly.
robelite said:
I was using TNT 4.2 with some bugs, but nothing major. I have the VS G Tablet I tried flashing the 3588 ROM. That failed. I then used the NV Flash process. It worked. I used the old ROM update with it but then got the 3588 from Viewsonic. That worked fine. Installed Clockwork Mod 08 and that went well. But when I tried the update zip I get this error:
E:unknown command [Bootloader]
E:unkwown command [/tmp/bootloader.bin]
TNT reports the install completed successfully.
Now I'm stuck at the VS birds splash screen. Can't enter recovery. It recognizes recovery was started but nothing but birds. I have tried this four times today. Cleared all caches, including Dalvik, tried formating everything. Many different attempts but the same result. I also redownloaded the TNT 5.0 again to be sure the file wasn't corrupt. Same results. I don't know where to go from here. I've googled and searched XDA. I like to try everything I can think of before asking. I can follow instructions well, or any ideas you may have, I'm willing to try. Thanks in advance XDA members.
Click to expand...
Click to collapse
Don't install ClockWorkMod after you get 3588 up and running. 3588 changes the recovery. Use the recovery that is included with 3588 to update to TnT Lite 5.0.0.
You will need to nvflash again. After that, reinstall 3588. Only boot up 3588 to get the TnT Lite 5.0.0 files loaded on the gtab, then reboot into recovery. The stock recovery included with 3588 will take care of installing the TnT Lite 5.0.0.
Once you are up and running on TnT 5.0.0, then install the updated ClockWorkMod recovery. The link is found on Roebeet's instruction page (1st posting) in the TnT Lite custom rom thread. Use this version of ClockWorkMod only. Using any other versions will hose up you gtab again.
I'm sorry, is the search button not working? Heck, you don't even need to search. Just look at the other 20 posts regarding the same thing.
It's been pulled, btw. Search for "TwoTapsX" - same build, different name. I forked it off due to all the issues that users are having. All the instructions and caveats and backout information is the same.
Related
I have a Motorola Droid and I've been messing around with my phone for quite sometime and I've reached a road block that I can't quite figure out. I've previously and successfully put JRummy, Cyanogen and Bugless Beast on my phone, but suddenly out of nowhere, NOTHING works. I'm attempting to put a custom ROM on my phone and I've had little to no success.
These are the steps I've taken:
Start at stock 2.1
Apply ESE81_SPRecovery with RSD Lite 4.6 (Proper drivers installed)
Phone boots successfully and I can boot into SPR successfully
Move custom ROM onto SD card named as "update.zip" (not update.zip.zip)
Reboot into recovery
Wipe data & cache 3x
Go to Install and Allow update.zip
Install update.zip (UD7 specifically -- not a corrupted download as I've downloaded several times from different locations. I've also tried several different ROMs)
Install is successful
Reboot and I get stuck at the Motorola M
I wait 10 - 20 minutes and no boot screen
Pull battery, wipe data & cache again, reboot
Same issue with Motorola M
I've tried literally everything and Cyanogen, Liquid, Bugless Beast, UD7, and numerous other custom ROMs all have this same issue. I've tried wiping my SD card completely clean.
I had momentary success when I flashed back to stock 2.0.1 sbf with RSD Lite, installed SPR, then applied Liquid custom ROM but I felt daring and tried to do the same process but with UD7 and it won't load. Since then, nothing has worked.
I've tried this same process on two different computers with different versions of RSD Lite (4.6 and 4.7), different sbf files, different ROMs and tried using SPR and Clockwork (With ROM Manager Premium and different versions of Clockwork). However, none of this has worked.
When these processes don't end up working I have to reflash the stock 2.1 sbf with RSD Lite because restore won't work either.
Anyone have suggestions?
Tried a 1000mhz kernel and that didn't work either. Any other ideas?
The format of the ram needs to be formatted as an update.zip, i recommend if you want to install roms install Rom Manger. Flash Clock Work Mod and you'll be on your way.
TheDeathly said:
The format of the ram needs to be formatted as an update.zip, i recommend if you want to install roms install Rom Manger. Flash Clock Work Mod and you'll be on your way.
Click to expand...
Click to collapse
The ROM has always been in the form of 'update.zip' when I'm using SPRecovery. It isn't update.zip.zip or anything like that.
I've tried using ROM Manager Premium to flash ROMs (predownloaded on my phone and downloaded through ROM Manager) while using Clockwork Recovery (2.5.0.1 and 2.5.0.0), and that yields the same result.
I started discouraging its use on TNT Lite after the TNT Lite 5 fiasco, but I didn't realize that my opinions carried so much weight. So I want to set the record clear for everyone.
First off, if the developer / modder requires clockworkmod for their ROM, then that's the tool you need to use. I've had more than a few PM's on this question, but the answer is simple. Use what the developer asks you to use -- but also understand the risks. I would guess that most of the devs here mod with clockworkmod in mind.
For my own two active mods (TNT Lite 4 and gADAM) -- for the gADAM, it requires clockworkmod to install, right now. The reason why is because you HAVE to do a data wipe post-install, which standard recovery does not have. I have this written clearly in the instructions. As for TNT Lite, I discourage it for flashing, but I have instructions for clockworkmod users regardless. gADAM 1.3.0+ and TNT Lite 4.3.0+ have something called "Recovery Pack" built into them. This allows the user to toggle between clockworkmod and standard recovery.
Flashing is my concern, btw. For nandroid backups, data wipes and SD repartitions, the cwm tool is an absolute must. And if you are flashing between 1.1-based mods, clockworkmod should still be a low risk. HOWEVER, if Viewsonic releases a 1.2-based mod with a new bootloader, then cwm becomes a much higher risk. My point with discouraging clockworkmod for flashing on TNT Lite is just to get people used to the idea that cwm has caveats that might become a problem, later on.
When that new firmware is released, we will pick it apart and tell everyone the results of what we find. Hopefully my concerns are for nothing and the new firmware will be safe for clockworkmod users.
Also, for reference: I've been throwing around the term "1.1-based ROM" for about 2 weeks, now. Viewsonic's stock firmware has come in three flavors, so far: 1.0.1 and 1.1, which seem to be on the same dev branch and compatible (from a clockworkmod standpoint). Most, if not all, of the mods here are 1.1-based. 1.2 is a new dev branch that was introduced with build 3991, which was never officially released. This build has a bootloader that, if not flashed with standard recovery, will soft-brick your device. This is the dev branch that concerns me and that we should be watching out for, when that new firmware is released. As I mentioned, we will test it when the time comes.
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
absorbers said:
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
Click to expand...
Click to collapse
Quicker is not always better, imo. If users here use cwm, they should understand the risks. I would argue that anyone using a mod here should also understand how to install and use nvflash - devices like the Advent VEGA, Notion Ink Adam and even Viewsonic's own Viewpad10s have nvflash-only firmware updates. I personally find it to be a critical tool for anyone modding their device.
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
severusx said:
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
Click to expand...
Click to collapse
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
There have been some discussions in the partition thread regarding the 'fix permissions' portion of CWM making the repartition suggestion obsolete. I don't have access to standard recovery to check if that option is in there too but the permissions thing may also be a feature of CWM that will be difficult to let go.
roebeet said:
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
Click to expand...
Click to collapse
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
brown14you said:
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
Click to expand...
Click to collapse
It's a set of scripts - just read my first post, and the Recovery Pack reference link, at the bottom.
jazzruby said:
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
Click to expand...
Click to collapse
If memory serves, you should get the "!" and then a reboot. But it might not do anything if there's no command file (just hang there for a moment, and then reboot).
Thanks. Got it!
Thanks, I just booted again to recovery, no command or update.zip and same thing.
jazzruby said:
Thanks, I just booted again to recovery, no command or update.zip and same thing.
Click to expand...
Click to collapse
To verify 100% that it's working, you might want to run an update.zip. ie. use the Recovery Pack standalone, it will just overwrite what's already there. Always good to know before you actually need it.
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
jazzruby said:
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
Click to expand...
Click to collapse
Pershoot's kernel may not work with standard recovery, just a heads up. But you can certainly give it a go.....
Pershoot's kernel is nested in a subfolder and I need/want to wipe first.
I just flashed 3588 with Stock recovery and all's good.
I got root and flashed 'RP' and CWM restored my backup.
I ran TE 'fixrecovery.sh', rebooted into Stock recovery and I don't see the (!).
Aside from the downloading animation it seems like a normal boot.
This was with no update.zip @ root or command file in recovery subfolder.
So I guess it's safe to say that no (!) is nothing to worry about.
Just to be sure I dropped an update.zip @ root and same results.
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
which method? Linux, windows?
windows version.
if you can, give us a list of files in your nvflash directory.
thank you, you got me in the right direction. i did not extract the gtablet file.
yea, with all these tools available, it's really hard (is it possible?) to brick g-tab . ..
210danielz,
Unless I misunderstood your first post, it sounds like you have a CWM problem.
Running CWM with 4349 will cause semi-bricks -- and several of us have tried
to post warnings to that effect all over the forum.
IMO, you probably should NVFlash back to stock and let the OTA update take
you back to 3588. Then you will be stock with a solid rom and can do what you
want.
http://forum.xda-developers.com/showthread.php?t=861950
Good Luck,
Rev
210danielz said:
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
Click to expand...
Click to collapse
Here is more info on 4349.
http://forum.xda-developers.com/showthread.php?t=1035983
Roebeet ran a lot of tests and found that 4349 is not compatible with CWM.
210danielz,
When someone gets a bad NVFlash like that I always tell them to:
Take the procedure and go through and check everything. Make sure right
.zip files used. Check every little detail.
Re-run the NVFlash.
If previous step fails again, try nvflashing CWM only:
http://forum.xda-developers.com/showthread.php?t=1030042
If you get a good flash on CWM and get it up, the go to the
Advanced Menu and Partition (2048/0), Fix Permissions, Wipe
Dalvic Cache. Then Return to Main Menu and Wipe Cache
and Wipe/Reset Factory Data.
Having done the above, shut down and go back and NVFlash
to stock again (having cleaned out and repartitioned to
hopefully make it work right this time!)
Hopefully this will give you a working G-Tablet with Bekit 1105
or stock Version 2638 on it. If you set up wifi it will pretty
quickly offer you an OTA to 3588.
From there you can go where you want.
Hope this helps,
Rev
I know there is a thread going (Easy [UNROOT]), and I would have posted in the development section, but I'm not aloud because of my limited posts.
First let me say, I did read this post:
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot+b90
And followed this tutorial:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
I have a B90 (US - rooted with RC) and had an issue in the unroot process - specifically flashing ASUS recovery. I did the first install, reboot, manual boot to recovery, and then when I tried flashing the 8239USrecovery.zip I get:
---
Finding update package...
Opening update package...
E:Can't open /sdcard/unroot/8239USrecovery.zip
(bad)
Installation aborted.
---
After the first failure I powered down, pulled the SD and deleted / re-downloaded / re-added the zip, and tried again. Same outcome.
Any thoughts are much appreciated!
UPDATE:
I tried going back to my restore last night, and that was a no go. I wiped again from CWM, and tried the whole process over again. Nada.
This morning I tried another download of the file, did another wipe of data, wipe cache, wipe dalvik, reboot, manual boot to CWM, and flashed the file.
And it worked! Fifth time's a charm? So if you have a B90, this method does in fact work. You might just have to give the second step a few tries.
How did you root it, because I'm trying to root my B90 using whatever process is shown here and nothing. Just get the gears turning and the exclamation point.
felix8787 said:
How did you root it, because I'm trying to root my B90 using whatever process is shown here and nothing. Just get the gears turning and the exclamation point.
Click to expand...
Click to collapse
Sorry for the delay! I missed this.
I used Razor Claw, though, at the time my firmware version was at .19 or lower. When I unrooted, I saw that I'm up to 8.6.5.21 now. I'm not 100% sure, but I'd check that out for compatibility with the latest RC.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!