Develop Bugs

Any custom Rom and unable to flash a different kernel. Help please...

I am currently running Leedroid and I sometimes switch to Paranoid Android just to see how things are developing there. Great rom but I cant do without sense camera and like the decent weather app with all its animations.
Back to reason, sorry, I cant change my kernel on neither rom. Just gets stuck on boot animation/loop. Knew problem because I used to be able to change kernels but now just cant. Any idea's to why. Much appreciated - I feel handicapped...

Well, did you repack the kernels AND flash modules?

tomascus said:
Well, did you repack the kernels AND flash modules?
Click to expand...
Click to collapse
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.

veroby said:
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
Click to expand...
Click to collapse
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?

tomascus said:
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
Click to expand...
Click to collapse
Correct. I have tried erasing cache via command line and I have tried erasing cache via cwm as well. Still no joy
Actually because of desperation I have tried everything in different orders as well. Example- flashing boot image before after flashing kernel. Still doesnt boot and eventually after long wait just loops. This problem is with both roms.

Stock kernel works right?

tomascus said:
Stock kernel works right?
Click to expand...
Click to collapse
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....

veroby said:
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
Click to expand...
Click to collapse
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?

KaiseRRUby said:
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
Click to expand...
Click to collapse
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:

veroby said:
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
Click to expand...
Click to collapse
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?

doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.

ARHD 11.1 jellybean smooth and sense camera full package

tomascus said:
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid ( i know you said try another rom but hadnt thought it to be necessary because I was having same problem with Leedroid and Paranoid Android jellybean), kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...:crying:
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.

KaiseRRUby said:
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.

veroby said:
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
Click to expand...
Click to collapse
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?

KaiseRRUby said:
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
Click to expand...
Click to collapse
Yeah understand, I used to be able to just fastboot flash kernel boot image, flash kernel modules via cwm and bobs ya uncle. Done. But no more. Guess I'll have to wait until i jump ship and update firmware to 1.28 for JB roms and re-format or something. Cheers anyways..

[Q] Flashing a rom...

Extract Rom and grab the boot.img
Make a Full Wipe (Factory Reset,System,Cache,and Davlik Cache)
Install ROM
Fastboot flash boot boot.img
REBOOT
Enjoy!!!
With these instructions *i've never flashed a rom before* I should download the rom, extract the boot.img where I have the fastboot.exe on my computer, do full wipe, put the zip file on my sd card and install in recovery, reboot and go into fastboot mode and flash the image, and then reboot again right? Or am I missing something? Sorry, as I said i've never done this before.

Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first

Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp

donhashem.dh said:
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Click to expand...
Click to collapse
atonz said:
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
Click to expand...
Click to collapse
Thanks for your help. I actually went ahead and tried mine first, to see because i'm impatient and it worked totally. Thanks everyone!!!

Ok, I'm having issues with this installing ROMs/kernels.
I entered fastboot
I flashed the boot.img for the kernel I want
I toggled to hboot
I went into recovery (twrp 2.2.0)
I did wipe -> Factory Reset, Cache, Dalvik Cache, System
I installed the zip for ROM I want to use [found here]
I flashed the zip for the kernel I want to use (to install the libs) [found here]
wiped dalvik/cache again
reboot system
Now my phone just bootloops. Not sure what I did wrong.
I should mention I did get it to boot once back when I first installed the ROM because I did a normal reboot not a reboot into fastboot (was doing the install the ROM then the boot.img approach at the time) and hadn't installed any boot.img (still had the stock) but ever since I overwrote it all i get is bootloops.
Also, I even tried the same steps using the boot.img included with the ROM as opposed to the other one.
To make things worse, backups are almost useless because with the phone being S-ON even if the boot.img is being backed up, it not getting restored. A point made extremely obvious by the fact that it still bootloops after restoring my backup.
I am currently running the RUU but am hesitant to try and install any ROMs without some idea of what I did wrong.
Any help is appreciated.
-----EDIT------
Ok, I think the problem was the recovery I used. I installed the CDMA TWRP from the OneV tool, and one linked in the cdma development thread and a couple CWM version found there as well. But what seemed to work was getting TWRP straight from the source. After running the RUU I installed version 2.3.1.0 and repeated the steps using the boot.img included in the ROM and it worked. If I'm feeling adventurous later I'll try my luck with the other kernel lol.

I need help please

Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.

mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse
So you didn't even flash the boot.img for the backup? It's located in /sdcard/clockworkmod/backups

mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse
I originally tried to flash ARHD but the file was corrupt and aborted. I managed to flash the boot.img and superwipe before hand. I'm wondering if this is why my phone wont boot up when i try to restore backup. Dont know what to do now.

tomascus said:
So you didn't even flash the boot.img for the backup? It's located in /sdcard/clockworkmod/backups
Click to expand...
Click to collapse
No...does that mean im screwed?

Try to flash different rom
If i helped you in any way then do click thanks
Sent by XDA Premium

coolprateek.kumar said:
Try to flash different rom
If i helped you in any way then do click thanks
Sent by XDA Premium
Click to expand...
Click to collapse
How do i get another ROM on my phone if my phone wont boot up? I'm stuck. Keeps bootlooping. I cannot find any boot.img for my nandroid backup either.

Hold power + volm down for 10-15 seconds until you get to bootloader screen man... if it doesn't work then you're doing it wrong.

tomascus said:
Hold power + volm down for 10-15 seconds until you get to bootloader screen man... if it doesn't work then you're doing it wrong.
Click to expand...
Click to collapse
I know how to get into the bootloader. I dont have any other ROM on my phone to flash. I have my back up which i tried to restore but i'm stuck in a bootloop. I dont have the boot.img in my phone for the nandroid.

Just a taught....
I don't know if you changed or upgraded the rom after you did the nandroid backup but if you have a bootloop it means boot.img doesn't match the rom.zip
You also need to flash boot.img with the ADB tools that matches your nandroid backup.
If you are not sure anymore, wisest and easiest thing to do is flash a new custom rom.
I would recommend you >> ARHD rom as they have a Superwipe script as well to clear all fat but leave storage in tact.
Your storage you can reach with Clockworkmod/mounts and storage/Mount USB Storage to copy the rom.zip and superwipe.zip to it.
Keep in mind that you will lose all your personal data like contacts and sms etc, all in internal memory.
mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse

mgf8384 said:
I know how to get into the bootloader. I dont have any other ROM on my phone to flash. I have my back up which i tried to restore but i'm stuck in a bootloop. I dont have the boot.img in my phone for the nandroid.
Click to expand...
Click to collapse
The boot.img should be inside the backup folder

Download a different rom and copy it to sd card through different phone....then install that rom
If i helped you in any way then do click thanks
Sent by XDA Premium

Nothing to Worry!
Ohk..Calm Down..there is nothing to worry at all.
Till the time u can go to Clockwork recocert all is well.
Now.
1.Download the ROM u want to flash.(And the boot.img Provided with it)
2.Boot ur into recovery Mode.
3.There will be a option mounts and storage.
4.Select Mount SD card(Connect ur phone to the computer before this)
5.Ur HTC ONE X STOrage will come up.now copy the ROM and the boot img on d card ..
6.Reboot and install the rom and flash the boot img.
Simple

Laurentius26 said:
Just a taught....
I don't know if you changed or upgraded the rom after you did the nandroid backup but if you have a bootloop it means boot.img doesn't match the rom.zip
You also need to flash boot.img with the ADB tools that matches your nandroid backup.
If you are not sure anymore, wisest and easiest thing to do is flash a new custom rom.
I would recommend you >> ARHD rom as they have a Superwipe script as well to clear all fat but leave storage in tact.
Your storage you can reach with Clockworkmod/mounts and storage/Mount USB Storage to copy the rom.zip and superwipe.zip to it.
Keep in mind that you will lose all your personal data like contacts and sms etc, all in internal memory.
Click to expand...
Click to collapse
Worked perfectly...thanx!

aman360elite said:
Ohk..Calm Down..there is nothing to worry at all.
Till the time u can go to Clockwork recocert all is well.
Now.
1.Download the ROM u want to flash.(And the boot.img Provided with it)
2.Boot ur into recovery Mode.
3.There will be a option mounts and storage.
4.Select Mount SD card(Connect ur phone to the computer before this)
5.Ur HTC ONE X STOrage will come up.now copy the ROM and the boot img on d card ..
6.Reboot and install the rom and flash the boot img.
Simple
Click to expand...
Click to collapse
Worked perfect. Thank You.

[Q] Another noob with a bricked HOX

At the moment it's on a bootloop with the HTC screen, although I've managed (just now) to flash CM10 which is now stuck on a loop of the CM10 Android splash screen
I'm feeling confident that this can be sorted as I can access phone through fastboot/adb and can mount the SD so all isn't lost... I'm on UK O2 HOX
Just looking for a little direction, I used to be fairly confident around the inside of my old HTC desire, but lost interest... Things are rather different with the HOX and I suspect I've maybe screwed up with some misguided bravado...
Mr Hofs has provided some excellent learning material on his responses to issues similar to mine but to no avail...
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Just looking for pointers on where to go next!
Starting to become concerned I've made a proper mess...

mathesonewan said:
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Click to expand...
Click to collapse
Additional to this - I've been through 10-12 pages of various fixes (searched bootloop within HOX forum) that's why the above is a little vague... They've all merged into one...

1: what hboot do you have now ?
2: what recovery are you on ?
and put the phone in the recovery in the mean time. it charges the battery there

Are you flashing cm10 or cm10.1 'cause cm10 does not support hboot 1.36.

Recovery is TWRP v2.4.1
HBoot is 1.36
and I'd read that somewhere about not supporting 1.36 and I've just checked it's 10.1 I was trying to flash

Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.

Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot

TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
Mr Hofs said:
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)

mathesonewan said:
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
Click to expand...
Click to collapse
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
I've expanded on the above steps to ensure I'm completing them correctly
1. Extracted the boot.img from the firmware zip contained within the CM10.1 zip, then ran fastboot flash boot boot.img from cmd line - this completed and reported "OKAY"
2. Full wipe done using TWRP - system wipe - for good measure wiped everything else too (wasn't sure if system was a catch all for the others or not)
3. Rom Flashed using TWRP install cmd (I've assumed this is the correct way to do it...)
4. Flashed Gapps similarly
It's now past the HTC "quietly brilliant" splash (very very quiet just now...) and is stuck on the CyanogenMod splash just circling round and round...
Going to try the other method see if I have anymore luck!

OK... So haven't had any luck with either method...
When flashing the boot.img it's behaving differently to how it did before - it now triggers the phone to reboot whereas it never did before... Is that normal?
Is there any more information I can give you guys that might narrow down the issue?
Thanks in advance!

i would try a stanrd sense based rom ..... just to check its all fine, i have seen more people that didnt get it booted, why ? no clue....
did a proper wipe....factory reset,wipe caches, dalvik cache, data, system ?
then it should work !

Just downloading the stock rom just now, going to try from there... At this point in time I'll be happy to just have a working phone!

Success!
I tried going back to the stock rom but something mad happened with the recovery (i.e. it didn't work anymore) and was replaced with a graphic of a flat HOX with a sync symbol and then the sync symbol was replaced by a red cross...
So had a minor panic, realised that something wasn't right with TWRP, so flashed on CWM, then flashed the boot.img from the stock zip, and flashed the rom perfectly.
I'm tempting fate but I started this process wanting a new rom and I will finish it, but I'm glad my phone isn't bricked!
Thanks to you both for your input, your faith certainly encouraged me to not give in!
Keep up the awesome work!

Well you can always try again to install CM10.1.....again but now with cwm.

I went with viper - which has flashed successfully, but everytime I unlock the screen it comes up with a white HTC screen... haha time to start trawling the viper forum... or go for CM again!

Strange.....tho i have the idea you missed something in the wiping process ?

Funnily enough for a "low stress" option I wiped everything (CWM > advanced > wipe em all) then reflashed the boot.img from CM10.1, then flashed the rom and it's loading into CM10 but repeatedly flashes "unfortunately the process com.android.phone has stopped"
There is something funny going on if no custom roms are working no?

Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
That should do it.....

ohhhhh the mounts and storage one is new to me... I'll try that now with a custom...

Meh didn't work... I'm going to reflash the stock and go to bed I think!

[Q] Need some direction with Restoring

Hi All,
Yesterday I took my Tegra 3 (International) One X back to Stock ICS using RUU. Everything went smoothly after I relocked my bootloader and ran the RUU.
Then I proceeded to get all the OTA updates until I had JellyBean (3.14.707.24) with no further updates pending. Yay for Jellybean! The next thing I did was install CWM recovery and perform a nandroid backup (which didn't seem to restore later, although was created correctly).
At this point, I thought I would try using a CM10 rom to remove sense and I went ahead and installed it, flashing over the boot.img as one normally would, but it wouldn't boot. I later discovered that I needed a modded-boot.img (for new hboot 1.36), but not before I tried running the 3.14.707.24 RUU.
This RUU got stuck at sending.... and did not finish. I didn't leave it more than 20 minutes and tried twice. I also tried my ICS RUU to no avail.
Right now I have no Rom installed (from what I can tell), but I have full fastboot access and would like to know how I should proceed:
1) should I install the CM10 rom again with proper modded-boot.img (for hboot 1.36) and see if it boots? That would at least get me functional.
2) should I try another copy of the RUU for 3.14.707.24 JB? (i found one)
3) should I try a rom like Android Revolution HD which is OK to work with my new HBoot 1.36?
I don't want to do too much too fast since I know what I've done, and used to be really into this. The phone has been sitting a while since I upgraded my device and I'd like to get it working for travelling purposes. I'd be happy with a Stock Rom at this point...
Thanks for any willingness to help me
Adam

Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor

As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app

Thanks for answering
big noob said:
Ofcourse if you want CM flash the boot.img that is made for CM..And then flash .zip file..And ofcourse after flashing use
"fastboot erase cache"
Sometimes if you dont clear cache your phone won't boot..
Sent from my Endeavor
Click to expand...
Click to collapse
Thank you very much for your response!

This brings me to a next question...
Marc199 said:
As you already said the old boot.img wont work with the new hboot. Just install cm10.1 as usually. Or any other JB Rom that is out there for the One X.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your answer!! Now I'm curious if I want to use some other ROM, but without any system, how do I get the .zip file for the rom onto my SD card for flashing.
Should I use CWM recovery and enable usb storage, or is there another way?
Thanks again,
Adam

Correct, use the recovery

Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app

Thanks!
Marc199 said:
Yes just mount usb storage in CWM.
Sent from my ProBam by codexc @xda using xda app-developers app
Click to expand...
Click to collapse
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:

THANKS!
Mr Hofs said:
Correct, use the recovery
Click to expand...
Click to collapse
Thanks so much. I'll see what happens and get back to the thread.

ALL GOOD!!
Thanks Everyone again. I'm Up and Running!
I think I was more freaked out by the RUU not working than just thinking that my phone is fine. Turned out CWM Recovery was still onboard so I just flashed a new rom using USB mounted storage. :good::good::good::cyclops:

adampollack said:
I'll try this later when I have the time. Thanks to everyone who responded. I was nervous I was on the bad road. Seems I'm in healthy shape, just lacking a rom.
Two more questions:
1) Can I still revert to stock? If so, how since RUU seems to get stuck at sending and not actually restore?
2) Any idea why when I tried to restore my stock nandroid backup just after installing CWM (which backed up successfully) it would restore but not boot (hung on One splash screen)? Should I have to wait a seriously long time for it to boot (I never used to have to?)
Thanks in advance!
Adam :angel:
Click to expand...
Click to collapse
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor

Hmmm....
big noob said:
1. You just need to find a RUU that will work..
2. Did you flash boot.img from sdcard/CWM/backup/ backup name folder?
Sent from my Endeavor
Click to expand...
Click to collapse
Hey, Thanks for responding!
1. I figured. Thanks for validating. :good:
2. I did not use the boot.img from the nandroid backup. I've never sent a separate boot.img when restoring from Nandroid. Is that something I need to do going forward/have been lucky not having to do until now? Perhaps the ICS builds of roms had a more similar boot.img?
Adam

Yes sir, always flash the corresponding boot.img file :thumbup:

Appreciate the help
Mr Hofs said:
Yes sir, always flash the corresponding boot.img file :thumbup:
Click to expand...
Click to collapse
:highfive:
Thanks! I'm just confused because I've literally NEVER had to do this and have flashed countless roms when I was on ICS builds.
Great tip :highfive::good::highfive: