Related
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
for the love of God can some body help me?
i just dont know what to do, this is the oem rom update and why the unit is not able to find the update in the sd card?
This post isn't about development, you posted the same thing in multiple places, and you can't install the AT&T update with clockwork, you need the stock recovery.
marvin02 said:
this post isn't about development, you posted the same thing in multiple places, and you can't install the at&t update with clockwork, you need the stock recovery.
Click to expand...
Click to collapse
yes thanks
where can i find it and how can i flash it?
elmanortega said:
yes thanks
where can i find it and how can i flash it?
Click to expand...
Click to collapse
+1
Please god, Ive been stuck on this **** for 14 hours now. SOLUTION PLEASE!
I've experience rooting/roming over 50 phones, and this is getting irritating!
CWM doesnt flash .pkg's, and I'm coming in way to late in the process to understand this QueTip program or w-e. A simple stock recovery flash tutorial n link would be amazing.
this will happen too when you flash it over 2.2 already but in your case your on 16 ryt?i would suggest google search for the stock 1.6 6601 recovery image and flash it and then flash clockwork and then apply the update.
try to look here.
http://forum.xda-developers.com/showthread.php?t=778397
try here also.
http://android.modaco.com/content/d...uide-to-upgrading-and-downgrading-the-streak/
whats your baseband prior to this update?
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery,
Download stock recovery from here. Make sure it is on your computer in the same folder as fastboot.exe
Excerpted from this streakdroid guide:
Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
Open a command window and use ‘cd’ to change to the same directory as qdltool.
Run: fastboot -i 0x413c flash recovery recovery.img
Run: fastboot -i 0x413c reboot
Either rename the file you downloaded to recovery.img or change the name of the file to flash in step 5 to match the file downloaded.
Boot into recovery and you should now have a stock recovery.
You can boot your phone and try downloading and installing the OTA upgrade or you can place the upgrade file on your SD card and name it upgrade.pkg and try to install it using the stock recovery.
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery.
Make sure that any ROM you try to install on your phone is appropriate for your hardware and carrier.
I personally was on the 318 build of 2.2... Downgraded to O2 2.1, then to O2 1.6, then to AT&T 1.6 with the BB downgrade... then upgrade to AT&T 340 2.2, its not that hard... get to stock AT&T 1.6 and leave the 340 "update.pkg" in the root of the SD card.
Instructions to get to AT&T 1.6 here > http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
marvin02 said:
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery,
Download stock recovery from here. Make sure it is on your computer in the same folder as fastboot.exe
Excerpted from this streakdroid guide:
Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
Open a command window and use ‘cd’ to change to the same directory as qdltool.
Run: fastboot -i 0x413c flash recovery recovery.img
Run: fastboot -i 0x413c reboot
Either rename the file you downloaded to recovery.img or change the name of the file to flash in step 5 to match the file downloaded.
Boot into recovery and you should now have a stock recovery.
You can boot your phone and try downloading and installing the OTA upgrade or you can place the upgrade file on your SD card and name it upgrade.pkg and try to install it using the stock recovery.
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery.
Make sure that any ROM you try to install on your phone is appropriate for your hardware and carrier.
Click to expand...
Click to collapse
I don't have a fastboot option, and am unfamiliar with QDLtool? Can I pick up on these steps even with CWR already installed?
here are my videos of my device turning on and going into clockwork etc
http://www.youtube.com/watch?v=u0wSH64PlsM
http://www.youtube.com/watch?v=zMiRGekzT_I&feature=mfu_in_order&list=UL
Truaim said:
I don't have a fastboot option, and am unfamiliar with QDLtool? Can I pick up on these steps even with CWR already installed?
Click to expand...
Click to collapse
If you are not on at&t's 1.6 than this is your only option. Also your only way to go back to the 1.6 is using essentially same steps as above. So just make sure fastboot is set up and follow the steps listed above. It will work regardless of os you are running now. I just did it and I was on dj steve's 1.8. On a side note how is the upgrade working for you?(those that installed it)
dacho said:
If you are not on at&t's 1.6 than this is your only option. Also your only way to go back to the 1.6 is using essentially same steps as above. So just make sure fastboot is set up and follow the steps listed above. It will work regardless of os you are running now. I just did it and I was on dj steve's 1.8. On a side note how is the upgrade working for you?(those that installed it)
Click to expand...
Click to collapse
hi do you have a chance to help me out with this?
how do you install universal androot? it only says install and run it
dowloading to my pc and click it doesnt work, copying to root of the sd card and trying to installed with clock work doesnt work
software upgrade via update.pkg on sd card doesnt work
im just thinking that im just plain stupid
is there a video tutorial?
is there some one that can help me i will pay im just tired.
You need fastboot. Plain and simple.
sent from my re-engineered dInc
Hellzya said:
You need fastboot. Plain and simple.
sent from my re-engineered dInc
Click to expand...
Click to collapse
i have fastboot
Yeah my installation came up with an error and it would not boot after it was applied so previously posted stock recovery does not work. So what you have to do is follow the steps to go back to stock at&t 1.6 rom. Here are the directions http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
I am in a process of doing this now so i'll keep you posted. However, once you do the downgrade from the link above you should be able to just install latest at&t rom without any problems. Hope that helps.
dacho said:
Yeah my installation came up with an error and it would not boot after it was applied so previously posted stock recovery does not work. So what you have to do is follow the steps to go back to stock at&t 1.6 rom. Here are the directions http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
I am in a process of doing this now so i'll keep you posted. However, once you do the downgrade from the link above you should be able to just install latest at&t rom without any problems. Hope that helps.
Click to expand...
Click to collapse
thanks ok first how do you install universallandroot?
elmanortega said:
thanks ok first how do you install universallandroot?
Click to expand...
Click to collapse
it should be in the market. I used to use SuperOneClick it should work for 2.2 and 1.6. just google the SuperOneClick.exe and you run this from the computer not the phone. universalandroot you run from the phone.
This comes with the .img of Amon_ra, 3 batch files to reboot into bootloader, flash it, then reboot into recovery (will need to type reboot recovery) into the shell for the 3rd batch file (it tells you so) then you are immediately into recovery. I made this batch file and if you repost, please give proper credits. This script can be easily modified to flash any recovery for any phone since it's just generic commands. This currently is using amon_ra for the HTC Evo 4g and can be used after gaining s-off using Revolutionary or any other root method. I used the install recovery.bat for switching quickly from Twrp to wipe for my roms. Anyway, here is the bat. Instructions are included when you run each batch file. So just extract these to your desktop as is meaning don't put the .bat files in the same folder as all the other files. They need to be seperate.
You run them in this order: Reboot1.bat>Recovery install.bat>Reboot2.bat
^ in order from left to right.
http://dl.dropbox.com/u/15069134/Recovery flash.zip
Thank you
Sent From DEEZ
popper668 said:
Thank you
Sent From DEEZ
Click to expand...
Click to collapse
Happy to help.
Sent by breaking the sound barrier
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
pinoymutt said:
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
Click to expand...
Click to collapse
Under CWM mount system, adb show error device nor found, its look that my only hope is a stock odin rom.
Thanks
Ouch, sounds like bad news. Hopefully someone will post something you can use to revert soon.
Sent from my GT-P3113 using Tapatalk 2
matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
stan.s said:
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
matrox00612 said:
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
Click to expand...
Click to collapse
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
masonjoe69 said:
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
Click to expand...
Click to collapse
Yes it is like that, we have to wait a little, but lets get the first dev to throw a working odin flashable file some motivation, i will donate 50 beers.
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
Here's the stock system dump Stock System Dump JSS15J...
Now that we have root and recovery, I know that some will delete their system files, want to update, and not be able to because they've deleted them.
No worries!
DOWNLOAD HERE
This is NOT a flashable zip file!
If you don't know what to do with this please don't download it, as it will do you no good. Ty.
ATGAdmin said:
Here's the stock system dump Stock System Dump JSS15J...
Now that we have root and recovery, I know that some will delete their system files, want to update, and not be able to because they've deleted them.
No worries!
DOWNLOAD HERE
Click to expand...
Click to collapse
Lol. That would me be... I bricked mine... Thank you for uploading this! So, how do I load this to the device?
luckymeeh said:
Lol. That would me be... I bricked mine... Thank you for uploading this! So, how do I load this to the device?
Click to expand...
Click to collapse
adb push filename /data/media/0/
phuduong said:
adb push filename /data/media/0/
Click to expand...
Click to collapse
Thanks for the response. So, replace the filename with the zip file or do I need to unzip it first?
yes please help, my internal storage in twrp shows 0mb and system just stays stuck on the nexus boots logo. thanks
phuduong said:
adb push filename /data/media/0/
Click to expand...
Click to collapse
So I did try: adb push Nexus7...zip /data/media/0/
I got "no devices found"
I'm on a Mac. Any idea what I should do next?
Thanks.
adb says it is not a directory.... am i going to have to wait for google to release the nexus 7 system image?
Can anyone make a flashable file? I'm trying to ADB sideload it but it fails.
bricked nexus 7!
guys, can someone please post a recovery flashable .zip? I wiped my system partition, and now I only have TWRP, but without USB debugging. I have tried everything I could. No luck. They only way I could think of is if somebody posted the flashable version. I can only use fastboot commands, and not adb ones, as the USB debugging state is wiped.