Credits to geek78.
I take no responsibility if your brick you device!!!
This worked for me and i am now on Stock 1.6 6601 with the original baseband.
Please do not ask me to support any issues.
1. You need to downgrade back to O2 stock 4399.
Download the official update 4399 from here : http://loadbalancing.modaco.com/download.p...104_4399_21.pkg
Copy this update to the root of your sdcard and rename it update.pkg
Download this zip http://hotfile.com/dl/62324940/5dea6fd/recovery.rar.html
Unzip it on your desktop
Put your streak in fastboot mode
Go to the directory where are the files from recovery rar and execute the right cmd for your situation :
fastboot-yourOS -i 0x413c flash recovery recovery.stock.new.img
push the the 2 volume buttons and at the same time execute the right cmd for your situtation :
fastboot-yourOS -i 0x413c reboot
Choose update from sd card …. And after the process you have now a 4399 21 build
Root your streak and install a browser like root explorer and a terminal from de market
2. Change the system so it will accept the 6601 pkg file when trying to restore.
Download the official 6601 build from HERE and place the file at the root of your SDCARD.
Download THIS FILE, unzip it and place it at the root of your SDCARD (the name of the file should show up as boot.img)
Download THIS FILE and unzip it where your want on your sdcard.
Then mount your / as rw and copy all the files unziped at the same place on the streak (etc to /etc, system to /system ...) do NOT overwrite entire folders, just copy the 3 files inside those folders to their respective folders under /system, /bin and /etc)
From terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
Reboot your streak in normal mode
Reboot your streak in recovery mode and apply the update from sdcard
Once booted you should be on 6601 1.6 at&t firmware and baseband.
Thanks for the post.
I am planning to return to 1.6
This would help me.
wow, very cool, will downgrade later. thanks!
When we mount / as rw, I'm assuming you want us to but the contents of etc to /system/etc, bin to /system/bin and then the recovery-from-boot.p to /system, correct?
Also, do you happen to have the fastboot-windows? It's not a big deal if you don't.
downgrade and baseband restore worked great. thanks a bunch. this is especially helpful now with the kernel released and I want to play with some custom roms, can always revert back to stock.
the first link does not work, just goes to the Modaco home page
Are you downgrading from 8105 2.1 or the earlier version? Since I updated to 8105 i have been unable to get to 4399.
Sent from my Dell Streak using XDA App
ok i found the stock O2 4399 elsewhere, but the zip file does not have a fastboot-windows, just mac and linux. do i just move my fastboot.exe file to the recovery folder that has the recovery.stock.new?
Yes just use the fastboot.exe and rename the file if you want to follow the instructions exactly.
Sent from my Dell Streak using XDA App
ok i just got
E:No signature (972 files)
E:Verification failed
joeclark said:
ok i found the stock O2 4399 elsewhere...
Click to expand...
Click to collapse
Where is a reliable location? The 4399's I've found indicate they may have been customized. I am looking for plain vanilla stock 4399. TIA.
GenghisKhent said:
Where is a reliable location? The 4399's I've found indicate they may have been customized. I am looking for plain vanilla stock 4399. TIA.
Click to expand...
Click to collapse
hxxp://loadbalancing.modaco.com/download.php?url=paul/streak/Streak_104_4399_21.pkg
ok that one is installing thanks for the full address
JaysFreaky said:
hxxp://loadbalancing.modaco.com/download.php?url=paul/streak/Streak_104_4399_21.pkg
Click to expand...
Click to collapse
After changing hxxp to http, I get a redirect to hxxp://www.modaco.com/; no pkg file.
joeclark said:
ok that one is installing thanks for the full address
Click to expand...
Click to collapse
No problem!
GenghisKhent said:
I get a redirect no pkg file.
Click to expand...
Click to collapse
Really? That's strange. I downloaded it and it seems joeclark was able to as well.
EDIT: I just tried it myself, and it's not working anymore, either.
Go to this page, and skip the zip (they're pre-rooted) and go to the pkg.
hxxp://android.modaco.com/content/dell-streak-streak-modaco-com/310618/19-aug-streak-1-6-downloads-how-tos-rom-superboot-recovery/
ok now i am getting fota mismatch
i got the 4399 installed and am trying to get to the 6601, i put all the files where they belong pretty sure i did the flash_image correctly
and then i went to do the recovery from the update.pkg and i get the error
trying the 2nd part again crossing fingers
FOTA model name mismatch. System restart in 30 seconds.
any ideas?
oh yeah and i have flashing lights now too.
joeclark said:
ok now i am getting fota mismatch
i got the 4399 installed and am trying to get to the 6601, i put all the files where they belong pretty sure i did the flash_image correctly
and then i went to do the recovery from the update.pkg and i get the error
Click to expand...
Click to collapse
Clubtech said in the other thread to remove your battery and send him the .dec file that is on the sdcard. Maybe he can help you with that.
joeclark said:
trying the 2nd part again crossing fingers
FOTA model name mismatch. System restart in 30 seconds.
any ideas?
oh yeah and i have flashing lights now too.
Click to expand...
Click to collapse
fota error and flashing lights so you have still :
recovery from 4399
boot from 6601
So you have made a mistake during the copy of the files to the right location. .. try again....
I wonder if this is working for both 6941 and 8105?
Related
Here's a dump of clean 8105 (official O2 2.1) firmware:
Streak_8105_img.zip
You may use it as a base for mods.
Dump as in nandroid, or you extracted the. Pkg
If the second then how?
fards said:
Dump as in nandroid, or you extracted the. Pkg
Click to expand...
Click to collapse
I manually dumped (cat /dev/mtd/mtd0 > /sdcard/boot.img) boot and recovery after rooting the device. Then reflashed pkg and clockwork, and dumped system and userdata.
damn i was hoping you'd worked out how to get into the .pkg
just thinking if we can unyaffs the recovery from a stock, we may be able to work out how they extract it..
brb
EDIT
Damn recovery is an binary standalone executable..
no joy with that one then
fards said:
damn i was hoping you'd worked out how to get into the .pkg
Click to expand...
Click to collapse
Is update.pkg something specific to Dell Streak?
Googling "update.pkg" gives references related to Streak only...
Thread temporarily stuck.
yeah it's an odd file system,
OSx and PS3 also use ,pkg files, but neither seem to have any relation to the update.pkg that we're getting from Dell.
I agree with you that it probably is a binary that takes over the device and puts things in correct places.
If you observe the update process it does a lot of things.
The binary approach gives a lot of flexibility and you do not have to relay on features built into the firmware.
Maybe this can help.... This is not a dump but the update.zip extracted from the update.pkg. You will see that it is the usual format of an update under android. There is also the baseband update in the zip.
http://www.megaupload.com/?d=9A1QI7PM
geek78 said:
Maybe this can help.... This is not a dump but the update.zip extracted from the update.pkg.
Click to expand...
Click to collapse
We are more interested in the extraction procedure.
Ah ok. You have to try to update a device with the wrong device type build. When you have the message "bat Fota ..." take out the battery. In the SD card you will have a file update.pkg.dec. This is a zip of a "standard" pkg file (under OSX you can expand this pkg file extracted). Credit to Clus3R
LOL. Neat trick ;-)
Reminds me how I extracted .msi packages from .exe ;-)
geek78 said:
Ah ok. You have to try to update a device with the wrong device type build. When you have the message "bat Fota ..." take out the battery. In the SD card you will have a file update.pkg.dec. This is a zip of a "standard" pkg file (under OSX you can expand this pkg file extracted). Credit to Clus3R
Click to expand...
Click to collapse
AWESOME!!!
hi - ive literally just got my Streak out of the box (standard Dell unlocked version)
Can i use this on mine?
And if so is there any special procedure??
Applying the .img with fastboot in usual way like the recoverys?
edit:
I think, this should work:
Code:
fastboot-windows.exe -i 0x413c flash recovery recovery.img
fastboot-windows.exe -i 0x413c flash userdata userdata.img
fastboot-windows.exe -i 0x413c flash system system.img
fastboot-windows.exe -i 0x413c flash boot boot.img
fastboot-windows.exe -i 0x413c reboot
edit2: hmm: userdata failed. Any ideas?
Friends I found simple way to get back to official froyo from steves 1.4.6
just u will need a official froyo packge.
if u have astro file manager place the package in th root of your sd card.
from astro rename the package as
first irase the file extention .pkg
then enter nee extention .zip.
after that you will find the update.pkg is just a zipped file.
then simply flash clockwork recovry.
then go to install zip from sd.
then select the update.zip(previously update.pkg) then this will install all kernel,boot image.....
after that reboot your phone.
then you will find that you are now all official froyo.
this will help you to get back on stock froyo.
sorry for sms language that I have used in my post.
i have sent it using dell streak browser.
If you want the recovery(boot.img) original.
Then u can simply extract from the package by doing the same told above.
If u find this helpful please rate thos post.
Thanking you.
If you want the performance of dj steves rom u will need not to flash custom kernel
Simply copy paste the files from smokkus froyo fixx and replace to files of streaks internal storage.
I done this and got 1500-1575 on quadrant.
Anybody here can confirmed and have tried this method and work
Sent from my Dell Streak using Tapatalk
All i do is Flash 309 Recovery then install 318 Rom and thats it
But using my innovative method you need not to flash any recovery
Kolteabhiman said:
But using my innovative method you need not to flash any recovery
Click to expand...
Click to collapse
you're flashing clockwork recovery...so you are
It takes like one button to flash a recovery..
Why would I want stock or official Froyo when Steve's build gets me quadrant scores of 1900?
the gps crashes all the way.some video formats are not playing well.
Kolteabhiman said:
Friends I found simple way to get back to official froyo from steves 1.4.6
just u will need a official froyo packge.
if u have astro file manager place the package in th root of your sd card.
from astro rename the package as
first irase the file extention .pkg
then enter nee extention .zip.
after that you will find the update.pkg is just a zipped file.
then simply flash clockwork recovry.
then go to install zip from sd.
then select the update.zip(previously update.pkg) then this will install all kernel,boot image.....
after that reboot your phone.
then you will find that you are now all official froyo.
this will help you to get back on stock froyo.
sorry for sms language that I have used in my post.
i have sent it using dell streak browser.
If you want the recovery(boot.img) original.
Then u can simply extract from the package by doing the same told above.
If u find this helpful please rate thos post.
Thanking you.
If you want the performance of dj steves rom u will need not to flash custom kernel
Simply copy paste the files from smokkus froyo fixx and replace to files of streaks internal storage.
I done this and got 1500-1575 on quadrant.
Click to expand...
Click to collapse
I don't know how you did this but the original .pkg files from DELL are ENCRYPTED!!! You can't just rename it to ZIP and flash it!
no friend i just diid it.
what means."from astro rename the package as
first irase the file extention .pkg
then enter nee extention .zip."
I thought astro only gave read only permissions? Also i cant grasp how its possible to install an offical dell package via clockwork? I thought it needed the stock image to load? I also thought clockwork was only useable with custom roms? Confused? ?? If it it does work simply changing the extension then that could be really useful to know
lufc said:
All i do is Flash 309 Recovery then install 318 Rom and thats it
Click to expand...
Click to collapse
Hey lufc - so you were on steves 1.4.6 then flashed 309 and updated via 318 pkg and that was it? Just confirming as i may do this from 1.5.0 (should be same concept)
Hey frend I did it
wow it worked
.....................
Rootshell file on the cooking 2.1/2.2 thread
Click here for the file.
To flash to 1.6
Go Here
Legen...wait for it...darryy!!
Awesome i saw ur post in the dev thread made my day!
Two questions 1) you mentioned in the dev thread it was restarting quite often is that fixed?
2)is there any means to flash it in internal memory?
muzik_demon said:
Legen...wait for it...darryy!!
Awesome i saw ur post in the dev thread made my day!
Two questions 1) you mentioned in the dev thread it was restarting quite often is that fixed?
2)is there any means to flash it in internal memory?
Click to expand...
Click to collapse
1. Yes, thats fixed, it works fast and stable ! (there's one big problem - sdcard is not properly seen for camera/music), still testing it ..
2. Yes, it will be possible to flash into internal memory later.
1) For the first problem i recommend throwing a pm to zdzihu- he has employed the same technique to get dual boot in x10 and his rom is able to access sdcard for camera/music but we cant mount sdcard
2) If flashing into internal memory is straightforward then i recommend it since it will solve all the above problems
Looking forward to testing
(where can i get x8.img and data.img? or are you gonna release it in some time?)
Well done pulpoff2, I will test this solution, when I gone back home from work. Thanks
thank you . i am downloading the flies .
pulpoff2 said:
So far so good!
I started a new thread cause other one is filled up with junk.
Following my weekend theory, I finally managed to boot 2.1 on X8 with root.
I will post the files shortly.
The process is quite complicated for now, but early testers are welcome.
So, to start u need :
1. Flash 1.6 and root it
2. Copy busybox and rootshell to /system/bin
3. chmod 4755 /system/bin/rootshell
4. copy chargemon.txt into /system/bin/chargemon
5. chmod 777 /system/bin/chargemon
6. copy data.img and x8.img to SDCARD root directory
7. Flash 2.1 KERNEL ONLY (put 2.1 firmware files, remove system.sin and userdata.sin from firmware directory, than flash)
8. reboot your new 2.1 pre-rooted X8 !
Wasted weekend .. was it worth the hassle guys?
Cheers!
Here are the files you need to boot :
pulpX8.rar
ext.rar contains e2fsck to check .img for errors before booting, if you will not install these, booting should work anyway.
P.S. this is a very early stage solution now, wait until I make it clean, or try it if you are a flash maniac
Click to expand...
Click to collapse
how to find rootshell?
isaac12 said:
how to find rootshell?
Click to expand...
Click to collapse
Its on the cooking 2.1/2.2 thread
Click here for the file.
To flash to 1.6
Go Here
thanks... flash only kernel.sin without amss.sin amss_fs.sin cache.sin fota0.sin fota1.sin simlock.ta and update.xml?
isaac12 said:
thanks... flash only kernel.sin without amss.sin amss_fs.sin cache.sin fota0.sin fota1.sin simlock.ta and update.xml?
Click to expand...
Click to collapse
No, do as I wrote in first post, move 2.1 files over 1.6 files, than just remove system and userdata and flash than..
This just keeps getting better and better
Sent from my E15i using XDA App
pulpoff2 said:
No, do as I wrote in first post, move 2.1 files over 1.6 files, than just remove system and userdata and flash than..
Click to expand...
Click to collapse
I'm flashing all files without system and userdata .phone booting only sonyericsson logo. overwrite files and delete user data and system?
pulpoff2 said:
So far so good!
I started a new thread cause other one is filled up with junk.
Following my weekend theory, I finally managed to boot 2.1 on X8 with root.
I will post the files shortly.
The process is quite complicated for now, but early testers are welcome.
So, to start u need :
1. Flash 1.6 and root it
2. Copy busybox and rootshell to /system/bin
3. chmod 4755 /system/bin/rootshell
4. copy chargemon.txt into /system/bin/chargemon
5. chmod 777 /system/bin/chargemon
6. copy data.img and x8.img to SDCARD root directory
7. Flash 2.1 KERNEL ONLY (put 2.1 firmware files, remove system.sin and userdata.sin from firmware directory, than flash)
8. reboot your new 2.1 pre-rooted X8 !
Wasted weekend .. was it worth the hassle guys?
If the answer is yes and you would like me to spend some time and make this perfect, don't forget the "donate" button.
Cheers!
Here are the files you need to boot :
pulpX8.rar
Firmware 2.1 (rus)
Firmware 1.6 (uk)
ext.rar contains e2fsck to check .img for errors before booting, if you will not install these, booting should work anyway.
P.S. this is a very early stage solution now, wait until I make it clean, or try it if you are a flash maniac
UPDATE
The system.img now comes with LauncherPro and other goodies, some vaporware removed and GingerBread (2.3) black theme !!!
Donation count : $0
Click to expand...
Click to collapse
may be superuser.apk put inside of your firmware?
dviktor said:
may be superuser.apk put inside of your firmware?
Click to expand...
Click to collapse
It is inside the x8.img, as well as su and rootshell and busybox.
So if phone gets stuck on boot, connect adb and u can get root in console and fix problems.
and if i am right understand all running files be booted from sd card? and if it's unmount the phone will be still work? or it will be freezing or rebooting? and may be then we can start 2.3 on expiria x8?
dviktor said:
and if i am right understand all running files be booted from sd card? and if it's unmount the phone will be still work? or it will be freezing or rebooting?
Click to expand...
Click to collapse
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
pulpoff2 said:
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
Click to expand...
Click to collapse
I'm flashing all files without system and userdata .phone booting only sonyericsson logo. overwrite 1.6 files and delete user data and system?. how to long wait for booting phone?
pulpoff2 said:
/system and /data are mounted from x8.img and data.img from Sdcard.
This is good to debug problems, without need to reflash the phone every time.
Once we have the Xrecovery for X8, it will be easy to replace/update files like on X10i.
Without sdcard, you will have 2.1 kernel with 1.6 system, it will get stuck on boot, but adb shell will work (with root!), so you can investigate/fix problems/put new /system files.
Click to expand...
Click to collapse
so, if i take a normal files with undeleted (clean) from system/app, and copy it in phone with root, i can delete x8.img and data.img from sd card? i am just a curator of 4pda (russian) thread by X8 phone. becouse i ask you about everything
Well... I am a new guy, I am happy that the root was released, however, I don't know about the post, so is there a detailed version with pictures please?
Regards
Sent from my E15i using XDA App
how to set chmod in windows vista?
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.