yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
fastboot flash boot and system then root again
[Nexus 7 Q&A, Help & Troubleshooting] Wayno-san:
Thanks but I'm not familiar with this process. Think I just used the tool kit for the root. Found this thread but states that all data will be wiped and I want to avoid that:

http://xdaforums.com/showthread.php?t=1907796

Is there a better how-to thread for the process that you describe that you could point me to?

Is there a log somewhere that I could check to try and ID what failed? Maybe there's an easier fix.

Thanks again for bearing with me... Haven't had time to keep up to date on the N7 as much as I would like.
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
i don't know why those howto just keep on telling people to erase everything then flash everything.

4.2.2 is just a textbook OS upgrade. All you need to flash is the boot.img which contains the kernel, and system.img which contains the essential system files, utilities libraries and kernel loadable modules etc.

you don't need to erase anything and even you do, only these two partitions.

the recovery partition doesn't need to be touched.

the booloader, I am wondering why it needs to be updated as well(as is asking what has been changed). My PCs can contain bootloaders that is 10 years old and is still running fine with numerous reinstallation of various OS.

the radio probably but I thought some said they are fine with old radio even running 4.2.2, again even you flash this it has nothing to do with your data or settings.
[Nexus 7 Q&A, Help & Troubleshooting] rexxxxx:
The same happened to me. After I replaced the debuggers and the other file nothing changed but after 2 days and maybe some restarts the update was available again. So my advice is replace both files and wait and restart.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
I believe that even the stock recovery drops a log file into /cache/recovery/ , does it not?

/cache/recovery/recovery.log or similar?

If you are getting an error with the stock recovery and your ROM is rooted, it should be straightforward to boot the regular OS and have a look at that log file for errors...
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
I don't remember seeing any post instructing people to wipe everything. While you are correct that it isn't necessary, you are also giving misinformation about things you admitedly know nothing about.

If someone is going to upgrade their OS, they should do the full upgrade. This means the bootloader and radio (if N73G). There is simply no reason not to, and many reasons why you should.
[Nexus 7 Q&A, Help & Troubleshooting] Wayno-san:
OK, Here's the last part of the log file; looks like debuggerd is still the culprit even after I replaced it, checksums do not match... Hmmm.

Finding update package...

I:Update location: /cache/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

Opening update package...

I:read key e=3

I:read key e=3

I:2 key(s) loaded from /res/keys

Verifying update package...

I:comment is 1604 bytes; signature 1586 bytes from end

I:whole-file signature verified against key 0

I:verify_file returned 0

Installing update...

Verifying current system...

file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache

failed to stat "/cache/saved.file": No such file or directory

failed to load cache file

script aborted: assert failed: apply_patch_check("/system/bin/debuggerd", "a2323a0c8e245e3879d6b8beff6b2c4802045271", "df2e705da097e4d535b4f4d98fab3bd76601e76c")

assert failed: apply_patch_check("/system/bin/debuggerd", "a2323a0c8e245e3879d6b8beff6b2c4802045271", "df2e705da097e4d535b4f4d98fab3bd76601e76c")

E:Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

(Status 7)

Installation aborted.

I:Saving locale "en_US"

I:timed out waiting for key input; rebooting.

I:Saving locale "en_US"
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
I don't what is should. If there is even just one case that not flash the radio or the bootloader and it still runs(with the new boot/system), it is not a 'should' anymore.

This is like the good old urban myth that any time one wants to upgrade windows, it MUST BE a clean install.

This is not mis-information, but MORE information. I didn't advocate not doing it, just that it is not a 'follow this or you are going to die' kind of instruction.

bootloader is not in general considered part of an OS, radio is in general quite independent too(not just in android but iOS as well and why there is the NOBB way of upgrade ), so is the recovery which is yet another seperate mini OS that takes no part in normal phone operation.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
You're not making any sense.

Can you run 4.2.2 on a N7 with a 4.1.2 bootloader and radio? Sure. Both the bootloader and radio APPEAR to be backwards compatible. I know this because I ran into an unrelated issue on my N73g during the upgrade process and had a hybrid install for a day until the full system images were released. However, there is a big difference between something working properly and working at all. The 4.2.2 update included many changes across the kernel and system as a whole. Many of these changes might tie directly into modifications to the radio, and possibly even the bootloader. Changes that could result in instability or other issues if everything isn't running the same version. And even if that isn't the case, one would think that an upgrade means better functionality or optimization. Obviously Google felt the need to release newer versions of both, so there certainly is a reason to upgrade. And unless someone can point to a flaw or issue with the latest release, regarding the radio or bootloader, there is absolutely no reason not to upgrade them too.

I will agree that there are situations where a radio upgrade might actually be detrimental and unwise for some people. The Nexus4 had that LTE hack which, according to what I read, got "patched" in the 4.2.2 release. If so, holding the radio firmware back might allow people to continue to take advantage of it (maybe, I don't have an N4 so can't speak on that topic from experience). And in some cases, chosing not to upgrade at all is a good decision for some. Many people stayed on 4.1.2 since 4.2.1 had so many issues. But doing a half upgrade is almost always a bad decision.

And I'm not sure why you felt the need to bring up clean installs of Windows, but in that regard you are once again mistaken with your "urban myth" claim. Sure, a person could theoretically go from 95->98->Me->XP->7->8, all by doing just an "upgrade install" each step of the way. But I can certainly guarantee that your system would have some serious issues that someone who did a fresh install of each would not experience. In fact, I would question whether it would even be useable after that many levels of upgrades. And it's not even a Windows problem. Even Linux distributions often recommend doing a clean install every so often to keep things fresh. The upgrade process isn't always perfect, and can result in things getting missed or just having a system bogged down with outdated crap. It's not a myth, it's the truth.
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
For home amateur, sure.
[Nexus 7 Q&A, Help & Troubleshooting] Wayno-san:
Well crap... I copied the debuggerd and the build.prop files over from the other post to the N7 again and this time it's failing to boot. Get's stuck at a blank screen. I can see that it's on because the backlight is lit but that's it. Gone from 4.2.1 to really bad in the last 24 hours. :eek:
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
Huh?

Easily fixable. Just flash the system image on top using fastboot.
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
If one can find the 4.2.1 image image. But then if one knows how to fastboot flash, why not just flash the kernel and system for 4.2.2 ?
[Nexus 7 Q&A, Help & Troubleshooting] Wayno-san:
I have the image for 4.2.2 but not having any luck getting adb to see the Nexus. Installed the USB drivers from the Asus website for the Nexus 7. I only need to be in the first bootloader (?) screen correct? The one immediately following pressing of the power and volume up/down buttons?

Again, I'm trying to be careful not to overwrite my data since I have gigs of software installed and would hate to re-download all of it again.

UPDATE: I managed to flash system for 4.2.2 via NRT and it boot up again. Do I still need to flash the boot partition? (it's currently in the process of updating apps).
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
yes, in general. boot and system usually goes hand in hand.

But being such a small upgrade(4.2.1->4.2.2), probably ok if you use the old kernel.

the rest is optional. For those who don't think so, get a copy of the OTA upgrade package and read what the upgrade script does.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
Wow, your posts just get more and more rediculous the more you babble on.

A huge portion of this upgrade was kernel related. To advise someone that it should be OK to skip the kernel is just plain stupid. Whether you go stock or custom, you should use a kernel built for the OS you are using. Even the custom kernel developers have incorporated the 4.2.2 changes in theirs. Let me guess - you're going to respond with another Windows metaphor about how it's OK to use a Windows XP kernel on Windows 7?

And enough with your ignorant "the rest is optional" claim. Go ahead and read the OTA script. Guess what it does? It upgrades the system, kernel, BOOTLOADER and RADIO (if 3G model). I didn't see any comments in the script letting me know that that part of the upgrade was superfluous and could be skipped if I wanted. Why you even bring this up makes me question your intelligence even more.

You have absolutely zero idea what you are talking about and are giving people false and misleading information. Stop.
[Nexus 7 Q&A, Help & Troubleshooting] chimpanzeexda:
you don't know how to read the OTA. of course it updates the bootloader and radio but read how it does it and not the superfluous what it does.

as for comment, of course there is no comment, they are generated automatically by a python script by comparing two build tree results :)

https://android.googlesource.com/de...ce877e05d216d34d354fda4ccd539/releasetools.py
[Xperia Z Q&A, Help & Troubleshooting] Diagrafeas:
I just found out that the default browser in Xperia Z/ZL is Chrome.

Is there a way to install Stock ICS/JB Browser (which is faster and supports Flash Player) and later Flash Player for it(or all in one package)?
[Xperia Z Q&A, Help & Troubleshooting] Ambroos:
Not possible to install the stock browser, but you can use Opera for Flash.
[Xperia Z Q&A, Help & Troubleshooting] reptile64:
Πήρες το Ζ?? :confused:
[Xperia Z Q&A, Help & Troubleshooting] Toss3:
Of course it is.
[Xperia Z Q&A, Help & Troubleshooting] Diagrafeas:
Όχι ρε πατριώτη, απλά είδα μερικά preview...
[Xperia Z Q&A, Help & Troubleshooting] Ambroos:
With root, yes. Without root, no.
[Xperia Z Q&A, Help & Troubleshooting] xperiax10.awesome:
Install Firefox !!

Note: Just google n install adobe flash as well..

sent from Giant Killer Galaxy Note 2
[Xperia Z Q&A, Help & Troubleshooting] budalica:
Browser

Install opera mobile ( so far I know that is the only browser that successfully finishes all downloads and gives no " parsing error " for downloads )

and then go here https://docs.google.com/file/d/0B3NaR-rGNd--T0dYaXJMWl9jNHM/edit?pli=1 and download and install flash player .
[HTC Amaze 4G] jpwall-cell:
Hi all,

I have unbranded version of htc version and its came with preloaded T-MOBILE ICS 4.0.3.

i have done s-off and unlocked bootloader to port nightmare sense 1.6.

Flashed a 4EXT recovery also.

When i have flashed Nightmare sense 1.6 via 4EXT, my phone stuck at Blue HTC Logo and vibrating every 5 seconds.

i have waited at least 15 minutes but no result.

Before i have flashed i have done , wipe cache,wipe delvik cache etc..

Bootloader version : 1.92.0002

Please Some one guide , is there anything i am missing ??

Please Help. :confused:
[HTC Amaze 4G] tagme:
Install version 1.1 and stay in recovery, don't wipe anything and then, install version 1.6 over 1.1... It worked perfect for me! I had the same problem two days ago!
[HTC Amaze 4G] jpwall-cell:
Thanks for replying.

I am gonna try it today. Let you know if works !!!

:angel:
[HTC Amaze 4G] aj_2423:
First off, are you positive it was on ics (4.0+)? Sounds like a common problem that happens when people try flashing a custom ics rom straight from GB. If it is for sure already on ICS, then it sounds like the kernel isnt flashing, which would be odd since you say you are s-off.

Did u try flashing another rom? You should always try flashing a different rom just to make sure if its something wrong with that specific rom or if something else is going on.

Hopefully its just something weird with the rom that doing what the guy above me said to do, will fix it
[HTC Amaze 4G] jpwall-cell:
Yes, ics is pre installed when i have bought a phone. its 4.0.3 rom from t mobile.

Stuck on htc logo but still i can boot into recovery.

one strange thing is that when phone came, bootloader marked as "Locked" but still i was able to use all sim cards.

thanks.
[HTC Amaze 4G] jpwall-cell:
can i rename nightmare.zip file as PG85IMG.zip and then flash ???
[HTC Amaze 4G] Double0EK:
No. Dont do that.

There is a video on the op for that rom for a how to install guide. Follow it to a T. If that doesnt work then install a different rom.
[HTC Amaze 4G] jpwall-cell:
Ok..Thanks..
[AT&T Samsung Galaxy S II SGH-I777] bqudamith:
Hi,

I bought a used i777 yesterday.. seller said that it has a problem with connecting to PC. i connected it to pc and it just charging only.can't mount storage.

im cwm also i cannot mount storage.. But internal storage seems fine..

i put it to download mode and flash it to stock ([Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root) by Entropy512)

it was successful .. but still have the issue.
[AT&T Samsung Galaxy S II SGH-I777] 122ninjas:
Hardware issue you have to replace the USB port

Sent from my GS4 running CM11 Kandy Kane
[AT&T Samsung Galaxy S II SGH-I777] bqudamith:
i did .. now it has new usb port.. still have the issue.. ;(
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
You posted this seven hours ago. And within that time, without knowing what was wrong when you first posted, you managed to find another usb port for this device, take it apart, install it, put it back together, test it thoroughly, and report back? I want whatever coffee you're drinking. Naow.
[AT&T Samsung Galaxy S II SGH-I777] bqudamith:
:D. When I posting the first actually phone is with a technician... To change the port..
[AT&T Samsung Galaxy S II SGH-I777] RatusNatus:
Flash a ROM that supported by Siyah kernel.

It has option to force USB mass storage.

Also check drivers on PC.
[HTC Pico (Explorer)] xpmode:
Can you post a logcat?
[HTC Pico (Explorer)] R. SAINT:
After unlock bootloader

Flash Custom Recovery

Flash Su

Flash any custom Rom.. :)

Follow this post

http://xdaforums.com/showthread.php?p=20763212
[HTC Pico (Explorer)] umarmsn:
thanks a lot

problem solved
[Nook Color Q&A, Help & Troubleshooting] kellym:
I used ManualNooter for my nook. As I recently installed a bunch of apps and ebooks, I thought I should back up my device. I went to Rom Manager for back up which then brought me to CWM when it was done to reboot. When I reboot it was stuck in boot loop. I turned the nook, then back on and whenever i reboot i get black screen of death. I can boot to CWM by holding all three buttons down. I tried wiping data, factory reset, reinstalling nooter zip, yet every time I reboot, I get black screen of death. Can someone help me figure out how to fix this? Thx.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Go to my NC tips thread linked in my signature and read item A15. That will restore you to stock and you can start over.

Sent from my Nook HD running CM10.1 on SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
My computer no longer recognizes the Nook (I have an HP laptop running Windows 8). Prior to the black screen, the computer did detect the nook when plugged in with the USB cable. How can I now copy the zip file to flash through CWM recovery? I have version 3.2.0.1 installed? I don't understand why trying to make a back-up file through the ROM manager would cause such failure? Thanks for your help.

EDIT: Should I now be trying the verygreen method via SD card? Apologies for the panic.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Make a bootable CWM card as described in my item A10. Then copy the 1.4.3 rom zip downloaded from A15 to the card. Put the card in the Nook, boot to CWM and flash the ROM zip.

Sometimes files get corrupted when writing them to the Nook. Obviously that is what happened with ROM Manager.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
What size SD card do I need? I tried copying the 1.4.3 rom zip (unzipped, used 7 zip to extract the other files) onto a 8 GB sandisc and a 16GB and both tell me the card does not have enough space. I've used Win32diskimager-v.07 (the link from manual nooter no longer works), I copied the CWM-5.5.04 image to the SD card. I had no trouble copying manual nooter onto the 8gb sandisc. I used a SD formatter program to format and wipe the disk before using it for this. Thanks.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
I guess I should modify my instructions. The 1.4.3 zip is so large that you need to use the 6.0.1.2 version of the bootable CWM SD. It has a little more room for the zip. It does not matter which size card you start out with.

Sent from my Nook HD+ running CM10 on SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
I'm back in business! It worked - whew! I had trouble with the 1.4.3 zip, so I used DizzyDen's 1.4.1. I was stuck in boot loop the first time I rebooted, then used the 5-6-7 partition fix zip, reinstalled the 1.4.1 zip and it worked like a charm. I also used the newer version of CWM you advised which was smaller in size, it's all on the 16gb SD card with no issue.

One last question, now that the stock rom is in order, am I safe to flash CM10? I'd prefer not to use manualnooter again as you said in a previous post, CM10 is leaps and bounds above nooter. If you think it's okay to flash, do I have to do the 8 count reset to fully wipe?

Many, many thanks for your clear, detailed instruction and patience!
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Glad you got it working. No, you don't need to reset. Just flash that 567 zip again and flash the CM10 rom. All should be ok.

Sent from my Nook HD+ running CM10 on SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
When I was last working on this, I had my external hard drive plugged into the computer via the usb port. I was backing up the files that were on my micro sd card, I had a 16gb in my droid bionic, I swapped it with the 8 gb I had in the nook when I couldn't get the older version of CWM on the card. Now when I plug in my external hard drive, all I see are the win32 imaging files on it. I take it, this process formats over everything plugged into a usb port? I've lost all my kids photos and videos, I can cry I'm so mad at myself for letting this happen. I've tried the two laptops we have and I get the same list of files in the folders. I guess this is one of those mistakes you only make once.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Oh no! Yes, burning a card writes over everything. There are some utilities that may let you rescue your old files, but maybe not. I would set it aside till you find out. I think the free MiniTool Partition Wizard has some paid companion products that may help.

Edit: just reread your post. It does not write over everything plugged into the USB. You just made a mistake when you burned once and selected the external drive letter. The same solution applies. Find a disk partition repair utility.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
Status 7 error

I finally found the time to do this. I flashed the 567 zip, then went to the CM10 download page for the 414 nightly encore zip. I received two errors:

symlink: some symlinks failed

E:error in /sdcard/cm-10-20130414-NIGHTLY-encore.zip

(Status 7)

Installation aborted.

What does this mean?

Thank you.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
I suspect a bad download of the CM zip. Try downloading again.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
You were right (of course!). I took the 407 zip and it flashed without issue. Very exciting! Thank you!
[Nook Color Q&A, Help & Troubleshooting] kellym:
Am I able to copy files to the SD card while it's running CM10? I wanted to copy some pdfs and ebub books to read and when I try to copy to the SD card it says the Nook is not responding or disconnected. I don't think this is a driver issue as I can see the Nook on my computer and can see the files stored either on internal storage or SD. When I'm in CM10 and go to file manager, I can only see what is on the SD card, I can't access any of my files that were on EMMC. That's fine, I have copies of my ebooks saved on my laptop, I just can't figure out how to read them now. Any thoughts?

Thanks.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
You need to be a little more specific.

There are two methods to connect to your PC with CM10 using the USB cable, MTP and USB mass storage. They are selectable in settings. Go to settings, storage, menu and USB computer connection. MTP is default and shows the Nook as just devices in Windows Explorer with no drive letters. If you choose USB mass storage, they show as drive letters in Windows explorer. But they do not contain anything until you activate them by touching a button on your Nook. And the button does not show if Android degugging is activated in settings.

So that is why I say you need to be more specific.

You say you can't copy to the SD. What are you seeing on your PC, drive letters or just labels that say internal SD and sdcard? And describe a little more the errors.

The reason you can't see emmc with the file manager that comes with CM10 is by default it is in safe mode. You have to change a setting to get it in root mode. Either get a different file manager like the free Root Browser Lite or change the setting in the CM10 file manager. To change the setting, press menu while it is open and you will see three dots in the lower right. Touch that. Go to settings, general settings and access mode and change it from safe to root. Then you will be able to see emmc.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
I think my quick reply didn't post. Anyway, thanks, again, for your help. When I went to transfer files from my external hard drive to the Nook, I was using the wrong lap top and then realized I had to update usb drivers which helped. I then followed your other steps to change settings, including safe to root, and I can now see all my files.

Can you recommend a file manager? The default one is a bit cumbersome.

Thanks again for everything.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
If you want a free one, I recommend Root Browser Lite. For paid, I like Root Explorer.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Q&A, Help & Troubleshooting] kellym:
I'd like to update to the May 4 nightly and new gapps, should I run the 567 partition zip again before flashing? If so, should I wipe cache and dalvik as well? Are you still using ADW launcher? I'm using Nova. Thanks.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
The 5/4 nightly is CM10.1. The version you were running earlier was CM10. You should be able to just flash the 5/4 nightly with only wiping the dalvik-cache. No other wiping or partition zips. Since CM10.1 requires a newer gapps (20130301), you should flash that too.

Yes, I still use ADW, but only because I am used to it and do not want to try something new.

Sent from my Nook HD+ running CM10.1 on emmc