Related
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
Download CWM Recovery.7z from attachments. Extract Recovery.tar
Download Superuser-3.1.3-arm-signed.7z (or newer from http://androidsu.com/superuser/). Extract Superuser-3.1.3-arm-signed.zip and copy it to your SD card (internal or external).
Put your phone in Download mode. Flash Recovery.tar using Odin.
Put your phone in Recovery mode. Flash Superuser-3.1.3-arm-signed.zip from recovery
Reboot and ready
Thanks developers!
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
I didn't needed. The other method posted makes the S7500L keep rebooting into recovery. So, I flashed stock firmware (S7500LVJLH1) with Odin and start over again, but same result.
I'd flashed again stock firmware and just flash recovery with Odin, then just write Superuser from recovery.
I hadn't time to verify if the problem was with boot.tar or with files that are installed in recovery mode by .bat file.
Sent from my GT-P1010 using xda app-developers app
شكراااااااااااااااااااااااااااااااا
thanxssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
Can i use this Superuser 3.1.3-arm.zip for rooting Galaxy Ace S5830 ??
Sent from my GT-S5830 using xda premium
Yeah... For any phone with ARM CPU core
Sent from my GT-I9100 using xda app-developers app
issues after flashing gt-s7500T
lokeshsaini94 said:
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Android System Recovery (3e) problem
i flashed "recovery.tar" as PDA via Odin3...then went into recovery mod but it say "Android System Recovery (3e)"..i think its Samsung's default recovery ... so where is CWM???
hi guys!
i have a problem with my ace plus and i have to bring it to a warranty center.. so i have to restore the stock rom and un-root.. any help?
is there a guide to do it? do you know where i can find the stock rom?
thanks a lot
If I root my phone, any advantage in the new root between old 1....
Can someone help me?
My Galaxy Ace Plus (S7500) doesn't want to boot in download mode
Thanks guys, great work
However, my Ace plus is GT - S7500W (London 2012 limited edition)
Is there anyway to root it?
Thanks so much!
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
kol12 said:
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
Click to expand...
Click to collapse
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
farodriguez said:
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
Click to expand...
Click to collapse
Thanks. So does installing stock firmware not write any files to the data partition of android? What about the apps that are included in stock firmware sms app, contacts,call logs, maps etc, will those apps data be lost with installing stock firmware?
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
The recovery.img you have is larger than the stock firmware recovery.img. Does this write more data somewhere?
here is Android 4.1.2 for Galaxy ace plus working
http://forum.xda-developers.com/show...5#post38450355
fido747 said:
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Click to expand...
Click to collapse
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Corsario_Negro said:
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Click to expand...
Click to collapse
Hi i have the same problem and the solution is flash this http://forum.xda-developers.com/showthread.php?t=2255561
i used odin, and works perfect.
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
vasilisaerox said:
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
Click to expand...
Click to collapse
Just flashed recovery and i'm having the same issue. Original 2.3.6 installed never touched.
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
i see this firmware in this post http://forum.xda-developers.com/showthread.php?t=2074458
how install in my tab p3113 please
i need root or clockworkmod recovery i dont know
sorry for my english i speak spanish
Dear baby tab owner..........
The instructions are clearly included in the thread you posted. There are tutorials in the general and development sections. Please read.
DigitalMD said:
Dear baby tab owner..........
The instructions are clearly included in the thread you posted. There are tutorials in the general and development sections. Please read.
Click to expand...
Click to collapse
no, my question is if I need to install the recovery or I can use the recovery that brings the tablet without root or other recovery
if you're installingnstock Samsung firmware, or those leaked OTAs, you only need stock recovery, i'd advise you to odin flash the UK 4.1.1 version for the 3110 instead, those OTAs are unstable and odd, the first 4.1.1 ota boots and gives wifi and autobrightness issues, the latest 4.1.1 ota does not go past the tab 2 bootscreen, I'm running the uk 4.1.1 for the 3110 from Sammobile on my P3113, overall, everything works smooth.
Sent from my GT-P3110 using XDA Premium HD app
those are test firmwares, and if arent sure how to install them then perhaps you shouldnt. if there is a problem you are gonna have a hard time fixing it.
RESOLVED: the ODIN flash did work once i got the right tar file.
I tried flashing one of those firmwares for 4.1.1 which was only 357 MB and it got stuck at the boot screen, It seems I had bad instructions I followed with a link to an incomplete flash file, perhaps part 1 of a 2 part download. When it flashed it last said it was updating remaining files and then went back to the recovery, When I rebooted it stuck at the recovery even after a data wipe. I tried flashing a 3113 rooted stock rom and it gives me an E:signature verification failed. I used odin to flash the 4.04 stock rom which passes, but it still freezes at the boot screen even after a data wipe. Should I try flashing CWM recovery through odin to get around the signature verification or does someone know another procedure that has worked to get back to stock 4.04 from this condition. I have seen this mentioned a couple of times in the development threads with users indicating that they got back to stock, but without details of exactly how.
The firmware I apparently partially flashed was GT-P3113_P3113UECLI4-OTA-P3113UEBLH2_XAR_374372839
Also I was not able to see if usb debugging was enabled since I could not do anything but recovery or download modes on the tablet.
Hi,
I currently have ClockworkMod Recovery 6.0.2.3 installed and am using ROM Manager Premium 5.5.1.5 to attempt to install CyanogenMod.
I have the correct rom downloaded for the Verizon version, but every time I try to boot into the ClockworkMod recovery, the standard Android Recovery screen comes up instead.
I have followed about 3 different tutorials, and each ended in the same result.
Any idea what could be going on?
Thanks!
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Edgehood said:
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Click to expand...
Click to collapse
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
CAKELIE said:
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Click to expand...
Click to collapse
How did it fail?
Sent from my LG spectrum (that's right) blazing fast on cm10!
I am having almost the same problem. I rooted my phone using this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT6 - ZSLO2 Fixed for bootloop
ZCLSF (no bootloop fix, proper default.prop)
http://d-h.st/users/philz_touch/?fld_id=16061#files
taken from here: http://forum.xda-developers.com/showthread.php?p=31911620#post31911620
as it matches my phone make, build, kernel's date, model, etc. The trouble is when I go to recovery mode from ROM Manager it just stops on its way showing me this green little robot and a progress bar in the middle and it could stay like this for hours without moving anywhere. I have to press my power button and then it moves on and reboots into CWM. I have tried a whole lot of different rootings methods but ROM Manager v5.5.3.7 simply refuses to work with PHILZ-CWM6-DDLSC-ODD-5.06.1-SIGND.ZIP... I am completely lost...
Could anybody suggest / advise anything please? I would highly appreciate it Many thanks in advance!
I am on Android 4.1.2 Jelly Bean, Samsung Galaxy Note GT N7000, build number is JZ054K.N7000DDLSC, baseband version is N7000DDLS6, kernel version is 3.0.31 – 906407 March 6, 2013.