Develop Bugs

[Q] Rom manager installs corrups phone

Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.

Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.

Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.

drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.

Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?

I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App

Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.

aiight sweet, I'll give that a go.
Cheers!

You're most welcome.

drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?

Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.

I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.

I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway

nvm I got in the recovery boot. Yeh the CWM-R are the same version.

drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.

drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.

Rebooting loads!

Hi My GNex is rooted.... and I've been running a Modoco ROM for 3 months with no problems. Recently I flashed his latest after a wipe and reset.... it worked fine for a day until this morning when I get continual reboots!
I wiped again completely tonight and installed AOKP ROM and it was fine for an hour or so, now its started rebooting again... what should I do?
Should I try and return it to Samsung... I'm guessing I'll have to flash stock and unroot (if thats possible?)
Thanks

What stage does it get to before it reboots again? (Google Logo or Animated splash or in the OS?)

mine on stock done it and now on google logo, re flashing stock images now, takes the piss abit.

These things happen. Frequent nandroid backups are highly recommended

It boots to the OS, then its fine for 30 minutes... reboots, then typically the reboots start to become more and more common!
I've just tried the superwipe script and reflashed again. I'll try going to stock otherwise.
I did a Nandroid by when trying to recover it said there was a check-sum error or something!

Did it say there was an error restoring data?
This happened to me, essentially the data partition had become corrupted, and no amount of custom ROM flashing would help. I had to flash stock images to fix, as I could not restore any back ups I had made.
Make sure you back up your SD card contents, as it's wiped during a factory image flash.
Sent from my Galaxy Nexus using XDA App

I think that's what I'm going to have to do
Though I don't get any messages saying there's an error restoring data!

It sounds like you have an issue with your recovery. Reflash CWM see if that fixes it and make sure its the right version GSM or CDMA!. I'm 90% sure that will fix it. (After that flash rom and wipe data.)

If its a corrupted data partition then MAYBE fastboot oem lock and then oem unlock may fix it.
Just back up your sdcard contents first.
If that doesn't do it then flash the stock images.

Can't boot ANY rom after Nandroid Backup

So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!

Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...

drew_grant said:
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Click to expand...
Click to collapse
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.

Mikef3j said:
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
Click to expand...
Click to collapse
First thing I did.

xIC-MACIx said:
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Click to expand...
Click to collapse
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?

drew_grant said:
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
Click to expand...
Click to collapse
Use fastboot.
Sent from my Xoom using xda premium

Has anyone determined why this is happening with the new JB roms? I got stuck in this situation last night and would love to try again if I could just figure out where I went wrong the first go around.

This is srsly the last time I'm posting this.
Code:
adb pull /data/media/ /SDBACKUP/
To get your SD contents back.
Then fastboot flash back to stock.
JB changes the directory that your data resides in...which seems to be why many are having problems.
I, however, have swapped back to an AOKP nandroid just fine.

Problems Flashing and Restoring custom roms

I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.

Bdadd34 said:
I have had problems flashing and restoring Roms both stk and aosp. By problems I mean getting stuck at boot screen after flash and backups failing at data and if restored without data stuck at boot. The only remedy I have found is a total internal memory wipe. I have tried many wiping techniques none worked long term. Last night when I had these problems again before I did full internal data wipe I used twrp file manager and looked around and notice after factory reset wipe which is suppose to wipe all data but data/media I still had data/app and when I tried to manually erase it failed. even with system mounted I couldn't delete. Maybe someone else having troubles can also check to see if data/app is still there after wipe. I dont know if its recovery related or caused by the aosp sd format. Maybe a combination? I don't think im the only one having these problems so I wanted to start a thread to try to figuer this out. Any help is greatly appriciated.
Click to expand...
Click to collapse
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
spleef..If you can check data/ folder from twrp before wiping internal data...I wonder if the data/app is from backup or previous rom as I believe it is being corrupted to not be wipable.

spleef said:
yeah just happened to me just now too dammit... tried to restore my lifeless backup to update prl and profile... restore went fine but i get the lg logo flash then blacjk screen....going to try again but damn this is one issue that need resolving.. usually i have no problems which is weird cause im not doing anything different maybe been couple weeks since my last restore to lifeless using same backup that wont work now
Click to expand...
Click to collapse
Bdadd34 said:
I'm going to try deleting data/app before booting to recovery when I flash from now on to see if it helps. I think something to do with the size of that folder is corrupting data in recovery as it seems to happen only when I run a rom for a few days adding apps. If I flash right away it works fine.
Click to expand...
Click to collapse
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.

engine95 said:
I'm seeing this happen to a lot of people and I don't understand why. I've been flashing all the ROMS and restoring from backups for months now with no issues. Maybe I just got a lucky phone.
Maybe this will help many of you.
In TWRP 2.5.0.0
Click Wipe
Swipe to Factory Reset
Back button to the Wipe menu
Advanced Wipe
Tick all 4--
Dalvik
System
Data
cache
Back to main TWRP menu and restore/install
Like I said, I've had no issues doing it this way. May the Force be with you.
Click to expand...
Click to collapse
thanks for the advice but I have wiped every which way including rebooting recovery after wipe before installing..no luck
I think it started from initially wiping internal memory and reloading data from pc backup to get rid of the aosp stuff on the sd card..
My advice to anyone else who wants the sd card back to stock is to leave it alone.

normally i have no problems going back and forth.... want to hear something even weirder.... restored my aokp and it booted into lifeless.... now either i restored lifeless again...which us possible big fingers and always in a hurry... or something very funny going on in my recovery i am on the older version 2.4.4 i think it is haven't updated it yet cause of all the issues people are having and the different wipe area... just seems weird top me but guess its time to do it and at least see if it will help
Sent from my LG-LS970 using xda premium

OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium

Bdadd34 said:
OK this is crazy...deleted data/app with ROM manager root browser..then entered recovery wiped everything in advanced wipe..system..both caches and data..then rebooted recovery checked data\ there was nothing but \media and a config XML file..then flashed a STK custom ROM...got stuck at lg boot logo. Got back to recovery went to filemanager and there it was data\app with all the apps had had installed in my aosp ROM. Loaded aosp backup and all is fine....but I deleted data\app with root browser and in recovery and still there.. :banghead:
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I usually wipe all data by all data I mean including data/media then I have no problems. Keep in mind this erases sdcard so you need to have rom on computer and adb push it to the sdcard to flash
Sent from my LG-LS970 using xda app-developers app

I think I will start from scratch with lgnpst and leave the internal memory alone this time and see if that was the cause.
update: Im back to stk going to root then unlock with freegee..Any advice for using freegee it soft bricked me last time and I had to flash tinybin

Well since I went back to unrooted and locked and started from scratch..tried using free gee then flashed tinybins all has gone well..no flashing problems anymore..I think messing with the internal memory is what caused my problems. Been almost a week and I have flashed between several roms and restored from backup many times.
Sent from my LG-LS970 using xda premium

I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to

BMP7777 said:
I had not seen this thread before or I would have chimed in by now. My issues don't go back to the 28th; only over the last week. My issue goes like this: I built and flash my own Beanstalk 1.561 ROM, and had no real functionality issues. I played with it for a day or two before realizing I hadn't backed it up. Did that, and at reboot, got a loop. WTF? I immediately thought it was the ROM, so I wiped Factory, dalvik and cache, and ran one of my older back ups. No problem. Flashed a new build of JellyBeer, updated everything, and backed it up. Restart and loop. Now I'm REALLY pissed. Restored my original stock back up; no prob. Okay, now I'm more confused than angry. Go to update my recovery(already running TWRP 2.5, but wanted a fresh install) Install of fresh recovery fails. I forget what the fail was for though, I was spitting nails at this point. Soooooo, really long story a little shorter, I downloaded and reinstalled TWRP 2.5, no problems. Dumped all of my 'standard' flashing files(Banks Gapps, Smoocha kernel, newer ROM downloads, etc), and redownloaded everything. Installed a fresh download of Beanstalk 1.561(build 7/07; original problem was on build 7/05), updated it, and performed a back up. SAME ISSUE. I think you can imagine the string of curses I want to put here. So, for me all back ups older than last week work fine. ANY BACK UP MADE EVEN TODAY FROM ONE OF MY OLDER BACK UPS RESTORES AND BOOTS FINE. But, any back up made form any of my newer builds(7/01 to now) flakes out. I haven't had the time to try other ROMs, and to be honest, I haven't tried to run anyone else's work since trying to install Vectus a few weeks ago. Does anyone have any info, advise, similar experience? This is driving me nuts, so anything would be great. PM me if you want to
Click to expand...
Click to collapse
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium

engine95 said:
Correct me if I'm wrong, but from some of your posts, i never hear you mention wiping /system. That could be some of the problem. Even restoring should have /system wipes.
Also on your backups are there at least 7 files in each? You might have ticked a button and aren't backing up /boot
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Thanks for the response. I'll check into that advice and post what happened.
Checking on my one back up that I haven't deleted before anything else.This is what I have:
boot.emmc.win
boot.emmc.win.md5
data.ext4.win
data.ext4.win.md5
efs1.emmc.win
efs1.emmc.win.md5
efs2.emmc.win
efs2.emmc.win.md5
efs3.emmc.win
efs3.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....

BMP7777 said:
It looks right to me, but honestly, I never looked that closely at the files. Looks the same as the other backups.....
Click to expand...
Click to collapse
Compared it to mine and it is. You just have the efs also. Maybe try formating /system then restore.
Also maybe try backing up without efs.
Just more options to try.
Sent from my LG-LS970 using xda premium
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Also, have you tried a flashable TWRP?
Sent from my LG-LS970 using xda premium

I have had this problem and I thought it was just my ROM, I have been making changes to different apks and then flashing and if it bootloops I restore previous working version. Several times however the restores work and then bootloop or they fail in recovery. When this happens I wipe cache, dalvik, system, internal memory, data, factory reset. Then I go into download mode and LGPNST and flash original stock unrooted, then root then flash teeny bins, then I'm ok. It's a pain, thought it was just from me tinkering with things. Anyway that gets me working again, then I can reflash the ROM.

Update: More recently when I've had this happen I just format data and then push what I'm trying to flash into /data/media. Much easier.
Sent from my LG-LS970 using xda app-developers app

[Q] Nexus 7 won't boot after updating to KitKat?

So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it

If you are not afraid to loose your data. Enter the recovery and do a factory reset.

BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.

vbaros said:
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
Click to expand...
Click to collapse
sfhub said:
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
Click to expand...
Click to collapse
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Sent from my Nexus 7 using xda app-developers app

BraddahBoi808 said:
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Click to expand...
Click to collapse
Sorry, I didn't read your original post closely enough, if you are bootlooping at google, then it is a problem with /system and wiping won't help. If you were looping at the bouncing balls or X, then that is user data related so wiping usually fixes it.
If you are stuck at Google, something went wrong with your flash or your flash memory got corrupted.
I would try reflashing the factory image, making sure to do the -w wipe option (by default that is what flash-all.bat does)
Make sure to pay attention to any errors that might show up.

I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35

msk said:
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
Click to expand...
Click to collapse
It worked all fine until i wiped data and cache at the end of your process... After rebooting it still bootloops and is now hanging at the Google sign... At this point I have no idea what I'm doing wrong...

Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app

BraddahBoi808 said:
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What method did you use to flash the factory images?
Sent from my Nexus 7

RMarkwald said:
What method did you use to flash the factory images?
Sent from my Nexus 7
Click to expand...
Click to collapse
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app

BraddahBoi808 said:
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So you did all of the steps listed here? http://forum.xda-developers.com/showthread.php?t=2469508

Yes..
Sent from my Nexus 7 using xda app-developers app

Now sure if this means anything, but when i send the ota update zip through aideload, at the end it gives me
script succeeded: result was [/system]
Does that mean it worked or the system had something wrong??

Not sure on that one.
- Sent from my Galaxy S3

K this stupid thing must hate kit Kat or something cause no matter what ROM I try to flash that's kit kat it still don't boot. I'm tired of this already. Idk what else to do. I thought nexus devices were suppose to be the easiest ones to get updates... /end rant
Sent from my SCH-I545 using xda app-developers app

BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..

Zaphodspeaks said:
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Click to expand...
Click to collapse
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...

BraddahBoi808 said:
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
Click to expand...
Click to collapse
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..

Zaphodspeaks said:
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Click to expand...
Click to collapse
I can restore back to JSS15R 4.3 fine and the device works fine, no issues. It's just for some reason it doesnt like anything 4.4, which I find very odd. It still hasn't gotten to OTA update either. After updating to 4.4 and it hanging on the Google screen, it can boot into stock recovery fine. I have wiped data and cache in there too to see if that works but nothing. Thanks for all your quick help by the way. So the method your saying now.. Do I flash that from my stuck 4.4 or from rooted 4.3?

I would try that from 4.3....Dont use the stock recovery.. Flash it from TWRP..