yashsingh1/xdaforums huggingface dataset:
[G Tablet General] jwhnlr:
Try Removing the file extension, if you have COMMAND.txt then you will be stuck on BL 1.1 3588
[G Tablet General] RREVETTE:
Finished with no stumbles but finisherd on 3588

Followed through this guide with no hitches at all but finished in 1.1 3588. In the final boot to recovery it appeared the file - 4349 zip was acted upon. The install is clean and back to stock TnT and on WiFi but it did not pickup 4349. I tried several more times to get it to load the 4349 zip file but no luck. Even went back for a new download of the 4349 zip and that also failed. Everything is perfect (?) and on 3588. What to do now? I want to get onto 4349.
[G Tablet General] ramerco:
Make sure the files are named properly when they are on the sdcard. THe only one called update.zip should be the 4349 update you download using the link in the OP to the file update-smb_a1002-4349-user.zip. Also make sure you have the recovery folder with the COMMAND file.

TBH though, 4349 is basically useless. It has incomplete HD video playback and no improvements over 3588 other than a lock screen. If you want to get on BL 1.2 you can do it with nvflash also.
[G Tablet General] Hendge:
New and Lost here. Really hoping for some kindness, hopefully more then a tell all link for a newbie to check out. I have read and read and still not getting it.

I am stock 3588. Want to try some 1.2 based Roms. Using this thread for a fool proof method - is there a better/easier way at this point?

Here is where i am at: Have repeated the steps and process outlined here trying a few different methods - unzipping files first etc...

For some reason when i go to install from SD card it says there are no files, trying again it has the basic android/DCIM etc files...i assume those are on the internal.

The files referred to in the OP are on my external SDcard! Verified only via my laptop.

Is there any know problems using 'Kingston' brand? When i am in mounts and storage and click mount /sd-ext (this is troubleshooting after the fact) i get an error message: error mounting SDEXT:!

What am i missing? Doesnt seem this should be so difficult. Appreciate any help/guidance in getting the most out of this Gtab.

Thanks :)
[G Tablet General] scube01:
Cannot install any apps

I am a noob and tried this for the first time. Follwed all the instructions step by step and all worked. However, now cannot install any apps onto the gtab. Help!!!
[G Tablet General] scube01:
Re: Cannot install apps

OK. Fixed issue with not being able to install apps. Did a Data wipe and then reboot. All is fine now. I am on the 1.2 bootlader with stock 4349. yippeee!!

Thank you much for your efforts.
[G Tablet General] ramerco:
SDCARD means the internal storage

SDCARD2 or MICROSD means the micro SD card you put in the slot on the side.
[G Tablet General] brotiminva1:
I tried this "foolproof way to go back to stock" thing 2 times. I hve changed ROM's about 10 times,,,with no issue. I guess I am just missing how to do 1 thing. it is this......"Creat a folder called recovery with a file in it called COMMAND inside it with the following line of text: --update_package=SDCARD:/update.zip" I followed to th letterhow to do this,,,but I got back to the stock 3588,,,but it showed the box with the arrow coming out upon restarting,,,but it never updated or installed the 4349. What do I need to do?
[G Tablet General] yamaha83:
did you rename the 4349 file to just update.zip? is the file you created called COMMAND or COMMAND.txt?
[G Tablet General] brotiminva1:
I renamed it. Then I made sure the file was COMMAND without the txt. I guess I just don't know how to make that file up. I tried uing word pad,,,,then downloaded Notepad +++,,, still must have done it wrong,,,,any thoughts?
[G Tablet General] jasonofx:
Just did this step-by-step. I am stuck at the new white g-tablet screen. Do I have to re-do root, CWM, etc?

Edit: Nevermind. Just did the flash and new CWM from the PC and all's good. Hooray to Calk&Clem v7!!!!!!!!!!!!!!!
[G Tablet General] wildwoodguy:
Stuck

I am stuck at the white g-tablet screen When I try to get back into CWM it shows a box with an arrow and a progress bar for like 5 seconds and the goes back to the white gtab screen. Any suggestions?
[G Tablet General] viskon:
Looks like you flashed a 1.1 rom over a 1.2 bootloader, or vice versa. If you are stuck at the birds, nvflash is your friend.
[G Tablet General] wildwoodguy:
No Birds

Not stuck at the birds stuck at the gtab screen.
[Xoom Q&A, Help & Troubleshooting] Scourge1024:
So, I've picked up my replacement Xoom after bricking my first. I decided to rip my system and recovery partitions again for completeness, after discovering BeagleBoy's system.img was different from mine. I've posted my Xoom WiFi (MZ604) recovery.img in another thread. Anyway, I can confirm the WiFi recovery partition on both my old Xoom and new Xoom have an MD5 of 1f853c8636ab22b5d651a5512f0865c0. Great success! I hope others with a virgin Xoom Wi-Fi can confirm with me.

And here's something interesting... After ripping a new system.img (MD5 4b7b974a0cc8cdc00521de970b7fc611) from my new Xoom, I did a compare against my first system.img from my bricked Xoom. And also against BeagleBoy's. ALL 3 ARE DIFFERENT. I think I may have compromised my first system.img from my bricked Xoom by doing an "adb remount" before ripping the partition.

Now to confirm... With system.img having been extracted (and backed up) from my new Xoom. I performed an "adb remount" and immediately ripped the system partition again. Did a new MD5 check and... It changed... It's looking like a RW remount does compromise the "virginity" of the system.img file.

One more thing... I'm hoping someone with a factory locked WiFi Xoom can replicate BeagleBoy's boot.img file (MD5 051d1f7e150d4077adb388b5f8e53462). He flashed the Tiamat kernel onto the recovery partition instead of the boot partition (to maintain its integrity) and booted into recovery (Beagle, if you can elaborate on how to do this, please do).

I asked for expert help so I will not be doing step-by-step instructions.

Testing method 1 (retrieving system.img and recovery.img):

1. Put virgin Xoom in fastboot mode (if you can't do this, you shouldn't be helping)

2. Do a "fastboot oem unlock" and "fastboot flash boot.img" where boot.img is the Tiamat boot image to give you basic root. Reboot into normal mode.

3. With USB debugging on, do an "adb shell". Do not do a remount during test!

4. At the root (#) prompt, extract your system and recovery using the following commands (do recovery first, much faster):

5. Do an "adb pull" of the two .img files you created in /mnt/sdcard/.

6. Run a MD5 on the two files and report here.

7. ???

8. Profit

Test method 2 (install Tiamat into recovery partition and extract boot.img and system.img)

1. I will edit this section as needed. But the gist of it is to install Tiamat into recovery partition and then extract boot.img and system.img using a similar method to above...

...

8. In fastboot, reflash the recovery partition I saved on

References:

BeagleBoy's thread for his boot.img and system.img (http://xdaforums.com/showthread.php?t=1017398)

My thread for the recovery.img file I first extracted (and hoping is consistant between all Xoom WiFi's of varying regions) at http://xdaforums.com/showthread.php?t=1036574
[Xoom Q&A, Help & Troubleshooting] Scourge1024:
Placeholder for an external link to my system.img file (when I have time to upload it somewhere for hosting)
[Xoom Q&A, Help & Troubleshooting] Scourge1024:
Scourge1024's MD5 test results on old Xoom (fail?):

boot.img - (not tested)

system.img - 203465c9fb9d6bc926dd0dea9b85ebc4 (not valid as a clean image after remount)

recovery.img - 1f853c8636ab22b5d651a5512f0865c0 (matches my new Xoom; may not)

Scourge1024 new Xoom (Win?):

boot.img - (not tested)

system.img - 4b7b974a0cc8cdc00521de970b7fc611 (never RW mounted, hoping this is consistant)

recovery.img - 1f853c8636ab22b5d651a5512f0865c0 (matches my new Xoom; may not)

BeagleBoy:

boot.img - 051d1f7e150d4077adb388b5f8e53462 (trying to find out if this is consistent)

system.img - fd78a2297290c3fdc7377ded6090e2ae (does not match either of mine)

recovery.img - (not tested; overwritten)

Now to see if people can get a consistant MD5 for boot.img...
[Xoom Q&A, Help & Troubleshooting] ydaraishy:
My expectation is that the kernel images (not the entire boot images) should be identical across devices and between boot and recovery.

The system image differences you're experiencing are probably expected -- remember *access* times are logged within the file system, it is ext4 after all -- and because you're pulling a system image, rather than the files themselves, you see a difference. Things like that are going to be difficult to eliminate.
[Xoom Q&A, Help & Troubleshooting] Scourge1024:
If system is left in read-only access, would the access times be affected? I'm thinking this is possibly the reason why my "fastboot oem lock" failed. I had been able to relock my device before touching the boot, system and recovery partitions. Userdata was obviously changed the moment I booted up normally so I think that can be taken out of the equation. Plus, it gets wiped each lock/unlock anyway.

Anyway, I'm NOT going to try relocking my new Xoom... One heart attack was enough. And Best Buy might catch on I'm doing something I shouldn't be. :)

Can someone grab their MZ604 recovery partition? I'd like to see if they get the same MD5 I do. I doubt anyone has a modified recovery partition besides BeagleBoy. I'm trying to isolate if there's any difference between Canadian Wi-Fi Xooms (like my own) and the US ones. I already know my recovery partition is different than the MZ600 Verizon Xoom.

Think about this people... If Moto isn't going to give us Wi-Fi guys official img files, we'll have to get them ourselves.
[Xoom Q&A, Help & Troubleshooting] ydaraishy:
I'd say mounting ro might help, but I'm not sure. It's possible filesystem metadata might change even if mounted read-only. I'd need to know more about ext4 to make a firm call.

One really needs to know what the "fastboot oem lock" procedure is using to validate the currently written images -- I have a feeling a signature check is being made, but I can't be sure of that. It might be fruitful to diff the Moto-provided images with ones dd'd off a running MZ600, perhaps. All just guesses though.

(let alone how cruddily designed it is to be only transitioned between lock and unlock states with correct firmware and no validation being made -- ie., it's very nicely easy to brick)
[Sony Ericsson XPERIA X10 Mini] leminhnguyen0703:
Hey guys, I'm currently running CM6, and when I tried to upgrade to CM7, from the version with overclocking and undervolting added, my fone always reboot and lag continously, unusable until i restore using factory reset.It never happened with any previous version of CM7. A couple day back, I tried the overclocking tweak for CM6, and the same thing happens. I have to restore using Xrecovery. Does anyone knows what the problem is ? I really want overclocking function :(
[Sony Ericsson XPERIA X10 Mini] Mr.Krypton:
stable overclocking is 768 or less.... this much i knw some dev will help you
[Sony Ericsson XPERIA X10 Mini] anon67:
You did say that you used the overclocking patch , but did not tell did you use SetCPU with set on boot option ? Also what is ur max and min settings in setcpu ?

Anyways , not sure if you will now be able to go inside setcpu , since ur phone is restarting.

On mini pro , for me 780+ Mhz caused reboot. And if you have setcpu set to set it on each boot , then u will end up in infinite loop. For me it happened , but luckily if you do not touch ur phone (touch screen touch ;-) ) after a reboot , it wont reboot (atleast for me).;

So after a reboot :

1. connect phone to PC

2. use adb to uninstall the setcpu

3. reboot again.

This time you should not be having trouble as your phone should behave normally.

Again install setCPU (if you are interested still !!) and set the max to anything below 760Mhz.
[Sony Ericsson XPERIA X10 Mini] batwingnz:
What should we do if there is the reboot loop but setcpu is already uninstalled? Or if its installed but overclock is not set on boot?
[Sony Ericsson XPERIA X10 Mini] leminhnguyen0703:
Hey thanks for the help, but I can't do anything at all with the phone after the patch, with or without setcpu. It booted up, on lockscreen, lag for 30sec and continous reboot then -.-''
[Sony Ericsson XPERIA X10 Mini] anon67:
will make much more sense letting people know what you have done. Just the normal OC module should not have ur phone rebooting.

Does the phone reboot if you do not touch it but just keep it connected to PC ? please answer or else its very hard to try and figure out an answer.

if you feel its causing an issue , then u got to figure out a way to disable that module.

The module gets loaded as x8oc.ko.

In CM6 - v4 , this is not there by default but will appear in hw_config.sh if you have patched it.

So u got to get /system/etc/hw_config.sh and comment out the line insmod for x8oc.ko and anything associate with it .
[Sony Ericsson XPERIA X10 Mini] batwingnz:
Did fresh install of v4 after factory reset, resulted in no overclock options and completely stable. Installed oc zip from cm6 oc thread which resulted in infinite reboots even when attached to pc, was not able to touch any settings. Reflashed v4 without factory reset and am back to no overclock and completely stable. Setcpu was not installed, recently installed on fresh v4, no options beyond 600mhz.
[Sony Ericsson XPERIA X10 Mini] anon67:
yep ..if u did a fresh install of v4 , it means the overclock is not functional as the module is not loaded in it.
[Sony Ericsson XPERIA X10 Mini] batwingnz:
Changelog for v4 says overclocked and undervolted, but never mind that. Installing oclock.zip as per instructions in that thread results in infinite reboot, does not stay up long enough to use adb shell or access setcpu. The fresh install of v4 does have overclock options in cyanogenmod settings, but values cannot be edited.

Are you implying that v4 will not support the oclock.zip or simply replying only to first sentence of explanation?

Any help is appreciated.
[Sony Ericsson XPERIA X10 Mini] anon67:
ok . so let me explain ( i know its quite hard on both ways ) . The overclock module (x80c.ko) is NOT loaded by the default V4 version. So if the module is not loaded Cyanogen setting will only show you the max (600 Mhz i thnk) and min (122 Mhz - I think). I did not find that module to be loaded in any of the init* scripts or in hw_config.sh. But the module is present with the build in the modules folder (but not active as its not loaded with insmod).

So if you just coming just after applying V4 - with no other patch. Then you do not have active overlocking module - hence overclocking wont work with SetCPU. Cyanogen does NOT provide you a scope to change the frequencies - you need setCPU - (you can change the max thru command line after enabling the module).

Now if you have patched the same with the oc patch , you have the module active (insmod works) , but another line of it in the hw_config.sh (patched one) does not become effective for me (some people reported it worked for them though).

The constant reboot which i faced was because i (with the help of SetCPU) had set very high frequency (causing the system to become unstable).

So inorder to fix it , you can do the following:

1. Full wipe through xrecovery

2. Apply V4 again.

3. Change hw_config.sh to add the insmod command to load x8oc.ko module.

4. Reinstall setcpu and see if you can set the max/min to safe values (say around 719 Mhz max and min as 300 or 400 Mhz).

5. If you see the system to be stable , well and good.

If by above , setCPU does not detect max/min (max should be 825 Mhz) , then you need to add the echo x27 > /proc/x8oc to hw_config just after the insmod line of x8oc.ko. (you will see some threads where sleep 2 or sleep 4 is also asked to be put in , but for unknown reason it did not work for me).

Whew!! that was long :) . But thats the way it worked for me.

For me when the reboots were happening , i had my phone connected to PC , but i was not touching the phone at all (if i touch , it used to reboot - but adb shell was working if i do not touch it).

If any further clarificaiton required , i would be glad to assist.

But before puting in a query , please try and give as much information was to what you did after which the reboots started (not just saying that i did the OC patch - cos for me just the OC patch never resulted into the reboots).
[Sony Ericsson XPERIA X10 Mini] batwingnz:
Thank you for that awesome explanation and sorry for the lack of relevant information earlier in the thread.

Should be able to do as you have suggested when I get home and will report back, either way your explanation has made it all clear and I can see where I have missed important steps. Many thanks.

Edit: edited hw config.sh, inserted insmod, sleep and echo lines. Stable ay 729, reboots at 748. Thanks again :-)
[Sony Ericsson XPERIA X10 Mini] anon67:
good to know it worked !
[Sony Ericsson XPERIA X10 Mini] WibyHere:
same problem with my minni....:( reboot again and again:eek:
[Sony Ericsson XPERIA X10 Mini] doixanh:
Check your baseband, it must be xxx15 or it won't work because of different kernel :)
[Sony Ericsson XPERIA X10 Mini] leminhnguyen0703:
Nah got everything rite, basband and kernel, just when I apply the OC tweak, the fone would boot up, but freeze at lockscreen. IT DOES BOOT UP, BUT STUCK AT LOCKSCREEN !!! So bloody annoying, then stuck on bootloop until restore /system using xrecovery
[Sony Ericsson XPERIA X10 Mini] batwingnz:
Don't apply the oversclock tweak from xrecovery, instead try editing hw_config.sh to have:

# x8 overclock

insmod /system/lib/modules/x8oc.ko

sleep 2

echo x27 > /proc/x8oc

I believe i had the same issue until i did this, then it was stable.
[Sony Ericsson XPERIA X10 Mini] martintspedersen:
my mini max cpu is only 691 mhz or else the reboots and its laggy as hell. LIKE all your work every wear:-)

have your lovely MDDI on to it help alot but still scrolling lag. maybe fresh install via seus?
[Sony Ericsson XPERIA X10 Mini] kersh:
wrong thread
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Howdy, I need some help, that I obviously can't fix myself. I did some looking and apparently found that the status 7 is when the md5 sum of the phone and the file don't match. Currentlly using CM7 Nightly 39, tried flashing 40, and got the status 7 update; never have had a problem flashing.

I tried re-downloading the file from the CM mirror network, no dice. I also tried re-flashing amon_ra 2.3 recovery, no dice. I can still use my phone perfectly fine. My next guess would be to try switching to clockwork, attempt to flash, then flash amon_ra [doing now].

If anyone has any ideas, I'd great appreciate it. :)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
I think I've narrowed it down to the actual night 40 file, as nightly 39 still flashes without a problem. Any help is still appreciated.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I haven't downloaded that nightly yet, but once im awake in a little bit Ill download and see if I have any issues with it. Although Im not on the same version of recovery at the moment. Have you tried flashing some other files, even more than just nightly 39, to see if it happens with anything else. Did you try downloading the nightly 40 again?

Perhaps its a bad download?

Edit: lol, told ya I still need to wake up... Saw that you already tried downloading it again. Sorry bout that.
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Lawlz, its all good man, it happens; but yes, I am able to flash other files from recovery.
[EVO 4G Q&A, Help & Troubleshooting] dirkyd3rk:
You know nightly 40 was jacked up right. So many people had the same issue but I don't know how old this thread is lol.

~ d3rk
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
I didn't hear about it, nothing came up on the search. I figured it was the file cuz I can install other roms. But I still wanted to check, and its only like 3 hours old. But thanks man.
[EVO 4G Q&A, Help & Troubleshooting] dirkyd3rk:
Wanna give it one more shot? #40 nightly build had the cwm commit that could be causing problems for some. Koush reversed the commit.

This is #40 w/o that one commit for clockworkmod.

http://www.mediafire.com/?06hmakkdtkndp0n

~ d3rk
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Thanks again; I'll try it in a few, as mediafire refuses to download. xD
[EVO 4G Q&A, Help & Troubleshooting] plainjane:
I can't believe there's something you had to ask a question for... I really thought you had the Evo encyclopedia stored in your brain :P
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Lol I do..sorta :p. I was surprised too. But I did have it narrowed down the to problem [which I was correct] but I'd had to make sure. :)
[EVO 4G Q&A, Help & Troubleshooting] dirkyd3rk:
Yeah he does, this guy above me owns the Q&A section, this is his territory. You're a walking evo wiki! Lol

~ d3rk
[EVO 4G Q&A, Help & Troubleshooting] gpz1100:
Are you sure that's what that error means? I have RA's recovery, the one with the signature checking off, and still got the same error. Although, I suppose sig checking and md5 are not quite the same thing.