Database Info

Read everyfing i can find on Bigstorage and still no success

Hi I know the big storage hack is plastered all over this forum but i still cant get it right.Some one please help me!
Ive got a magician with rom version 1.13.00 WWE radio v. 1.12.00 (i used to have 1.12.00 but i upgraded it by accident.<I woz finkin of it anyway>)
I fink Ive tried every procedure possible but always have problems but basically this is what ive done:
1.Using OS image tool ive copied my rom to pc.
2.Ive changed the 80 00 00 thingy to b8 01.
3.Ive tried to use the os image tool to write it back t ppc but it comes with a usb/communication error in programme A.Im using this way because I have only 32mb mmc card.
Any help would be much appreciated,
Thanks

wiki
Try the wiki (top right link on the page) & go to the magician section. It contains a description howto patch a shipped-rom, the one you used to upgrade to 1.13WWE, & get BS. Apperently you missed this method.
Cheers, M

I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth

I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth

Stop,
You're going in the wrong direction. The BS from shipped-rom method is about patching the provider supplied exe file. & after the patch you run it like a regular rom-upgrade. No SD or MMC involved!!! It's a rom-update via USB like the normal update.
pls read it once again @ the wiki.

ok thanks im trying that now.Im stuck on getting nbfdec to run.Ive extracted it to the unzipped rom folder.I open ms-dos command prompt and drag and drop the .exe on the command line to save typing the path.The program runs but then it crashes.Can anyone help me?

Try putting everything in "C:\BS" saves a lot of typing errors including filename handling.

Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks

garethsimpsonuk said:
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks
Click to expand...
Click to collapse
Hi Rod,
To go to C:\BS from your personal doc&settings type on the commandline:
cd \ [Enter]
now you should be in C:\
then type:
cd bs [Enter]
now you should be in C:\BS
Works for other directories too.
Cheers, M

Thanks, that helped me a lot.Ive done everything els now so I converted it back to nbf and then executed the maupgrade_noid.It checked device info then displayed the rom to and from screen and both were blank.I proceeded and it displayed the 'success' screen but nothing had actually happened on the ppc.Ive tried the other upgrade program and the one thats cracked on the site.
Any help would be much appreciated
Thanks

Did you reset after the update process finished? & if so did it boot normally? & if so did you look at the internal storage folder size? Cause that's the only thing that's changed & the ext-rom has disappeared. Oh & you shouldn't see the customization start after a hard-reset...
btw rom to & from shouldn't be blank, pls run the update program without patch cause I think the editing somehow invalidated the shipped-rom. The original upgrade program should work & if so you know what's going on. If the original program fails there might be something with your device.
So start the plain shipped-rom first to find out..

Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8

Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8

The header contains info about romtype & provider name, probably some things more I'm
not sure about. The reason for changing it is to avoid errors like the country id error. With the use of maupgradeut_noid it's less important.
One thing I'm questioning is the reason why some of us have probs with connecting to the, I believe, special O2 services. Some claim there not able to connect anymore... Can some other setting as well. I'm on T-Mobile & everything works fine.
Basically if the upgrade was succesfull, you have an enlarged storage & the rest of your device will be working as before.
Cheers, M

how much space would i have in my main memory now? i have a 64+64 system (O2 Xda Mini) now branded to T-Mobile 1.33 and now applied the new patch (BIG STORAGE) using the Wiki Information guides. However any idea how much FREE space on first reboot i should have.

did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?

nevermind got it
Total Main Memory - (FREE MEMORY) - 43.99MB Storage / 25.54 MB Programs! woo hoo this is HOT

shivam said:
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
Click to expand...
Click to collapse
First boot takes much more time than next boots.
Have fun, M

all,
look over here.
cheers!

Sorry to say, but it's old news. We got a thread about it for three months now I guess with that method. Problem is you always need to update first & then dump your rom again. & somehow not all dumps are accurate. The brick change with a SD is larger than with a shipped-rom.
M

[REF][05.04.08] Bootloader (mtty) commands [ONLINE]

Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls

wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader

Very nice....
task command does not work for me...
you may want to add "lnbs"

htctouchp said:
wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Click to expand...
Click to collapse
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?

ababrekar said:
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?
Click to expand...
Click to collapse
snoopy pro is just a usb port sniffer, it will record everything that passes a port. u cant actually see the flashing data, but u can make a log file out of it and after the flashing is over, u can analyze that log file. that post which u've given as reference, does the same thing. it records the session (usblog data) using snoopypro which later on u can open in hex editor. just try it out while flashing a ROM, and analyze the log later on. may be u can also find something useful

Hey guys!
Has anyone used the ls command?
Is it used like:
Code:
>ls
or
Code:
>ls c:\dump.nb
or
>ls \"Storage Card"\dump.nb
I tried the first one and waited,waited,waited...but (1)I got bored and (2)nothing was really downloaded to my pc so aborted You can see what mtty shows right below:
Code:
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
*Edit1:I'm asking for this command because I think it's a way to dump your rom(IPL,SPL,OS,etc.)
*Edit2:I found this nice tool, but it seems it doesn't work for my phone!Could anyone give it a try too and confirm?

Reading through an SPL.nbh file with a hex editor yielded the following known commands (as listed in the first post here):
SetDsbDBGMSGT
ClearDBGMSG
ReadExtROM
WLANReset
SDSelect
emapiCountryID
emapiInit
emapiWlanMac
emapiPwrDwn
emapiRead
emapiTest
emapi
getdevinfo
ruustart
ruurun
progress
wdata
password
set
SetDebugMethod
checksum
ResetDevice
BTRouting
lnbs
ls
Attached is a text file with a copy/paste of the results from issueing these commands in MTTY.
From what I can figure out you can load an NB or NBH file using lnbs or ls, BUT only ony a Super-CID or CID-unlocked device otherwise you get an error
Code:
Not allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)
So, bootloader commands issued through MTTY can be ery usefull for retrieving your Device ID and Model ID, and once CID unlocked you could load an image through MTTY instead of using RUUloader etc, but it looks tricky to figure out how to get things working for a CID-locked/bricked device.
Logic would indicate that somewhere in the NBH file would be a checksum relating to the Vendor-ID and/or Device-ID, having an NBH file where the ID and checksum don'y match would result in the 270 error - corrupt image (one could assume).
So, the big question in my mind at the moment is "How can one figure out where the checksum is in the NBH file". If we can figure out the address of where it resides, we could maybe use the checksum command to pull that info back? Then theoretically, to fix a bricked device all we would need to do would be hex-edit the NBH file to replace the vendor-ID and checksum with the correct one for the particular bricked device?
Thoughts/comments from any of our resident experts in USPL etc would be greatly appreciated!
Craig

good effort Craig
but how to revive an Elf(in) stuck in bootloader is still a mystery for most of us. lets hope for the best that someone out of us can unfold this mystery someday

Interesting!!!
Does anybody knows more comands Im searching for a hardreset via MTTY or a Cleaning DOC leaving behind the task 28 cuase in cmd> dont works... only in usb> i used it just once in a G3 HTCwizard then i cant do it anymore.
Maybe "format" command before the CMD>

kokotas said:
Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls
Click to expand...
Click to collapse
Hi do you know a command for unlock the CID, because i tried to flash my phone P3300 an his broken, I can enter only in bootloader, every time when I try to intall a rom shows me error 300, so I think I didn't unlock the CID first time! Thank you and sorry for my english

Hi
You mention your device is P3300, this forum is about the Elf/in P3450 and P3452. No surprise it doesn't work ...
Use this link http://forum.xda-developers.com/forumdisplay.php?f=316

Unable to downgrade an RC9 model DREA110

When i follow all of the sticked guides, and the ones in the announcements i keep ending up with the same screen..
I have tried this with 2 different sd cards, both 2gb scandisk ones. Followed the guides..
Here is what i have tried so far, even though its listed in the guides..
Formated sd card both trying through the usb cable on the phone, and on an sd card reader on xp. to FAT 32, with allocation of 4096 (might have mispelled the number), done this using both the built in format function gui, and the cmd way using /fs and /a parameters.
I've tried both the RC7 and the RC29 versions of the DREAIMG.nbh file, even tried renameing to dreaimg.nbh, dreaimg.NBH and DREAIMG.NBH.
When i hit cam key + power, i get the first screen with a RGB and white row, and then it loads the bootloader aka grey screen. And when it gets past the second stage of loading it, i get a red number 00028002 followed by a blue text, Not allow.
Now it throws me back to the RGBW screen, with the Serial0 text to me..
The text otherwise available to me on the rgbw screen is as follows.
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RAID0-1.22.14.11
sep 2 2008.
When i check the about on the phone to get the firmware stats etc i get the following.
Firmware version
1.1
Baseband version
62.33.20.08U_1.22.14.11
Kernl version
2.6.25-01845-g85d4f0d
[email protected] #27
Build number
kila_eu-user 1.1 TMI-RC9 128600
ota-rel-keys,release-keys
I hope you guys have a solution for me to hack this nice little gadget, so that i can install my apps on the sd card, and not use space on the phone it self!! (and i gotta admit, being able to use a linux kernl, ex the ubuntu kernl, would sound beautiful to my geeky eyes!)

after the format of the SD-card you did not mention the qmat-procedure with a WM-device plugged in and using activesync.
i got that same error when i did not create a goldcard-image via qmat.
After using the qmat-steps it worked like a charm.
Greets,
JP

Cuz i couldnt find a way to get hold of a free Qmat program, i read around that in order to do the steps, one would need to buy the full version. In order to make the goldsomething..
Is there a link to the guide, that obviously made you successfull ?

Just got hold of an older version now However, when i hit save to wince sd, it goes throug with it and gives an ok, but i dont see any files on the sd card... logic ?

You don´t see the file goldcard.img on the card afterwards, but try it, it should work then!

Nvm It worked lol! Had to use Case Sensitive.. Yuck..

theorion said:
Nvm It worked lol! Had to use Case Sensitive.. Yuck..
Click to expand...
Click to collapse
can you tell me which you did wrong before?
because I met the same problem as you met.
THX alot

xwxxp said:
can you tell me which you did wrong before?
because I met the same problem as you met.
THX alot
Click to expand...
Click to collapse
You need to be 100% sure that the name of the file is exactly as it states, capital filename, small extension!
If u use a windows platform use cmd and verify by doing a dir or something
I guess the terminal would suffice for linux based platforms, as for mac i dont know!

how do I get out of the bootloader screen. I am on the same one as him but mine says DREA100. I have no options just stuck on the RGBW screen

Tyco, I found your message while searching for the answer. I think this thread is about rooting European G1s. I'm still searching!

okay cool! why do I always run into problems with doing these things ...

Can't do Firmware downgrade. Goldcard needed?

Hi people,
I'm trying to write this message with links to the relevant guides I used, but since this is my first post I can't add links to this. I hope it is still kinda clear what I mean.
I've got an HTC Desire Z (or G2 as I think it is called in the US). I bought it new from a store here in the Netherlands without any contract so there is no connection with any carrier. I now want to root my phone so that I can put Cyanogen mod on it. For this I followed some guides which led me to do a firmware downgrade. A guide on the cyanogenmod website worked all well, until I got to step 8: "Select Bootloader to flash the 1.34.707.3 firmware.". After doing this my phone gives an error saying the following:
CID incorrect!
Update Fail!
Press power to reboot.​
So after some searching I found that I need to spoof a CID using a "Goldcard". And here I'm kind stuck.
I searched around for goldcards and I found a lot of guides using some sort of Goldcardtool. This however, only works on windows, and since I am on (Ubuntu) Linux I can't use that. I tried to follow a youtube guide, which when typing "cat /sys/class/mmc_host/mmc1/mmc1:*/cid", ended in a "No such file or directory" error.
I then found a guide on the Droid-den website ("Android Guide: How To Create a Gold Card") with which I created two .img files after which I needed to do some hex editing. For this I installed a hex editor called ghex. I can open the .img files I downloaded, but I am not able to select my micro sd card in the hexeditor. I tried Bless hex editor as well, but no luck there either.
So my questions:
Do I absolutely have to use a goldcard (even though my phone is not carrier branded) or am I simply doing something wrong?
If absolutely needed, what am I doing wrong in creating the goldcard? Is there another (preferably easy) way to create a goldcard on Ubuntu?
All tips and hints are welcome!

Hi!
Use "cat /sys/class/mmc_host/mmc1/mmc2:*/cid" or "cat /sys/class/mmc_host/mmc2/mmc2:*/cid"

[Q] Something Missing from my files?

Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S

Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S

First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).

new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS

another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight

Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.

jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).

albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS