Related
A huge problem seems to have arisen on my Desire Z.
After using Andromadus 8 for a while I decided to try some other ROMS.
They were:
- Andromadus V10 and 11
- Virtuous Quattro RC3
- Ice Cream JIBwich 1.1
- BlissDroid
- Android Revolution HD 7.0
All of these ROMS flashed after using Superwipe G2 however were stuck on the initial boot screen.
I left some of these ROMS on for more than an hour on the boot screen to no avail.
The only ROMS that still seem to function are Andromadus V8 and MIUI ICS (however with no Wi-FI)
Please can anyone give an indication of what is wrong?
Some roms don't want you to wipe anything because the flashing will do it for you. Although it could've been that the roms have problems?
Sent from my CM7 G2!
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Cleared dalvik and checked all the MD5. Everything seems fine except it doesn't work
Tried a ordinary factory reset/data wipe?
-Nipqer
starop013 said:
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Click to expand...
Click to collapse
Superwipe does clear dalvik cache.
I am at my wits end
ONLY Andromadus 8 works for some reason
I cleared it and cleared it, and reflashed every combination of roms
BUT only 8 works and I'm tired of not having my camera anymore
I've even tried bare Sense 2 ROMS to no avail. Every ROM is stuck on bootloops
Does anyone have a solution?
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Have you tried flashing from recovery directly? RM is great for convenience, but I just don't trust it to do things properly. I've had this happen to me sometimes where a ROM looks like it's flashed, but hasn't. Weird, I know. Try the following, it worked for me before:
1. Flash SuperwipeG2+ext4 (if you want the ext4 filesystem)
2. Flash your ROM
3. Check to see if it worked
4. If it didn't work, flash your ROM again without wiping
Usually that fixes it for me. In 4EXT recovery, you can check the partition sizes to see if the ROM installed properly. Not sure if CWM does that as well.
Nipqer said:
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Click to expand...
Click to collapse
Nipqer
You sir are a legend
An obvious solution that makes me wonder why I didn't think of it
Thank you, thank you
flashing through recovery is just easier for some, and if your not near a computer. but for best results always fastboot -w and flash rom via fastboot, just makes life easy the first time. and im ocd a little so i also flash superwipe and manually wipe data/cache. so if you dont wont any issues, fastboot wipe, fastboot flash... your golden!
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Hello!
After some fiddling around I have finally succeeded into installing the MIUI custom rom. (had a heck of a work around to perform because I forgot to put the custom ROM on my SD card first.)
Right now, I've got Clockwork Recovery 5.8.4.0 installed with the latest miui. Fastboot is also installed and working, and my phone is unlocked. The correct boot.img has also been installed.
It even boots. BUT. After it has showed the MIUI logo and goes to my home screen, it starts loading for like 4-5 seconds where everything still works, and it then stops. Crash. The screen freezes and my phone reboots. It seemed like a SIM card problem to me, but even removing the SIM card and booting my phone wont solve this issue. Does anyone have any clue what I can do?
Summary of installed software:
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
Latest MIUI for One X (downloaded this afternoon)
Latest ADB Development Kit. (Not used though)
Latest Flashboot.
Factory Reset performed (Whole phone is empty except for above mentioned programs.
Thanks in Advance!
P
Erase Cache
While in Fastboot Mode .Perform This command
Fastboot erase cache
Should do the job for u!
I would suggest flash the boot.img again and then erase cache again.Will work
Tried it, but..
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
^^ for ARHD 16 u need hboot 1.33 , 1.36 depending on your CID
for miui did you do full wipe?
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache? I think ARHD does that anyway, but might be worth doing the superwipe.
Oh, and if you're restoring system data or system apps with Titanium backup, stop it.
HBOOT!
I am afraid ur not on the right CID version for installing JB roms.
Please update ur Hboot
@ali3nfr3ak: Yes, I did a full wipe before MIUI. After every flash I do a Dalvik Cache Wipe, Factory Reset Wipe and Cache Wipe. Even the fastboot receive a cache wipe after every flash.
How do I update my HBOOT? The rest seemed pretty straight forward, but there are tons of versions out there, and I do not know which one I should be taking. And what is CID? I've also been having troubles porting a Super Wipe toward my mobile phone. Can a Super Wipe be performed within fastboot/recovery?
Haha and no, I'm not using Titanium Backup
Right, I've succesfully restored my phone to it's old state. Flashing MIUI again provided the same error. Could it be that my hBoot is out of date here? My One X still has the 4.0.4 android version, whilst MIUI is based on 4.1, right?
Change the rom, miui isn't good.
Hello!
The last couple of days I'm struggling to get any custom kernel running on my phone.
Every custom JB kernel is tried resulted in almost instant instability (while setting up my phone after a full wipe for example).
Even Alex's kernel which is almost stock with only the S2W function build-in is unstable for me.
Real stock kernel is running rock stable, and in the past(ICS) i hadn't any issues when flashing custom kernels.
My phone is on Hboot 1.31 <updated to 1.39> and I have a variant 1 Tegra 3.
I'm using Renovate Final 1.1 (and as far as I read the comments in their thread, nobody is experiencing the instability issues).
I tried the following kernels (repacked for my rom):
* Alex-v s2w
* XM-Kernel
* KozmiKKernel
* NXC V6
I have flashed in the right steps:
* Clear cache/dalvik/system/data (recovery)
* Full wipe
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install rom.zip (recovery)
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img custom kernel (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install modules.zip (recovery)
* Clear cache/dalvik/system/data (recovery)
Normally(ICS) my phone would run fine after the above steps, but now my phone is really unstable after flashing one of these custom kernels.
Is there something wrong with my hardware or are these custom kernels not build for my variant 1 ?
Since stock kernel is really stable without any issues.
Dude you are making things overly complicated.
1. Fastboot flash boot boot.img
2. Fastboot erase cache
3. Go to recovery
4. Select ROM zip
5.full wipe option in aroma installer OR you could have wiped system/data/cache in recovery
6. Flash modules zip
7. Reboot
PS variant affects overclocking and undervolting ability. Also, Alex kernel shouldn't cause problems since its just stock kernel with sweep2wake. And you don't need to perform wipes a billion times, its like trying to tidy an empty room.
Sent from my HTC One X using xda app-developers app
tomascus said:
Dude you are making things overly complicated.
1. Fastboot flash boot boot.img
2. Fastboot erase cache
3. Go to recovery
4. Select ROM zip
5.full wipe option in aroma installer OR you could have wiped system/data/cache in recovery
6. Flash modules zip
7. Reboot
PS variant affects overclocking and undervolting ability. Also, Alex kernel shouldn't cause problems since its just stock kernel with sweep2wake. And you don't need to perform wipes a billion times, its like trying to tidy an empty room.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
d33f said:
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
Click to expand...
Click to collapse
Are you repacked the KERNEL for your ROM? If don't try to repack with http://forum.xda-developers.com/showthread.php?t=1815607. Most of the Developers recommend to repack the KERNEL to the ROM!!!
Thant said:
Are you repacked the KERNEL for your ROM? If don't try to repack with http://forum.xda-developers.com/showthread.php?t=1815607. Most of the Developers recommend to repack the KERNEL to the ROM!!!
Click to expand...
Click to collapse
The kernels are repacked for my rom(those I tried)
then dont use s2w?
d33f said:
Hello!
The last couple of days I'm struggling to get any custom kernel running on my phone.
Every custom JB kernel is tried resulted in almost instant instability (while setting up my phone after a full wipe for example).
Even Alex's kernel which is almost stock with only the S2W function build-in is unstable for me.
Real stock kernel is running rock stable, and in the past(ICS) i hadn't any issues when flashing custom kernels.
My phone is on Hboot 1.31 and I have a variant 1 Tegra 3.
I'm using Renovate Final 1.1 (and as far as I read the comments in their thread, nobody is experiencing the instability issues).
I tried the following kernels (repacked for my rom):
* Alex-v s2w
* XM-Kernel
* KozmiKKernel
* NXC V6
I have flashed in the right steps:
* Clear cache/dalvik/system/data (recovery)
* Full wipe
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install rom.zip (recovery)
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img custom kernel (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install modules.zip (recovery)
* Clear cache/dalvik/system/data (recovery)
Normally(ICS) my phone would run fine after the above steps, but now my phone is really unstable after flashing one of these custom kernels.
Is there something wrong with my hardware or are these custom kernels not build for my variant 1 ?
Since stock kernel is really stable without any issues.
Click to expand...
Click to collapse
d33f said:
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
Click to expand...
Click to collapse
The reason why you end up in the bootloop is because you clean up too much , after you flash the rom with the default kernel that comes with it (boot.img) let it boot up in system , after that wait at least 5 mins for it to load everything and seddle then do a full reboot, after that you can flash the kernel , if you don't know how to repack on your own use this link = http://nibble.cc/repack/ , in the *source* box put ROM boot.img and in the *kernel img* put the boot.img from the kernel that you want to flash , wait few mins to repack it , download it, rename it into *boot.img* and done, after that flash exactly as i type:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Your bootloops were happening because you were wiping SYSTEM which means you delete the SYSTEM of the ROM = 100% bootloop , when you install modules you're not install whole new system on the phone only the kernel ram disk and few other small things. NEVER wipe anything else then what i wrote above. Anyhow after you boot up in the system let the phone seddle for 5 mins at least and then do FULL REBOOT . after that do whatever you want to doo. Hope it helps.
I didn't had any boot loops, only stability issues.. (rom is booting fine, only my phone reboots as soon as I start Antutu and let it benchmark).
Furthermore I tried to install my rom again with full wipe and I've done these exact same steps after flashing my rom:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Still really unstable as soon as I push my phone (freeze and reboot)
The only reason I can think of is that I didn't let the rom settle (flashed the rom and immediately flashed the custom kernel after).
But in the past(ICS) I've done this the same way without any issues
d33f said:
I didn't had any boot loops, only stability issues.. (rom is booting fine, only my phone reboots as soon as I start Antutu and let it benchmark).
Furthermore I tried to install my rom again with full wipe and I've done these exact same steps after flashing my rom:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Still really unstable as soon as I push my phone (freeze and reboot)
The only reason I can think of is that I didn't let the rom settle (flashed the rom and immediately flashed the custom kernel after).
But in the past(ICS) I've done this the same way without any issues
Click to expand...
Click to collapse
You should never flash the kernel right after the rom , you should let the Rom with it default kernel and boot img boot up 1st for the 1st time, set it up if you like or not , but let it seddle at least for 5 mins, then do 1 full reboot and after that flash kernel.
Even if this doesn't help then probably your chip isn't strong enough for Oc'ed version of Kernels , if you have variant 0 that could be your issue , or perhaps 1 , but 1 should support this, my cousin has variant 1 and he can flash / use kenrnels without issues. Anyway try after the flash to boot up the phone and do what i wrote above , if that doesn't help report back i'll try to think of something else in the meanwhile lol.
Edit - nevermind about variant forgot you mentioned you have variant 1. Oh well just try with other things i suggested.
Shan89 said:
You should never flash the kernel right after the rom , you should let the Rom with it default kernel and boot img boot up 1st for the 1st time, set it up if you like or not , but let it seddle at least for 5 mins, then do 1 full reboot and after that flash kernel.
Even if this doesn't help then probably your chip isn't strong enough for Oc'ed version of Kernels , if you have variant 0 that could be your issue , or perhaps 1 , but 1 should support this, my cousin has variant 1 and he can flash / use kenrnels without issues. Anyway try after the flash to boot up the phone and do what i wrote above , if that doesn't help report back i'll try to think of something else in the meanwhile lol.
Edit - nevermind about variant forgot you mentioned you have variant 1. Oh well just try with other things i suggested.
Click to expand...
Click to collapse
Thanks for your advice, I'll try it again later today and report back..
My rom has settled for a couple of days now with stock kernel, so I'll see what it does with a custom kernel again.
I tried NCX V13 today, it's stable!
What I've done differently is that I didn't wipe anything in recovery after flashing the modules.
Furthermore I let the phone settle for 5 minutes before running Antutu.
I don't know if this is really the cure for my issue or that this V13 kernel is the first kernel stable enough for my SoC, but it works now!
Did got a few hard reboots today while running Epic Citadel/Antutu with gaming boost enable and phone on charger.. I reflashed the kernel, let the phone cool down and everything is running stable again
Hello,
since I had ICJ 1.5 on my HOX I wanted to do an update to ICJ 2.0.
I have HBOOT 1.12 and my CID is H3G__106. I already tried to install ICJ 2.0 on it, but it gets stuck at the boot animation (the cross^^).
Are there any possibilities to do the update or do I have to live with 1.5 forever?
cheers,
z3xi0n
I'd imagine you need a Jellybean hboot(1.3x), as 2.0 is running on the newer 3.10 kernel.
You could try flashing the rom, and then a 2.6 kernel (http://forum.xda-developers.com/showthread.php?t=1873615) in the same process?
did you fastboot flash the boot.img from the new 2.0 zip?
remember, you need to move all sdcard\0 files to sdcard\
i did it in recovery
i did the following steps..
nandroid backup
full wipe (data, cache, dalik cache)
erase fastboot cache
fastboot flash boot boot.img (from the 2.0 zip)
erase fastboot cache
moved sdcard/0 into sdcard/
flashed the rom
flashed gapps
now it gets stuck at the boot animation (the cross does not glow). after this i tried 1.7.2 and it works perfect
I first had installed a RUU to update my hboot from 1.12 to 1.36, after that i unlocked my hox again and put the new ICJ on it
z3xi0n said:
i did the following steps..
nandroid backup
full wipe (data, cache, dalik cache)
erase fastboot cache
fastboot flash boot boot.img (from the 2.0 zip)
erase fastboot cache
moved sdcard/0 into sdcard/
flashed the rom
flashed gapps
now it gets stuck at the boot animation (the cross does not glow). after this i tried 1.7.2 and it works perfect
Click to expand...
Click to collapse
everything seems right, fastboot erase cache < right? hmm
maybe you want to re download the boot.img?
i actually cleared out all sdcard data, full wiped, install rom + gapps, full wipe again, copy sdcard data and booted
tarreltje said:
I first had installed a RUU to update my hboot from 1.12 to 1.36, after that i unlocked my hox again and put the new ICJ on it
Click to expand...
Click to collapse
Any links for tutorials or something to do the update? Didn't found any Maybe used the wrong search terms ^^
@stevvy: ofc fastboot erase cache ^^
ncx v13
I installed ICJ 2.1, i didnt upgrade my hboot, i am on 1.12. I wanted to use the old kernel. I repacked it, everything was fine.Booted, and was working,but then I installed gapps, and it didnt boot up anymore. I did all the necessary full wipe+dalvik+cache wipe. Any suggestions?
sol81 said:
I installed ICJ 2.1, i didnt upgrade my hboot, i am on 1.12. I wanted to use the old kernel. I repacked it, everything was fine.Booted, and was working,but then I installed gapps, and it didnt boot up anymore. I did all the necessary full wipe+dalvik+cache wipe. Any suggestions?
Click to expand...
Click to collapse
Did u use gapps for 4.2? For note..lowest hboot support at 1.28..
OneX Fueled by Tegra 3 Driven by IceColdJelly
---------- Post added at 12:56 AM ---------- Previous post was at 12:45 AM ----------
z3xi0n said:
Any links for tutorials or something to do the update? Didn't found any Maybe used the wrong search terms ^^
@stevvy: ofc fastboot erase cache ^^
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32539598 try read here...maybe there can help you out..
OneX Fueled by Tegra 3 Driven by IceColdJelly