Database Develop

[Q] Wi-Fi Only Stock Rom

I picked up a Streak 7 Wi-Fi Only yesterday. I was playing around with it and tried out the honeycomb ROm posted here. Decided I wanted to go back to stock but my Nandroid backup is gone (I think it was on sdcard1 and not sdcard2). I managed to restore a stock image I found here someplace but it is the t-mo image and wifi does not seem to work. Anyone know where I can get the wifi-only stock image?

Wrong section
Sent from my LG-P999 using XDA Premium App

ledname said:
I picked up a Streak 7 Wi-Fi Only yesterday. I was playing around with it and tried out the honeycomb ROm posted here. Decided I wanted to go back to stock but my Nandroid backup is gone (I think it was on sdcard1 and not sdcard2). I managed to restore a stock image I found here someplace but it is the t-mo image and wifi does not seem to work. Anyone know where I can get the wifi-only stock image?
Click to expand...
Click to collapse
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809

Can the original poster please confirm if this worked? I bought a Dell Streak 7 Wifi yesterday and would like to know.

andyo70 said:
Can the original poster please confirm if this worked? I bought a Dell Streak 7 Wifi yesterday and would like to know.
Click to expand...
Click to collapse
I can confirm this works!! Thanks so much op. I used this to get back from dj_steves honeycomb b3, and i did have to take a couple of extra steps. Once everything completed I was stuck at the dell logo. So I booted into recovery, to see what i could do, which was almost nothing other than clear cache etc. The internal sdcard would not mount so I couldn't put steves streakdroid 1.3 on it to try and see if it would flash. At a brick wall, I decided what the heck and I flashed the original recovery through fastboot. I rebooted into recovery and preformed a factory reset and and to my amazement was greeted with the lock screen a short while later. However, I had a notification stating that my sdcard was unformated or not the right system type. (certain on unformated cant remember the second suggestion, but i believe thats close). I went to settings>sdcard & tablet storage and pressed "format internal tablet storage", then mounted the internal tablet storage. And thats it. Back on stock 2.2.2 (wifi-only). Mega thanks op.

Thank you for confirming. Now I can try out the Honeystreak!

worked
this worked perfect for me.

i might add
i might add, that i had flashed the honeystreak in the dev section and my 7 would lock up, go to sleep (or in my case, lapse into a coma) and boot when it wanted to. had to reset with pin in the hole all the time. did this for about 3 days and said heck with it. seems to be some power issue with that flash. thanks to solidsnake66 for uploading these files. now my 7 seems to be normal again.

ok, this will help me. When I used the t-mobile backup, the partitions were different, because of the t-mobile files...I only had (I think) 11 or so GB of free memory. If I remember right, I had 12 something before. Is the .bat in this re-written to give me the 12gb, rather than the 11gb? Even if it is the WiFi files, I would like the same amount of memory I had before.
EDIT: Nevermind, I think I'm wrong, and they both use the same partitions.

Clockwordmod
Hey guys. So I used this howto to revert my dell streak 7 running on honeystreak hd7 back to android 2.2.2. Once i rebooted into the system i noticed that although in stock android, it was still rooted. While I know how to unroot, i can't get rid of clockwordmod recovery. How do i do that? I tried to uninstall the clockwordmod, but it doesn't show up under my apps. i am at my wits end. I want to send in my dell streak 7 to dell for repair, but i want it in "fresh" condition with no root or clockwordmod recovery. Any advice will be greatly appreciated. Thanks.

Files now working for me
On my fourth attempt the files worked great.

solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809
Click to expand...
Click to collapse
Do you have the stock "system" image for use with fastboot? for a wifi only streak? I can only find the tmobile one.
What I did was to an out of the box wifi only streak 7,
1. rooted with gingerbreak 1.2, renamed a couple .apks which were supposed to eliminate the cell standby battery drain.
2. restored the device to remove my google account (this device is for a friend and owned by her!!) It was stupid and I should have used her google creds first but she was not around. I didnt think it would hurt. The device was stuck at the android click to start screen and nothing I did could get it any further.
3. used fastboot to restore the system_orig.img posted by someone else, this fixed my issues, but it was a tmobile image so I am looking for the same thing system.img but in a wifi only flavor. THought you may have it.
Thanks much.

The links he gave are for Wifi version only. First download the first link then you have to get nvflash, unzip it onto your computer then unzip the files from the first link into the folder. He is advising you that you need to follow the directions on the 2nd link.

Berryblue said:
The links he gave are for Wifi version only. First download the first link then you have to get nvflash, unzip it onto your computer then unzip the files from the first link into the folder. He is advising you that you need to follow the directions on the 2nd link.
Click to expand...
Click to collapse
Actually, postb8822 is saying that the files in those downloads are ClockWorkMod Recovery and Rooted, not stock. The Root can be removed via Gingerbreak (I've done it, once...) but the CWR recovery images are all that I find in the files provided.
Berryblue, you said that you have a backup on an SD, right? Would you please place the recovery.img and boot.img (and system.img separate from those two perhaps) at some dropbox somewhere?
Thanks.

solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Click to expand...
Click to collapse
Downloaded all these files and then followed the directions in the other thread. Ended up stuck on dell logo. Then found this posting:
metal1f3 said:
I can confirm this works!! Thanks so much op. I used this to get back from dj_steves honeycomb b3, and i did have to take a couple of extra steps. Once everything completed I was stuck at the dell logo. So I booted into recovery, to see what i could do, which was almost nothing other than clear cache etc. The internal sdcard would not mount so I couldn't put steves streakdroid 1.3 on it to try and see if it would flash. At a brick wall, I decided what the heck and I flashed the original recovery through fastboot. I rebooted into recovery and preformed a factory reset and and to my amazement was greeted with the lock screen a short while later. However, I had a notification stating that my sdcard was unformated or not the right system type. (certain on unformated cant remember the second suggestion, but i believe thats close). I went to settings>sdcard & tablet storage and pressed "format internal tablet storage", then mounted the internal tablet storage. And thats it. Back on stock 2.2.2 (wifi-only). Mega thanks op.
Click to expand...
Click to collapse
This person's problem and fix seem to be exactly what I need to do. But what I don't understand is the "flashed to original recovery through fastboot" part. I can run fastboot and it sees my Streak but I don't know where I would find the recovery mentioned in the quote. Right now when I try to go to the recovery menu I see what seems to be the normal streak recovery menu but when I choose either factory reset I get to some other dialog I never saw before. I take it that this is some new recovery thing which is why I should be restoring the "original recovery" as mentioned in the quote.
To follow-up on my own posting: After staring at my bricked streak awhile, I decided that the poster must have meant the restore_orig file from the other thread. So I went back and reran the sequence. First the restore of all those img files then the fast boot recovery of the original restore img file. Boot with volume + to get to restore screen. Reset and reboot. Exactly what I'd done before but this time it worked. Perhaps the fact that the drivers were already installed helped since the sequence of operations wasn't interrupted by those driver installs. Perhaps I was more careful the second time. Regardless, it worked. I'm back and running. Even have root now; saving me from downloading gingerbreak. I'd assume if someone was doing this to return their Streak that they'd want to run gingerbreak to remove root. One additional caveat here: Once booted to the main Dell window (can't remember name of the Dell launcher) I had to reformat the internal disc. Not a big deal for me since I didn't expect any of my user data to survive. But just a warning for others.

solidsnake66 said:
I have the nvflash files, and if necessary the images, you need. I'll get them up somewhere and post a link for you in a bit later today.
Edit:
Here are the files you need:
http://www.multiupload.com/OM0VO9HBO9
Just download these and use the same instructions here:
http://forum.xda-developers.com/showthread.php?t=1018809
Click to expand...
Click to collapse
I(we) can really use the stock img files needed to flash to stock. I hope someone posts it.

ClockworkMod Recovery loop and error:-1 during solution
Sorry, I posted on the wrong section, Thanks Chemus!

The img files that mssahota1986 referenced are the t-mobile (3g/4g) images rather than the Wifi images.
However following the reposted instructions in your post shows that the t-mobile boot and recovery images can remove the CWM, which I thought was incorrect. Combined with the altered and rooted system images previously provided, I might be able to get close to stock on my wifi, since GingerBreak 1.2 was previously able to remove root from the Wifi.
If Dell ever actually upgrades to HC, I'll try the OTA updates...maybe I'll get lucky.
Still hoping for a drop of the actual WiFi stock images (apparently the System.img is necessary)
Update: No luck on combining different file versions for me. It seemed to work, but the WiFi would not turn on.

Chemus said:
Still hoping for a drop of the actual WiFi stock images (apparently the System.img is necessary)
Click to expand...
Click to collapse
My buddy just ordered a dell streak 7 off ebay. As soon as he gets it if it's all stock I'll create images from the device without the clockwork mod and root files. I don't know when he'll be getting it but I'll post the files ASAP

anyone else getting a white screen during the restore process near p11?
third time trying and i am stuck on dell logo. cant get into recovery at all.
any ideas.

TPT ICS NANDROID Backup (rooted w/superuser - completely virgin) and other goodies!!

Hey hey XDA! (ignore the account name, I was 13 years old when I first joined XDA in like '08)
My father bought a refurbished TPT from TigerDirect and literally nothing worked. I factory wiped it and tried to update it so I could get the cameras working and other such things - but no luck. I started to crawl my way through the internet but neither Lenovo nor anybody else seemed to have the answers. I thought that since I was failing the SHA1 hash checks that I might as well start replacing the files and see where it gets me. Five hours later:
First try to restore my ICS nandroid backup, but if not, follow the mini-guide below! Also look at the end of the post for all my files!
For those of you that can't update because you're failing assertion checks:
Root your current version with one of the root tools in my package. Go to your advanced properties and see which Lenovo internal version you're running "0089, 0075, 0060, etc". There are three toolkits that I included and they all work; use the one for your version.
Flash the Ventana CWM.
Do a nandroid restore through CWM by going to backup->restore. It's going to wipe and install a clean 0075 Honeycomb build.
Root again, the pre 0089 package should be a relatively easy root to do.
Restore the factory recovery. I have one fresh from my tablet and one that I found floating around on the internet. You could use either (the one floating around worked fine for me, but if you want something 'newer' just use mine).
Connect to a WiFi network and check for updates. This is the part where it might get tricky. Not all of the files in the 0075 build that I attached were original (it wasn't my build, not my fault). If you get an assertion check, look at your error and see which file has failed. I only had to replace three files, gps.conf, Generic.kl, and the busybox binary. This theoretically should be the same for you. Try to update without replacement, and as the updates start to fail replace the files that are causing failure. The ones you need are attached in my bundle, but I have others too - so let me know if you'll need them!
By this step you should be on the ICS update. Root using the debugfs kit (in the ICS folder for rootkits) and then flash Koshu's recovery (which only worked for me on ICS). Do a backup. Live a happy life.
This procedure isn't meant to be very 'easy'; I am just attempting to make your inconsistencies match mine so they can be fixed in the same manner. A quick Google search showed me that a lot of people are missing different files with barely any files available. Everything I have was extracted from official packages from previous versions. I think I managed to 'get lucky'.
You can find everything that you need on my website. I won't ever take this down save for a plane crashing into the datacenter where it's hosted. There are copies of all the files I mentioned in this tutorial and even copies of Lenovo's official updates since their servers go down more than Kim Kardashian.
Go to http//davidstancu.me/TPT
I'm also working on a small Android app to replace these files to the factory files (kind of like the way Windows has sfc /checknow or whatever that command is. I would also like to extend a massive thank you to everybody who made the tools that I used to get this done.
Since my account doesn't have 10 posts yet I can't post a link, so you'll have to manually include the colon. Sorry

What is your tablet version? US? ROW?
I am looking for 16 US version.

i have inadvertantly deleted my original ics files when upgrading to Koshu's JB. I need to restore the stock ics so would like to use your cwm restore files.I've downloaded the files but the md5 check doesn't work.I assume it's only because i need the actual name of the folder these files are saved in the cwm backup folder. can you please either post it or email it?

smiley1960 said:
i have inadvertantly deleted my original ics files when upgrading to Koshu's JB. I need to restore the stock ics so would like to use your cwm restore files.I've downloaded the files but the md5 check doesn't work.I assume it's only because i need the actual name of the folder these files are saved in the cwm backup folder. can you please either post it or email it?
Click to expand...
Click to collapse
'
don't worry. I just created a new blank nandroid.md5 file and it took.Unfortunately, my TPT would not boot up. It just stuck at the Lenovo logo. Any suggestions to get it working?

My guess is that a file was corrupted. Try redownloading?

Thank you so much for the detailed guide and the files! My TPT came with a strangely named bladenct...0037_0001 (US) firmware so I couldn't have updated to ICS otherwise.
In other words, confirmed working for a US 16GB TPT. :good:

BrazenRain said:
Thank you so much for the detailed guide and the files! My TPT came with a strangely named bladenct...0037_0001 (US) firmware so I couldn't have updated to ICS otherwise.
In other words, confirmed working for a US 16GB TPT. :good:
Click to expand...
Click to collapse
Based on that version number I'm curious... is that a TPT from Tigerdirect? Is the model number 1839AJ6 or 1839AD7?

US vs ROW
da_reeseboy said:
My guess is that a file was corrupted. Try redownloading?
Click to expand...
Click to collapse
Damn.I justchecked the build.prop and the ICS nandroid backup is for a US version. I've got a ROW version.
Anyone out there got an ICS nandroid ROW backup I can use? I'd really appreciate the help.

smiley1960 said:
Damn.I justchecked the build.prop and the ICS nandroid backup is for a US version. I've got a ROW version.
Anyone out there got an ICS nandroid ROW backup I can use? I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe this can help you - http://forum.xda-developers.com/showthread.php?p=37330646#post37330646

da_reeseboy said:
Based on that version number I'm curious... is that a TPT from Tigerdirect? Is the model number 1839AJ6 or 1839AD7?
Click to expand...
Click to collapse
I bought it second-hand (and it seems to have had quite a rough life as is cut out for a ThinkPad), but it's an 1839AD7.

BrazenRain said:
I bought it second-hand (and it seems to have had quite a rough life as is cut out for a ThinkPad), but it's an 1839AD7.
Click to expand...
Click to collapse
Thanks for the reply. I am trying to help another member get his up to ICS, and he has the same weird software version. Did you restore the nandroid or follow the mini guide?

I used the mini guide. Unlike the original poster, I found nothing broken in the stock software. The rear camera has some serious magenta artifacts on the side but that remained in ICS and CM10 so I'm guessing that's hardware damage. (This tablet seems to have been through a lot. Thus I got it at a reasonable price from ebay.)

Awesome! Thanks again for replying.

Active I537 having trouble with 4.3 upgrade after root/unroot.

I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.

tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
Try this thread. http://forum.xda-developers.com/showthread.php?t=2611278
I think most issues related to the update have been covered pretty well. Best of luck to you.
Sent from my SAMSUNG-SGH-I537 using Tapatalk

It sounds like you have quite a bit more reading to do so that you can understand exactly what you are trying to do. That said I'll try to answer your questions.
tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
Click to expand...
Click to collapse
Is TitaniumBackup the only root app you've used, have you frozen anything, installed any mods, or messed with any of the apps in your system/app folder? This will become important later.
tweakedlogic said:
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Click to expand...
Click to collapse
It sounds like you need to uninstall BusyBox. Normally SuperSU will uninstall this but it sounds like you tried a different method of unrooting that may have left bits in your system and since you weren't technically rooted anymore SuperSU didn't know what it needed to do.
tweakedlogic said:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
Click to expand...
Click to collapse
It sounds like you have the AT&T i537. This phone has a locked bootloader as you know. AT&T has required Samsung to lock down the i537 and will not allow them to release any firmware on Kies, this is why the software says your phone is incompatible. Basically AT&T is screwing us hard.
tweakedlogic said:
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Click to expand...
Click to collapse
The website you linked to is giving you bad information. The MI2 file is not technically "Official Firmware". This is a pre-release version of the firmware that DesignGears was able to get for the community. This will become important below.
tweakedlogic said:
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
As you've stated, this MI2 zip file that you've downloaded has a single exe file in it. This exe file should be run from a computer and it will allow you to flash new firmware to your phone. BUT, as I mentioned above this is pre-release firmware. What that means is you will forever be stuck on this firmware, you will not be able to take official updates from AT&T or Samsung. If you're ok with that, then go ahead and flash your phone with the pre-release of 4.3. If you want the official 4.3 update you have a little work to do. Above I asked you if you messed with any of the files in system/app, this is because the official update file can be downloaded and can even be flashed but it checks nearly every file in the system/app folder to make sure that it is the original file. If you've modified anything in there, the update is going to fail.
I'm going to post a few links of stuff you should read, but there is definitely a lot more that you should be reading.
How to flash stock MF3 - this is most likely the firmware you are on, but this thread will tell you how to get it back to stock, the way it was when you took it out of the box. This should allow you to take the official 4.3 update if other methods don't work.
MF1 Pre-release (4.2.2) - this is a pre-release of 4.2.2, you should read this.
MI2 Pre-release (4.3) - this is a pre-release of 4.3, read this thread to understand the benefits and drawbacks of flashing this pre-release firmware.
Official 4.3 Update Thread - this tell you what you need to do to try to update your phone to the official version of 4.3. Currently there is to way to root the official 4.3.
SafeStrap Thread - this will allow you to flash TouchWiz 4.2.2 based ROMs on your phone. Again, you need to read before you do anything. There's actually a lot we can do even though our bootloader is locked.
I can't stress enough how important it is to read. Once you've read everything and you think you understand what you're doing, READ MORE. There's always somebody who's done what you're trying to do and someone has more than likely given the answers you're looking for. Read as much as you can and you can avoid bricking your phone and ending up with a paperweight.
Good luck and us know if you have any questions, everybody is here to help.

You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.

tweakedlogic said:
You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.
Click to expand...
Click to collapse
You need to read the links I posted, all of this is explained including how to get the apps back that you deleted.

I so much miss being able to just flash with clockworkmod. Things were so much easier.
Sent from my SAMSUNG-SGH-I537 using Tapatalk

Nexus Build Number (Google Images vs.. on device)

I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben

aergern said:
I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben
Click to expand...
Click to collapse
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.

youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though

youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I'll just flash the img files individually to the current Factory and reroot.
Thanks!

TacoLord187 said:
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though
Click to expand...
Click to collapse
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.

but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...

indianajonze said:
but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...
Click to expand...
Click to collapse
A quick google would suggest that LNX07M is the lollipop developer preview

so he was just pushed to his retail device the developer preview build?

Sounds like his phone came with the developer preview installed, and the initial update just took a few days to appear for him which he didn't manage to install so is still on the preview.

aergern said:
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.
Click to expand...
Click to collapse
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!

TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.

TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
Phantom Shadow said:
A quick google would suggest that LNX07M is the lollipop developer preview
Click to expand...
Click to collapse
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.

aergern said:
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.
Click to expand...
Click to collapse
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)

TacoLord187 said:
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)
Click to expand...
Click to collapse
Sure.
Hit me up. :good:

aergern said:
Sure.
Hit me up. :good:
Click to expand...
Click to collapse
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
2. Where is the folder that I need to move them too?
3. EDITED OUT. Misread something
Thank you so much for your help!

Answers inline.
TacoLord187 said:
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
You download the factory image tarball from Google's Android dev site. You then untar it wherever you like. I would probably untar it as root in /tmp/ then you can just mv the files to where you need them.
2. Where is the folder that I need to move them too?
The SDK is a zip file. You can unzip it wherever you like. I do this in /usr/local/ and then do a softlink to the directory it makes.
example: ln -s /usr/local/android <sdk directory>
I then cd into the tools directory and do this .. ./android which starts the UI so you can download the rest of the SDK. Do not bother with anything older than 4.4.4 packages.
I then move the img files from the factory image directory in /tmp to /usr/local/android/platform-tools/
You can then use the commands from the other post.
You can cat the install scripts for any syntax you might need but I think you'll find the commands I put in the other post to work for you.
3. Do I need to reroot/TWRP after? I can if needed, just want to be prepared!
Indeed you do. You can also move the CF img to the platform-tools directory. I would keep the tgz of the factory image somewhere else than /tmp in case you need it again.
Click to expand...
Click to collapse

aergern said:
Answers inline.
Click to expand...
Click to collapse
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!

TacoLord187 said:
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!
Click to expand...
Click to collapse
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.

aergern said:
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.
Click to expand...
Click to collapse
I have my adb set so I dont have to type the paths always. It just reads from a folder called android on my desktop (im on a mac). It normally works, but it wanted the paths for this one. Oh well. No big deal! Its updated and working!
Thanks again

aergern said:
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.
Click to expand...
Click to collapse
His phone might have been shipped that way as some people phones where shipped with Android 4.4.4.

[Q] GG1 Bricked

Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance

catfinger said:
Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance
Click to expand...
Click to collapse
Sounds confusing. Not knowing exactly what you tried or what you have flashed, start over. If you can get to download mode try putting on a stock image and see what that gets you. Its not bricked if it boots and you can get to download and recovery. Sounds more like a cable issue, bad download or something. Here's my copy folder that has ne9 and nf1, do ne9 first as nf1 is not a full ROM.
---------- Post added at 03:38 PM ---------- Previous post was at 03:30 PM ----------
catfinger said:
Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance
Click to expand...
Click to collapse
Edited my post. Responding incase you read the original one.

Ducter said:
Edited my post. Responding incase you read the original one.
Click to expand...
Click to collapse
Thanks mate, that worked. I now have the watch back to asking me to pair with a phone.
One last thing, can you point me in the right direction to getting this rooted and ROMed without having to connect to a Samsung first? I'm on HTC One M8 so can't go down the cydia impactor route.

catfinger said:
Thanks mate, that worked. I now have the watch back to asking me to pair with a phone.
One last thing, can you point me in the right direction to getting this rooted and ROMed without having to connect to a Samsung first? I'm on HTC One M8 so can't go down the cydia impactor route.
Click to expand...
Click to collapse
People have different degrees of success with your set up. Here is a post you can read and decide for yourself. Other option is go back to android on your watch, specifically null, try that. If it fails you can delete...forgot the exact name sec.setup.Samsung or something like that from the null zip then flash it, basically turns your watch into full blown android but missing most the watch features leaving you with finding third party apps to do what you want.
I got fed up trying to get my watch working with my note 3 on aosp lollipop and ended up flashing a Samsung ROM. On kit kat everything worked well enough for me, lollipop, not so much.
if you used the ROMs I linked they are rooted already. Just Google galaxy gear on non Samsung phone, you'll find plenty of info.