Hi,
this is my first post, but it's been a while that i'm playing with this phone and I looked for solutions but could't find.
I smoothly managed to flash PAC ROM 4.3 (stable version) following these instructions and used it for a while without any problem. Then I decided to take the next step to move on to some custom KitKat ROM. I did a nandroid backup and I tried to install the kitkat android 4.4 Cyanogenmod 11 but i'm always stuck at the cm logon screen.
I did flash the boot from ROM.zip as I am S-On.
My hboot is 3.01
What am I missing? This is where my knowledge ends. Is it about kernel? (as I am trying to go to a 3.4 kernel from a 3.0 kernel. Any help is appreciated. Thanks!
Related
The .629 update has been nothing but a headache. All I am trying to do is flash the new stable CM 7.2 mod on a D2G running a rooted version of .629. I constantly get stuck at the "M" boot logo then because of the locked bootloader, have no choice but to .sbf again and start the process all over. It's definitely becoming a hassle!
So I ask are any of these thing possible:
Flashing CM 7.2 from a rooted .629
Restoring a Nandroid backup from earlier (a CM 7.1 nightly that ran fine)
Not having to re-do the whole .sbf process EVERY TIME something goes wrong with the boot process.
I've searched up and down but I have just run out of patience. Any help is GREATLY appreciated.
Sincerely, exasperated.
If you're installing CM7 from the official Cyanogenmod site, that's exactly what you are doing wrong.
Repeating this for the 52nd time: official stable builds of Cyanogenmod 7 available from the official Cyanogenmod site are made for 2.4.x firmware and are incompatible with 4.5.x and its kernel.
You must be on 2.4.x to run official CM7.
Hello guys.. I would be grateful if any of you could help me with your thoughts regarding this matter...
For security reasons I prefer flashing stock recovery and locking down the boot loader after I settle on a custom rom/kernel combo. Been doing this for a while and I dont mind building my phone up from the scratch when I change ROM.
With CM 10.1 stable coming up.. I think I'll finally switch to 4.2 in a few weeks time. I read on the forums that the file system change in 4.2 doesn't play nice with 4.1 recoveries and ends up creating duplicate folders all over the place. Now... I'll surely use latest CWM or TWRP to flash CM 10.1 but later... when I flash the stock recovery (v3e, i think the latest for our device) just to lock down my device- is there any possibility that my system would get messed up? As the latest stock recovery for Nexus S was released with 4.1.2 it isn't supposed to be compatible with 4.2.2 roms technically.
..enlighten me please! with my little knowledge, i'm unable to work it out in my head
I have tried numerous times to install Cyanogenmod 11 nightlies on my HTC One S, but always get a fail when flashing. phone is one s S4 as I am in the uk.
hboot 215
I have the latest twrp version installed
but it wont have it.
I have flashed roms onto it in the past suck as jellybam, Miui and my current daily driver black bean v8, so am sure everything is being done correct.
even tried to instal cyanogen installer but found it doesnt support one s
any help much appreciated :crying:
HI did you use the modify recovery provided by the cm11 tread. It should fix your problem
Try TWRP, and dont forget if you dont have s-off - you need to "fastboot" the image
Yes, you don't necessarily need the latest version of TWRP, but the modified one posted in the thread. Try it! Good luck!
did it
Bogdan9183 said:
Yes, you don't necessarily need the latest version of TWRP, but the modified one posted in the thread. Try it! Good luck!
Click to expand...
Click to collapse
hi Bogdan9183;49734267 manged to get unoficial carbon 4.4.2 installed had to install Philz touch recovery advanced to achieve it thanks for the help.:good:
I am also considering to get CM 11, but how do i get hboot 2.15? I've stock branded internationell S4, that is rooted, unlocked and s-off.
Howdy y'all. I bricked my old G2 D800, I don't want a repeat with the new one. I tried doing all the research I could. I have a new D800, 10d, 4.4.2. I want CM11, tried reading the threads on that and custom recovery. I just need a little help to make sure I have the order of operations down pat before I crash another. I've rooted and flashed ROMs before, but not with th locked boot loader and security AT&T has.
Please just correct me if I'm wrong. Through the threads I have read I believe this is what I am to do.
1.) Flash my 4.4.2 back to 4.2.2 using LG FT
2.) Root using IO23
3.) Download Flashify & install TWRP 2.7.7 with Loki
4.) Follow steps to install CM 10.2
5.) Follow steps to install CM 11
Of course make backup once 4.2.2 plus root and TWRP is achieved before trying CM. I just want CM like I've had on previous phones. Thanks in advance.
All is good back to being ROM junkie. Anyone who does read and wishes to flash custom roms and get custom recovery on KK. Obtain root via IOroot25, then use AutoRec Recovery Installer for TWRP recovery.
So I've been trying to update my Shield LTE ROW since this Friday from the stock based rom LL (version 3.1.1) to the MM-based rom (version 4.2) and spend a dozen of hours failing to update :crying:
When I install a MM-based rom the shield boots and the nvidia logo shows a few seconds and then the screen goes black. When the tablet is attached to my pc I noticed that the tablet is not turned off but booted in APX-mode.
These are the things I've tried:
Installing the recovery image 4.2 (fails)
Installing the recovery image 4.1 (fails)
Installing the recovery image 4.0.1 (fails)
Installing the recovery image 3.1.1 (works)
Installing several full and incremental OTA updates to 4.x (fails)
Installing CM 13.0 (fails)
Installing carbon 5.1.1 (works)
Followed the guides mentioned in topics: http://forum.xda-developers.com/shield-tablet/help/unable-to-update-to-marshmallow-rom-t3444124 and http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 (fails)
I've tried a lot of things, but now I'm out of ideas.
Has anyone a explanation why MM-based roms don't want to boot on my tablet? And has the knowledge to fix this?
All feedback is welcome and appreciated.
You are currently able to flash and boot with 3.1.1 or stuck in apx mode?
I'm able to flash and boot with 3.1.1. Only MM-based roms are stuck in apx mode when booting.
You are probably on the Lollipop boatloader still. With that bootloader MM based roms don't work. Flash the latest stock from here, root it with cf-autoroot, flash twrp and MM based roms should work.
Thanks for your advice, I'll try it this weekend.
Just a quick question, why do I need to root and flash twrp? Shouldn't it work if I only flash the latest stock?