Stock Rooted OTA 4.08.605.19 710RD Rom
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom.
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.
DOWNLOAD ODEXED - MD5 - Mirror
DOWNLOAD DEODEXED - MD5 - Mirror
_
2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2
Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.
IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.
cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?
IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).
Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/
leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.
Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!
Related
So yesterday I finally found some time to root Gingerbread on my Nexus One. We're moving to Germany from the U.S. in a month and the last couple of weeks I just didn't have any time to get it done. I had my N1 rooted when I was on Froyo and was desperate to root it again on GB.
Last night I set a couple of hours aside to familiarize myself with the GingerBreak exploit and ended up with a rooted N1 and Gingerbread 2.3.3
Here's the funny part... not 30 minutes after rooting I get an OTA notification to update to 2.3.4. Go figure!
Can anyone confirm that 2.3.4 will break root on the N1? If so, will the GingerBreak exploit still work to root GB again?
What would be the preferred/easiest method to upgrade to 2.3.4 and retain root?
2.3.4 will break root. just use the gingerbreak app again and youll be rooted
I figured it would break root but just needed some confirmation!
I didn't actually use the .apk but ran the exploit myself. I think this time around I may just use the .apk though.
Is it confirmed that the app will root 2.3.4?
Just boot into recovery, flash the update as file from SD, and then flash the su zip...
danger-rat said:
Just boot into recovery, flash the update as file from SD, and then flash the su zip...
Click to expand...
Click to collapse
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.
The new OTA break the root
This morning i have rooted my nexus one and root died.
I am trying Gingerbreak 1.2 after 25 minutes i cancelled it.
GldRush98 said:
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.
Click to expand...
Click to collapse
Wouldn't this method require my boot loader to be unlocked?
Not if you already have a custom recovery installed...
danger-rat said:
Not if you already have a custom recovery installed...
Click to expand...
Click to collapse
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?
Don't apply it as an update, because your phone will reboot once it's done. If you reboot, you will lose your custom recovery. Use the "install zip from SD" option...
I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.
Nikos_s3 said:
I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.
Click to expand...
Click to collapse
I'm getting the same error. I thought maybe it was because I had deleted Google Books from my system apps but after restoring the BooksPhone.apk I still get it. Not sure what the problem is.
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
That worked! Thanks for the help! Learned something new again.
danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
this is only for those who havent flashed the un-edited update i guess. I flashed the original update too soon and it removed the root access on my wifes N1. I tried flashing the su last night it didnt work, really frustrating... ahihihihi
I was thinking if I flash the backup on 2.3.3 will that bring back the root access? or at least I can already use Gingerbreak then? ty
XodoX said:
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?
Click to expand...
Click to collapse
Try this...
http://forum.xda-developers.com/show...1&postcount=19
Click to expand...
Click to collapse
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!
Pepits said:
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!
Click to expand...
Click to collapse
To do what? To root? This procedure is to, in this case, update to 2.3.4 from 2.3.3 without loosing root.
Now I have an additional question. I wasn't able to use the original update file from Google, presumably because I had deleted the Google Books app. I kept getting the above-mentioned error.
Just out of curiosity, how could I get Google Books back so the update would run? Just placing it in /system/app didn't seem to work.
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.
XodoX said:
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.
Click to expand...
Click to collapse
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...
Nikos_s3 said:
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...
Click to expand...
Click to collapse
how can you go back to 2.3.3? i wanna do the same thing for my wife. ty
Hi, after test for some times, i made the flashable root package for 2.3.4 (That the device has flash the leaked HKTW 2.3.4 and unlocked the device)
NOTE:
Unlocked Atrix 4G with HKTW 2.3.4
Please flash the CWM recovery first: http://forum.xda-developers.com/showthread.php?t=1138541
You should have a external sd card in your device, because the recovery cann't recognize the internal card
DOWNLOAD:
PLEASE download from the attachment, I'm really sorry that my site was down.
I think all of you know how to flash zip from recovery, so I'll not give hint about this, LOL
MD5SUM:
986c5fe6bf0e8eeef5dd5235b2c57cb5
Original Post @: http://ligux.com/t-60-1-1.html
More infomation, please goto: http://LiGux.com
shafa,,
you rocks,, chinese rocks
Cool I needed this. Thanks
Sent from my MB860 using XDA App
vista1984 said:
shafa,,
you rocks,, chinese rocks
Click to expand...
Click to collapse
LOL, you know the Chinese Pinyin: shafa? Cool
Anyone know how to get back to stock, or another rom like greyblur. I am stuck on a softbrick.
kleeman7 said:
Anyone know how to get back to stock, or another rom like greyblur. I am stuck on a softbrick.
Click to expand...
Click to collapse
You can flash the official sbf file to restore to origin, like the 1.2.6 sbf
kleeman7 said:
Anyone know how to get back to stock, or another rom like greyblur. I am stuck on a softbrick.
Click to expand...
Click to collapse
Did sbf rsd lite work for you?
Sent from my MB860 using XDA Premium App
flzyup said:
You can flash the official sbf file to restore to origin, like the 1.2.6 sbf
Click to expand...
Click to collapse
I was using a update sbf, not a full rom one. Up and running again. Thanks.
flzyup said:
lol, you know the chinese pinyin: Shafa? Cool
Click to expand...
Click to collapse
哈哈 沙发我更懂了 跨国来支持
Works great! Thanks!
kleeman7 said:
I was using a update sbf, not a full rom one. Up and running again. Thanks.
Click to expand...
Click to collapse
Yeah I think alot of people make that mistake. That's why when people ask I always say make sure to grab the "full" sbf not the service!
Thanks for the zip root method! Much appreciated!
Uses this and trying to flash with the newest CW build that is available with no avail.
Keeps being unable to mount SDcard ...
Will have to try the other way to do this for now but thank you for the work.
Worked perfect. Thanks
Sent from my MB860 using XDA App
how do i use this?? already have teh new cwm
now waht???
i HATE when pple leave out basic info, i got school work, i cant remember EVERYTHING EVERYTIME.
Hey, so, I ran into a slight problem.. It doesnt actually root the phone... Or so I've found. What happened to me is it worked perfectly, flashed via new cwm nicely, and I had SU in app drawer. I then decided to try and restore my apps via TB, and it doesnt let me batch anything, see anything, etc. It's like I don't have root. Then I tried getting root explorer and it FC's on opening the app. WTF?
jbrussee said:
Hey, so, I ran into a slight problem.. It doesnt actually root the phone... Or so I've found. What happened to me is it worked perfectly, flashed via new cwm nicely, and I had SU in app drawer. I then decided to try and restore my apps via TB, and it doesnt let me batch anything, see anything, etc. It's like I don't have root. Then I tried getting root explorer and it FC's on opening the app. WTF?
Click to expand...
Click to collapse
try rebooting the device ( i had to do it a couple of times )
slowpc said:
Uses this and trying to flash with the newest CW build that is available with no avail.
Keeps being unable to mount SDcard ...
Will have to try the other way to do this for now but thank you for the work.
Click to expand...
Click to collapse
This is because you didn't read my post carefully. You should have a EXTERNAL SDCARD in your device first! Because the recovery cann't mount the internal sdcard.
jbrussee said:
Hey, so, I ran into a slight problem.. It doesnt actually root the phone... Or so I've found. What happened to me is it worked perfectly, flashed via new cwm nicely, and I had SU in app drawer. I then decided to try and restore my apps via TB, and it doesnt let me batch anything, see anything, etc. It's like I don't have root. Then I tried getting root explorer and it FC's on opening the app. WTF?
Click to expand...
Click to collapse
There is another way to check whether the root of your device work or not.
Run cmd in Windows or terminal in Linux.
execute the following cmd:
Code:
adb shell
su -
After you input the "su -" cmd, you should have a dialog to allow root access in your device. I.e, the root works. Otherwise, it doesn't work.
BTW, does your device unlocked and flash the HKTW android 2.3.4 rom?
jahizen said:
how do i use this?? already have teh new cwm
now waht???
i HATE when pple leave out basic info, i got school work, i cant remember EVERYTHING EVERYTIME.
Click to expand...
Click to collapse
TOO bad, the zip file should be flashed as the normal way to flash rom.
GOTO recovery then choose this zip file to flash.
BTW, you should copy the zip file to the external sdcard first!
michael0619 said:
哈哈 沙发我更懂了 跨国来支持
Click to expand...
Click to collapse
=============
Fun!
i did't backup root using rootkeeper and just flashing 219 using rsd. then i found that the superuser is still there but the root(su) no longer working.... i have tried everything, wiping, unroot, root(droid4utility0.4)...nothing work, even the safetrap doesn't work... i really really need you help to get my root back. millions of thanks~~~~
sbf back to the old version 215, factory reset, install root, install voodoo rootkeper and use it, then apply the update zip, reboot and go into voodoo and restore root.
myfishbear said:
sbf back to the old version 215, factory reset, install root, install voodoo rootkeper and use it, then apply the update zip, reboot and go into voodoo and restore root.
Click to expand...
Click to collapse
thanks so much buddy! and do you have the sbf 215 version link? i really don't konw where to find it...
matthewzx said:
thanks so much buddy! and do you have the sbf 215 version link? i really don't konw where to find it...
Click to expand...
Click to collapse
Look in the EternityProject Droid 4 ROMs thread in the dev section.
Sent from my DROID4 using XDA
myfishbear said:
sbf back to the old version 215, factory reset, install root, install voodoo rootkeper and use it, then apply the update zip, reboot and go into voodoo and restore root.
Click to expand...
Click to collapse
still doesn't work... might be somebody can up;oad the voodoo ota rootkeeper's root backup files and let me hve a try.... thanks so much to all of your guys~~
Here is the thread with the fastboot files in case anyone else can't find it: http://forum.xda-developers.com/showthread.php?t=1622256
I'm surprised that Superuser was still on your phone after flashing the fastboot file. Did you wipe data and cache?
SGMD1 said:
Here is the thread with the fastboot files in case anyone else can't find it: http://forum.xda-developers.com/showthread.php?t=1622256
I'm surprised that Superuser was still on your phone after flashing the fastboot file. Did you wipe data and cache?
Click to expand...
Click to collapse
yep, many times wiping... when using the droid utility 0.4 it says "fail...read only file system..."
Try using motofail. If it doesn't work the first time run it one more time.
Grizzy3 said:
Try using motofail. If it doesn't work the first time run it one more time.
Click to expand...
Click to collapse
ok...i will try tonight...3xs~
Grizzy3 said:
Try using motofail. If it doesn't work the first time run it one more time.
Click to expand...
Click to collapse
still not working... when i choose the storage mode the superuser installed successful but no root(voodoo ota keeper tells)...
i think the last option is trying someone's voodoo ota root keeper's root backupfile...
would you please upload yours? thank you so much buddy!
Hello all,
I have an I9000B model. Volume keys do not work.
So far I've managed to install everything through ROM Manager. But now, while trying to update from some CM10 nightly to the stable version, the installation is aborted with the message:
============================================
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
============================================
I understand that if I just rolled the menu down to perform installation again it would work, but I'm unable to do that! My question is: can I modify updater.sh to install again without requiring me to explicitly selecting the menu?
Is there any alternative option?
regards,
Never mind! I just opened updater.sh and modified it to not check for the file.
regards,
wsteel said:
Never mind! I just opened updater.sh and modified it to not check for the file.
regards,
Click to expand...
Click to collapse
Nice! But what the hell does it mean? Where the file is? How to update that?
The updater.sh -Skript you can find in the zip-file for example when you opening it with winrar, 7zip or something else ...
Look in the zipfile of your CM nightly ..
I think wsteel edit the file and removed the request for the partition layout or he set it "true" in the skript so he would not ask while flashing ...
mess18 said:
Nice! But what the hell does it mean? Where the file is? How to update that?
Click to expand...
Click to collapse
mess18 said:
Nice! But what the hell does it mean? Where the file is? How to update that?
Click to expand...
Click to collapse
You don't need to worry about that file.When the warning comes, just check "install zip" again and it will be flashed. It is just a warning. Anybody who reads opening post can find that info there.
tetakpatak said:
You don't need to worry about that file.When the warning comes, just check "install zip" again and it will be flashed. It is just a warning. Anybody who reads opening post can find that info there.
Click to expand...
Click to collapse
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Thanks for the info ...so now you can flash your ROM which you wanted ...
mess18 said:
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Click to expand...
Click to collapse
mess18 said:
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Click to expand...
Click to collapse
Once you take off for upgrading to CM10.2 the partition warning will appear again, as CM10.2 uses now different system partition size than the CM10.1x does. Don't care about that, just choose again "install zip".
Just don't forget to backup all your data (contacts, sms, app data etc). Once upgraded, you should be able to restore /data from your nandroid backup done by CM10.1x (under "advanced restore") Titanium backup can restore app data.
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
mystborn said:
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
Click to expand...
Click to collapse
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
mystborn said:
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
Click to expand...
Click to collapse
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
nkk71 said:
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
Click to expand...
Click to collapse
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
mystborn said:
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
Click to expand...
Click to collapse
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
nkk71 said:
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
Click to expand...
Click to collapse
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
mystborn said:
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
Click to expand...
Click to collapse
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
nkk71 said:
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
Click to expand...
Click to collapse
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
mystborn said:
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
Click to expand...
Click to collapse
That did the job, now I am running 4.3
mystborn said:
That did the job, now I am running 4.3
Click to expand...
Click to collapse
Congrats mate, I thought I saw an earlier post with something like "OTA Check Tool"? What's that?
Anyway, glad it worked out :good::good:
You may want to change the main thread title to include [SOLVED] for other to know
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
mystborn said:
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks, I'll check that tool out when I get a chance, but like you said, it doesn't seem very accurate (at least yet).
And yes, I do believe you had an interesting approach at flashing an OTA