{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems quite a few peopole encounter this when they wipe in this way, and unable to wipe Humberos builds anymore? Anything relevant to the Humberos new MTD?
bravokylee said:
It seems quite a few peopole encounter this when they wipe in this way, and unable to wipe Humberos builds anymore? Anything relevant to the Humberos new MTD?
Click to expand...
Click to collapse
AOKP build 23 is a non MTD partition system HumberOS is MTD. According to the instruction you will need to restock to GB Stock Safe by team overcome, and install overcome kernel with it before installing humberOS22. Even after that, you will need to flash the new HumberOS TWICE.
The first flash will give you crazy bootloop because that is when the script changes the partition system therefore it will automatically exit out from the flashing job. So don't forget to flash 2x.
yappoe said:
AOKP build 23 is a non MTD partition system HumberOS is MTD. According to the instruction you will need to restock to GB Stock Safe by team overcome, and install overcome kernel with it before installing humberOS22. Even after that, you will need to flash the new HumberOS TWICE.
The first flash will give you crazy bootloop because that is when the script changes the partition system therefore it will automatically exit out from the flashing job. So don't forget to flash 2x.
Click to expand...
Click to collapse
Thank you for your kindly guide. But it is not AOKP，it is Alroger's Kang 23. There are quite a few poeple having reported this glitch and they also did restock. But they can only successfully wipe in Kang builds, but whenever wipe Humberos builds, it start to bootloop again. They guess this is either because the problem in Kang 23 or in Humberos MTD, but no definite solutions.
bravokylee said:
Thank you for your kindly guide. But it is not AOKP，it is Alroger's Kang 23. There are quite a few poeple having reported this glitch and they also did restock. But they can only successfully wipe in Kang builds, but whenever wipe Humberos builds, it start to bootloop again. They guess this is either because the problem in Kang 23 or in Humberos MTD, but no definite solutions.
Click to expand...
Click to collapse
I see what you mean. Alroger's is from CM9 too I believe.
Follow these instructions by Humberto himself:
http://forum.xda-developers.com/showpost.php?p=26537170&postcount=1415
Related
I am a rookie,sorry.
I believe you can't change the kernel because the (locked) bootloader checks a cryptographic signature on the boot partition before it'll boot it.
You can replace the recovery partition, I thought, but during a cold boot the boot scripts rebuild it from the boot partition. (See /init.rc calling /system/etc/install-recovery.sh although I have no such file on my running phone, I presume it's erased or over-mounted...)
That's why you can battery-pull if your replacement recovery is broken, as long as it doesn't prevent reaching that far into /init.rc...
mvp3 said:
I am a rookie,sorry.
Click to expand...
Click to collapse
Because the Droid 3 bootloader is locked down unlike the original Droid 1. Without a unlocked bootloader it is impossible for custom kernels or fully custom recoveries.
Does this also mean we will be unable to flash the new Linux 3.0 kernel (where ICS runs on)? No idea if that would matter though..
rvschuil said:
Does this also mean we will be unable to flash the new Linux 3.0 kernel (where ICS runs on)? No idea if that would matter though..
Click to expand...
Click to collapse
We already have ICS booting on D3... it will be a couple months until there is a decent beta available though.
rvschuil said:
Does this also mean we will be unable to flash the new Linux 3.0 kernel (where ICS runs on)? No idea if that would matter though..
Click to expand...
Click to collapse
The only way to change the kernel is with an official update from Motorola or an unlocked bootloader. The ICS we will likely see first for this phone will be a custom build (Hashcode) which will be built on the the kernel we currently have.
Sent from my DROID3 using XDA App
mikedyk43 said:
The ICS we will likely see first for this phone will be a custom build (Hashcode) which will be built on the the kernel we currently have.
Click to expand...
Click to collapse
According to the kernel version in Hashcodes ICS build it actually is different than our stock kernel. Not saying that is the kernel that will be in ICS (or if its truely different) but it is indeed a different #
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last few days i've been trying to install the ICS version on my galaxy note. I asked ppl here and watched more than 1h of videos on youtube but i found nothing. Maybe the instructions are hidden on threads of 500 pages and i couldn't find it, or the information was not complete, idk.
So I also did nothing, better than hardbrick, but i already used the ICS on galaxy nexus and now i'm addicted to that sys.
I'd like to ask if someone here could create a full tutorial, with "how to perfectly install ICS".
Which kernel we should use, which rom is trustable, remember, we are jumping from GB to ICS.
Thank you,
Enio.
PS: I mean we BEG your help lol
Check the links on dr ketans signature for all kinds of rioting and upgrade guides.
Are they updated according to bad kernels and roms?
let me just tell you how i do it....
go to stock GB rom..KL3 would be good....
flash it...root it...
put the rom that you want in your SD card...
go to CWM and wipe data factory reset....wipe cache...wipe dalvid cache...
reboot to recovery...
install the ICS rom...
enjoy....
next time you want to install a new ICS rom...
download Redpilltouch Recovery...flash it...reboot to recovery and do all 3 wipes and install the RoM
If you are on GB and not rooted then easy way is to flash GB Speed mod kernel odin version through PC odin then you will be rooted (of course you will get yellow triangle thats not a problem you can use Triangleaway app from CF) then flash Abyss 4.2 redpill kernel boot into recovery of abyss perform 3 wipes then proceed to flash any custom ICS rom and you are done.
Its already rooted since day 1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What i must NOT do after ics instalation? And when the official update comes? Can i update it normaly?
The only thing i did is root. I was afraid to brick it lol. So im running the stock rom
I was planning to install criskelos v7 rom. Seems very stable. Is any other process needed?
Sent from my GT-N7000 using Tapatalk
Cruzaders said:
Its already rooted since day 1.
What i must NOT do after ics instalation? And when the official update comes? Can i update it normaly?
The only thing i did is root. I was afraid to brick it lol. So im running the stock rom
I was planning to install criskelos v7 rom. Seems very stable. Is any other process needed?
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Criskelo,Midnote,Rocket...they all are good and pretty stable...you can just donload the stocj ICS and flash it...but its no good compared to those roms...so just follow the steps i said...and you will be good...
you can check these videos for detailed info... :
Thank you very very very very much!!!
It took a while to completly start the system but it worksssss!!!!!!
Thank you very much dude!
Hi
I am new to flashing/rooting/installing roms. So pardon my noobness.
I have managed to rootand flash my gtP1000 by folowing the overcome guide
http://forum.xda-developers.com/showthread.php?t=1881981
And wiped/flash recovery mode to install cm 10 in this link
http://forum.xda-developers.com/showthread.php?t=1871113
Now, i would like to try alroger's 4.2.2 jb, should i just wipe cache and install it via recovery mode or i need to flash some kernels first?
forum.xda-developers.com/showthread.php?t=2043421
Here are some info about my tab
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-P1000 using xda app-developers app
hi
there is no need to install kernel
you can do it on CWM
only because of repartitioning on this rom on rom installation process tab will be reboot and continue to install rom afer boot automatically
good luck
hfalahaty1 said:
hi
there is no need to install kernel
you can do it on CWM
only because of repartitioning on this rom on rom installation process tab will be reboot and continue to install rom afer boot automatically
good luck
Click to expand...
Click to collapse
What do you mean by repartitioning? Does it make partitions on my sd?
So basically i only need to go on recovery mode and install this along with its gapps? Pls correct me if im wrong.thanks.
Sent from my GT-P1000 using Tapatalk HD
hi
as you know there are several types of partition
in windows there are fat16, fat32, ntfs
in linux there are many diferent types
repartitioning in your tab means this ROM (10.1) needs to run on MTD partition, so its change your tab partition to MTD
in this case you lost all your data such as contacts, app and ...
and the other is when you want to came back to GB ROM you should use ODIN and follow restock rom installation
good luck
Ohh.. now i get what repartition means.. thanks.. ill try to flash 10.1 when i get time. Thanks again
Sent from my GT-P1000 using xda app-developers app
So I have rooted, TA-back-upped and then bootloader-unlocked my XZ on a .244 generic firmware and would like to install cyanogenmod 10.2 stable or 11.
There's a lot of talk about flashing ROMS from recoveries on this forum. I have read that out of the two available, the (unlocked version) CWM has problems flashing CM, while TWRP does better. Then there is XZ Dual Recovery.
Yet, in the cyanogenmod wiki for the XZ, there is no talk of installing a recovery before flashing the CM zip file, yet somehow CWM is mentioned as a recovery from which to install the zips.
I really wonder how according to the wiki I am supposed to boot into a CWM, when I didn't install it beforehand.
Does this mean that once you flash CM from sd card, it comes with its own recovery, and you don't have to install it separately?
If this is correct, is it more recommended to flash CM from an sd card or from a previously installed recovery?
And is it even possible to flash CM from a recovery I previously installed on stock kernel (I am obviously still on stock kernel). From what I understand, CM comes with its own kernel as it doesn't work on stock kernel. I imagine that a recovery would disappear when I replace a kernel, as the recovery is part of the kernel. But if so, why is there even talk about flashing CM from a recovery?
Lastly, would something like the MEOW kernel be even more suitable for CM?
I'd really appreciate anyone enlightening me on these matters and how to go about doing this flashing of the most standard of all custom ROMs.
Thank you.
You need to extract the boot.img from the CM zip and flash it using fastboot.
This will then allow you to boot into recovery and flash CM.
Edit - See post #2 of this thread for basic instructions - http://forum.xda-developers.com/showthread.php?t=2540633
Sent from my C6603 using Tapatalk
kingvortex said:
You need to extract the boot.img from the CM zip and flash it using fastboot.
This will then allow you to boot into recovery and flash CM.
Edit - See post #2 of this thread for basic instructions - http://forum.xda-developers.com/showthread.php?t=2540633
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thank you, King Vortex. I have managed to successfully flash CM 10.2.
By the way, could I flash MEOW kernel on top of the current setting, as it's CM-compatible, or would I have to re-do CM as well?
You're welcome. You can flash another CM compatible kernel over the top of the stock CM kernel. No need to reflash the rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kingvortex said:
You're welcome. You can flash another CM compatible kernel over the top of the stock CM kernel. No need to reflash the rom.
Click to expand...
Click to collapse
Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 12.1
Hello all,
We are use crackling repo files build to unofficial CyanogenMod 12.1 for Wileyfox Swift, but it work fine on Android One 2nd Gen. smartphones.
Main Thread
Forum One Team
Working
All Features
Not Working
Radio
Installation
Place ROM & Gapps (Open GApps, Arm64-5.1) in SD card
Reboot in Recovery Mode
Wipe Data/Factory Reset
Wipe Dalvik cache
Install the ROM zip
Install the Gapps zip
Reboot
Screenshots you can see here
Downloads
ROM
GApps
Twrp 3.0
Sources
Device
Kernel
Vendor
@caneray
@atakan58
@kaankulahli
Rezerved
Thread & Links Updated
+ http://forum.xda-developers.com/cro...stom-cyanogenmod-13-android-one-2gen-t3294192
Every Android One is already running on MM since a few months.
Why should someone waste time, downgrading to an outdated OS, which will never get any official updates?
Also, for the "real tinkerers", CM 13 is long time available.
vel_tins said:
Every Android One is already running on MM since a few months.
Why should someone waste time, downgrading to an outdated OS, which will never get any official updates?
Also, for the "real tinkerers", CM 13 is long time available.
Click to expand...
Click to collapse
We could give official update but Our Msm8916 Recovery is not supported.
You can install official crackling cm 13
https://download.cyanogenmod.org/?device=crackling
Today We will share Official Cm13 in Forum One Team
You can follow for other Roms
http://forum.one-teams.com/Forum-Custom-Romlar-137
+ Our Flyme Port Project
http://forum.xda-developers.com/cro...nt/5-1-1-flyme-os-4-5-4-2r-unoffical-t3301651
If radio-modem is meant by "radio", then there's no sense in having a custom rom for phones if the radio does not work. Or did you mean FM radio? :silly: