[Q] Infuse zip flashing stuck at "Finding update package" - Samsung Infuse 4G

Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.

baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.

I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.

baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes

Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?

yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm

Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)

baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.

I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...

baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?

Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.

baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links

Related

Trouble installing new roms through CWM

I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
Since this isn't development related, you should post it in the general board.
You didn't install clockwork correctly, or you didn't follow all of the directions when you did install it. Did you follow the instructions and press "flash clockworkmod recovery", which downloads the latest version and puts the update file on your phone?
i did, i have the latest recovery version. and i uninstalled and then reinstalled it before trying again.
Wrong section and you have to use the option that says choose zip from sdcard not the one that says install update.zip
Sent from my GT-I9000 using XDA App
Mrblackroot said:
I always get an error saying E:/ cannot open file /cache/update.zip (bad), no matter what ROM it is. theres not even an update.zip anywhere on my phone or sd card, and i cant manage to get to this so called /cache. please help.
Click to expand...
Click to collapse
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
If there is no update.zip then in Rom Manager you need to select the first option that reads Flash ClockworkMod Recovery. That will bring up a screen asking which phone. If you are installing an i9000 rom choose i9000. If not choose the Captivate. That will install an update.zip on your sd card
Then select install rom from sd card and it will probably take you to stock recovery so select install packages (or whatever the 2nd choice is). That will get you into CWM. Install whatever rom from there
Click to expand...
Click to collapse
Thanks a lot, this worked. is there anyway i can just move this thread to the general forum, or would that require a moderator?
Shammyh said:
First off, this is the right section, as this thread is *somewhat* development related.
I had a similar problem a while back, and never did figure out exactly what was causing it. Might have been because I often just use the Clockwork update.zip (bootstrapped from stock recovery) to flash ROMs without always "installing" it from Android itself. Though, even when I got that error, I could still flash new ROMs without problems.
Either way, flash to stock w/ oneclick, then do a master clear, fixes the problem right up.
Click to expand...
Click to collapse
Mmmm.. last time I checked the development forums was for developers to start topics on things they have developed or are working on... not for Q & A. There's another board for that..
I get this error all the time.
Open ROM Manager, hit Menu, hit Clear Download Cache.
Then hit Flash Clockwork Mod Recovery, choose Captivate, and let it go. Then hit Reboot Into Recovery and it should work fine. You may have to select Reinstall Packages if you end up in the stock 2e recovery.

TNT keeps force closing on newest OTA update

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.

Receiving Exclamation point

Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
GManLynx said:
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
Click to expand...
Click to collapse
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Alright, I'm sorry but I came the G2.... And I was wondering what NVFlash is? I'm gonna google it, but it will be nice if you answer it too.
Setting up NVFlash
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
darbear5610 said:
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
Click to expand...
Click to collapse
yup and when u get ready for commands u can copy and paste them
techboydino said:
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Click to expand...
Click to collapse
First - the above is the truth - learned the hard way by many.
From the "triangle" comment, I would have thought you were not able to get into recovery anymore, but you said you had tried flashing in recovery - are you still able to get into recovery? Also, when you said you moved the file to the SD - internal or external?
You could re-download the ROM on you computer and/or move the one you downloaded when in USB connect mode if you can connect through USB. and then try flashing it again.
Otherwise - did you do an nandroid back-up first (add that to the G2X Club rules). If so, and you can get into recovery, you can restore it through recovery. If not, you are truly back to square one (except for rooted).
At some point, you need to NVflash a real recovery. The one-click method in the Dev section is the easier way to go. If you can't get into recovery (you only see the triangle and it only does a factory reset), then you HAVE to start there.
Yeah I am still able to get to recovery mode. And external sdcard.
I think i'm just gonna go staright to the NVFlash way. I have a history class today so I have a hour and a half to burn.
And thanks guys for all the inputs.
I'm loving my G2x so far. So fast and sleek
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Alright thanks. I just installed via NVFlash and now I will try again to install CM7
player911 said:
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Click to expand...
Click to collapse
Agree with all the above (I have and use both), except for making nandroids, which was not mentioned above. The only ones where I have had a check-sum issue with trying to restore are nandroids I did with ROM Manager. I would stick with doing them straight from recovery.
Others have had issues with flashing nightlies also, but I have not noticed that as I always head straight to recovery to flash.
Question - I had flashed real recoveries with ROM manager on MT4G - why the "false" recovery issue on G2X?
So player, once I have NVFLASH and CWM, I can download ROM manager to backup/restore/flash any ROM from the list without worrying about anything?
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
I would redownload the zip file over the computer, happened to me before with a different rom, make sure it doesnt unzip. and then drag it to your SD card.
Okay I am perfomring that now, will edit with results.
My goodness... I think you fixed it for me. I feel like an idoit. I've been saving it to hte internal Sdcard i didn't even know that was possible.
Damnit... same problem.
Yay I got it. Thanks so much guys for all the help.
GManLynx said:
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
Click to expand...
Click to collapse
The ROMs were probably going to the internal SD by default. Just move them with a file manager to the external SD (unless you set up recovery to use the internal SD).
Also, do not rename them update zip - leave the names as-is so you will know what your are dealing with if you have multiple ROMs .
Then you flash it as a zip file on SD card - not as "update.zip" - that would be for the OTA update - if we ever actually see one for the G2X!
Good job Gman
Different roms put the external SD card in different places.
By default Rom Manager is set to read/write to /sdcard/... not /sdcard/external_SD that is the norm with the stock(based) roms.
Once you have CM7 on there and everything setup under standard conditions, Rom Manager will work as it should.

[q] help please

Hello everyone i have a problem with my htc hd2 this is my first time flashing my phone and it went smooth until i try to put the rom in my sd card. it always tells me that the zip file is no longer on my computer but out of curiosity i tried ad recovery to see if the zip file is there and it is there but when i try to load the custom rom it says the zip file is (bad) and installation aborted i don't know what to do next
iluuvmochi said:
Hello everyone i have a problem with my htc hd2 this is my first time flashing my phone and it went smooth until i try to put the rom in my sd card. it always tells me that the zip file is no longer on my computer but out of curiosity i tried ad recovery to see if the zip file is there and it is there but when i try to load the custom rom it says the zip file is (bad) and installation aborted i don't know what to do next
Click to expand...
Click to collapse
how are u transferring them? should just copy n paste. do it from CWM (9. ad recovery). go under "mounts and storage". then go down to "mount usb storage" n wait for PC to recognize it. then copy... paste. should work. for additional help youll need explain your whole flashing procedure from task 29 to rom installation. hope this helps
MEG4LOM4NI4C said:
how are u transferring them? should just copy n paste. do it from CWM (9. ad recovery). go under "mounts and storage". then go down to "mount usb storage" n wait for PC to recognize it. then copy... paste. should work. for additional help youll need explain your whole flashing procedure from task 29 to rom installation. hope this helps
Click to expand...
Click to collapse
from magldr i go to (4.usb mass storage) and then when it connects i drag the zip file onto my sd card folder and then it would show that its copying but i after a few minutes it would tell me that it no longer on my computer. im trying to NAND flash my phone and was trying to put hyperdroid but i could not get past the part where i have to put the rom on my sd card oh and every time my sd card folder opens i get this pop up saying "PLEASE INSERT THE LAST DIK OF THE MULTI-VOLUME SET AND CLICK OK TO CONTINUE" and it say on top compressed (zipped) folders
iluuvmochi said:
from magldr i go to (4.usb mass storage) and then when it connects i drag the zip file onto my sd card folder and then it would show that its copying but i after a few minutes it would tell me that it no longer on my computer. im trying to NAND flash my phone and was trying to put hyperdroid but i could not get past the part where i have to put the rom on my sd card oh and every time my sd card folder opens i get this pop up saying "PLEASE INSERT THE LAST DIK OF THE MULTI-VOLUME SET AND CLICK OK TO CONTINUE" and it say on top compressed (zipped) folders
Click to expand...
Click to collapse
so your not using Clockworkmod Recovery then? just flashing directll to NAND?
---------- Post added at 02:16 AM ---------- Previous post was at 01:59 AM ----------
Most newer roms are compatible only with Clockworkmod Recovery (aka CWM or CWR). u must install this after maglr.
Just went over to the OP for hyperdroid v 3.0.1. thats why in the file u downloaded says: Hyperdroid-CWM-v3.0.0-MAGLDR-CWM-ZIP.
*note the bolded abbreviations... means u need Clockworkmod Recovery for this rom to work... not hard just an extra step that i highly recommend
There are roms that dont require this and a few ways around it as well but its easier to just install CWM. like i mentioned before seems most (all the ones ive used in the past ten months) roms are going this route for CWMods added features and benefits
Heres a little guide i cooked up bout an hour ago in another thread to help
I just posted this in another thread to clear some things up for some guys shortly after my first reply to you....guess ya inspired me in a way, hahaha. you might be more concered with steps 5 through 6 seeing as how you already have MAGLDR installed...... hope this clears up the process for you a bit
............................excerpted from previous post........................................
********BTW i have attached a little template that i use when flashing various roms and storing them on my PC. has task29, HSPL & MAGLDR already in it. all u need to do is go to the xda hd2 master radio thread to grab your appropriate radio and put that into the empty radio file. then find the rom you want to test out and usually the developer will have both rom (obviously) and the appropriate CWM that u should use with it and just put those in their respective empty folders i have in the attached file. that way all the steps below will line up to the files i have attached
OH YEAH, FORGOT... THESE STEPS ARE TO BE DONE AFTER THE INITIAL PREREQUISITES i.e. windows mobile device center, activesync, proper spl version...blah blah blah
--------the following steps 1 - 4 are to be preformed while at the tri-color boot screen (easiest way to reach is to turn off your phone while its connected to your PC then immediately hold volume down button till you see it n wait for it to say usb in the white section).
(by the way your device will ALWAYS automatically restart itself after a couple seconds if it is shut down while plugged in via USB to either a wall/car charger or hooked up to a PC this is normal and a small hiccup either due to the use of magldr or the hspl but dont worry)...cant quite remember
1. run task 29
-double click the only icon in file if your using the one provided by doloop
-wait for it to run and do its thing. when its finished it will automatically turn off your device so be sure to hold down the volume key as soon as it does.
2. install radio
-run the "customRUU" file with the HD2 icon in the radio of your choosing
-it will operate in a similar fashion as the task 29, automatically turning off device upon completion.... down on the vol key
3. install hspl3/hspl4
-run the "HSPL3_PKG/HSPL4_PKG" file. should be the only one in there
-make sure you select 2.08.HSPL in the setup and it will execute itself just like the installers in the previous two steps n turn off your phone... down vol key
4. install magldr113
-make sure your selecting "rom update utility" in the magldr113 file. dont run the "DAF" it wont work properly if you do and youll get errors
-BUT THIS TIME AS IT TURNS ITSELF OFF HOLD DOWN THE POWER BUTTON ON YOUR DEVICE AS IT BOOTS UP UNTIL U GET TO MAGLDR AND CONTINUE TO HOLD IT DOWN UNTIL YOU SEE ABOUT 12 DIFFERENT OPTIONS...
5. install CWM recovery
-go to option 5 "USB Flasher" and hit the green call key. wait a few moments till it shows USB....USB make sure the second usb pops up and your PC recognizes the connection. then when it does sync you get to......
-while still in the usb flasher mode above, simply run you desired CWM recovery which should the one your developer recommends for the builds as the requirements tend to vary from rom to rom.
-this is achieved by selecting the "DAF" file from the clockworkmod recovery your using
-and again this installer will shut off your device upon completion and HOLD DOWN THE POWER KEY LIKE ABOVE TILL YOUR BACK AT THE MAGLDR MAIN MENU (with options 1-12).
6. install rom
-go to option 8 "AD Recovery" and hit the green call button to enter into the CWM recovery u just installed
-after it loads up (GO!GO!GO!) go down to the "mounts and storage" option that is third from the bottom and hit the call key.
-once there go to the last option "mount USB storage" and hit the call key.
-give your PC a few moments to recognize the sd card for your device and choose to open it when your PC prompts with the regular file explorer or just find it and double click on the newly recognized drive (sdcard) if your PC doesnt auto prompt you.
-the new drive (sdcard) should be empty (depending...) then just find the desired rom you chose to use, right click on it and copy.....then over to the new drive (sdcard) and paste. might take a min or two depending on the roms size
-once the copying is complete hit the call button to "unmount" your sdcard then the back button on your device till your back at the CWM main screen
-go to the fifth option down and "install zip from sdcard" and hit the call button
-select the second option "choose zip from sdcard" and select the zip file you just copied to your sdcard. then it will begin to install the rom and all rom install times vary by build. some take a minute, some seem like they take forever.
-once installation is complete hit the back button till your back at CWM main screen and choose the last option which is to "power off"
-then tap the power button(if u unplugged it from usb otherwise it wil reboot by itself) to turn on your device and give it some time for the initial boot and load as it has to set up everything u just installed. subsequent boot wont take as long but again it can all vary from rom to rom.
-after initial load and a successful bootup you should arrive at ether the lockscreen or a startup screen. give the rom a few more mins to settle and dont hit any buttons. then unlock the device or skip through the startup options and get to the home screen. maybe give it another min to settle the launcher and the last bit of data and resist the urge to mess with the features. your gonna hate this but hold down the power button and select power off device from the popup menu. i know it sucks but it is best practice when flashing roms. after device shuts off wait a few seconds and turn it back on and let it reboot. should be faster this time and when u get to your lockscreen simply give it a few seconds to settle again, unlock and go to main launcher a wait a couple more seconds for it to finish settling and.....have fun! (every time i restart my device for any reason i will always give it a few moments to finish loading up before just blazing away with the apps)
WOW! maybe its not so abridged after all, but oh well tried my best to be as clear as possible so people can utilize their HD2 to its fullest potential.
HOPE THIS HELPS AND PLEASE HIT THE THANKS BUTTON IF IT HAS
Hello meg4lom4ni4c! you are awesome! thank you so much for helping me and it feels good to know that even though im a noob i still inspire people ahahaha
i was having problems connecting to my pc before but for some reason when i tried it again using the usb port tat the back of my pc it connected and and i put CWM and did what you said to put the zip file on CWM (mounts and storage) and copy and pasted the file and it worked! yey! now the only thing is when i go to market it always forecloses and i don't know what to do to fix it. when i go to market there would be a yellow box on top saying that "this application is not compatible with your phone" and it always forecloses. was wondering if i need task 29 and and radio if i want to change roms and to start it, would i go to the tri color screen and run task 29?
Starting HD2 ANDROID SO FRESH N SO CLEAN!
iluuvmochi said:
Hello meg4lom4ni4c! you are awesome! thank you so much for helping me and it feels good to know that even though im a noob i still inspire people ahahaha
i was having problems connecting to my pc before but for some reason when i tried it again using the usb port tat the back of my pc it connected and and i put CWM and did what you said to put the zip file on CWM (mounts and storage) and copy and pasted the file and it worked! yey! now the only thing is when i go to market it always forecloses and i don't know what to do to fix it. when i go to market there would be a yellow box on top saying that "this application is not compatible with your phone" and it always forecloses. was wondering if i need task 29 and and radio if i want to change roms and to start it, would i go to the tri color screen and run task 29?
Click to expand...
Click to collapse
well what the task29 does is pretty much whipe your whole devices NAND (internal) memory. it wont wipe your radio or the HSPL. it takes care of wiping the rest of the space (MAGLDR and CWM).
so your options are as follows:
-try fix permissions trough CWM
-wiping davlik cache (helps clean up issues with apps n such possibly your market situation, but this could be largely due to the type of rom your using as well as none are perfect...some are really close)
or start fresh to minimize chances for errors and force closes
do this by restarting your device into CWM
-in CWM execute the following commands in the following order (this is a little overkill but better safe than sorry i suppose).
at main CWM screen
-wipe data/factory reset
-wipe cache partition
then at main CWM screen go under "mounts and storage"
-format /boot
-format /cache
-format /data
-format /sdcard
-format /system
-format /sd-ext (only if u made one)
then back at main CWM go under "advance"
-wipe davlik cache
-can also find fix permissions here if needed i personally havent used this much(but maybe i should be every once n awhile...might be good practice)
at this point your ready to start at step one in my guide two posts up....run task29 at tri-color boot screen and so on and so on
*********Please note that the use of CWM is essential for most current builds that utilize a rom-zip format. not sure about sd card builds as i havent used them. i came into the hd2 flashing game right when they got it to run solely out of NAND. just seemed like a better way to do it to me but i could be wrong
hope this helps and lemme know if everything worked out for you. also include the rom you are attempting to install for further assistance. and also corrections are always welcome as i am definitely no developer just have a knack for nerdy stuff (sometimes)
Hi!
so i was reading your post very carefully coz i don't wanna mess up and panick and mess up even more LOL im just gonna go ahead and do cwm wipe and format first but how do i go to cwm screen from my phone and do i have to be connected to my pc?
i downloaded task29 the repack by shadrac one but could not decide which radio to get..any advice? and as for the rom i really don't know what rom im gonna get because i just started flashing my phone but if you have any suggestions i would very much like to hear it the rom im using right now is "Hyperdroid-CM7-v2.1.0-HeadyHoneyBadger" and it works good except the market, it just keeps foreclosing i really like cyanogenmod but i think there is a lot of different kinds so i really don't know which one is good.
Thank you so much for taking the time to help me YOU are really AWESOME!!!
iluuvmochi said:
Hi!
so i was reading your post very carefully coz i don't wanna mess up and panick and mess up even more LOL im just gonna go ahead and do cwm wipe and format first but how do i go to cwm screen from my phone and do i have to be connected to my pc?
i downloaded task29 the repack by shadrac one but could not decide which radio to get..any advice? and as for the rom i really don't know what rom im gonna get because i just started flashing my phone but if you have any suggestions i would very much like to hear it the rom im using right now is "Hyperdroid-CM7-v2.1.0-HeadyHoneyBadger" and it works good except the market, it just keeps foreclosing i really like cyanogenmod but i think there is a lot of different kinds so i really don't know which one is good.
Thank you so much for taking the time to help me YOU are really AWESOME!!!
Click to expand...
Click to collapse
Hmmmm where to start....
You were in CWM when u copied the rom to the phone... remember? to get there turn off device then restart it while holding down the power button to get you to MAGLDR. Option 9. AD Recovery = ClockworkMod Recovery (aka CWM or CWR) in there is where u use my little wipe/fresh install guide
The version of Hyperdroid your using is from a months ago. Pongster has released v.3.0.0 "the insightful impala" with a hotfix to version 3.0.1. I would recommend using that as most of your market issues will be addressed i would imagine.
i attatched a file in my previous post... download it. it comes with the task29(provided by doloop), HSPL3, and MAGLDR113 that i use. the lil guide i posted follows how i have the files in the "HD2 rom template" arranged. if you unzip the attached file (use 7zip,winrar....etc) youll see files labeled 1-6 (1.task29 2.radio 3.HSPL 4.MAGLDR 5.CWM 6.ROM). the radio file is empty because i was unable to compress it enough to include it( there is a 8mb attachment limit ) The CWM file and rom file are blank as well because both will vary from build to build.
if u use my attachment as a kind of template it will make the steps easier to go thru thats why they are numbered
to get the appropriate radio on xda type a search for "radio master thread" and open the post. there you will see a bunch of different radios. BE CAREFUL SOME MIGHT BRICK YOUR DEVICE!!! read the post it explains which ones not to use i believe. the one i use and have noticed a lot of others use is 2.15.50.14.... has always worked for me. download it and put it in the empty radio file in my template.
now go back to Pongsters hyperdroid cm7 OP and download both the version 3.0.0 and also download the v3.0.1 hotfix and put both of the zip files in the empty rom folder.
in Pongsters second post he has the CWM for you that youll need if you already dont have it (its on step three of his little guide on his second post) download and put that in the empty CWM file in the template.
now that you have all the files you need and in a nice tidy order.... reflash time!!!!
follow my "fresh install/wipe/format procedure" in my previous post then use my install guide post afew posts up and follow it using the lil template i provided and that u put the radio,CWM,rom & hotfix into
notice how the 1-6 steps in my install guide follow the 1-6 on my "HD2 rom template" attachment?
******oh yeah when u get to the installing the rom step only install the v3.0.0 zip via CWM first and follow the recommended new rom startup section at the end of my lil guide. make sure the rom has had plenty of time to settle and everything like it says n go ahead and play around with it a little and try it out. but then after u rebooted it a couple times like it says reboot it a third time into CWM and go to the install zip from sdcard option and go in and install the hotfix(sorry i tend to repeat myself sometimes)
lemme know how it goes and have u tride Tyweens rom??? Its pretty good itself in case your not crazy about the Hyperdroids' minimalistic and monocrome look. Both are great though.....
---------- Post added at 01:36 PM ---------- Previous post was at 01:31 PM ----------
oh yeah go to www.android.hd2roms.com for a site i use that someone made that kinda keeps track of most of the HD2 roms floating around on xda. its pretty acurate and gets updated constantly. help u see most of the flavors of android on the HD2.
YEY!
YEEEEEEEEY! IT WORKED! you are AWESOME! thank you so so so so so much! if it wasn't for your guidance i wouldn't be able to understand it! i did all the stuff you told me and it worked! i didn't have any problems while flashing my phone! did i say thank you already? THANK YOU!!!!!
and thank you for all the links that you suggested it was really helpful! thank you thank you thank you!!

My phone wont boot into Cmw recovery, Please help.

My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.

Categories

Resources