I'm trying to get custom roms provided in de Android Development section on my phone but it doesn't work out well.
YES I DID READ ALL KINDS OF GUIDES, but it just wont work.
Got an Lt26i model running ICS build 6.1.A.0.452
I unlocked the bootloader, i putted Doomlords CWM on it but it gave me problems, bootloops with the doomlord logo.
Seemed i flashed with the wrong kernel. What i did was flashing the stock ROM again and it worked but CWM is gone aswell.
What i like to do now is put CWM on it and root the phone.
Who can give me an very clear explanation how to do this.
Doomlords explanation says to get back to GB i just dont get it.
Please who can help
Related
Hi guys, thanks to the great tuturuals i've succesfully rooted my device But i have a question. Im still new to the hole android and rooting, so please bear with me.
After i flashed my XWKE7 kernel with the CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 kernel, i followed the tururial to get rid of the yellow triangle. I flashed origial kernel back on my device (I9100XWKE7_Nernel), however my device is still rooted... So why should i follow the rest of the tuturial to flash the cf_kernel with CWM?
Isnt it better/more stable to keep running it with the original kernel? The root is still active, so why should i flash the rooted one back with CWM?
bump
really nobody?
The (for me important) difference are these:
1. While the phone is not booted yet, you can still access superuser through adb. This is important if you screw something up and the device is in a boot loop.
2. You have ClockworkModRecovery, where you can take backups, install updates from sdcard etc.
I don't think the original kernel is more stable, because the custom kernel is based on the original.
hello i just did a clean fresh install on official se 2.1, rooted, busybox installed, flashed xrecovery about ten times now so i can flash the new zKernel. i can only get xrecovery to actually work prob 1 in 10 power ups and iv flashed the 20072011.zip file 3 times now yet it doesnt actually work. when i open about in settings its still the stock kernel, is there a way of flashing the new kernel using the flash tool or just plain without xrecovery????
cheers if anyone can help
What baseband are you using with the zkernal and tell me how to you make xrecovery appear on the boot up? There is only one way to do it.
Sent from my Atrix 4G with XDA Premium App
had the same problem... just made a work around which worked for me.. as i see, flashing zkernel does not delete anything... but this uuntz kernel delets the stock kernel any applies the custom kernel... so what i do is first flash the uuntz kernel which deletes the stock kernel and applies itself.. and straight after it without reebooting i flash the zkernel... and it works... i dont know how the hell it works this way but it works...
im having problems with xrecovery as well so flashing the two kernels is proving to be difficult. iv had xrecovery for about 6mths and booted into it fine everytime but now im on official se rom as i mentioned less than 1 in 10 boot ups will boot into x recovery
its giving me the ****s i hacked/flashed different roms from day 1 of owning this phone but now im on se rom nothing works iv even let se pc suit update it three times and started from scratch. ill keep trying xrecovery cheers for your help
Hey so, im getting really mad at my phone atm. Ive been trying to add a room to the phone after i rooted it using Odin.
version 2.3.5, the phone IS rooted, i can use clock work mod, change files with root explorer. etc
Here is my problem, when i try to backup my phone using ClockWorkMod Recovery, i get ''failed to verify whole-file signature'' Ive been googling my problem now and read ****loads of posts about it.. I also get this error trying to room Cyanogen
I got Android Recovery e3 or something, i tryed to add a edited version with Root explorer, didnt work.
Im trying to add galaxys2 / nightly by Cyanogen version 7.1..
So what can i do to remove this ''failed to verify whole-file signature''
Downgrade to e2? And how do i do it..? if thats the case
Im a complete noob, i had the phone for like 1 week, and i really want a custom room...
You're using stock recovery, not CWM recovery.
So e3 is stock recovery? How can i then get CWM recovery? I download it, flashed etc, but i still got the same e3 when i reboot my phone
flash a custom kernel with cwm integrated (eg spedmod/hardcores/cf root)
So uhm, im checking this link out.
http://forum.xda-developers.com/showthread.php?t=788108
And i should download one of the files, i got no clue what files i should download. And should i just add the pdf file into Odin?
Because when i followed this guide on Youtube, i only needed to download a pdf file and click start.. Thats prob my problem? I should have uploaded a bootloader aswell? (assuming bootloader = bios/android recovery)
Can u guys help me picking the file on that site, i have no clue what to download -.-
My Phone says, I9100xxiki4
The one under says [email protected] #2
Build number GINGERBREAD.Xwki8
For starters, wrong device thread!
Read this, and then read it some more.
http://forum.xda-developers.com/showthread.php?t=1103399
We could tell you how to do it, but it's best to understand what you're doing. Everything you need to know is in the link above.
Please read the sticky guide to rooting it will have link to chainfire thread follow instructions.. its far more simple than reads.
At the moment you still have stock kernel and no recovery due to this.
Sent from my GT-I9100 using Tapatalk
offff, im trying to read up and everything. But this isnt so easy for a guy coming from a Iphone to android.. ive rooted my phone using a guide on youtube.. The Phone is rooted, i used a file that was completely the same as i got just that it was rooted instead of stock... Guess i have to read a little more
You will likely run into issues if you try to flash CM7 from a CF-Root kernel from what *I've heard*.
http://forum.xda-developers.com/showthread.php?t=1176411
What I'd do:
-run CF Root for a while; get to know the phone and what it can/can't do,
-back up your efs folder before you start flashing ROMs or other kernels,
-when you decide it's time for CM7 flash a Siyah kernel via CWM recovery,
-then flash CM7 paying particular attention to the instructions in the link.
So i think i got it now, or. Cyanogen mod 7 loops in the startup -.-..
What i did before is that i used odin, i should have just restarted my phone there.
Not going into Clockwork thingy and flash it, when i did that the phone just went back to e3.. Now i restarted the phone and got more options (cwm.based recovery v5.0.2.7)
1 Update
Trying to sort this out -.- I prob just went full retarded with my phone.. I had Cyanogen version 7.1 on my sd card, tryed to update it. And didnt work, just loooppping..
Can someone plz help me, i got so many dumb problems from just rooting my phone...
2 Update
Now its just stuck on the startup screen, ive been messing around and stuff in the cwm. How can i undo this, atm i just want my phone back to normal. And work from scratch -.- And how come i couldnt update the Cyanogen from sdcard........ --.--
Clean phone
Download Odin and relevant stock rom for your phone .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
boot to cwm recovery
Mounts and storage format cache data system and sdcard ,
Remove and replace battery go to download mode flash stock rom via Odin .
Root via .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Im such a noob, how do i clean the phone?
Im really sorry for wasting your time with my noobness, i though when i finally got cwm recovery thingy to work i could finally install my cyanogen mod... But then something failed, i booted the phone, and it got stuck on the screen. Now only samsung galaxy s2 thingy shows. And nothing else happends.... Geeeeeeeeeez i shouldnt have messed around without knowing what to do, and i would have saved u guys some time...
update, The triangle is gone and everything. Im back to e3 but my phone just wont boot... I dont get it... sigh
update 2, Can u help me finding my stock kernel ? Maybe im just ****ing up with something there?
Did you read the install instructions from the CM7 nightlies thread I linked you to?
Did you try to flash to CM7 from a CF Root kernel? (many/most aren't successful flashing CM7 from a CF Root kernel)
Did you flash it twice? (must flash it twice upon first install)
Your best bet now is to follow the directions that JJEgan linked you to to at least get your phone up and running again on stock firmware. Take it one step at a time and save any more modding for another day.
Ninja Edit: you got a free "thanks" from me by accident. Paypal me $5 and we'll call it even.
I dont get it, why wont it load when i loaded in my stock kernel... After i wiped and everything using e3.. Man this is sooooooo annoying...
And mudferret i would if i had my card here. trust me i would pay $1000 if i got this **** to work, this is frustrating
sucks to be a noob
Im prob spamming something on this site with my edits and posts.
My kernels have been on 40 mb, because i picked the Stock Kernel, now i picked 'Nordic' Lets see if this works. This file is on 272 mb
Update
Got it working now!!!
Think im gonna put my superskills away for a while untill i read up and understand how this works! Thanks alot for helping me out <3
Glad you're sorted out. Take your time, no rush to mod. Good luck.
Sent from my MicroTAC 9800X using speech to fax modem
I've been having a look at trying a few custom roms on the Neo V and some say to install a different baseband. Some of the links aren't clear what I should be using. Is the baseband for the Neo the same as the Neo V?
I'm guessing that if I flash 4.0.2.A.0.62 then I'll get baseband 64, but I'm looking to see if I can flash just that baseband without the whole stock rom.
Yes you can! i have neo V .42 but having .283 kernel .62 baseband of neo! works perfectl!
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Celtic67 said:
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Click to expand...
Click to collapse
Rightly said my friend!
Well I was wondering the same thing- Can you flash basebands from 62 on 283? This thread has given me some answers.
I have some other questions though. I am a noob running stock neo v .283 firmware with unlocked bootloader(testpoint method) and CWM(the one for stock roms) installed. I want to flash the CM9 by FXP tonight. I have made a backup through CWM so that I can revert back in case something goes wrong.
Now the CM9 installation process involves flashing different kernel+baseband. If at some point I want to restore my previous CWM backup(taken on .283 stock rom), then what should be the procedure I should follow? For example, do I need to flash stock .283 .ftf+kernel again before I restore my backup through CWM?
I had a good search & didn't find a great deal about basebands. It would be useful to have something in the Neo section.
Flashing the stock ftf should include the kernel, I believe. You should be back at the same baseband & kernel and just need to install CWM again and restore your backup. I'd do the usual wipe everything in CWM before restoring, though.
Having said that, You've made me realise that I didn't note which firmware I was on before doing mine. So even though I took a CWM backup, I've no idea which stock to flash. Ah well, I wasn't planning on going back.
I later decided that the .283 firmware is simply too old and not supported by kernel/ROM developers anymore; besides flashing the entire stock .283 every single time just for restoring a backup seems too big a hassle. So I relocked my bootloader, updated to stock .62 firmware through PC companion, unlocked bootloader again, and then flashed a custom .62 kernel with recovery. After that I made my backup through CWM and installed CM9 afterwards. This way, all I will have to do for restoring my original backup is flashing the same custom .62 kernel. no ftf flashing involved.
I just got this motorola atrix
bootloader unlocked, rooted and twrp recovery.
info:
build 4.5.91
Android 2.3.4
baseband N_01.77.30P
WEBTOP 1.2.0-110
KERNEL [email protected] #2
I use to play with hd2 and load trough recovery almost about anything.
Is this the same game or got to watch out...
I mean i load a new rom trough recovery?
nothing to worry about?which rom is more stable?
thanx
hei, u dont have to answer or help....
i find out that u need just to load new rom into card and install trough recovery...nothing to worry about if is costum rom...
hope it helps somebody else...
yes you are not expected to have any issues flashing. Make sure you read the ROM thread carefully about datawipe/factory reset.
Some ROM owners specify you to do it and some don't.
Make sure you have latest CWM. I happened to used old CWM made by Tenfar and soft-bricked mine. After installing ROMRACERs CWM I was able to load CM9 without issues.