[Q] trouble installing 4.2.2 - Nexus 4 Q&A, Help & Troubleshooting

I currently have "stock rom" and "franco kernel r72"...
i searched everywhere before getting 4.2.2 update and followed the instruction:
1. Download stock kernel from here:
http://forum.xda-developers.com/show....php?t=2024982
2. Flash it in recovery.
3. Boot into android.
4. Go from root explorer to system/lib/hw and*
i) Delete power.msm8960.so
ii) Remove .fkbak extension from power.msm8960.so.fkbak so it looks like, power.msm8960.so
iii) Fix the permissions to rw-r--r--
5. Reboot to recovery
flash the update from recovery and install the best kernel out there again.
Click to expand...
Click to collapse
but even after following all these instructions I continue to get error on "power.msm8960.so" file.
so I checked the file and the "power.msm8960.so.fkbak" turned out to be damaged by recent trial of Minco ROM...
(power.msm8960.so.fkbak's modified date turned out to be the same day I installed the minco rom)
simply saying: franco kernel backed up not the original but one that was edited by minco rom (correct me if im wrong)
now that Im back to stock rom but with a wrong backup file of power.msm8960.so, I'm stuck and need the original file...
can anyone (with a stock kernel) send me a original backup of "power.msm8960.so" located in "system/lib/hw" ???
so that I can replace my wrong backup.... thank youuuu

Related

[HOWTO]Backup your ROM via Rom Manager on Galaxy S 2.2

Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Just installing CF-Root with Odin is the simplest solution for me which roots your device and installs ClockworkMod
http://forum.xda-developers.com/showthread.php?t=788108
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
alexhull24 said:
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
Click to expand...
Click to collapse
I have just updated my rom manager and the change is a new layout with icons and it looks much nicer
The guide is for those, who don't want to change the factory kernel in the rom. Flashing CF-Root/SpeedMod/Voodoo or whatever you sympathize with is the best solution I agree, as it comes with several benefits aside rooting, but not everyone wants to do it that way.
I would add, just to be sure, after backup copy the backup file to external SD card..
myrddral said:
Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Click to expand...
Click to collapse
hi, i did the same and got the update.zip in my phone but when i try to apply it during 3e recovery, i always get the <E:failed to verify whole-file signature xxxxx Installation abort>
can anyone help me with this issue?
many thanks in advance.
p/s: the phone is already rooted and rom manager installed with the latest CWM recovery 2.5.1.2
current firmware 2.2, kernel version 2.6.32.9, build number froyo.DXJPE
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
dereut said:
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
Click to expand...
Click to collapse
Same here!
On same ROM...
There is an excellent guide on this forum, and on another one that specify that galaxy s with froyo 2.2.1 and recovery3 needs to install CF-ROOT :
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000
and
http://forum.xda-developers.com/showthread.php?t=1035995
what this thread here is about is how NOT to need CF-ROOT
this is a bit like biting your own tail. I think the most important part for me is: if you flash another kernel, can you revert to your previous one as it is not possible to do a nandroid backup before flashing the kernel
for warranty sake, it would be important to be able to revert to a nandroid backed-up ROM, then revert to recovery3 than unroot the phone before bringing it back in case of need of repair
I found an app, sgs kernel flasher, it might be possible to backup the original kernel this way
so it would go like this :
root the phone (onclick root worked well with my phone)
install rom manager
install sgs kernel flasher
backup the kernel
flash CF-ROOT as describe in http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000 (the clearest guide I found so far)
flash CWR (or is it not necessary with CF-ROOT)
do a nandroid backup
save preciously the backup and the previously backed up kernel
play with the new toys .....
when warranty is needed:
restore the nandroid backed-up ROM
revert to original kernel with sgs kernel flasher
unroot with oneclick
can someone with experience revue this list and tells us if it sound correct ?
thanks
reup
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
dereut said:
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
Click to expand...
Click to collapse
You and me are in exactly the same situation. To do nandroid backup for warranty reason we have to brake that same warranty.
Only I didnt use cf-root, I went for hardcore speedmod...

[GUIDE] CWRecovery flashable working Root SperUser for stock ICS 4.0.3

1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664

[Q] Rom Problem

I wanna ask something.I have this phone and i have 2.2.1 stock rom U8800V100R001C00B136SP02CUSTC264D001.Here is my problem : i installed miui rom and now i don't know which files have to be in there.Here is the list.
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
cust_data folder
Is this correct? Or do i have to delete some of these ?
Does Stock rom installation delete any of these files ?
I have a problem with my phone, my screen freezes sometimes, unresponsive Because of this, i wanna send it to the technical service.
Sorry for my English
If I understand correctly, you've flashed original firmware, and that should get the whole device back to stock.
Try booting to recovery and see if it's the right one (e.g. not CWM etc.)
HFZenon said:
If I understand correctly, you've flashed original firmware, and that should get the whole device back to stock.
Try booting to recovery and see if it's the right one (e.g. not CWM etc.)
Click to expand...
Click to collapse
Yes.Trying to get back to stock I will send it to technical service.
Flashing the official 2.2.2 or any of those roms from huawei writes everything back to stock, even custom recovery images and all that.
I have 2 backup.
1) A folder named : cust_data\massmarket\tr\ (This one from the original phone)
2) A folder named : cust_data\hw\ideos_x5\ (I got these from after i installed stock rom)
There is something wrong.What can i do with this? Can they figure out this in technical service ? I don't want my phone get out of warranty

[Guide]ATT KitKat leak working with root

I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?
freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.
anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.

Flashing stock rom gives Treble Compatibility error

Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?
Download the zip file again from miui.com, if you’re using a custom rom go to ‘Wipe’ -> ‘Advanced Wipe’ and wipe the ‘Cache’, ‘Dalvik/ART Cache’, ‘Data’ and ‘System’ partitions.
Once you are done, go back and tap on the ‘Install’ button and browse the rom file.
If this doesn't work, try the fastboot method with the miui flash tool.
delete compatibility.zip in rom file and flash normally
Thanks for the replies. I already formatted and wiped, and tried redownloading the stock rom file, but got the same error. I also tried the MIUI flash tool but got an error after doing the last step.
However... I did end up fixing the problem moments ago.
As I was leaving work, a nerd directed to a wepage that had instructions that worked:
https://www.androidexplained.com/redmi-note-7-unbrick
16. May 2020: the tip: unzipping - deleting - zipping and flash that new file worked for me also. Redmi Note 7 Lavender; Rom Lineage 17.1 20200215. Very nice. Ernest from Germany
FligMupple said:
Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?
Click to expand...
Click to collapse
Why not orangefox?

Categories

Resources