I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob
I'm in the same boat. Trying not to have to start from scratch so I really prefer to run the update instead of flashing the entire device. Vague recollection was that debuggerd gets replaced by stickmount but I tried reverting to the backup file that I had and it still gave me the same (Status 7) error.
I think we just have to find the correct version of debuggerd and overwrite it, then sideload. Let me know if you make any progress.
If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk
skiman10 said:
If I remember correctly you have to be completely stock. If you changed anything the update will not work.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.
Wayno-san said:
It's only aborting on that one file as far as I can tell. Would love to get an original copy and just overwrite the one that's on my Nexus 7 to try if it would work.
Is there a way to get back to stock but not lose all the installed apps and data? I don't mind not using the update file, I just do not want to go through the hassle of setting everything back up (reloading apps, wifi, etc.) again.
Click to expand...
Click to collapse
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk
skiman10 said:
Is there anything you changed when you were messing around with it? Like adding the stock browser or flash? Something like that...
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.
Wayno-san said:
No, I just recall having to change the debuggerd file to get stickmount to work. I don't remember the details exactly (it was a long time ago) but I'm pretty sure that is all it was.
Click to expand...
Click to collapse
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk
skiman10 said:
Sorry then I can't help you. I would titanium backup and go completely stock or flash or something. Hope you get it worked out buddy.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
KodachromeBob said:
I am currently running Nexus 7 (2012) Wifi Android 4.3 Build JWR66Y rooted with CWM and stick mount but when I try to update Android 4.4 OTA it fails on status 7 system bin debuggered. As I was able to just run the Android 4.3 OTA when I upgraded from Android 4.2.2 without any problems this Android 4.4 update is certainly very frustrating. Since I am still a newbie at this could you please provide a step by step of how to get this to work using NRT? Do you have to unroot before installing the update and then reinstall all your apps after? Any help would be greatly appreciated.
Thanks,
KodachromeBob
Click to expand...
Click to collapse
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck!
Step by Step Required For This Noob PLEASE
Wayno-san said:
No worries. I just found another post (sucks that search is down) that says that if we just flash the boot, system, and bootload img files from KK that it should update without deleting programs or data... I think I'll give that a try.
---------- Post added at 02:42 PM ---------- Previous post was at 02:10 PM ----------
Apparently I flashed in the incorrect order and just flashed boot and system. Nexus 7 appears to have booted up and my apps/data are still present. About screen shows
Android: 4.4
Kernel version: 3.1.10-gee1a0b2
Build: KRT16S
Do I still need to flash bootloader?
---------- Post added at 03:13 PM ---------- Previous post was at 02:42 PM ----------
The method of flashing boot, bootloader, and system img seems to have worked. Might want to give that a shot if no one uploads the proper debuggerd file. Best of luck![/Q
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse
KodachromeBob said:
Did you use NRT to accomplish this and would you mind providing the step by step procedure and files that made this successful for you? Being new at this I just don't want to screw it up.
Thanks in advance
KodachromeBob
Click to expand...
Click to collapse
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)
Yesterday my nexus downloaded the update and asked me to press 'ok' to shut down tablet and install.
Just like after every system update the following happend:
Nexus turns off
... thats it, it simply turns off and nothing happens! Device is 2 weeks old now and i am thinking of returning it.
I'm on 4.3 and system tells me that there is no update available...
Nexus 7 2013 sucks!
Sent from my XT910 using xda app-developers app
Wayno-san said:
Yes, just download the 4.4 image from google here:
https://dl.google.com/dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
Unzip it until you can pull out the 3 image files I mentioned above. Then use NRT to Flash the files one at a time. You should be good to go. (fingers crossed)
Click to expand...
Click to collapse
Yes, you have to unzip the .tgz file, then unzip the .tar file to get the folder with the image files. 7zip works great. If you are on the stock rom/kernel rooted with a custom recovery (CWM or TWRP) you can fastboot flash on both the system.img and boot.img. Those are the only ones you need. It doesn't look for file verifications in system, it just puts the latest system image there. Flash the latest supersu in custom recovery and you get back root.
Successfully Updated to KRT16S
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob
My nexus does not even have the Option to start in bootmenue.
As i told, this tablet sucks.
Sent from my XT910 using xda app-developers app
KodachromeBob said:
Could not have done it without the help of Wayno-san. I flashed Boot, Boot Loader and System images with NRT and voila a successful update to KRT16S. I had to ROOT again and reinstall Busy Box but that was not a problem. Thanks again Wayno--san for all your support.
KodachromeBob
Click to expand...
Click to collapse
You're welcome Sir!
Can anyone send me the JWR66Y debuggerd?
I'm also stuck trying to update to 4.4 and I'm hoping to avoid reflashing back to the stock /system. I've reverted all of the system files I touched so it's only debuggerd that's holding up the update. Thanks!
--
kcc
I also had to update manually because of Status 7 update in CWM during OTA flash. Slight inconvenience yes, but nothing major as I didn't flash "Data" via Fastboot command. Had all my apps retained in the next boot
Missing ART though. I don't really want to flash a custom ROM for it.
Anyone willing to send me the KRT16S debuggerd?
If no one has the JWR66Y version, I can just edit the install script to not check (and not patch) debuggerd, then load the KRT16S debuggerd after the update completes. Thanks!
--
kcc
Related
It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
hasbrobot said:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
Click to expand...
Click to collapse
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Ben Ling said:
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
jazzespresso said:
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
Click to expand...
Click to collapse
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Ashenphoenix said:
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Click to expand...
Click to collapse
my OTA failed too, different error. this usually always the case if /system/ folder integrity check failure (error 7), means files in /system/ folder are not original or modified. Yours does not give any details, but I bet it is. to see what error, try to flash it thru CWM or any other custom recovery you use.
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Ben Ling said:
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
okay...will my data be erase when installing?
Sent from my Google Nexus 7 using XDA Premium App
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
Tried your SystemUI,don't work...keep on stopped...so I replace back...
Sent from my Sony Xperia™ sola using XDA Premium
I guess I'll download the Nexus Toolkit, click on the flash stock + unroot button, so it flashes the stock 4.2.2 and then I'll try to OTA update again.
I already unrooted, but I think it's not a problem.
Seems like it is not fixable!
I used fast boot to push my missing file.
I used es file explorer.
I used titanium back up to make the app, system...
No way, nothing. Not the slightest luck.
(My missing app is xt9ime.apk)
I haaaaaate this situation.
the worst thing is that xt9ime.apk is asus keyboard, and it is disabled by google on nexus 7.
why should not having an app that they don't want to use be a problem. X(
Sent from my Nexus 7 using XDA Premium HD app
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
jaysus145 said:
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
Click to expand...
Click to collapse
I did full unroot, and I also did a factory reset, but it still fails to install.
Using Wug's Toolkit to flash stock 4.2.2 is a good idea?
Then try to OTA update 4.3 again?
Same problem
Hi,
I think I have the same problem:
What to do?
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is Fastboot?
Theuntje said:
What is Fastboot?
Click to expand...
Click to collapse
Sadness.
Fastboot is a utility used to control the base fastboot firmware on many Android devices. It lets you do low-level actions such as flashing a custom recovery, ROM, or kernel. Toolkits run fastboot behind the scene, but automate the commands for newer users.
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
I downloaded the system file here: https://developers.google.com/android/nexus/images#occamjwr66v
Then, in the Nexus Root Kit, launch " flash stock + unroot" and select the downloaded system file.
The flash lasts 5 minutes, and the system will reboot.
Then you need to reactivate the usb debugging .
The next action is to relock the Nexus, with the "OEM Lock" in Nexus Root Toolkit.
The system will reboot after flash.
Then, the 4.3 update will be available automaticaly but this time the installation won't crash.
I hope this could help.
el chibro said:
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
...
I hope this could help.
Click to expand...
Click to collapse
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
RocketOptics said:
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
Click to expand...
Click to collapse
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I wanted to save my data and wasn't sure if going directly to 4.3 would be safe. Was just being cautious and letting the OTA do the update.
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
I'm stuck too, how did you flash the stock file?
sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587296
here for 12b recoveries
and search through the thread for edited roms
I have the TMO verison but plenty of my friend have successfully flashed trwp using flashify also what kernals and roms are you trying to flash over? are you clean or dirty flashing?
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
zekurosu said:
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
Click to expand...
Click to collapse
Can you post a link to the latest twrp recovery for tmo? ive been looking but couldn't find one.
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
ceredics said:
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
Click to expand...
Click to collapse
Have you tried to flash back to the 12A and not use the 12b
tbishop91 said:
Have you tried to flash back to the 12A and not use the 12b
Click to expand...
Click to collapse
Nope, the one i was using i believe was the 10. Also, when it boots it was secure boot unsuccessful. Im seeing a handful of people stuck with this with no solution thread.
You used ioroot did you open a cmd prompt and push a loki file using a adb command
tbishop91 said:
You used ioroot did you open a cmd prompt and push a loki file using a adb command
Click to expand...
Click to collapse
I used ioroot res i did. But no i dont recall EVER using adb....
ceredics said:
I used ioroot res i did. But no i dont recall EVER using adb....
Click to expand...
Click to collapse
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
tbishop91 said:
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
Click to expand...
Click to collapse
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
ceredics said:
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
Click to expand...
Click to collapse
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
tbishop91 said:
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
ceredics said:
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
Click to expand...
Click to collapse
have you tried to use twrp instead of clockwork, I think that's what cwm stands for make sure whatever you do you double check that method does not harm your device.
It didnt work... Fckkkkk. So to make it clearer
VZW
Lg G2
Rooted with io
Rom when rooted was stock latest ota
currently stuck in CWM with nothing to boot into because of consistent abortion then status 7.
can you sideload aboot.img from adb
Id need step by step instructions on how to sideload something because ive never messed with adb. It seems if i adb a different recovery or a specific file it may start to work. Can i sideload TWRP?
let me consult my know it all friend lol
Hello,
I rooted my Nexus 7 (older generation) with wug tools. Since 4.2 I have been updating the firmware with no problem. However this time 4.4.4 will not install properly. After reboot it (in firmware installation page) it will issue an error and after a few minutes will reboot back to Android.
Every few days the 4.4.4 will prompt to install again and nothing is changed.
Does anyone experience the same thing? Do you know any workaround?
Thanks.
Try Odin?
You made system/App changes that the update needs to patch the os.
sarmadys said:
Hello,
I rooted my Nexus 7 (older generation) with wug tools. Since 4.2 I have been updating the firmware with no problem. However this time 4.4.4 will not install properly. After reboot it (in firmware installation page) it will issue an error and after a few minutes will reboot back to Android.
Every few days the 4.4.4 will prompt to install again and nothing is changed.
Does anyone experience the same thing? Do you know any workaround?
Thanks.
Click to expand...
Click to collapse
After you rooted the device You Likely have changed a System File or app that The update is trying to push a Update for. Some Root required apps can do this as well. Since your asking this . I would assume you do NOT Know whats modified. So your Best bet is to RETURN YOUR DEVICE BACK TO STOCK UN rooted. Not Recommended but you can use THE TOOL KIT To do this . Fastboot thru adb Would be best.. Flash THE Factory stock image from GOOGLE FOR 4.4.4 AND THEN Re root your Device. YOU WILL Have to back up your data as this will cause you to loose everything..
Hope this helps.
There are plenty of threads on here to explain how to RETURN To stock .So I will not give Instructions.
---------- Post added at 11:21 AM ---------- Previous post was at 11:18 AM ----------
samjam said:
Try Odin?
Click to expand...
Click to collapse
ODIN IS A Samsung device flash utility .. USE FAST BOOT Via adb for Nexus devices ..
To add on, you can try with adb, erase system, boot, cache and recovery if necessary and flash stock 4.4.4 equivalent. This way, your device data is still intact.
Sent from my Nexus 7 (grouper) using Tapatalk
Solution: get paranoid android
JazzieBoi said:
Solution: get paranoid android
Click to expand...
Click to collapse
regardless of how you feel custom roms arent for everyone
why not just flash the factory img via fastboot and get it over with?
I just flashed factory 4.4.4 and rerooted, no big deal.
simms22 said:
why not just flash the factory img via fastboot and get it over with?
Click to expand...
Click to collapse
This ^^^
Exactly!
As others said, download the tgz from the nexus stock images site, extract it and put it in your adb folder. Boot your device into bootloader and type-
Code:
[fastboot update image-nakasi-ktu84p.zip/CODE]
Let it update and reboot. You will be unrooted. Flash your recovery and Supersu again and you should have rooted 4.4.4 :)
It's out guys!
https://developers.google.com/android/nexus/images
jarjar124 said:
It's out guys!
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the heads up!
if anyone is going to flash this, could you please benchmark it encrypted?
i saw a bench today where someone had fullspeed even encrypted. is this on 5.0.1?
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
wolfnumba1 said:
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
Click to expand...
Click to collapse
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
ohhdavid said:
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
Click to expand...
Click to collapse
There might be as there are new binaries I believe. I'll need to check when I'm home.
BRKotucs said:
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Right that was only for flashing OTA update files right? Doing it through fastboot should just work, taking nandroid and then flashing after will post status
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
---------- Post added at 06:59 AM ---------- Previous post was at 06:57 AM ----------
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 4 using Tapatalk
wolfnumba1 said:
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
Nope, I took 5.0.1 kernel, unpacked it, changed from force encrypt to encryptable and repacked. Will post it in that thread as soon as I'll get back to PC.
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
I have noticed the same thing on 5.0
I got the amazing speeds upon first boot after flashing then never again. 160/140 is similar to what i'm getting now. was that the same as encrypted?
Maybe it was all a placebo.
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
XorZone said:
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
Click to expand...
Click to collapse
Thanks!
wolfnumba1 said:
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Click to expand...
Click to collapse
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
What app are you using to measure?
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
Ill let you know, its updating now after flashing however I am going to reflash like I said before, I will check root status first though, I am sure the root is gone now.
Click to expand...
Click to collapse
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
What app are you using to measure?
Click to expand...
Click to collapse
1. cf-autoroot after flashing and 1 time booting works fine
2. androbench
Is the kernel the same? I'm curious if they changed it.