Hey guys,
Need urgent help here. i think i hard bricked by rooted unlocked i727 SR.
I had CWM Recovery 5.0.2.7 installed and i wanted to update it to the CWM Touch Recovery version 5.8.4.3.
i downloaded the file from the clockworkmod.com site and put it into the external SD card. Then from the terminal emulator i put in these commands:
su
dd if=/mnt/sdcard/external_SD/recovery-clockwork-touch-5.8.4.3-skyrocket.img of=/dev/block/mmcblk0p6 bs=4096
I am pretty sure this is an incorrect command (especially the memory block) since it flashed the memory block and as soon as i restarted it..boom. Nothing happens. No power, no vibration, no beeps, cant get into recovery, cant get into download mode, none of the key combinations work, plugging in the charger doesnt work.
Pls help! Have i hard bricked it!! Is there a solution to this?
candiesdoodle said:
Hey guys,
Need urgent help here. i think i hard bricked by rooted unlocked i727 SR.
I had CWM Recovery 5.0.2.7 installed and i wanted to update it to the CWM Touch Recovery version 5.8.4.3.
i downloaded the file from the clockworkmod.com site and put it into the external SD card. Then from the terminal emulator i put in these commands:
su
dd if=/mnt/sdcard/external_SD/recovery-clockwork-touch-5.8.4.3-skyrocket.img of=/dev/block/mmcblk0p6 bs=4096
I am pretty sure this is an incorrect command (especially the memory block) since it flashed the memory block and as soon as i restarted it..boom. Nothing happens. No power, no vibration, no beeps, cant get into recovery, cant get into download mode, none of the key combinations work, plugging in the charger doesnt work.
Pls help! Have i hard bricked it!! Is there a solution to this?
Click to expand...
Click to collapse
Yes,you have.your'e gonna have to spend some money to repair it.I had the same issues.Either go to MobileTechVideos.com or go to there ebay site and pay $15 less. $35.00 search for JTAG.Sorry for the bad news
You tried taking the battery out and putting it back in?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
jtag revival is needed bootloader is corrupt.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-skyrocket-jtag-brick-repair/
you could try a jig but i'm most certain jtag is required.
how come you didn't just odin flash the tar?
candiesdoodle said:
Hey guys,
Need urgent help here. i think i hard bricked by rooted unlocked i727 SR.
I had CWM Recovery 5.0.2.7 installed and i wanted to update it to the CWM Touch Recovery version 5.8.4.3.
i downloaded the file from the clockworkmod.com site and put it into the external SD card. Then from the terminal emulator i put in these commands:
su
dd if=/mnt/sdcard/external_SD/recovery-clockwork-touch-5.8.4.3-skyrocket.img of=/dev/block/mmcblk0p6 bs=4096
I am pretty sure this is an incorrect command (especially the memory block) since it flashed the memory block and as soon as i restarted it..boom. Nothing happens. No power, no vibration, no beeps, cant get into recovery, cant get into download mode, none of the key combinations work, plugging in the charger doesnt work.
Pls help! Have i hard bricked it!! Is there a solution to this?
Click to expand...
Click to collapse
Why did you flash mmcblk0p6 when Skyrocket's recovery is on mmcblk0p22?
And, oh yeah, try jtag if it will work.
Sent from my Calculator with Android.
for future reference there are easier and better ways to get cwm on our phones, either one of these have proven to be brick safe
Clockworkmod Touch 5.8.1.3..... Hit thanks for tpmullan, read OP
ClockworkMod TOUCH 5.5.0.4 v4.3..... Hit thanks for sk8erwitskil, read OP
use odin to flash on a stock phone
UZ7 said:
You tried taking the battery out and putting it back in?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yup - tried that the first thing probably, doesnt work ofcourse.
popcorn900 said:
jtag revival is needed bootloader is corrupt.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-skyrocket-jtag-brick-repair/
you could try a jig but i'm most certain jtag is required.
how come you didn't just odin flash the tar?
Click to expand...
Click to collapse
I dont know really. I think I wasnt reading properly. Should have just used an Odin tar instead of trying to be super smart by typing out the command!
jose makalolot said:
Why did you flash mmcblk0p6 when Skyrocket's recovery is on mmcblk0p22?
And, oh yeah, try jtag if it will work.
Sent from my Calculator with Android.
Click to expand...
Click to collapse
Hey jose, when you say 'try jtag if it will work', i hope you aren't implying that there are chances it will not work. Is that so? I am looking for someone here in my country who will do Jtag for me. I found a few guys but they are all familiar with i9100 models not the i727. I am hoping its not too different - especially the soldering part onto the phone motherboard.
Has anyone tried Jtag and came out unsuccessful?
Will keep you guys posted once I go and speak to one of these fellows.
vincom said:
for future reference there are easier and better ways to get cwm on our phones, either one of these have proven to be brick safe
Clockworkmod Touch 5.8.1.3..... Hit thanks for tpmullan, read OP
ClockworkMod TOUCH 5.5.0.4 v4.3..... Hit thanks for sk8erwitskil, read OP
use odin to flash on a stock phone
Click to expand...
Click to collapse
Thank you thank you. Noted and remembered. No more typing through the terminal.
Happy to announce that my SGS2 SR i727 is back alive and kicking.
JTAG did the trick. Had to trace this guy in another city who seems to be an expert in all things JTAG, JIGs etc. He repaired it in less than 2 hours!
So if anyone is looking for a JTAG repair service in Mumbai or Delhi in India, give me a buzz. I can help you out.
hello guys i'm very sorry for my bad english
i'm in the same problem of candiesdoodle i hard brick upgrading recovery from clockwork 2.0.1.3 to clockwork 5.8.1.3 directly from the phone
now it is in a jtag reparation
when it will be repaired i'd like to know:
1) can i put it in recovery mode or it brikked again?
2) which recovery i'll be found?
3) what is better to do?
i think for first put it in download mode and flash clockwork 5.8.1.3 with odin and than go in recovery for upgrade to cyano 9.1.0 is this correct?
muchas gracias
gringo italiano said:
hello guys i'm very sorry for my bad english
i'm in the same problem of candiesdoodle i hard brick upgrading recovery from clockwork 2.0.1.3 to clockwork 5.8.1.3 directly from the phone
now it is in a jtag reparation
when it will be repaired i'd like to know:
1) can i put it in recovery mode or it brikked again?
2) which recovery i'll be found?
3) what is better to do?
i think for first put it in download mode and flash clockwork 5.8.1.3 with odin and than go in recovery for upgrade to cyano 9.1.0 is this correct?
muchas gracias
Click to expand...
Click to collapse
nobody can help me? :highfive:
gringo italiano said:
nobody can help me? :highfive:
Click to expand...
Click to collapse
You must first flash to stock using odin
Then root and flash a recovery, I recommend "Team Win Recovery Project" TWRP
Then with your custom rom downloaded, flash the rom file.
I suggest one of the 4.1.2 roms, Those are the latest android releases.
If you flash your custom rom but do not see Gmail, Make sure to flash Gapps.
Be sure to wipe cache and fix permissions,
If you wipe system be sure you have a rom downloaded to flash
If you don't then you will end up soft bricked, and it's not easy to get out of that.
If you follow the instructions for flashing each rom exactly, then you will have a working rom.
If you mess up and your phone acts crazy, just try wiping cache and flashing again.
TearRoar said:
You must first flash to stock using odin
Then root and flash a recovery, I recommend "Team Win Recovery Project" TWRP
Then with your custom rom downloaded, flash the rom file.
I suggest one of the 4.1.2 roms, Those are the latest android releases.
If you flash your custom rom but do not see Gmail, Make sure to flash Gapps.
Be sure to wipe cache and fix permissions,
If you wipe system be sure you have a rom downloaded to flash
If you don't then you will end up soft bricked, and it's not easy to get out of that.
If you follow the instructions for flashing each rom exactly, then you will have a working rom.
If you mess up and your phone acts crazy, just try wiping cache and flashing again.
Click to expand...
Click to collapse
His phone was bricked in case you didn't read the whole thread..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
yes i brick it
my steps was
- buy the phone
- unbox the phone
- flash clockwork 2.0.1.3
- root
- flash cm-9.1.0-skyrocket.zip --> boot loop
- flash cm-9-skyrocket.zip --> boot loop
- flash cm-10-skyrocket.zip --> boot loop
-upgrade from terminal clockwork 5.8.1.3 for boot loop problem... successfuly
- reboot system
- died, black screen, no boot, no recovery mode, no download mode no pc, hard bricked
totaly 2 hours life for my little children
gringo italiano said:
yes i brick it
my steps was
- buy the phone
- unbox the phone
- flash clockwork 2.0.1.3
- root
- flash cm-9.1.0-skyrocket.zip --> boot loop
- flash cm-9-skyrocket.zip --> boot loop
- flash cm-10-skyrocket.zip --> boot loop
-upgrade from terminal clockwork 5.8.1.3 for boot loop problem... successfuly
- reboot system
- died, black screen, no boot, no recovery mode, no download mode no pc, hard bricked
totaly 2 hours life for my little children
Click to expand...
Click to collapse
You need to do some research before flashing. Know what you're flashing and make sure its for the skyrocket
Yup you are hard bricked. Jtag works and is well worth the money
If you still have a warranty I would send it in and get a new skyrocket. I did this before and sent in my hard bricked phone and never heard back from at&t about why it was not working. I told them I woke up and it wouldn't turn on. I hope this helps some good luck.
xcrazydx said:
You need to do some research before flashing. Know what you're flashing and make sure its for the skyrocket
Click to expand...
Click to collapse
yes it is my friend i take almost all from this xda section but i dont remember where i download clockwork 5.8.1.3 i dont know probably is that or probably upgrading recovery from terminal because candiesdoodle (the autor of thread) had my same problem with same steps (or my ex girlfriend messaging during process ) but anyway the phone now is in a jtag laboratory i hope it back alive i think is a simple botloader flash i'd like to know which recovery i'll find and which are my future steps
gringo italiano said:
yes it is my friend i take almost all from this xda section but i dont remember where i download clockwork 5.8.1.3 i dont know probably is that or probably upgrading recovery from terminal because candiesdoodle (the autor of thread) had my same problem with same steps (or my ex girlfriend messaging during process ) but anyway the phone now is in a jtag laboratory i hope it back alive i think is a simple botloader flash i'd like to know which recovery i'll find and which are my future steps
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1777970
xcrazydx said:
http://forum.xda-developers.com/showthread.php?t=1777970
Click to expand...
Click to collapse
mmmhh... I'm a little afraid to work from terminal
is not better flashing from odin?
You would have to flash cwm 5 with Odin and then flash 6 through the cwm 5 via zip file
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
You would have to flash cwm 5 with Odin and then flash 6 through the cwm 5 via zip file
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
ok i'll flash cwm 5 and i'll take a break
is it still a good recovery or not? can i flash cyano roms with this version or i'll have boot loop problems?
Related
hi all,
Firstly apologies if this is covered somewhere but for the life of me I cannot get to the bottom of this. I have spent 2 weeks on and off trying to get a solution but my Sensation is still boot looping.
The problem occurred when I turned on the camera but was faced with a blank screen. I could return to home screen but the camera would not work each time I launched. So I rebooted the device but then I was stuck in this boot loop.
Device info
HTC Sensation S-OFF RL
HBOOT-1.27.0000
RADIO-11.21.3504.13_2
I was running Insert Coin 2.3.5 ROM for some time without issue
I was hoping I could just do a superwipe and flash a new ROM
FAIL - each time I boot into CWM and select Recovery, it just goes back to bootloop.
I selected Factory Rest from CWM menu
FAIL - it just goes into bootloop
Also cannot use ADB as the device will not connect to the PC. Im using a card reader to put files on the SD card but have not being successful resolving the issue.
Tried an SD card from a stock Sensation, no difference. Booting with no SIM, not working.
Most Bootloop fix's seem to involve super wipes / flashing new ROMs but because my Recovery goes into the bootloop I dont have this option. I wish it was so easy.
Can anybody offer an other ideas.
Thanks for you patience, I am not much of a modder or Android expert. I had just flashed a ROM many months ago to help improve battery life and I was happy with that.
Have you tried re-installing your recovery throught the bootloader?
try different recovery (4EXT) or reinstall recovery again
thanks guys.
I found these flashable recovery files. Both CWM and 4EXT. I have tried both zips and ran the update in HBOOT but am still booting in CWM and if I select RECOVERY is goes too bootloop again.
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
I think I might just give up and drop the phone into a phone repair shop and let them try it.
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Try this pg58img (it helped me)http://www.wuala.com/LuckyThirteen/Elegancia/Official RUU Sensation/ it will update your sensation to ICS, (you will maintain s-off)
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
GROGG88 said:
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
markmcie said:
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
Click to expand...
Click to collapse
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
If you can boot normally into ICS and you are rooted, then get the 4Ext app or the ROM Manager app and flash the recovery through one of those.
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
Ill do this a few times over the weekend and hopefully I can get up and running again. I will let you know how I get on.
Thanks
markmcie said:
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
Click to expand...
Click to collapse
Well I'd have to agree with dublinz then...
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
markmcie said:
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
Click to expand...
Click to collapse
Flashing the ICS PG58IMG.zip doesn't replace the recovery.
Fix recovery first. Use stock recovery. When you get that working, change to "simple" cwm recovery.
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
before flashing stock recovery...can you try this first
get this recovery image
and flash the recovery via fastboot
steps:
1.go to fastboot in your device and connect it to your pc (after this device should read fastboot usb)
2.get the adb/fastboot setup ready guide here
3.go to your adb folder and place the downloaded recovery.img there
4.type fastboot devices (it should show your device serial number)
5.now to flash type
fastboot flash recovery recovery.img
this should do...if it didnt work then let me know ASAP...then we'll think of other solutions
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
EddyOS has them , search that. I'll try to locate them.
I remembered incorrectly, it was only CWM and 4EXt
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
But you can find stock recovery in this forum:
http://www.htcsensationforum.com/ht...ota-update-on-rooted-phone/msg76452/#msg76452
scroll down a little bit ...
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
Here you go:
http://db.tt/kvTvDblW
It should include all MID's and most CID's that I know of...
GROGG88 said:
Here you go:
http://db.tt/3YSslZVg
It should include all MID's and most CID's that I know of...
Click to expand...
Click to collapse
Link is doing a 404 ...
SanityPreservation said:
Link is doing a 404 ...
Click to expand...
Click to collapse
Fixed...
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
Hi,
I am new to this forum.
My captivate is on stock firmware UCKH3 (2.3.4)
I think I've done something wrong while flashing a custom kernel.
The kernel was flashed, the phone is booting but I am unable to get into the CWM recovery. Tried button-combo and also from ROM manager but no luck. Hence I am unable to flash any roms in the forum except odin tar's!!
I would like to try ICS roms but I couldn't find odin packages.
Please help me with this issue or post a link which may help my case.
Thank You,
Pradeep Kiran
Which kernel did you flash, and what combination are you attempting?
were you able to get into recovery before .?.
I had to use ADB to get me into recovery on my i897. If you dont know what ADB is, look it up as i did.
Careful with Odin, it will brick ur phone, but no worry many ways to get unbricked. I had to make a jig. you can order one, same price either way, just if you make one check the ohms, needs to be 301k resistance.
korockinout13 said:
Which kernel did you flash, and what combination are you attempting?
Click to expand...
Click to collapse
I've used Boog kernel with CWM from this link
http://forum.xda-developers.com/showthread.php?t=1242533
Tikiflame said:
were you able to get into recovery before .?.
I had to use ADB to get me into recovery on my i897. If you dont know what ADB is, look it up as i did.
Careful with Odin, it will brick ur phone, but no worry many ways to get unbricked. I had to make a jig. you can order one, same price either way, just if you make one check the ohms, needs to be 301k resistance.
Click to expand...
Click to collapse
Well, I got I897UCKB2 firmware when I've purchased the phone,
I tried the one click executable I897UCKH3 from the stock Rom's thread and my phone got bricked!! I made a jig to put it into download mode and flashed the same package. It is working now but I've screwed up my recovery!! I am unable to get into recovery by using adb, button combo or rom manager.
krnprdp said:
Well, I got I897UCKB2 firmware when I've purchased the phone,
I tried the one click executable I897UCKH3 from the stock Rom's thread and my phone got bricked!! I made a jig to put it into download mode and flashed the same package. It is working now but I've screwed up my recovery!! I am unable to get into recovery by using adb, button combo or rom manager.
Click to expand...
Click to collapse
Whoops, at least you got it going again :good: maybe you can take a shot at a different one click .jar
The one click jar that I used in download mode was SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar *which you need to be rooted so use Root Checker App to make sure you are rooted if not Super One Click v 2.3.3 Short Fuse :good:<---{there needs to be a huge thanks button here}
If that does it from there reinstall Rom Manager and enjoy cwm Recovery, and I flashed Devil 1.6.1.zip from cwmR :cyclops:
* A few more poost and i can post links, sorry
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.