Database Develop

[Help] Stuck on boot

Hello, I have a samsung I9001 But now i have installed recovery clockworkmod thats was going then i wanted to install
cyangonemod 9 and then its go wrong when i boot it its keeps on booting i have a backup but thats fails to
I can go into recovey mode and download mode but thats was it
i tried to install a stock rom with odin but odin keeps saying setup connection
anyone who can help me

You can from your computer download cm9 and gapps...put them into a sd card...and put your sd card in your phone...go into recovery..fullwipe...cache dalvik...and then istall rom and after gapps...i do this way
sent from a phone surely better than iphone...
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
Sorry i forgot to told you...before the rom download twrp recovery 2.2.1 and install...after that install the rom
sent from a phone surely better than iphone...

jordy55 said:
Hello, I have a samsung I9001 But now i have installed recovery clockworkmod thats was going then i wanted to install
cyangonemod 9 and then its go wrong when i boot it its keeps on booting i have a backup but thats fails to
I can go into recovey mode and download mode but thats was it
i tried to install a stock rom with odin but odin keeps saying setup connection
anyone who can help me
Click to expand...
Click to collapse
if it's boot in recovery mode( every time you start it go in recovery mode) you should flash the bootloader. at cwm recovery section from i9001 wiki page you can find.
edit: this is http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330

Thank you both You make my day really better thanks thanks thanks !

jordy55 said:
Thank you both You make my day really better thanks thanks thanks !
Click to expand...
Click to collapse
if so then push the thanks button :good:

jordy55 said:
Thank you both You make my day really better thanks thanks thanks !
Click to expand...
Click to collapse
don't forget to hit thanks

Haha done, Its working fine Android 4.0 is new for me looks great

jordy55 said:
Haha done, Its working fine Android 4.0 is new for me looks great
Click to expand...
Click to collapse
enjoy it

[ROM][4.4 KK]Pure AOSP builds by dhacker29 [XT925/XT926]

These are pure AOSP builds by dhacker29, all credit goes to him.
Please note these are hot off the press and may have bugs. Users have reported trouble with flashing, etc, but when you manage to get it to run the ROM runs smoothly.
Still, AOSP is bare-bones and will need device specific modifications that custom ROMs provide. Consider it a stable-ish alpha build, but not a dependable daily driver.
Please ensure you do your backups. Nobody is responsible if your phone bursts into flames.
All files you need are here:
Prerequisites: KitKat requires TWRP 2.6.3.0 which can be found here
xt925 ROM
xt926 ROM
GAPPS
By default AOSP has no root access, however Chainfire's root will work just fine. Just flash and install SuperSU.
Have fun with KitKat!
Changelog
20131108 Fix sd-mount, update blobs with 4.4 MotoX leak
Known Issues:
Ext-SD not activated
As with other AOSP builds, Google Keyboard is not working. Make sure to use AOSP keyboard.
Does not work with 16GB internal storage https://twitter.com/dhacker29/status/398946262172446720 (Try different versions of TWRP to address this)
Front camera may not work - will crash camera app. Go to app info and clear data to run it again
Video playback problems for some
Some HDMI problems when plugged in

I'm pretty happy on CM 10.2, but I may have to flash this just to see what 4.4 is all about...
Thanks for sharing! :good:

Thanks for sharing.

From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk

Just tried to flash the ROM using CWM... obviously didnt work lol.
Flashed TWRP 2.6.3.0, then flashed the ROM
Setting up device now.
Ill post after a day or so of usage to let everyone know how its going.

TXKSSnapper said:
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
You got right.

Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.

madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?

dabanhfreak said:
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
Click to expand...
Click to collapse
do you mind editing the OP to include a list of known issues?
Thanks!

koftheworld said:
do you mind editing the OP to include a list of known issues?
Thanks!
Click to expand...
Click to collapse
Yet to run into any tbh (besides ex-SD of course), will give it about 24hours and see what folks pick up.

koftheworld said:
do you mind editing the OP to include a list of known issues?
Click to expand...
Click to collapse
Got stuck on the M Logo. But now, I'm wondering if it's not the infamous "Stuck on the M Logo" bug more than the recovery not working on the XT925. I'll try again.

madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.

flight666 said:
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
Click to expand...
Click to collapse
Using Flashify. It flashes OK, but I can't get to the recovery... Hanging on the M logo. Damn it.

Can the atrix HD flash this??
Sent from my MB886 using xda app-developers app

Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
Click to expand...
Click to collapse
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.

madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Good to see

I'm noticing that there's a bug in the AOSP launcher, I can't seem to add a new home screen.
I installed the Nexus 5 Launcher as well, same result.
No such problems on Nexus 7 when installed Google Launcher.
EDIT: nvm, it seems that installing Google Launcher messes with the AOSP launcher... didn't make sense to me either. Oh well, no N5 experience
Uh, no, not that either. I think it was a custom Wallpaper.

you've to drag an app to make a new screen on the new kk launcher ?
pls correct me if i'm wrong..

madmonkey57 said:
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol

flight666 said:
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
Click to expand...
Click to collapse
Downloads are slow and tend to fail before the end... We'd better be careful! I am currently re-downloading all files needed.

[Q] need help in slimkat rom

hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this

harishke said:
hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this
Click to expand...
Click to collapse
what i normally do using philz recovery
1) wipe data ( complete wipe to install a new rom)
2) flash slimkat rom
3) flash slim gapps
4) as im having as c6902, i need to flash modules of c6902, hence, flash the modules provided in the monx thread in Xperia Z1 android development
5) flash superuser zip to gain root access later on
6) reboot

Hey
[/COLOR]
harishke said:
hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this
Click to expand...
Click to collapse
you have to download this file: https://drive.google.com/file/d/0B_3SvSLy59OXUTUweFJpWjYwd1E/edit?usp=sharing
then flash it.

Exact problem. Give This zip a try. Also can you explain what is This file do???
---------- Post added at 04:57 PM ---------- Previous post was at 04:24 PM ----------
stoan123 said:
[/COLOR]
you have to download this file: https://drive.google.com/file/d/0B_3SvSLy59OXUTUweFJpWjYwd1E/edit?usp=sharing
then flash it.
Click to expand...
Click to collapse
Working. thanks bro
Sent from my z1 on slimkat rc2

a
jobangill99 said:
Exact problem. Give This zip a try. Also can you explain what is This file do???
---------- Post added at 04:57 PM ---------- Previous post was at 04:24 PM ----------
Working. thanks bro
Sent from my z1 on slimkat rc2
Click to expand...
Click to collapse
there're diferent between c6903 and c6902. i think that is modem
you can read more detail from thread

thanks a ton guys finally it worked by flashing modem and was able to use the rom:good:

[Q] S3 Mini Telus - Custom Recovery Problems

I recently got an S3 Mini and I wanted to install cyanogenmod on it. I have experience because I have cyanogenmod on my S4 and TWRP custom recovery.
After I use Odin to flash the TWRP custom recovery to the phone, whenever I try to boot into recovery the screen just freezes and these lines and green film start to appear on the screen.
I have uploaded the picture of the phone trying to boot into recovery
Can someone please help me?
Thanks

McMahonus4 said:
I recently got an S3 Mini and I wanted to install cyanogenmod on it. I have experience because I have cyanogenmod on my S4 and TWRP custom recovery.
After I use Odin to flash the TWRP custom recovery to the phone, whenever I try to boot into recovery the screen just freezes and these lines and green film start to appear on the screen.
I have uploaded the picture of the phone trying to boot into recovery
Can someone please help me?
Thanks
Click to expand...
Click to collapse
Did you flashed TWRP from maclaw?
---------- Post added at 08:19 PM ---------- Previous post was at 07:57 PM ----------
Which model is this phone, it's not a GT-I8910 right?

Clostry said:
Did you flashed TWRP from maclaw?
---------- Post added at 08:19 PM ---------- Previous post was at 07:57 PM ----------
Which model is this phone, it's not a GT-I8910 right?
Click to expand...
Click to collapse
you're right, it can't be a I8190. Look at where the camera is (right top side). On the original it's on the left top side

koragg97 said:
you're right, it can't be a I8190. Look at where the camera is (right top side). On the original it's on the left top side
Click to expand...
Click to collapse
The photo is not clear but the camera seems where it should be to me
Just telus is a canadian company, this made me think it could be a sm-g730...

Clostry said:
The photo is not clear but the camera seems where it should be to me
Just telus is a canadian company, this made me think it could be a sm-g730...
Click to expand...
Click to collapse
There's literalyl 390248230948023948 variants of the S3 mini, fairly certain it is the SM-G730 confirm it on the model or in settings. Maclaw's recovery or any other recovery is not compatible with your phone, and as far as I know your phone does not have a recovery yet hence why it bootloops. You need to revert back to stock: forum.xda-developers.com/attachment.php?attachmentid=2530506&d=1390328847 and all shall be well. There's no active development on your phone as far as I know but do give this thread a visit: http://forum.xda-developers.com/showthread.php?t=2469413&page=11

So can it be that I'm flashing the wrong twrp file? Because I'm flashing the wrong region?? Any suggestions on how to fix this issue and get it working?

McMahonus4 said:
So can it be that I'm flashing the wrong twrp file? Because I'm flashing the wrong region?? Any suggestions on how to fix this issue and get it working?
Click to expand...
Click to collapse
It's because there is no TWRP for your device, there are no TWRP or CWM builds for the TELUS S3 MINI the ATT&T S3 MINI and the VERIZON S3 MINI.(as far as I know) Only solution is to compile it yourself, and that's quite involved but there are numerous guides out there.

I see.... Thanks anyways, I may try to compile my own, if I do get it working I will upload it here

McMahonus4 said:
I see.... Thanks anyways, I may try to compile my own, if I do get it working I will upload it here
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
TWRP is easier to compile after you got a working CWM recovery, as you only need to add in a couple of TWRP flags.
You need to run ubuntu natively or through virtual machine (VMWare, etc) and download the CM source code which may take a while depending on your internet speed (it's quite large about 15gb i think or so )

The same thing happened to me when I tried to install CWM for my s3 mini sm-g730w8( this is the Canadian version for telus) Boot into download mode (VOL DOWN+HOME+POWER) then just choose reboot device and it should be okay. If it still doesn't work then boot into download mode and then flash the stock rom via odin. Also regarding the custom recovery for our phone, even if you did port a working custom recovery the works for our phone, you won't be able to install it because our bootloader is locked; which is also why your screen turned green after trying to boot into your custom recovery. I found 2 possible solutions for flashing scripts and mods: kn0x0ut Toolbox http://forum.xda-developers.com/showthread.php?t=2550120 and Flash Gordon http://forum.xda-developers.com/showthread.php?t=2250555 I haven't been able to try them yet but I think kn0x0ut toolbox is more reliable. I hope this helped

N9208 updated to OL1

Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much

it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem

I updated but he never tried to flash so can't help there. Trying to figure out what improvements it has.

casper1 said:
it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem
Click to expand...
Click to collapse
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. from power off, did you reboot holding the Home Button, Volume UP and Power Button all at the same time? that would boot you to recovery. From there, i would wipe caches or perform a factory reset if your phone does not boot up normally. by the way, this new release is available at sammobile.com for the N9208 with the BRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.

cortez.i said:
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. by the way, this new release is available at sammobile.com for the N9208 with theBRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.
Click to expand...
Click to collapse
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?

casper1 said:
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?
Click to expand...
Click to collapse
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
---------- Post added at 04:07 PM ---------- Previous post was at 03:42 PM ----------
also wanted to know if you tried flashing the tar files that contained rooted kernels from the Original shipping firmware and the AOJ3 update.

casper1 said:
Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much
Click to expand...
Click to collapse
OL1 still rootable. But OK3 blocked non Samsung recovery. So you would need to downgrade bootloader to OK2.
Boot loop if you try to flash custom recovery without OK2 bootloader.
Mr. Gundal ..we love you!!

cortez.i said:
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
Thank you thank you... the Sboot solved the problem, appreciate that very much... i have been trying that for 2 days...
Click to expand...
Click to collapse