Database Develop

Phone only boots to recovery, nothing else!!!

Hi!
Yesterday my msging app wouldn't open so I rebooted the phone, something I do at least once every 2 days, and it booted into recovery without me touching anything.
This error would also show up:
E:Can't read MISC:
(No space left on device)
I can't do ANYTHING. It ALWAYS goes to recovery mode. reboot bootloader goes into recovery. power + camera button goes into recovery. letting it boot goes into recovery.
--all with the same error in recovery, the can't read misc thing.
Did anyone have this problem? I didn't even flash anything, i was just rebooting the phone like I always do and it just appeared. Any ideas? Is this bricked? I don't want to get a new phone until I know I've tried everything. I've already scoured the net for this error with no results.
Thanks!

What recovery do u have? Do u know your phone info? Running a custom Rom? What have u done to the phone before now?
Not bricked btw if u can get into recovery it's fixable
Sent from my HTC Magic SparksMod using XDA App

Hey, thanks for replying!
I'm using RA 1.7 recovery, not sure what phone info you want, its a G1, I'm using CM 6.0 RC1 and have been using for a month now, and before that I've just been using CM, keeping my phone up to date with the stable releases (I don't flash the nightlies)
I'm glad that its not bricked. The problem is that it ONLY boots into recovery, even if I don't press anything...
Thanks!
johnson8cyl said:
What recovery do u have? Do u know your phone info? Running a custom Rom? What have u done to the phone before now?
Not bricked btw if u can get into recovery it's fixable
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse

Ok. I'm looking for spl and radio. Do u have danger spl? Or firerat mtd patch? Sounds like u ran out of internal memory somehow and now won't boot into os is why I ask
Sent from my HTC Magic SparksMod using XDA App

Oh Gotcha - yeah I followed the guide on the CM wiki, so I have danger SPL i believe, and yes, I used firerat's MTD patch
If i remember correctly I used the "all" thing so it went through everything in that patch.
I did that maybe around the time I got CM 6 - so I've been using CM6 and firerat's patch for maybe a month before this happened.
thanks!
johnson8cyl said:
Ok. I'm looking for spl and radio. Do u have danger spl? Or firerat mtd patch? Sounds like u ran out of internal memory somehow and now won't boot into os is why I ask
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse

Interesting. U don't need danger and mtd patch they do the same thing. I'm confused but maybe u have conflicting internal memory partitioning and that's causing it. Do u have a nandroid backup u can go back to that will boot into the os?
Sent from my HTC Magic SparksMod using XDA App

I do but it gives me the same error:
"Can't read MISC: etc etc etc"
This happens when I try to do anything, data wiping, wiping the cache, anything!
I don't even know if it acutally restored the image or not or if the wipe actually happened, because the progress bar is always present for whatever I'm trying to do, its just at the end the error comes up.
In terms of wiping I've tried wiping everything and installing CM6, to no avail. I can't re-reroot the device or downgrade it because recovery always comes up instead of fastboot... I'm stuck!!
Thanks for your insight!

If u plug your phone into the computer and select USB toggle does your sdcard show up on your computer?
Sent from my HTC Magic SparksMod using XDA App

Yep! I can select that MOUNT SD thing and I can transfer files over. Thats what I did to try and flash the rom again, but like always it just gives me that error after its done.

Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.

johnson8cyl said:
Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.
Click to expand...
Click to collapse
yeah hopefully something like that will be a solution.. thanks!

http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=669019
It would appear that you can run adb commands while in recovery using a shell. Maybe you can do that and use df to see what has low space. When you find that out you can cd to that directory and type ls and get a list of what is in that directory. Maybe delete a few things to clear some space? Can anyone confirm this?

johnson8cyl said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=669019
It would appear that you can run adb commands while in recovery using a shell. Maybe you can do that and use df to see what has low space. When you find that out you can cd to that directory and type ls and get a list of what is in that directory. Maybe delete a few things to clear some space? Can anyone confirm this?
Click to expand...
Click to collapse
Yeah I saw that post but I didn't try what the guy suggested - I will definitely try this when I get home. Too bad that post ended up having no resolution.

johnson8cyl said:
Well i hope you have a spare phone for the time being. I will try to figure something out and keep you informed. Or someone smarter than me will come along and give you the answer. It seems several people have had this prob. but i have not found the solution. Has to be something you can do from a shell in recovery mode to create some space or something to get back into the os. Ill get back with you hopefully with some good news.
Click to expand...
Click to collapse
If your in recovery, can't you just do a full wipe ?

crz6662 said:
If your in recovery, can't you just do a full wipe ?
Click to expand...
Click to collapse
He tried. Doesn't seem to be working. Gets same error. Need more help. Lol. Fun fun.
Sent from my HTC Magic SparksMod using XDA App

johnson8cyl said:
He tried. Doesn't seem to be working. Gets same error. Need more help. Lol. Fun fun.
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse
Yeah, when I do a full wipe it says wipe completed and then right after I get the same error.
What could be wrong!!

Ok, looks like you are in the elite group....this issue is not that common...
See below thread...some useful information from Lbcoder and ezterry....check and see if this can help..
http://forum.xda-developers.com/showthread.php?p=7225151
harryema said:
Hi!
Yesterday my msging app wouldn't open so I rebooted the phone, something I do at least once every 2 days, and it booted into recovery without me touching anything.
This error would also show up:
E:Can't read MISC:
(No space left on device)
I can't do ANYTHING. It ALWAYS goes to recovery mode. reboot bootloader goes into recovery. power + camera button goes into recovery. letting it boot goes into recovery.
--all with the same error in recovery, the can't read misc thing.
Did anyone have this problem? I didn't even flash anything, i was just rebooting the phone like I always do and it just appeared. Any ideas? Is this bricked? I don't want to get a new phone until I know I've tried everything. I've already scoured the net for this error with no results.
Thanks!
Click to expand...
Click to collapse

Yeah I found that thread already... but like me they didn't find a solution either. Plus I do not have a backup misc image so me deleting it would be rather disasterous.
Any other ideas or things I could try?
I'm just about ready to wait for the desire Z or the galaxy S instead of trying to tinker with this old phone...

Every custom rom gives a symlink error on install

My phone has/was working fine for the longest time. Was running cog 3.04. Ever since trying to update to cog4, i get symlink error EVERY time i try to install. I am flashing back to stock, and doing a master clear every time.
Thinking it was the cog4 rom, i have tried serendipity, and paragon. Though the error is on different lines, it gives me a symlink error everytime it is installing. What gives! I will throw this phone in the garbage if i have to be stuck on stock now!
On another note, anytime i try to restore a backup (os backup, not apps), it will successfully restore, but then when it reboots it is back to the stock recovery. UGH. Someone please give me some guidance!

Do you get an error like this:
E: Can't symlink /system/bin/cat
E: Failure a lin 7:
symlink toolbox SYSTEM:bin/cat
installation aborted
I probably get at least one of these errors every time that I flash. I have asked around and some people say that it can be a bad download. I would recommend downloading cog4 again and maybe even 2 to 3 times and putting all of those on your internal memory (name them cog4, cog4a, cog4b.zip or something like that). This is what I do and typically at least one of the three/four that I have on there will work.

Yea I had one of these last night and it was just a bad download. Compared the file size and they were different
Sent from my SAMSUNG-SGH-I897 using XDA App

PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.

xsteven77x said:
PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.
Click to expand...
Click to collapse
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.

xsteven77x said:
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.
Click to expand...
Click to collapse
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work

indomikey said:
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work
Click to expand...
Click to collapse
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.

xsteven77x said:
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.
Click to expand...
Click to collapse
How about formatting through recovery menu? and then reinstalling with odin

indomikey said:
How about formatting through recovery menu? and then reinstalling with odin
Click to expand...
Click to collapse
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.

xsteven77x said:
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.
Click to expand...
Click to collapse
But even then, why would cog 3.04 install? And no other custom rom?

xsteven77x said:
But even then, why would cog 3.04 install? And no other custom rom?
Click to expand...
Click to collapse
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?

indomikey said:
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?
Click to expand...
Click to collapse
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!

xsteven77x said:
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!
Click to expand...
Click to collapse
Sorry I'm noobish when it comes to ADB, try this thread.... not sure if it will help: http://forum.xda-developers.com/showthread.php?t=717874 realize, it is not specific for captivate or any of our ROMS, its talking about Cyanogenmod, but hopefully you can use something there
I have to head out, if you are still having problems when I get back, I'll keep searching, good luck

Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF

xsteven77x said:
Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF
Click to expand...
Click to collapse
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?

Pirateghost said:
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?
Click to expand...
Click to collapse
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.

xsteven77x said:
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.
Click to expand...
Click to collapse
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....

Pirateghost said:
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....
Click to expand...
Click to collapse
That didnt come out right. It was meant to read "i do not believe that every rom maker messed up the su symlink". Meaning that ya, it is just me, i know it works fine for everyone else.

[Q] How to start over?

I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.

atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv

Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.

Redownload?

Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?

I would redownload everything and try agian

littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?

atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?

I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App

http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium

wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.

Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.

i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721

I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!

i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.

How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).

i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop

Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.

re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used

Nexus 7 - Extreme lag + Exchange services error all the time

Hi,
Since the kitkat update I get exchange errors all the time, and the nexus is slow as shi...
Factory Reset didn't solve the problem.
Any Help?
Version: 4.4.2

No one with this problems?

Di0g0 said:
No one with this problems?
Click to expand...
Click to collapse
You could try reverting back to 4.3 then update to 4.4.2 by installing a custom rom.

Hum,
But this problems are normal on the oficial 4.4.2?

Di0g0 said:
Hum,
But this problems are normal on the oficial 4.4.2?
Click to expand...
Click to collapse
Nope they are not
---------- Post added at 11:34 AM ---------- Previous post was at 11:26 AM ----------
By any chance your extreme lag also affects the audio performances? I and a friend of mine had in the same period (for 2 weeks) EXTREME lag, signal lost on mobile network. The lag was so powerful that even music was interrupted. The only way to get rid of this was rebooting the tablet.
The most awkward part is that the bug persisted over ANY KIND OF ROM/KERNEL. Even the official one from Google Developers (any android version).
Best part: It was fixed by itself. Lags started to be increasingly rare and at some point they stopped.
I tried to catch some logs...at the moment of failure, just once they pointed me to some lines in the source code...so I quit trying to figure it out what happens..

I had the same problem, I solved it installing SlimKat, but probably you can solve it with any custom rom, I tried many times to restore 4.4.2 but always the same, only installing custom roms seem to solve it...
I remember it, is like a nightmare to me, turn the tablet On and let it 5 minutes before open any app, open Google Play and see how it lags, installing apps always causing freezing... It remembers me my Windows XP years...
At the beginning i let it thinking it will solve itself, haha, after months I was about to broke it with a stone

Kilek_360 said:
I had the same problem, I solved it installing SlimKat, but probably you can solve it with any custom rom, I tried many times to restore 4.4.2 but always the same, only installing custom roms seem to solve it...
I remember it, is like a nightmare to me, turn the tablet On and let it 5 minutes before open any app, open Google Play and see how it lags, installing apps always causing freezing... It remembers me my Windows XP years...
At the beginning i let it thinking it will solve itself, haha, after months I was about to broke it with a stone
Click to expand...
Click to collapse
Ya it's my situation now...
al3x1393 said:
Nope they are not
---------- Post added at 11:34 AM ---------- Previous post was at 11:26 AM ----------
By any chance your extreme lag also affects the audio performances? I and a friend of mine had in the same period (for 2 weeks) EXTREME lag, signal lost on mobile network. The lag was so powerful that even music was interrupted. The only way to get rid of this was rebooting the tablet.
The most awkward part is that the bug persisted over ANY KIND OF ROM/KERNEL. Even the official one from Google Developers (any android version).
Best part: It was fixed by itself. Lags started to be increasingly rare and at some point they stopped.
I tried to catch some logs...at the moment of failure, just once they pointed me to some lines in the source code...so I quit trying to figure it out what happens..
Click to expand...
Click to collapse
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.

Di0g0 said:
Ya it's my situation now...
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.
Click to expand...
Click to collapse
If you want to keep the official rom you can just try to reflash 4.4.2 wiping everything, just copy to PC the files you want to keep and after flashing copy again to tablet, i would recommend you to copy only important data, not everything, and specially not copy the folders with strange names that you dont know what they are

Kilek_360 said:
If you want to keep the official rom you can just try to reflash 4.4.2 wiping everything, just copy to PC the files you want to keep and after flashing copy again to tablet, i would recommend you to copy only important data, not everything, and specially not copy the folders with strange names that you dont know what they are
Click to expand...
Click to collapse
How to reflash the 4.4.2?
It's necessary root?

Di0g0 said:
How to reflash the 4.4.2?
It's necessary root?
Click to expand...
Click to collapse
Before flashing anything try to restore the tablet, copy all your stuff to PC and format it by going to settings / backup and reset / factory data reset and checking to wipe all on internal memory/sdcard
It will wipe all your data, apps and everything, so be sure that you dont forget anything to be copied to pc.
Maybe it solve the problem without flashing
About root and flashing:
You dont need it, but you can root it if you want after flashing,
I dont know how much you know about flashing and all that, so Im gonna make you an quickly tutorial
Basically all you need is:
Nexus root toolkit from here: www.wugfresh.com/nrt/
4.4.2 firmware (can be downloaded directly from the Nexus Root Toolkit)
And be sure that you have copied to PC everything you dont want to be deleted, you can just copy all to PC and after flashing copy to tablet only what you want...
On tablet turn on USB debugging, on developer options (To unlock it go to settings /about tablet /build number and click it many times until it says "you are now a developer", then go back and you will see it)
When its done follow the Nexus Root Toolkit instructions to "flash stock + unroot" (by clicking a button with that text) you should select Android 4.4.2 (KOT49H) and check the option "automatically download"(dont remember what the option says exactly)
And the tool will download it and tell you when you have to do something. Just dont disconnect the tablet until the tool ends its job
Maybe you should install some drivers if you get an error message like "device not found"
If you want to know more about insalling drivers, you get any problem or something else just tell me, but maybe im gonna make you wait because tomorrow is my birthday and I wont be checking it for few hours.

Kilek_360 said:
Before flashing anything try to restore the tablet, copy all your stuff to PC and format it by going to settings / backup and reset / factory data reset and checking to wipe all on internal memory/sdcard
It will wipe all your data, apps and everything, so be sure that you dont forget anything to be copied to pc.
Maybe it solve the problem without flashing
About root and flashing:
You dont need it, but you can root it if you want after flashing,
I dont know how much you know about flashing and all that, so Im gonna make you an quickly tutorial
Basically all you need is:
Nexus root toolkit from here: www.wugfresh.com/nrt/
4.4.2 firmware (can be downloaded directly from the Nexus Root Toolkit)
And be sure that you have copied to PC everything you dont want to be deleted, you can just copy all to PC and after flashing copy to tablet only what you want...
On tablet turn on USB debugging, on developer options (To unlock it go to settings /about tablet /build number and click it many times until it says "you are now a developer", then go back and you will see it)
When its done follow the Nexus Root Toolkit instructions to "flash stock + unroot" (by clicking a button with that text) you should select Android 4.4.2 (KOT49H) and check the option "automatically download"(dont remember what the option says exactly)
And the tool will download it and tell you when you have to do something. Just dont disconnect the tablet until the tool ends its job
Maybe you should install some drivers if you get an error message like "device not found"
If you want to know more about insalling drivers, you get any problem or something else just tell me, but maybe im gonna make you wait because tomorrow is my birthday and I wont be checking it for few hours.
Click to expand...
Click to collapse
I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !!

Di0g0 said:
Ya the tablet is extremely slow, and freezes sometimes for some seconds!
What do you mean with "rebooting the tablet"? Factory Reset on the original recovery menu?
Thanks.
Click to expand...
Click to collapse
No...just a simple restart. As I stated, I tried different resets and flashes and everything and nothing worked...
Di0g0 said:
I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !!
Click to expand...
Click to collapse
Be careful about "Returning to stock" method as I think Google broke their "flash-all.bat" from the arcvive of Android 4.4. Flash every file by your hand. I used that idiotic flash-all on any android version, but on 4.4 it completely broke my motherboard by flashing wrong boot.img.

[QUOTW=Di0g0]I tried to restore the tablet and that didn't worked (look at the first post).
I will try the 2º option, thank you !![/QUOTE]
Okay, I was no sure that you also format "SD card" factory reset do not delete user data/sd card on some devices and Im not sure if in N7 you have to check the option
Try the 2° option but take a look at this comment:
al3x1393 said:
No...just a simple restart. As I stated, I tried different resets and flashes and everything and nothing worked...
Be careful about "Returning to stock" method as I think Google broke their "flash-all.bat" from the arcvive of Android 4.4. Flash every file by your hand. I used that idiotic flash-all on any android version, but on 4.4 it completely broke my motherboard by flashing wrong boot.img.
Click to expand...
Click to collapse
If thats true then try to flash 4.3 and install 4.4.2 by OTA, just select 4.3 instead 4.4.2 when you are about to flashing

Ok,
I flashed the nexus 7 2012 directly to the factory 4.4.2 using the nexus root toolkit, and everything is working fine without problems, at least for now.
The tablet isn't giving exchange errors, and doesn't hang everytime, but I only used it for some minutes, lets see how it works after some days/intensive usage.
Anyway, as I said, I flashed to 4.4.2 directly using the toolkit, and it worked without any problem
Thank You!

TWRP - backup partition error?

For some time now when making a TWRP backup I see these two errors,
Unable to locate '/aboot' partition for backup
Unable to locate '/modem' partition for backup
Click to expand...
Click to collapse
See screenshot.
The phone boots and has no errors, makes calls etc etc. It seems I can ignore the errors but wondering if anyone else sees the same or knows why?
OS is OOS 5.08, and have seen this this through a number of TWRP versions, now on v3.2.3.1

btb55 said:
For some time now when making a TWRP backup I see these two errors,
See screenshot.
The phone boots and has no errors, makes calls etc etc. It seems I can ignore the errors but wondering if anyone else sees the same or knows why?
OS is OOS 5.08, and have seen this this through a number of TWRP versions, now on v3.2.3.1
Click to expand...
Click to collapse
After I posted the question I reset TWRP to defaults and the errors went away, I'll leave up in case anyone has a similar problem!

btb55 said:
After I posted the question I reset TWRP to defaults and the errors went away, I'll leave up in case anyone has a similar problem!
Click to expand...
Click to collapse
Weird, but at least it went away!
Just as an aside, the TWRP build you are using will mess your Encryption up if you ever use it to Format. (Fine for normal operations though).
If you do ever need to Format for whatever reason, remember to update to 3.2.3-10 first:
https://androidfilehost.com/?fid=1395089523397907195

Dirk said:
Weird, but at least it went away!
Just as an aside, the TWRP build you are using will mess your Encryption up if you ever use it to Format. (Fine for normal operations though).
If you do ever need to Format for whatever reason, remember to update to 3.2.3-10 first:
https://androidfilehost.com/?fid=1395089523397907195
Click to expand...
Click to collapse
Thanks, I've update.