Database Info

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.

[GUIDE] Newbie's Step-by-Step: From Stock USCC Mesmerize -> Custom Rom/Kernel

THIS GUIDE IS SPECIFICALLY FOR THE MESMERIZE
Steps To Customize Your Mesmerize (For upgrading from any version to FROYO 2.2 EC10)
1.) Upgrade from any setup to 2.2 EC10 (Official Froyo) - If you have not already done so, you will need to upgrade your phone to EC10 2.2. If you have already, skip to the next step. (You can check this in "settings->about phone" under "firmware version" (should be 2.2.1 if you've already done this) NOTE: There is a custom rom listed in this post, I will detail that down below.
NOTE: The roms for this version come pre-rooted, so no need to root. However, if you have issues with superuser permissions (or are staying stock with root), you can use the SuperOneClick Root tool located here
If in the previous step you installed the leak that had the CWM upgrade pre-loaded or you have already manually updated CWM, skip step 2.- You know you have the updated recovery if when you boot to recovery it takes you to the red recovery with voodoo, backup and other options.
2.) Upgrade CWM manually (if needed) downloading this., (this next step by step will upgrade your recovery so that you are able to flash custom rom's/theme's/kernels.)
1.Shut phone off, pull battery out and leave it out.
2.Run odin (assuming you have it installed)
3.Load the cwm-recovery-all.tar file into the PDA spot
4.Plug usb into computer, then into your phone.
5.Hold the volume down key until phone goes into download mode, there will be a yellow android picture.
6.In odin, one of your com: spots should light up yellow - this means your phone is seen by odin (if not you may need drivers)
7.If above step is true, press start and odin will flash the recovery file to your phone. If all goes well the yellow box will turn green and your phone will power off.
8.Now you're able to boot into CWM recovery using the three button method (see glossary here)
3.)Upgrade Kernel With EC10 brought a new turn of events which thanks to jt has allowed fasicnate users to develop kernels which are compatible on the entire line of this model, so be sure to read phidelt's post on kernel's located here and choose one that is compatible with your rom. AOSP and MIUI require a different kernel, so keep this in mind as if you're restoring you may need to flash the appropriate kernel as the restore does not do this for you.
4.) Flash a custom ROM Choose from one of the Custom Rom's that we have out right now;
EC10 Pick and Pack DOWNLOAD HERE -- This is our stock deodexed rom with bloatware moved to a seperate .zip containing flashable packages with those removed apps. - < created by: phidelt82 >
EC10 Custom RomDOWNLOAD HERE - This is a custom rom built by phidelt82 which incorporates some aspects of AOSP into the EC10 rom - launcher and calendar are to name a few.
AOSP -DOWNLOAD HERE - This is a custom ROM/Kernel built with the android open source project code (by lmartin), one of the most "vanilla" rom's meaning no manufacturer's additions such as touchwiz. It's very lean and runs well, but is in BETA stage so beware it may not be for your daily use. NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
MIUI -DOWNLOAD HERE - This is a custom ROM running on the AOSP kernel, you can learn more about it in the thread linked here.NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
GAS EC10 PNP based rom -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Learn more about it in the linked thread.
HEINZ 57 EC10 (PNP/ED01/EC10 based rom) -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Thanks to Sbrissen, it has a lot of extra settings in the TM parts settings menu, allowing you even more customizing. Learn more about it in the linked thread.
5.)Flash a custom THEME Pick one that's compatible with the ROM you are running, from this list.
HELP MY PHONE IS SCREWED (GO TO STOCK 2.2)!!!: If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.NOTE: Being as going to stock means it's expecting your phone to be formatted to RFS instead of EXT4 (lagfix enabled) you should disable lagfix before doing so or you will have errors and md5 mismatches which will disallow you from flashing from recovery. If for some reason you can't access recovery you will just have to disable lagfix manually which is detailed in this thread here.
---------------------------------------------------------------------------------------------------------
==================================================
---------------------------------------------------------------------------------------------------------
THIS IS THE OLD GUIDE FOR CUSTOMIZING 2.1
When I began this process, I had zero experience flashing any sort of software to any sort of devices, and a very minor understanding of "rooting". After much research and crawling I was able to work my way through these steps with little headache, and learned a lot along the way.
Keep in mind there are many variations to each step, this is what worked for me the easiest as a newb.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps To Customize Your Stock Mesmerize (For eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal, trust me .
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two zip files located in the first post here
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator (Come with me if you want to live )
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the mesmerize. By now - you better damn well trust me , this is just what works with our model
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
You could always install the old Voodoo kernel located here, if for some reason you do not want to take advantage of the new, sound improved one.
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
Note: There are a few ways of getting into this recovery mode, the best way if all else fails is to hold phone from the back with left hand (thumb on volume button, in the middle holding both down and pointer on power button) hold these down until the mesmerize logo pops up then slide your thumb down a bit to volume down only (if you slip don't worry it might blink but it'll still go to recovery) Sometimes this is easier with the back case off. However the best way, is to download and use the QuickBoot app, it allows boot to recovery/reboot/poweroff options from the app.
4) Custom ROM : Download and install the ROM of your choice.
Just pick one from this list Here-They are all there along with other very useful links, read through the first post of each before you decide, some are plug and play some take a few steps first. These are currently only 2.1 eclair builds however right now they have an (somewhat unstable) 2.2 froyo rom/kernel that being worked on but is not quite yet ready for day to day use (some features are not working quite yet). But be patient because these guys will have something long before Samsung let's us have theirs, but who cares - "ours" will be so much better
HELP MY PHONE IS SCREWED!!! (GO TO STOCK 2.1): If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.
MASSIVE AMOUNTS OF Credit go to all of the OP's and many others (some included in my sig), these people are awesome, show them some love! Without them we would be stuck in stock US cell/Samsung HELL!
Final NoteIf you have any suggestions, additions, corrections, subtractions, or multiplications; PLEASE LET ME KNOW! I'm very open to all of the above and since this is now more of a community article let's stick to the android motto and keep it...open source

I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!

phidelt82 said:
I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!
Click to expand...
Click to collapse
Hey thanks, and believe it or not this is the exact reason I decided to put this together with this much detail (aside from answering someone's question). I figure, I'm no android developer but I can follow instruction and explain myself pretty well so I put this together to take some of that off of you guys. (A small token of my appreciation)

Nice work! Stickied for others to follow
Oh and love that comment:
Now open TerminalEmulator (Come with me if you want to live )
Click to expand...
Click to collapse
Gave me a good laugh!

the_scotsman said:
Nice work! Stickied for others to follow
Oh and love that comment:
Gave me a good laugh!
Click to expand...
Click to collapse
Haha well good and thanks, I almost put /badjoke at the end of that comment
EDIT: Edit to main post.

Good Job! This pretty much covers everything. Hopefully soon we can add to it :S

Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.

LaTuFu said:
Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.
Click to expand...
Click to collapse
Usually it only takes about a minute or so to complete. If it gives you problems, give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here.

Just wanted to say thanks for all the hard work and for the write ups for those of us new around here. You guys make the scene available for the rest of us.
Sent from my SCH-I500 using Tapatalk

Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.

Mesmerizeuser said:
Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.
Click to expand...
Click to collapse
It's not you. I believe Koush's repo is down right now. Hopefully it will be back up soon and you will be able to finish up.

Thanks for the heads up. Is there any way to get the recovery on the phone without using rom manager, or will I have to wait for the repo's to come back up?

never mind

It's back up. Just flashed to a voodoo kernel. Thanks again for the great instructions.

Very good write up.. You actually made it kind of fun to read if that makes sense.. lol

I seem to be running into problems. Whenever I go into recovery mode my phone doesn't verify the update.zip file. I was wondering how do I fix it or get another one? Also what part does this file play in changing roms?
Error:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Install aborted
Also very good write up A++ would hack again
Edit: got it working. I had to rerun redbend_ua and make sure it went through a full reboot and didn't stall. I think I wasn't giving it super user permissions. Great writeup thanks again!

thanks this is worked great for me on the Froyo step by step

jmtenny said:
thanks this is worked great for me on the Froyo step by step
Click to expand...
Click to collapse
Great, glad to hear it! This is a new addition and I've just made some more changes and also reformatted the OP so i'ts more obvious that there are two processes.

Thanks so much for taking the time to do this!
I'd like to think that now I have a better understanding of what I'm doing.

I'm having some problems and was wondering if someone could help me please.....
I successfully installed the EA11 leak and updated from 2.1 to 2.2. However, when I boot into the blue recovery and try to hit update.zip from there it just shows me an exlamation icon and never goes into the red recovery instantly like it should according to everyone's directions.
At thiis screen it will stay showing this icon, and the only way off of it is to hit the menu key which takes you back to the blue recovery screen. It then has a description below the blue text that says:
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to verify whole file signature
E:signature verification failed
Installation aborted.
Am I doing something wrong? Any feedback would be so appreciated.

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.

[Q] Sidekick 4G Woes

Argh! Pulling my hair out over this one. I've been flashing custom ROMs and rooting my phones for years now, since my old HTC G1. Even had KitKat running on my HTC Desire 4G!
... but this Sidekick is proving another matter. I've been through forum after forum, all saying the same things on how to root/flash this thing, but I haven't managed to get anything to work! So, here's step-by-step of what I just did and the result I get every single time, no matter the initial method:
1: Fired up ODIN3.
2: Wiped the user data and cache from the stock recovery (Android System Recovery (3e)).
3: Connect USB cable, reboot phone into download mode (using the battery-pull method).
4: Successfully flash to stock ROM, reboot.
5: Sign in with Google, enable WiFi.
6: Run SuperOneClick, reboot.
7: Grab ES File Explorer from the Market, after it updates.
8: Attempt to replace "recovery" in /system/bin with custom
... and here's where things break. Doesn't matter what version of SuperOneClick I use (and I've tried from 1.9.1 through 2.2.3), nor does it matter what exploit I select. What happens? Well... aside from everything on-screen claiming to be okay, and everything claiming it's working, once the rooting is "successful", I reboot like it says, see that SuperUser is in the applications, it shows me an su binary version...
... but anything that tries to run super-user (ES File Explorer included) that gets added to the super-user list simply does not work. I can't over-write the recovery, can't delete or muddle with anything that requires elevated privileges, and the ROM Manager for sure won't work because I can't get CWR installed.
I love my phones with keyboards. I really do. I'd love to keep this thing, but the stock firmware is driving me up a wall (especially that stupid media scanner). So if anyone has any ideas to throw at me, care to offer some? Haven't a clue at this point what I'm doing wrong.

Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around

demkantor said:
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
Click to expand...
Click to collapse
Awesome! I'll give this a go once I'm all done with today's activities and see if it works.
Well, apparently I have root access for the moment, but it is denying my replacing of /system/bin/recovery - in adb shell, it states "Filesystem is read-only", so I re-mounted /system -rw and no dice. Going to attempt to try again in a moment, after a reboot.

Okay, so since there's a problem with all of this, I'm going to try that second ROM (KD2 I think it was) - but as I recall, it was on a very slow server. Plus I have a load of things to do tomorrow, so it probably won't be until tomorrow evening sometime when I'll be able to flash it. Once I've used Odin to re-flash, I'll get back to you.

Well, I had to dissect "t839-Sidekick4G-UVKG2-One-Click.jar" and remove the xml file from within it, but I acquired the necessary package to upgrade to KG2 from KD1 through Odin3. Took a while to figure out just how to deal with it, and I was successful in flashing... and I even replaced the recovery file after rooting it again!
... however, now it just sits there at the "T Mobile Sidekick 4G" start-up screen when I attempt to boot into recovery, so now I'm preparing to re-flash it again to recover the stock recovery. So... still more on this, later.
EDIT: Also, I named the tar file "KG2OdinHeimdall.tar", since I basically ripped it right off the "HeimdallPackage.tar" file from the Heimdall one-click thing. Turns out, it apparently works just fine if you remove the .xml file from the original tar.

Finally!
I ended up having to use my own method to get the KG2 update installed because the one-click program kept crashing on me when selecting "Show all devices", and I opted to use AntTek Explorer (all you have to do is go into the program's options and it'll attempt to acquire admin privileges, if the device is rooted) to copy the recovery file to /system/bin - but your post worked for everything else, once I got past not being able to copy the recovery file.
I opted for the CM6 package and it's quite fast! Thank you loads, demkantor!

Nice! I'm glad all worked out well for you!
If you get a chance try out the one gingerbread ROM, its cool to see it running but there are still driver issues so keyboard is borked, really makes it pointless to have on this phone...
But there are a few nice froyo ROMs ready to be played with, someday development will hopefully pick up again
Until then, happy flashing!

Rom size errors

After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie

siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You would have a better chance of finding a working solution if you go to the M8 forum.
I'll bet @xunholyx can get you straight, he's pretty experienced with the M8 I think.

siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.

xunholyx said:
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
Click to expand...
Click to collapse
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!

siepod said:
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
Click to expand...
Click to collapse
Download this splash.zip, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Next, download this RUU onto your PC to update to Lollipop. Hook up your phone and double click on the download, then follow the prompts. You'll probably get a "fail hboot pre-update" (or something like that). The first run updates the hboot with old firmware. Just run the RUU a second time without disconnecting, and the conversion back to Sense will be complete.

xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
You are an absolute star, thank you. Will give this a bash when I get home from football later today, and let you know how I get on or if I have any problems. Great written instructions though, thanks!

xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie

siepod said:
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
Click to expand...
Click to collapse
I'm not sure.
Try the splash.zip download and instructions from here. It should be the same file, but trying another download and flashing from your PC might work better for you.

xunholyx said:
I'm not sure.
Try the splash.zip download and instructions . It should be the same file, but trying another download and flashing from your PC might work better for you.
Click to expand...
Click to collapse
Brilliant, tried those and it worked a treat. Then installed using the RUU you gave me, and as promised I was greeted with a full back to stock Sense version, and have been able to install the ROM I wanted. Thanks once again for all your help, truly appreciated!
I'm guessing it was the CID that was causing the error, if anybody has the same problem in the future and ends up on this thread. I'm guessing if I'd have changed the CID your method with the HBOOT would probably have worked too (as out of curiosity I tried the HBOOT method with your file and it then worked).
Thanks again, great to know there are people out there willing to try and help each other. :highfive: