Related
After painstakingly researching into jfupdater, fixing a bad adt and sdk installation, and realizing that both the 1.1 and 1.5 sources could not coexist in one project, it is done. This program will work for JACHero 1.7 / TwistedZeroP and later builds. Due to the pre-work nature of TwistedZero, this will ensure that at least one of the system.zip archives is on the ext partition (it may not provide the most updated programs, but it will at least allow the update to be installed) You have the option to poll all updates, just JACHero, just TwistedZeroP or just TwistedZeroM. So far, only JACHero's updates will download because I am still working on getting mine on a dedicated server. I will try to keep as up to date as possible with download availability. Anyway, without any further stalling:
http://twistedumbrella.googlepages.com/heroupdater.ui.apk
Updating to the latest *working* version
You will need to have transferred the build.prop file to the /system/ folder of the phone for this to work.
They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that.
Currently working on getting my builds program ready. Default update type is TwistedZeroP (can be changed in menu). Program is now a free download on market. Hero Update.
Very nice......
great job man
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
kickfliprock13 said:
Freakin Sick Just used it and it was awesome! It still displays downgrades buts thats fine! I love it!
Click to expand...
Click to collapse
It will display downgrades if you either have a version it cannot detect that is compatible with the updates or haven't gone to the configuration menu and unchecked display downgrades
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
thefunkygibbon said:
ace. i thought all the hero roms required a wipe before each upgrade so this comes as great news.
thanks
Click to expand...
Click to collapse
You're still gonna get wiped depending on the build.
it told me error while downloading what am I doing wrong...?
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Great idea, thank you Twisted & JAC!
How do I use it? It shows me TwistedZero 1.7P as an update - can I just download it and then it will be installed?
No wipe or something like that?
an error occured while downloading 1.7P ?!
tep065 said:
Very nice . This will truly make things easier. Nice work Twisted and Jac =).
So..I get a message when using update. The update app says "Your system is running an unsupported OS. (Version unknown) Please manually upgrade to JACHero 1.7 / TwistedZeroP or later and try again"
I understand its still a work in progress..just reporting my experience with the process.
Is "M" not a newer version than "P"?
I would assume, that even if the updater could not find an update for M, that M would still be a supported version and that it would just give me an error of not able to find an update for it or something. Not that M is unsupported.
FYI for all..I downloaded the files via the phone, installed linda file manager, android .Zip app(AndroZip) and AppsInstaller app. I Extracted the build.prop with and androzip, moved the file to /system/ on the phone with Linda, installed the HeroUpdater.ui.apk with Appinstaller. And then I get that message about an unsupported OS.
Click to expand...
Click to collapse
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Configuration menu
jawash22 said:
Do I replace the build.prop file I already have on my /system/ folder or do I not even need to worry about the build.prop?
Click to expand...
Click to collapse
Ok, I just did an overwrite of my existing build.prop and it shows me the twisted 1.7 update, but I am on JAC 1.8. Hitting Menu does not bring up configuration menu...what's wrong?
Backup
DanOtero said:
Yes, the idea is that you replace it. The only difference between both files is a new reference to the build name (so the apk can tell what version you are on). Nevertheless it's always a good idea to back things up before you overwrite any files (learned the hard way throughout the years . So simply do something like 'cp /system/build.prop /sdcard/build.prop.old' from the terminal or 'adb pull /system/build.prop' from your computer before actually replacing the build.prop file.
Click to expand...
Click to collapse
Thanks alot..I should know by now about backing up system stuff. Anyways, I still can't get the Menu and at the bottom it says "Running Version:unknown". I used the JAC 1.8 build prop also. I'll leave it alone for now and see if anyone else on JAC reports bugs....thanks again Twisted! You are appreciated.
man! cyan needs one!
DanOtero said:
Did you reboot after copying the build.prop? Rebooting did it for me (seems like this file is read when the system comes up).
Click to expand...
Click to collapse
Yah...i didnt reboot after...just rebooted and i had an update available thanx..gonna run the update while watching transformerrss in imax theater
where's the file?
"They are available through my site's main page for my builds, and for now on my google code for JACHero until I get a new page coded for that."
That would spare 20minutes of timewasting
How do you transferred the build.prop file to the /system/ folder of the phone? thanks in advance.
Just like our USCC friends, I'm currently working on several mods for Cellular South's release of the Desire. I'll keep this post updated with new developments.
Linked is a custom boot.img from our stock ROM with apps2sd support. You will still need to download and flash the latest Darktremor apps2sd release and format your SD card accordingly.
How to flash?
Place the dphase-apps2sd-signed.zip file on the root of your sdcard and flash it as a zipped update.
Download Link (Cellular South, also confirmed working with Alaska Communications):
http://dphase.net/desire/dphase-apps2sd-signed.zip (2.3 MB)
MD5 checksum: 70df556ceb6891cbdcc3801d807d58af
US Cellular stock boot.img with apps2sd support
http://dphase.net/desire/dphase-USCC-apps2sd-signed.zip (2.3 MB)
MD5 checksum: e11b6f40b26811e252f0579f0ed5861c
Latest Darktremor apps2sd:
http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
------------------------------------------------------------------------------------------
Zipaligned and PNG optimized system apps:
Code:
% du -sh original optimized
62M original
42M optimized
As you can see above, I've zipaligned and optimized the images in the system apps, which shaved off 20MB from total files size. This should lead to faster load times.
To install, untar the optimized archive to the directory of choice and boot to recovery. Mount the /system partition then do the following command with adb from within the directory holding the apk's (adb should be in your binary path, if not, fix that to make life easier in the future):
Code:
adb push . /system/app
You'll then see, for example:
Code:
push: ./DCSImpl.apk -> /system/app/DCSImpl.apk
push: ./HtcDialer.apk -> /system/app/HtcDialer.apk
push: ./EnhancedGoogleSearchProvider.apk -> /system/app/EnhancedGoogleSearchProvider.apk
... (etc)
Link:
http://dphase.net/desire/system_app_optimized.tar.gz (40MB compressed)
MD5 checksum:
2dc5fe2683e657006d2a8026c4ac32dc
reserved for later use
So what exactly does this accomplish? Is it basically adding apps 2 sd to the stock 2.1 rom? Any chance it will run on my US Cell desire?
Yes, adds apps2sd support to the stock rom. The latest a2sd will automagically move portions of /data over once it sees a properly formatted card.
In theory, this should work on USCC, but ymmv.
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
con247 said:
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
Click to expand...
Click to collapse
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Updates posted, please test and enjoy.
dphase said:
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Click to expand...
Click to collapse
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
con247 said:
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
Click to expand...
Click to collapse
I've modified your boot.img and placed a link in the first post.
dphase said:
I've modified your boot.img and placed a link in the first post.
Click to expand...
Click to collapse
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Just booted and WOW look at all that new Space!!! Time to get more apps
seesser said:
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Click to expand...
Click to collapse
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
How do you change the MD5 of the file
dphase said:
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
Click to expand...
Click to collapse
I guess I did it a little differently. I already had the sd card partitioned so I just took a backup swapped the boot.img and edited the MD5 with note++. Restored the modified backup and then ran the apps2sd.zip and rebooted.
I did it this way just in case something went wrong I could restore the backup that I didn't modify.
Going to try out that app optimize next.
Thank again.
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
Hello and yes I was running that rom but did not like that friend Stream did not have twitter. with that rom you still had to tell the phone to move the files (a little bit of command line codding). With this boot.img and apps2sd on my stock rom backup I went from 15mb to 71mb so this one works great right out of the box.
I Explained how I did it from a backup of my stock rom up a few lines hope this helps.
I too am a little lost on this push of the app optimize. Could you explain it a little more? I have done a little adb shell programming but am lost with your directions.
Thanks,
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
No, none of this can be flashed as a rom.
I'm not sure why anyone is changing MD5's, I included those so one could verify there was no data corruption during the download.
fixed. no worries..
con247 said:
I keep getting an MD5 mismatch after I edited the nandroid.md5 to the one in the original post
Click to expand...
Click to collapse
There is zero reason to edit that. Are you trying to use nandroid to flash the image? If so, that's the wrong answer.
con247 said:
fixed. no worries..
Click to expand...
Click to collapse
Did you restart the phone after you modified the MD5? I had that problem also until I restarted the phone and It worked after that.
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.
Thanks to dangpzanco for the GREAT IDEA.
I finally got my Rooted GB working here. I can't provide a download link now but I'm going to do it later for sure.
Apparently there was a final signature check that was done somewhere after mounting the cache partition, preventing me from booting with a pure update.zip on top of froyo /system. Thanks to dangpzanco I could bypass it and get root.
Quick Guide (requires froyo, root and Droid2bootstrapper):
1. Download fixed SBF bellow. It's made from the CH leak containing ONLY: CG35.smg (boot) CG47.smg (recovery) CG61.smg (devtree) firmware.hmg (header) RAMDLD.smg (flash updater).
2. Download root_and_recovery.zip and copy it to SD Card.
3. Download full leaked SBF from General Forum (CH, signed) and use MotoAndroidDepacker to extract all images.
4. Copy the CG39.smg to /sdcard/
5. Boot into CWM
6. From CWM open adb shell and use this command: dd if=/sdcard/cg39.sm of=/dev/block/system
7. Still on CWM apply root_and_recovery.zip
8. Still on CWM wiped everything
9. Boot on bootloader and flash fixed SBF
10. Reboot
I actually did the same thing! I read it somewhere in one of the topics. I installed Defy BootMenu instead of CWM. Works great! Right now I've almost removed all the Chinese crap and got the GApps working (from CM7).
I also removed the Blur items for the Chinese SN's. I'll see if I can get Twitter and Facebook working with it.
2nd-init would be nice too actually. Does the method provided in the other thread work with this ROM?
Edit: the instructions were indeed from dangpzanco!
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
w0ndersp00n said:
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
Click to expand...
Click to collapse
Here it works fine. Have you tried to edit /system/build.prop?
Change device from ME722 to A953.
Yes, I changed it to A953...
Maybe I have deleted something that was necessary for the viewfinder... But what xD
Edit: Allright, nevermind. Somehow a reboot fixed it :-D On to the next step
Something bad happened when I tried to apply 2nd-init on this. The phone rebooted just after 2nd M logo not allowing me to get into CWM. Wierd, since CWM should take place before 2nd-init. Will need to raflash froyo and start over. We should find a way to root Gingerbread without CWM to make things faster.
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
w0ndersp00n said:
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
Click to expand...
Click to collapse
Yeps, it is easy indeed, but to do it I need to SBF froyo before installing GB again. In other words if I mess up the phone I will need to flash 2 versions instead of one. That's why it would be easier to flash just GB.
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
I tried that with froyo but it didn't work.
you can try also this defy leaked gb rooted nandroid backup.
http://www.multiupload.com/SPZ8SIEC60
version 4.5.1-134 multilanguage.
use fixedsbf from new leaked milestone2 rom and milestone2patch from MS2Ginger thread.
In this rom /system/app/kpilogger.apk cause battery drain so delete it after install.
Something is seriously wrong... My backlight never shuts down. It's black, but when it's dark you'll see it's still on!
I actually can't change the brightness from settings. So I did a complete reinstall and the problem persists!
I'm using brightcontrol app now to adjust the brightness, but does anyone else has this issue? Or is it something I did?
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
julianlatasa said:
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
Click to expand...
Click to collapse
My system is messed. I still need to get 2nd-init to work. I'm having a lot of trouble trying to compile my custom version of logwrapper hijack. As I don't have experience in compiling stuff to ARM/Android it is being a pain in the a**. I'd appreciate some help here
Try setting up a QEMU environment with the GB leak kernel's zImage.
Edit: Now we can port CM7!!! Devtree.img is now signed.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
Try setting up a QEMU environment with the GB leak kernel's zImage
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
And how do I do that?
I tried some ways till this point:
- Installed CodeSourcery G++ Lite toolchain (could compile, but android didn't run)
- Installed NDK and tried some commands I could find on blog posts (no luck)
- Now I just finished setting up an ubuntu 10 VM with all the steps described on developer.android.com. I think I am now able to compile android system, but I don't want to as it will take a LOOONG time.
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
I'm a developer, and have compiled stuff to run on linux/unix many times. But this ARM stuff is way complicated. Writing the code isn't the problem, but compiling is. Lots of flags I haven't seem before, and so on.
r2beta0 said:
And how do I do that?
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
Click to expand...
Click to collapse
I just uncovered this answer by myself.
A 'make toolbox' on root folder seems to work just fine. Now I need a way to define new targets on android build system.
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps I've made a full repo sync. It took 3 hours and is worth 6GB disk space
Great news! Can't wait to see a true custom ROM working
Just thought I'd share what I've learned: don't mess too much with your build.prop Somehow my modifications were the reason of my backlight not working right and making every app crash that wanted to use a sensor. But it's working again
Thought I backed up original ROM, when I opened the file today it was blank (NVFLASH).
I did copy the internal sd and have a copy of that but its not the right file type.
I also have some image files of the ROM, can I use either of these?
How about a little more information.... what file did you open that was blank?
Do you have files that look like 09_APP_raw.img? Did you use a script or just type a bunch of stuff in at the command line?
How did you copy the internal SD card that it is not the right file type?
What are these image files of the ROM?
So many questions...
The way I copied the internal sd was in the file manager, had to click show hidden files to do it.
The blank file was a file that brk asus transformer root toolkit made. Went to do a restore with it the next day and file not found,
The image files I have are ones that another version cwm m ade doing a backup a few times that I got from the market. But that version of cwm doesnt support asus.
OK- it that helps. If you just want the stock firmware, you can get that from the ASUS website. You might have to get the 8.6.5.9 version and then upgrade to 8.6.5.13 via the ota. From there you can root again and/or install CWM if you want.
There are TF specific versions of CWM- solarnz and roach each have a version in the dev section. These might allow you to flash the data partition from your backups to restore any apps that you installed. I think brk's tool uses one of the modded versions of CWM.
As far as the internal sd card, you might have to copy those over with an external SD card/adb/ftp/etc.
If you want to restore one of the CMW images you have, that might be tricky, but you can extract them with the unyaffs tool. Google should find it for you. They might be flashable with one of the modded versions of CWM, but I think the modded versions have a slight difference in the parts that they backup/restore. You can try the "advanced restore" option to restore the data.img, but I'm not sure what would happen.
I looked at asus website for the rom, all I found were firmware and kernels are those the roms? I would prefer doing it that way.
Yup- select the android OS and pick your country specific firmware (aka ROM).
It might be tricky if you are downgrading I.e., you flashed 8.6.5.13 and want to flash the stock 8.6.5.9 firmware. I'm not sure if you can downgrade the "easy" way.
The easy way is to unzip the firmware and place the whole ASUS folder on your external SD card. Turn on the TF and insert the SD card when it is running- a notification should pop up to flash. ASUS has some documentation with pictures in the Manuals section. Look for one of the "Update SOP" files.
Let me know if that works. I've never tried to downgrade that way, so I'm not sure if it will work because you might be on a higher build number. If it doesn't, there is another way if you are rooted or you can use nvflash.
Let me get this right, do I use the firmwaree or the kernel.
Use the firmware.
Thanks, I reread the firmware aka rom. I'm in the us so the us one right! Will let you know if it works, says something about downgrading in there...
If it won't let you downgrade, then you have to do it the "hard" way.... but you have to be rooted.
Download the firmware and unzip it. It should be something like ASUS/Update/some.zip
Unzip the some.zip file and it'll contain a blob. Copy the blob to your external sd card or use adb to push it to your TF.
It would be a good idea to verify the MD5 sum of the blob. The US one that I downloaded for 8.6.5.9 is
MD5(blob)= 57d4c4342277d39e523e26b943891a1f
Use terminal on the TF or adb shell from your PC and type the following:
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
the last three characters are zero-pee-four. It's important to get this right or you could mess up your TF.
If you copied it somewhere else, then adjust the /Removable/MicroSD/blob part.
It will take a while because it's a big file, but when it's done, type "reboot" or just turn off, then turn on your TF, and it will flash you back to stock. You should see a blue progress bar that moves very slowly. Be patient, it takes a while and should reboot when it's done. You will be unrooted with a stock recovery at this point.
Afterwards, you can verify that you have the downgraded firmware and then check updates to receive the OTA to upgrade to 8.6.5.13. Lastly, clean up and remove the blob file from your sdcard- it's 521MB!
Your awsome man! You took all that time to help me out and I won't forget it gee!
So did the downgrade work, or did you have to flash the blob?
Not gonna try tonight, thats how I lost the backup as I was tired... Will try tomorrow and will let you know what workes.
I have prime on here now so I dont think that would technically be a downgrade?
Yes I am rooted.
So while I have you, will a rooted machine get OTA updates?
Yup, the updates still download, but they usually break root or won't flash because something is not stock, such as kernels.
Of course, you can mod them so they flash and keep root.
Good idea about starting fresh tomorrow.
r u Randal in Ca?
No, sorry.
No worries, just reminded me of the big guy. Will let you know how everything goes. I try to be sure before I comet to a change I can't recover from so will have to sus up everything first.
I want to thank you again for the help, I hope you get compensated for it?
Hardy har har, and I'm still in thi situation!
We will see tomorrow!