Related
Hi,
I'm looking for some advice about my attempts to put a new ROM onto my phone (HTC Tattoo currently running Android 1.6). I'm struggling to copy an image file to the sdcard. Basically, I can copy the file to there from my PC but adb can't see the contents of the /sdcard folder from within the shell. I also can't use adb push to copy anything to /sdcard. I just keep getting permission denied errors or file not found errors.
I've followed the procedure to root the phone and all *seems* to have worked OK. When I go into the shell I can su and run all the other commands I try work OK but I just can't see the content of, or copy to, the sdcard.
My confusion is several fold:
1. How can I be sure the rooting has happened successfully? I've read in other posts that people get a message on the phone when they run su in the shell. I don't - so does this mean that I'm not rooted??
2. Assuming I am rooted properly, why can't I see the /sdcard folder? I've tried all sorts of things including creating a gold card but that also fails because the sdcard is not visible to adb.
3. Finally, what about unlocking the phone? I thought creating a gold card would unlock it but that process fails as described above. Do I need to get the phone unlocked before the rooting will work properly?
I don't really want to pay the £20 to get the phone unlocked if its not going to make any difference. However, if it means that the rooting will work properly (assuming it hasn't done yet!) and then everything else will fall into place then I'm willing to give it a go.
Hope someone can help clear the waters for me,
Martin.
My phone is a HTC Tattoo currently on Android 1.6 and the phone is locked to Orange.
To ensure rooting was successful, you can download root checker from the market
I AM NOT RESPONSIBLE FOR ANY HARM DONE TO YOUR DEVICE THROUGH METHODS MENTIONED BELOW. THESE METHODS WILL DOWNLOAD UPDATES THAT WILL WANT TO INSTALL. DO NOT INSTALL THEM THEY MAY BRICK YOUR DEVICE. STICK TO THE INSTRUCTIONS BELOW AND YOU SHOULD BE FINE.
Also note it may be weeks, perhaps months before Atrix 2 updates begin rolling in. It's a very new device!
Now, the fastest way we are going to get this Bootloader unlocked is with a little ol' fashioned teamwork. These methods have worked for other devices but require some participation and patience.
Previous devices having used the method:
Bionic
ATRIX 4G
Here are the methods we will be using:
1.Motorola, ATT SBF files for Motorola Atrix 2
2.Project Cheesecake - finding update versions on Motorola servers
1. SBF files
If you or someone you know is able to provide SBF Files intended for the Atrix 2, you can post them here or email them to me at [email protected] if anonymity is an issue.
2. The tried and tested Project Cheesecake!
Automatic Method:
What you will need
1.an ADB setup.
2.Obviously, Root.
3.ClockworkMod Recovery set up on the phone.
4.You should have an FXZ Ready in case you mess up.
5.Root Explorer from market
Now an app does it all for you. Imagine that.
1. Okay, so, download THIS APP RIGHT HERE.
2. Install the app on your phone.
3. Open the app. Click the first button.
4. Reboot.
5. Open app, click second button. Select a server. QA And Staging servers seem most common for updates, but we need to check them all. The default is in Production -> master-blur.whatever.com if you need to get back to it.
6. now click third button in app to check for update. click setup (the moto account thing is bs). Now if it gives you a wifi error, that means the server is down that you chose. If the server is up it will check for an update.
7. If that didn't work, select a new server with button 2, and then check again with button 3.
8. Any comments in this post about the ghettoness of my app will result in replies including but not limited to A) Slander, B) flaming, and C) death. Try to keep the thread pretty on topic to cheesecake method and other info. I know my app can be refined, jcase has been giving me some tips on streamlining my programming and su permission reduction, but it does good stuff, don't worry. It even remounts system as RO when it uses it.
9. godspeed, guys.
What do I do if my phone finds an update?
if you are uncomfortable dealing with it for sake of bricks / other bad stuff, let someone else know or post it in the thread. It will be attended to properly.
DO NOT INSTALL IT. IF YOU FEEL COMFORTABLE YOU CAN DOWNLOAD IT
Depending on what the update contains, it could brick your device. Get in touch with a developer ASAP if you don't know what to do. Post in this thread which server you found it on. load up adb. The file you found should exist somewhere in /cache. pull it to your computer. Then delete it. Be warned that the update after downloaded tries to install every 2 minutes and while typing a text i accidentally clicked install once. I almost messed myself up.
log onto chat.andirc.net and go to #bionic. You might find me in there.
Log onto irc.freenode.net and join #droidbionic and #bionic-dev. The bionic-dev channel is ONLY for dev-related talk. If you just want to kick it, converse in #droidbionic.
Someone experienced here can help you, and let you know what you've found.
If you liked my work here, click the thanks button at the bottom of this post! Thank you all for reading.
Click to expand...
Click to collapse
Link to original topic:http://forum.xda-developers.com/showthread.php?t=1281675
Manual Method:
Instructions:
List of servers:
Code:
master-lab.blurdev.com
master-demo.blurdev.com
master-dev.blurdev.com
master-qa1.blurdev.com
master-qa2.blurdev.com
master-qa3.blurdev.com
master-qa4.blurdev.com
master-staging1.blurdev.com
master-sdc1.svcmot.com
master-blur.svcmot.com
master-homer.blurdev.com
master-bart.blurdev.com
master-lisa.blurdev.com
master-maggie.blurdev.com
master-marge.blurdev.com
master-bqa1.blurdev.com
master-bqa2.blurdev.com
testcloud01-sdc1.blurdev.com
1.Root the device
2.Navigate to /system/etc/motorola/com.motorola.blur.service.blur/ in a root file explorer [ie. Root Explorer]
3.Edit data_wifi_only_settings.mkitso. Replace "data_wifi_only_feat_avail=1" with "data_wifi_only_feat_avail=0"
4.Edit defaults.xml. Replace the entire file contents with:
Code:
<map><string name='blur.service.ws.useApnProxy'>0</string><string name='blur.service.ws.masterCloud'>master-lab.blurdev.com</string></map>
5.to /system/etc/motorola/com.motorola.blur.setup in a root file explorer and Edit defaults.xml. Replace the entire file contents with(you settings may already look like this, if so ignore it):
Code:
<?xml version='1.0' encoding='UTF-8'?>
<map>
<boolean name='AllowActiveSync' value='true'/>
<boolean name='ShowSkipSetupMenu' value='true'/>
<boolean name='ShowConnectionChooser' value='true'/>
<boolean name='ShowDataSaverInSetup' value='true'/>
<boolean name='WifiPreference' value='true'/>
<boolean name='loc_consent_unchecked' value='false'/>
<boolean name='CloudPreference' value='true'/></map>
6.Wipe data and cache
7.Navigate to Settings > About Phone > System Updates
8.If it says "Update Available," let the update download. Do not install the update, because it could potentially brick your device.
9.Pull the update.zip file from /cache [Root Explorer or ADB] and upload/post the file for developer interest
10.Continue to test the next server. Navigate to /system/etc/motorola/com.motorola.blur.service.blur
11.Mount the folder as read/write
12.Edit defaults.xml. Remove "master-lab.blurdev.com" and put in the URL for the next server.
13.Repeat the steps from "Wipe data and cache" every time.
Click to expand...
Click to collapse
Credits: They all deserve thanks so if you see them around the forum, or wish to go to their original topics click that button!
- eval- for his initial discovery on the Atrix 4G
- Navalynt for scanning servers
- SamCripp, the2dcour - working on "Project Cheesecake" and "Pudding" unlock projects
-kennethpenn for the instructions as well as setup.
-Phydo for automatic method and app!
We might try this. It automates the process. All the credit goes to phydo for this though. I am looking at it now to see if we can try it on our Atrix 2
http://forum.xda-developers.com/showthread.php?t=1281675
Jim
I saw that as well... Let me know if its working on the ATRIX 2 and I'll edit the topic accordingly. Thanks again for your continued interest, I really appreciate it.
Sent from my MB865 using XDA App
Phydo's app works beautifully. I installed and ran it on severall of the servers, if it asks to setup and account just click setup... then if it asks to setup a wifi connection then that server is down, which I am getting on most of them right now as would be expected.
Jim
Works flawlessly on my end too.. updated the first post with instructions.
Sent from my MB865 using XDA App
Just pulled Blur_Version.55.11.16.MB865.ATT.en.US.zip with cheesecake.
Judging only by the number in the filename, this is the stock version of blur... probably.
Can't post links so...
Awesome man! I'll check it out!
It's only 50 megs so I don't think it's the full filesytem.
This might be the update from the mythical 2.3.4 version listed on the moto dev site.
edit: I see some recent timestamps... system\etc\motorola\ap_flex_version.txt
Code:
GAS_NA_EDSNGBATT_P015
Sat Oct 29 10:13:33 PDT 2011
derp derp
Code:
Blur_Version.55.13.15.MB865.ATT.en.US %Blur_Version.55.11.16.MB865.ATT.en.US
Went ahead and too a giant leap and upgraded.
After a few harrowing minutes, it was updated to 55.13.15
Android version is 2.3.6
Baseband is
2011-10-28 12:44 Off.Bld
LUD_EDISON_R1D7_PATCH_34_111028_1226
Webtop has been updated, looks like firefox 7.0.1 is installed now, can't test it myself.
Getting prompts from motorola to "upgrade".
Lost root in the update. Going to try to get it back...
Edit: Root works!
Code:
fastboot oem unlock
... FAILED (remote: unsupported command)
what files were in the update? was there an fxz or an sbf? were there any files with I think mbl in the name? Those would be the bootloader, if so we need to take a look at them. I will put it down and check it out.
I am not quite ready to install that yet, since I am on the right track to have a FULL ubuntu desktop running in webtop, right now I have broken tomoyo, so no facls, or security on the webtop files, and I have a terminal and sudo, as well as synaptic, so I will hold off on 2.3.6 for now, since there is a webtop update in there.
I will start a new thread for the webtop stuff once I have more. Now I need to get with tallnerd1985 to get webtop2sd working on our phones.
Jim
Thank You for warning everyone else even while you are still having trouble. You can take it back to At&t/Bestbuy or wherever you bought it - They won't know and 99% don't care especially about the Atrix 1 or 2...
Just act PISSED! If anyone asks you a question...
Looks like motorola really is trying to push an update to me, 15 MB file update to 55.13.16. I'm not going to touch it for now. Gotta get some sleep
Don't see any SBFs or FXZs...
This is my first rooted android phone, so i'm just flying blind here.
Now that I can post links, here's the one linked to through tinyurl above.
Ok, so in the 55.13.15.MB865.ATT.en.US file, there are 2 boot loaders, one is called prologue_loader.ldr and the other one, which I am guessing is the one we already have is called production_loader.ldr
This will require some more looking to see if the prologue_loader.ldr is unlockable, so that they can load thier updated image, then relock it with the production_loader.ldr
This might be good news and it might be nothing, but I will keep everyone posted, with what I find.
Jim
Keep up the good work guys
Try to find the stock build as well, because if that is found i could probably unbrick my phone!
moofree said:
Looks like motorola really is trying to push an update to me, 15 MB file update to 55.13.16. I'm not going to touch it for now. Gotta get some sleep
http://dl.dropbox.com/u/14536681/Blur_Version.55.13.15.MB865.ATT.en.US.zip
Don't see any SBFs or FXZs...
This is my first rooted android phone, so i'm just flying blind here.
Now that I can post links, here's the one linked to through tinyurl above.
http://dl.dropbox.com/u/14536681/Blur_Version.55.11.16.MB865.ATT.en.US.zip
Click to expand...
Click to collapse
Jimmy273 said:
Try to find the stock build as well, because if that is found i could probably unbrick my phone!
Click to expand...
Click to collapse
Ok use the link above and try to get it on the root of your SD card, I am not sure if that zip file work or not, for CWM or fastboot, if you can connect to ADB with fastboot, you should be able to flash it from that.
Jim
Ok .. this is driving me nuts here. Trying to apply the Blur_Version.55.13.15.MB865.ATT.en.US.zip update to my Atrix 2 .. since there is NO WORKING ClockWorkMod that can be used .. tried doing it other way that jimbridgman suggested and that was fastboot.
Well .. that doesn't work either .. receive error message:
>fastboot -w update Blur_Version.55.13.15.MB865.ATT.en.US.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Anyone else have any ideas of how to apply this update ?
LordGeek said:
Ok .. this is driving me nuts here. Trying to apply the Blur_Version.55.13.15.MB865.ATT.en.US.zip update to my Atrix 2 .. since there is NO WORKING ClockWorkMod that can be used .. tried doing it other way that jimbridgman suggested and that was fastboot.
Well .. that doesn't work either .. receive error message:
>fastboot -w update Blur_Version.55.13.15.MB865.ATT.en.US.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Anyone else have any ideas of how to apply this update ?
Click to expand...
Click to collapse
Good question, though you'll need to start from the first file...
Blur_Version.55.11.16.MB865.ATT.en.US.zip
I think the filenames are for the versions that the patch gets applied to, not the version it'd be updated to.
This is all new to me, I'm guessing you could boot up with VolumeUp+VolumeDown held down, choose the recovery mode, and do volup+voldown for the recovery menu and choose update, and the zip from that menu...
Edit: This works. Updated from 55.13.15 to 55.13.16
Baseband got pushed back a few days
2011-10-25 11:19 Off.Bld
LUD_EDISON_R1D7_PATCH_33_111025_1101
Lost root again, but thankfully the zergling rush is a highly effective strategy still
-=Insert warning about updating being AT YOUR OWN RISK and not being responsible for bricks etc... =-
Additional warning that this might cut the phone off from official OTA updates from Motorola...
@moofree:
You are correct, I was successful in getting the 2 updates on, and yes, root was lost. However, I was unable to get the root back !!
Tried manually, tried the 1-click.. Neither would give root. So, since I just received the phone the day before from BestBuy, I did the next logical thing.. Bricked it and returned the phone defective.. LOL
So, now I have a replacement, new Atrix 2.. I'm leaving it exactly where it is until either the OTA's come through the right channels, or something more permanent and correctly working has been done for unlocking the bootloader and rooting.
If not.. 30 days from 11/01/11.. Options are still open with the HTC Vivid and SGS2 Skyrocket.
Sent from my MB865 using Tapatalk
I Want to reiterate to everyone who is trying to help unlock the boot loader by using the cheesecake method here that you don't want to apply any of these updates directly. Motorola always relocks the bootloader with 99% of these updates. It will be one of the development versions that we are looking for, you just want to download the zip file and upload them with a link attached in here to grab the file you get.Then we can have a look at the files contained in them.
We are looking for the magical developmental unlocked bootloader that we can make our own update zip file, with just the bootloader that is unlockable, in it.
Again don't apply the updates that you get from this process. You may brick your phone or worse, permanantly be unable to root or unlock the boot loader.
This is a cat and mouse type of a thing wiith thses big phone makers.
Jim
Sent from my MB865 using XDA App
I have a My Touch 4G currently running 2.3.4 that I want to downgrade to 2.2.1 so I can root it. I am unable to get it to take the PD15IMG.zip to take once I hit the bootloader. It says its extracting fine, but the phone never reboots and if I manual reboot it, it boots up on 2.3.4.
I was using the following instructions.. cyanomod instructions and I did everything fine but get stuck with step 8.
Here is a copy of my ABD session:
Open to any suggestions.. I did some searches but no luck.
I tried to paste the URLs for the pastebin and the instructions I used but was blocked because of the stupid spam rules for newbies.. so PM me and ill send them to you.
Also as you can see I have been a member for over a year now, I just do a lot of lurker so I don't post much. I usually can find my answer searching without asking but I am stumped on this one.
This exact same thing happened to me.
The problem was that ADB wasn't pushing the entire PD15IMG file to the SD card. Every time I tried it it was missing exactly 53 bytes. (You can check this by looking at the file size of the PD15IMG on your hard drive and see if it file size matched EXACTLY on your SD card down to the single byte.)
I fixed it my using the file manager on my computer to just drag and drop the PD15IMG file onto the SD card. For some reason that transferred the entire file without problem.
I ran through the steps again and viola, 2.2.1 upon reboot.
You might also have a corrupted PD15IMG file. You can fix that by re-downloading the file, preferably from a different source just in case.
why u need downgrade 2.2.1 ?
@skipjacks - ill try that, on the 2nd attempt at it yesterday I manually copied of the file over after I downloaded it from another source, yet it still would not upgrade. I will give it a 3rd shot and report back.
@Ridofu - I am tried of having the HTC offical software crashing on me. I would like to root and then install CM7.1
Same thing..
I downloaded PD15IMG.zip manually over the HTC E:\ drive I have mounted.. did all the commands again, went to bootloader, it says it installs but then never reboots or does anything...
the image say loading, and I see a blue bar on the right top corner... then it switches to checking with a yellow/orange bar in the right top corner..
then it just goes back to the main screen and doesn't do anything..
all i see is fastboot, recover, factory reset, simlock, image crc
Id love to run the adb shell md4sum /sdcard/PD15IMG.zip but everytime I run it it comes back with md5sum: not found
Any ideas?
How I rooted my MT4G
Try this guide:
http://androidrootking.blogspot.com/2011/10/how-to-root-your-mytouch-4g-original_12.html
This is a step-by-step guide to root your MT4G. It has a link to another guide that will help you downgrade your phone.
You must downgrade FIRST, in order to root, because the root tool (gfree) DOES NOT WORK with Android 2.3, it only works with 2.1.
If you really like GingerBread, and want to keep root, go here AFTER you're rooted:
http://forum.xda-developers.com/showthread.php?t=1264704
—E!
Do you have MicroSD card reader in/for your PC?
Try to use it instead of copying the file through the phone.
@Ericm301 that is the exact method I have followed and it does not work. I have done the Push method, I have done the copy via USB cable to the E:\ drive that is mounted and neither allow me go to bootloader and load the file.
@Jack_R1 I will try getting a Micro usb adapter and copying the file over as well.
I tried taking the SD card and copying the file manually, I also tried to use the file from a 3rd source. It will not downgrade. I can post a video if you want to see it fail.
Just wanted to give a update. I did the manual downgrade 2 or 3 more times and I finally gave up on it.. then I switched to Fastboot Downgrade method and it worked perfectly the 1st time..
man what a frustration!
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"
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