Database Info

[Q] Flashing a new kernel onto an existing mod

Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?

try flashing the rom(gapps if needed) then the kernel, then reboot.

simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?

I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.

mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.

Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.

[Q] Nexus S 4g official ICS problems

So I know there are various other threads similar to this out there, but none of them have solved my problem so here it goes. Yesterday, I restored back to my Official 2.3.7 from CM9. I had heard the the official ICS had come out and wanted to do a proper update from stock rom. So I did this and the tried to update, but the update failed half way through. Since then, I haven't been able to connect to usb and I haven't had a cell signal. Does anyone know what the problem is and how to fix it?
Edit: So now I tried, stupidly, to just reformat everything. I'm sure you could see how that was a problem because now I'm stuck in bootloader or clockworkMod Recovery unable to install any operating system whatsoever...

go into clockworkmod
How to Update or Clean Install Roms and Kernels
Clean Installing Roms:
1) format /system /data /cache /boot
2) wipe dalvik cache
3) flash rom and gapps
4) Boot up for the first time and it should work
5) Optional: Only do this after you booted up once. Flash the kernel.
Updating Roms and Kernels:
Wipe Dalvik Cache and Cache before updating
That should solve it. make sure you wipe ALL of those.

pokefan213 said:
Edit: So now I tried, stupidly, to just reformat everything. I'm sure you could see how that was a problem because now I'm stuck in bootloader or clockworkMod Recovery unable to install any operating system whatsoever...
Click to expand...
Click to collapse
how CWM unable to install any ROM? any error message?
might not be relevant, which CWM version you're using?

signature verification failed during OTA update for JB

Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks

d960 said:
Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks
Click to expand...
Click to collapse
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.

You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.

jayjay3333 said:
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.
Click to expand...
Click to collapse
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?

albundy2010 said:
You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.
Click to expand...
Click to collapse
Thanks for education. Still pretty new on this...

d960 said:
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?
Click to expand...
Click to collapse
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:

jayjay3333 said:
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:
Click to expand...
Click to collapse
Thanks. I managed to update to JB following the guide you are refering to and also the steps you took (i.e., doing OTA update). In general it went smooth but I do encounter some issues that I want to ask the OP of that thread.

Flashing a JB ROM

Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.

What version of CWM are you running?
You should be fine, but it never hurts to check. You flash a JB rom just like any other. Wipe wipe wipe and flash.

The whole wipe wipe wipe is completely unnecessary. One wipe is sufficient and any additional won't do anything.
It's like saying that unless you wipe exactly 3 times the Android Gods are going to demand a human sacrifice for your phone to boot.

lol i think dvorak meant wipe cache, wipe dalvik cache, wipe data (wipe wipe wipe) but that's my take..
anyway, if you can flash MIUI ICS with whatever CWM version you currently have, you should be able to flash other JB ROM. Nandroid as always.. Goodluck!
Sent from my Nexus S using xda premium

jacob66 said:
Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.
Click to expand...
Click to collapse
This is what I did :
1. Boot into recovery and perform a nandroid backup of my MIUI installation.
2. Wipe.
3. Flash XenonHD 9 JB ROM + marmite 4.2 kernel.
My phone is running really smooth now. Good luck.

[email protected] said:
lol i think dvorak meant wipe cache, wipe dalvik cache, wipe data (wipe wipe wipe) but that's my take../QUOTE]
Yep, that's it. Of course wiping everything 3 times would be unnecessary.
Click to expand...
Click to collapse

jacob66 said:
Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.
Click to expand...
Click to collapse
if you get a cluster f*#@ of problems then clean install. It isn't that hard. Use Titanium Backup and good to go.
In Recovery:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with only bootloader, recovery and radio...dalvik-cache resides on /data, so it's gone already.
3. flash rom
4. gapps & custom-kernel (if needed). No need to let the phone boot & settle before flashing them (most custom-kernels have a script that automatically wipes /cache & dalvik during kernel-install)
5. reboot
6. Run TB -- restore missing apps with data --1st option under restore
just updating rom:
1. flash rom-zip
2. wipe /cache and dalvik-cache
3. reboot
Do this before reporting any issues on the thread since the problems are often related to this and not the ROM or kernel.

[Q] stuck in boot with CM rom and with back-up rom

Hello,
my tf700 doesn't finish the boot after I've installed CM.
Before flashing a new rom I've tried to make a system back-up from GooManager.
I don't know if the back-up is fully functional because in the "Breaking back-up in multiple archives" it has remained stuck at 100% (or complete progress bar) for like an hour.
After an hour or so I've interrupted the back-up process and entered the TWRP Recovery v2.5 (which I'm still able to access at the moment) and tried to flash a ROM downloaded by GooManager (cm-10.0.0-tf700t.zip). I've wiped the Dalvik cache and Cache in the process.
The flash seemed to be successful but the reboot doesn't finish, even though I've let it for two hours or so.
After that I've reentered the TWRP and tried a different rom cm-10.1-20130513-NIGHTLY-tf700t.zip, but with similar result, after installation it doesn't finish the boot.
I've reentered the TWRP and tried restoring the back-up. It did restored the system, passed the "configuring application" stage and gave the message "Finishing boot" and nothing afterwards, it just stuck in the process.
Right now I'm still able to enter TWRP, and navigate through the folders on the tablet, but I don't have a functional rom.
Can you please help me with some advices?
Thank you.

Which ROM did you have before, and which bootloader version?

_that said:
Which ROM did you have before, and which bootloader version?
Click to expand...
Click to collapse
Before that I had the stock ROM with the latest OTA firmware from Asus.
I don't know what was the initial version of the bootloader.
I've unlocked the device using Asus apk
I've pushed the TWRP on the tablet using the TF700T-ADB- Tool v3
I've granted super user rights from TWRP, I think using SuperUser application.
Ive installed from market GooManager and after that I've done what I've described in the previous message.
Thanks for your prompt answer.

Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?

_that said:
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
Click to expand...
Click to collapse
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?

Mihai_Preda said:
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Click to expand...
Click to collapse
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.

It seems strange that the back-up isn't fully working either, it gets stuck after "Finishing boot".
I've noticed somtheing while flashing the two CM ROMs. On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
But I don't know if it's alright not findind the MD5.

_that said:
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
Click to expand...
Click to collapse
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?

Mihai_Preda said:
On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
Click to expand...
Click to collapse
The missing MD5 file is not a problem. If it says "installation successful", you can assume that it is.
Mihai_Preda said:
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Click to expand...
Click to collapse
Your backups not working is somewhat strange, but that's another area where I have very limited experience.
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.

_that said:
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
Click to expand...
Click to collapse
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?

Ok, I did wipe the data, and even though it erased the user data too (media, docs, zip files etc) it restore the tablet to cyanogen mode not the original stock ROM. It finished the boot restore my gmail account. SuperUser is updated. And it seems the overall responsiveness is better.
Thank you for your time and advice!

Mihai_Preda said:
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Click to expand...
Click to collapse
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.

_that said:
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
Click to expand...
Click to collapse
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
If you have little more time and you know what happened here please let me know.
Thank you again!

Mihai_Preda said:
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
Click to expand...
Click to collapse
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.

_that said:
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
Click to expand...
Click to collapse
That means the TWRP didn't actually restore the ROM from back-up even if it did say the restore was successful...The last installed ROM was a CM one.
Thanks for the help!