Hi, i'm trying to cook a n9005 rom (deodex, root, busybox, init.d support, data/app support) using dsixda kitchen version 0.224 (updated with this package) but, after rom installation in CWM, at reboot, i get the message "could not do normal boot" in odin mode.
This is what i do:
1. setup working folder and follow instructions to extract system and cache img
2. deodex using api level 18
3. add root permissions (choosing "f" - chainfire-update)
4. install busybox
5. add /etc/init.d support
6. add /data/app support
7. delete some apks from system folder (like polaris office, chrome, etc)
8. build rom, option 99, using "1" interactive mode (zipaligning, creating update.zip and signing, all whitout errors)
9. install in cwm without errors
10. reboot
11. odin mode with message "could not do normal boot"
I think i miss something, maybe during root or init.d support processes, but i don't get any error message while cooking.
What can i do? Thanks.
Hi,
I have the same problem. Also i used kitchen version 224 but not updated with that package.
Seem to work everything ok, but when i want to flash it, it hooks up, sometimes with an cwn error, and sometimes with the same message you got.
After trying a lot with other custom roms the solution for me is that the update-binary is not correct. Copied over from other rom, edited updater script to my needs and everything is fine....
Still do not know where tje problem is.... always take clean samsung stock rom, doesn't matter if i use windows or ubuntu, result is the same
So i use the workaround and it works at least for me...
Sent from my SM-N9005 using xda premium
I'll try, thank you! Do you know how update binary is created?
Inviato dal mio SM-N9005 utilizzando Tapatalk
No sorry, i can't help you out with that, i am really a noob on Android-stuff.... i put that mod on my kitchen.... now update binary fits, but boot.img won't work... i get a cwm error 7
... i read all the messages about error 7, and.it would be easy to handle if those lines which you should delete were there )) nothing helped out, till i testet a boot.img from another custom rom....
Finally i got my "own" rom working.... ))
Best regards..
Sent from my SM-N9005 using xda premium
daywalker386 said:
No sorry, i can't help you out with that, i am really a noob on Android-stuff.... i put that mod on my kitchen.... now update binary fits, but boot.img won't work... i get a cwm error 7
... i read all the messages about error 7, and.it would be easy to handle if those lines which you should delete were there )) nothing helped out, till i testet a boot.img from another custom rom....
Finally i got my "own" rom working.... ))
Best regards..
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
Thank you! Finally i solved my problem using original samsung boot.img (in some way the kitchen modify/corrupt the boot.img)
jackyaway said:
Thank you! Finally i solved my problem using original samsung boot.img (in some way the kitchen modify/corrupt the boot.img)
Click to expand...
Click to collapse
i get an error 6 on cmw, can you or anyone help me find the syntax error? also, it only installs using cmw, any clue as to why twrp wont work?
Related
Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse
has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app
It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app
New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable
CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440
6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7
Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD
No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
reflash rom and flash otas in order 1,2,3,4 , THEN update su binary and AFTER THAT install kernel
Sent from my GT-S5360 using xda premium
Maybe your update.zip is corrupted hmm. Try download another update.zip and install it via cwm. Here
http://forum.xda-developers.com/showpost.php?p=26609075&postcount=3
Don't forget to mount system
Sent from my GT-S5360 using xda premium
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
flash stock rom....root again...then update su binary...then flash jbv3 by removing boot.img to not install kuro kernel and to stay with merruk....flash ota 1,2,3,4 one by one.....done....enjoy!!!!! :laugh:
Tried exactly the same!!
denysw0w said:
reflash rom and flash otas in order 1,2,3,4 , THEN update su binary and AFTER THAT install kernel
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
(First of all i thank(ed) all of u for your advises to help me out of this)
I did exactly the same!!
>flash stock>delete ext partition on sd>root>update subinary>flash JB without boot.img>flash all OTAs in order>update suBinary(though its already updated)>kernel MT2.0 pre-final !! :highfive:
But finally i got the same result.
actually i tried it multiple times in different ways..but in vain!
What i hope is that some1 make a cwm flashable zip of that su provided ... which perhaps might help!
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
i will make you tomorrow a flashable zip with the su file provided in the first post to flash via cwm
Sent from my GT-S5360 using xda premium
'disable superuser' means??
anmolsharma1293 said:
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Sir Anmol,
i cannot understand what exactly u mean by 'disable superuser' !!
and about removing superuser.apk : may i do that with root explorer or L2SD is explicitly required?
but i'm afraid i may not want to go with those 'removing' kind of steps because i already did the whole process of flashing frm start to end many times and now tired and want to settle with some less riskier ways!! :angel:
Anyway, thanks for your reply and support :highfive: :good:
try this bro maybe it will help.flash it with cwm,mount everything.
http://db.tt/3slPTkNX
MaestroCharan said:
Sir Anmol,
i cannot understand what exactly u mean by 'disable superuser' !!
and about removing superuser.apk : may i do that with root explorer or L2SD is explicitly required?
but i'm afraid i may not want to go with those 'removing' kind of steps because i already did the whole process of flashing frm start to end many times and now tired and want to settle with some less riskier ways!! :angel:
Anyway, thanks for your reply and support :highfive: :good:
Click to expand...
Click to collapse
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
thanks brother..i'll try them!!
anmolsharma1293 said:
Do this thing.....
Go to superuser>>>it will show update binary failed.....than go to settings>>>than disable superuser>>than again enable it.....now u hv root access..
Now go to link2sd & remove superuser.apk
Than install superuser from playstore....dont install supersu
Now their will b no problem...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
blackpanther2209 said:
try this bro maybe it will help.flash it with cwm,mount everything.
http://db.tt/3slPTkNX
Click to expand...
Click to collapse
Thanks bro :good:
anmolsharma1293 said:
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Ok bro i'll try that :highfive:
MaestroCharan said:
Thanks bro :good:
Ok bro i'll try that :highfive:
Click to expand...
Click to collapse
u may also flash other stable kernels like hells,savies etc to solve ur problem if still not solved
As you said...
anmolsharma1293 said:
First of all dont call me sir....
Its the working method which i use when i get superuser conflicts....
If u have no problem with root access than go to link2sd & just remove superuser.apk.....
And just download superuser from market.....
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
samir basnet said:
u may also flash other stable kernels like hells,savies etc to solve ur problem if still not solved
Click to expand...
Click to collapse
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
MaestroCharan said:
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
Click to expand...
Click to collapse
I dont know what has happened...
i never faced such problems....
now its better to flash stock and than any other rom.....
Sent from my GT-S5360 using xda app-developers app
problem solved (i think)
MaestroCharan said:
Did as u said : remove superuser apk and reinstall from market.
But still the same..
Finally, to me it looks like a problem associated with the kernel.
Yo bro..looks like its time for me to look for some other kernelsThanks for the suggestion anyway!!
Click to expand...
Click to collapse
i just had the very same problem like yours. then i installed superSU chainfire from app store, and it work fine.
hope it help you too
Can you help me?
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
Hi! i also have the same problem with you
it occur after i install merruk kernel 2.5
you said that you've just rooted again after following the steps that denysw0w said, does it mean that i have to flash JBV3 and ota 1,2,3,4 again, ill be back to 0 in upgrading my phone? help me pls...
Louie Jay said:
Hi! i also have the same problem with you
it occur after i install merruk kernel 2.5
you said that you've just rooted again after following the steps that denysw0w said, does it mean that i have to flash JBV3 and ota 1,2,3,4 again, ill be back to 0 in upgrading my phone? help me pls...
Click to expand...
Click to collapse
No come back to 0 broo...
Im use this methode everything work fine and good for me...
1. Flash stock rom (if you in custom rom)
2.install merruk kernel (for this case Im install the stable version 2.0 original dev.)
3. After finish, Im install superuser from chainfire in the market.
4. And Install custom rom and you can update the OTA
I hope this help you..
Sent from my GT-S5360 using Tapatalk 2
I have the problem with mising su binary after uninstall SuperSU, but fix it easily with this - http://forum.xda-developers.com/showthread.php?t=1538053&nocache=1
MaestroCharan said:
Situation : I'm on JellyBlast3.0.4 with Merruk 2.0 pre-final kernel.
After flashing kernel on JB3.0.4 .. i wanted to update su binary but could not.
Though the su is working fine (prompting and proving root access) but i'm unable to update its binary (ss attached below).
What i tried : Tried to re-flash 'update.zip' (though its already rooted) but cwm showed .....blah....blah.... E:Error in /sdcard/update.zip (Status 7) Installation aborted.
Then tried to replace the old su binary from its location with the updated one(attached below)..but failed..since as soon as the old file was removed, root privilages were lost and i was popped with an error saying 'your device is not rooted'.
So, i decided to reflash the whole rom and kernel once again but in the end its the same result : cannot update su binary!!
And hence i'm Here
Please, help me out since i'm still new and would like to do it on my own but.. don't know much.
Click to expand...
Click to collapse
Try flashing other kernel! No offense to the maker of meruk but that kernel is way outdated! Try Percy or Savie!
IGI83 said:
I have the problem with mising su binary after uninstall SuperSU, but fix it easily with this - http://forum.xda-developers.com/showthread.php?t=1538053&nocache=1
Click to expand...
Click to collapse
And by the above link, I think he means, download Super SU from the Play store...install. Once you open that app, it will tell you that you need to update your binary. Click "Normal" and it should work.
I had a major root issue here but I didn't want to wipe my work phone and deal with 5 hours of setup haha. This is what finally worked for me.
(PS, the reason I needed root was for Good For Enterprise - Exposed Module) http://forum.xda-developers.com/showthread.php?t=2040163&page=76
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
hi guys, i want to updata to cm11,so i install the twrp 2.6.3.2, and wiped dalvik,system, data and cache without backup. but after that when i try to install the CM11, it told me
set_metadata_recursive: some changes failed
E: error excuting updater binary in zip <my cm11 rom>
error flashing zip
and failed at last.
cuz there is no os on my phone, i don't know how to deal with it.
i looked it up and found that might be a TWRP issue, but i don't know which version should i use and how can i install it? cuz everytime i try to use adb push, it told me error: closed.
i m really anxious now,need your help.
forgive my bad english, and please give me some advice asap!!!!!!thanks!!!!!!!!!!!!!!!!!!
crixus3811227 said:
hi guys, i want to updata to cm11,so i install the twrp 2.6.3.2, and wiped dalvik,system, data and cache without backup. but after that when i try to install the CM11, it told me
set_metadata_recursive: some changes failed
E: error excuting updater binary in zip <my cm11 rom>
error flashing zip
and failed at last.
cuz there is no os on my phone, i don't know how to deal with it.
i looked it up and found that might be a TWRP issue, but i don't know which version should i use and how can i install it? cuz everytime i try to use adb push, it told me error: closed.
i m really anxious now,need your help.
forgive my bad english, and please give me some advice asap!!!!!!thanks!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
your going to have to flash CWM, also what rom are you on? it sounds like your aboot image is not right
4.4 Roms can not be flashed using 2.6.3.2 you need to find a version of 2.6.3.3 or 2.6.3.4 for your device.
Sent from my LG-vs980 using xda app-developers app
Hi.. First step is to follow step by step th is guide i link to http://forum.xda-developers.com/showthread.php?p=46204640
If u succes to install stock Rom.. Then u re root and install unofficial cwm, Can be found in ur devices forum.
Then download/transfer The cm rom u wanted, and GAapps IF needed... Just remember to read install instructions and follow them. And do a backup before installing cm rom
Sent from my LG-D802 using XDA Premium 4 mobile app
2.6.3.3 and .4 typically come in a flashable zip. You flash it in twrp like you would a ROM and it updates it.
If you do not have a ROM downloaded you can use to get back to a ROM to download side zip file, then you should check the thread on here (that you should have originally used to get your recovery image to flash on your phone.)
And follow the directions on there how to push it using adb. Once that's done you should be able to flash normally.
Sent from my LG-vs980 using xda app-developers app
Update? Please reply if it worked for you.. And i would recommend u to use CWM, because alot of people, experience problems using twrp including myself..
Sent from my LG-D802 using XDA Premium 4 mobile app
Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!
izanaghi said:
Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!
Click to expand...
Click to collapse
Do you have access to custom recovery ?
bender_007 said:
Do you have access to custom recovery ?
Click to expand...
Click to collapse
the phone is rooted but I haven't installed any custom recovery.
I thought i could be possible to grab someone's backup system archive and use the xdabbed apk to restore default applications.
Actually I should describe a bit more the problem, the camera is there, the player is there but the gallery has disappeared.
There is an LGgallery.apk that comes with xdabbed package but i can't install it. When I try a manual install (just launch the apk), it is just telling me that the app couldn't be installed.
hope we can do something from it, otherwise I'll install a custom recovery and follow any advises you might have,
Thanks,
The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex
bender_007 said:
The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex
Click to expand...
Click to collapse
Ok so i replaced the old LGgallery, remove the odex, changed permission and reboot but no luck with that.
installing a custom recovery sounds quite complex and I am ready to take a risk and try your archive. (hope it'll do the trick)
Otherwise I'll resort to install a recovery,
Many thanks
Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
:
If you want to risk:
modified xdabbeb's installer(install the stock files)
If you want the recovery way(installing recovery is one click job) tell me
bender_007 said:
Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
If you want to risk:
modified xdabbeb's installer(install the stock files)[/URL]
If you want the recovery way(installing recovery is one click job) tell me
Click to expand...
Click to collapse
I am usually stubborn but I listen the advise this time, could you advise me on the best way to do it or direct me to an appropriate thread?
Since you are already rooted.
first: download this
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. AutoRec d802 You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.
bender_007 said:
Since you are already rooted.
first: download
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.
Click to expand...
Click to collapse
Many thx to Bruce and yourself but I did as described installed TWRP (worked), install the zip (worked), reboot (updated 1 app) but still no sign of the damned Gallery????
What am I missing?
let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash this (gallery)
bender_007 said:
let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash (gallery)
Click to expand...
Click to collapse
Downloaded it, flashed it, loved it!
Thank you very much for your (and Bruce? ) time, patience and expertise .
First post great support
Again many many thanks :highfive:
No problem