Related
I just flashed T-Mobile firmware and i got bootloop. It's not CWM bootloop. I can go in download mode but i can't go in recovery. I don't know what to do, and help will be appreciated.
digitz_ said:
I just flashed T-Mobile firmware and i got bootloop. It's not CWM bootloop. I can go in download mode but i can't go in recovery. I don't know what to do, and help will be appreciated.
Click to expand...
Click to collapse
connect your phone to the computer
go into donwload mode
start odin
flash http://www.hotfile.com/dl/176669754/95e7a92/S6500DXXLD3_S6500DPROLD1_PRO.zip.html
RoSinner said:
connect your phone to the computer
go into donwload mode
start odin
flash
Click to expand...
Click to collapse
Nope, still same thing.
digitz_ said:
Nope, still same thing.
Click to expand...
Click to collapse
you flashed the file I linked and you're still getting a bootloop ? you must be doing something wrong
RoSinner said:
you flashed the file I linked and you're still getting a bootloop ? you must be doing something wrong
Click to expand...
Click to collapse
What can I do wrong? I putted MD5 in PDA and flashed.
I tried to flash CWM and diffirent firmwares but no luck.
digitz_ said:
What can I do wrong? I putted MD5 in PDA and flashed.
Click to expand...
Click to collapse
As I know, the one package file of extension (.tar.md5) is placed under One Package field & not in PDA.
Also u need an ops file which should be placed under OPS field.
Sent Via XDA™ Premium
Galaxy_Rohit said:
As I know, the one package file of extension (.tar.md5) is placed under One Package field & not in PDA.
Also u need an ops file which should be placed under OPS field.
Sent Via XDA™ Premium
Click to expand...
Click to collapse
I was flashing before like this, everything was fine. There must be a way to fix this.
Nobody? Is anything possible with adb or fastboot?
EDIT: I fixed it. Thanks anyway.
Galaxy_Rohit said:
As I know, the one package file of extension (.tar.md5) is placed under One Package field & not in PDA.
Also u need an ops file which should be placed under OPS field.
Sent Via XDA™ Premium
Click to expand...
Click to collapse
nah we can flash one package with pda
How did you fix it?
digitz_ said:
Nobody? Is anything possible with adb or fastboot?
EDIT: I fixed it. Thanks anyway.
Click to expand...
Click to collapse
Hello, I'm having exactly the same problem. I went back to stock from cm10, but now I have a bootloop (boots until samsung logo and reboots.)
I think I just need to wipe data, but I can't access recovery. I even flashed cwm a few times and flashed the stock rom with a pit file, but I'm still stuck on samsung logo.
So, any help?
Here: http://forum.xda-developers.com/showthread.php?t=1853159
bro .. use odin
first switch to download mode then connect ur mob with pc , then use odin and update it with original pda ..
digitz_ said:
EDIT: I fixed it. Thanks anyway.
Click to expand...
Click to collapse
How did you do it, I cannot install adb drivers for some reason, I went back from CM10.1 to stock but now it just keeps repeating boot animation. Please help.
tom1890 said:
Hello, I'm having exactly the same problem. I went back to stock from cm10, but now I have a bootloop (boots until samsung logo and reboots.)
I think I just need to wipe data, but I can't access recovery. I even flashed cwm a few times and flashed the stock rom with a pit file, but I'm still stuck on samsung logo.
So, any help?
Click to expand...
Click to collapse
Hi, I had exactly the same problem, flashed the stock firmwire but it gets stuck on samsung logo, flashed few CWMs but nothing. I really didn't know what to do, then my battery became critical so i connected it to the pc and let it charge. While charging, I tried to acces the CWM recovery (home+volume up+volume down + power) and BAM! It opened recovery, I deleted all user data, cache and factory reset, rebooted and it worked.
Try to flash stock rom
Flashing stock rom didn't work.
Sent from my GT-S6500D using Tapatalk 2
digitz_ said:
Nobody? Is anything possible with adb or fastboot?
EDIT: I fixed it. Thanks anyway.
Click to expand...
Click to collapse
how did you fix this? i have exactly the same issue.
polys643 said:
how did you fix this? i have exactly the same issue.
Click to expand...
Click to collapse
Hi All,
I was struggle with bootloop issue for 3 days. I got my problem when I forgot to wipe phone returning ROM 10.2 to stock rom. Before I didn’t have any problems with getting to recovery mode but after I was not able to get to CWM. Also did try (vol+) (vol-) (home) hold while odin reset all I get RUMDAMP ARM9. Same when trying to hold recovery combination while normal boot. I have no problems with getting to Download mode.
Phone show Samsung animation and then vibrate once, pause, vibrate twice.
What work for me.
Recovery Combination = (vol+) + (vol-) + (home) + (pwr)
1. With odin 3.04 (don know if version matters I hade SS_DL.dll in same folder as odin) I install cwm-6.0.3.3-b2-jena.tar.md5
2. It restarted and get boot loop again
3. When I hold recovery combination phone didn’t boot. But what did I remove battery plug it again. Press (pwr) and immediately (maybe 0.5 sec) I hold rest of the recovery combination. Phone boot and show me logo so I release the buttons. To my surprise I did boot to CWM. (don’t know way but I didn’t do wipe immediately but I restart did try it again to be sure if this works – and it did, at least for me)
Rest was easy (WIPE Factory Reset, Cache, Dalvik Cache and just in case fix permission) restart and did boot to Stock ROM. For some unknown reason now I can normally CWM just buy holding combination and releasing as soon as Samsung logo show up.
I hope this will help somebody.
Now im using CM 10.1 07/07
My phone is S6500D no NFC
Cheers,
Maciej
digitz_ said:
Nobody? Is anything possible with adb or fastboot?
EDIT: I fixed it. Thanks anyway.
Click to expand...
Click to collapse
pleeees tell me how u fix it my phone hase the same proplem u had can u
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Medarioth said:
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Click to expand...
Click to collapse
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
JasSingh93 said:
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
Click to expand...
Click to collapse
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Medarioth said:
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Click to expand...
Click to collapse
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
JasSingh93 said:
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
Click to expand...
Click to collapse
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
The link you gave redirect me for a post of yours.
Medarioth said:
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
Click to expand...
Click to collapse
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
JasSingh93 said:
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
Click to expand...
Click to collapse
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Medarioth said:
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Click to expand...
Click to collapse
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
JasSingh93 said:
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Medarioth said:
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Click to expand...
Click to collapse
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
JasSingh93 said:
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
Click to expand...
Click to collapse
ok will try and keep you updated
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
Ok, you shouldn't have any problems anymore :fingers-crossed:
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Medarioth said:
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Click to expand...
Click to collapse
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
JasSingh93 said:
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
Click to expand...
Click to collapse
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Medarioth said:
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Click to expand...
Click to collapse
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
JasSingh93 said:
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
Click to expand...
Click to collapse
done. waiting in progress ....... :fingers-crossed:
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
It should definitely work this time! I've actually just flashed TWRP recovery, and I can already say I prefer it over ClockWorkMod!
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Medarioth said:
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Click to expand...
Click to collapse
Yayyy!!! Nice one! Good teamwork we got there in the end! Happy to help
Have fun!!
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?
HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.
HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day
i recieved several times a message saying that i have to install a security update (at&t), after some time i decided to install it but when i try to i get a status 7, another thing what do i need to install a custom rom on my arix hd, it has android 4.1 from at&t, unlocked bootloader, cwm, and carrier unlocked (i dont want to loose this), in my touchpad i just have to download the rom + gapss and install them from a custom recover, so i dont know if this is the same for the atrix hd, thanks in advance.
You need to be running stock recovery and stock ROM to install the update.
The update includes security patches and some modem updates. This update may be necessary for taking the OTA KK update.
audit13 said:
You need to be running stock recovery and stock ROM to install the update.
The update includes security patches and some modem updates. This update may be necessary for taking the OTA KK update.
Click to expand...
Click to collapse
ok thanks for answering, i have stock rom so, but unlocked bootloader can i install it then just by installing the stock recovery?
You may need to be unrooted in addition to having stock recovery.
If you removed too many of the att apps, that may cause the update to fail as well.
audit13 said:
You may need to be unrooted in addition to having stock recovery.
If you removed too many of the att apps, that may cause the update to fail as well.
Click to expand...
Click to collapse
where can i find stock recovery?, because when i turn the phone on it takes about 40 secs to reboot into recovery to update, so i cant do anything with it now :S
maur1c10 said:
where can i find stock recovery?, because when i turn the phone on it takes about 40 secs to reboot into recovery to update, so i cant do anything with it now :S
Click to expand...
Click to collapse
Did you phone take the update or is it automatically booting into recovery?
The best way to get the update is to flash back to stock ATT 4.1.1, take the OTA update, re-install CWM, and carry on using a custom ROM. This is exactly what I did with a Bell Canada Atrix HD.
You can try re-installing stock recovery in fastboot.
audit13 said:
Did you phone take the update or is it automatically booting into recovery?
The best way to get the update is to flash back to stock ATT 4.1.1, take the OTA update, re-install CWM, and carry on using a custom ROM. This is exactly what I did with a Bell Canada Atrix HD.
You can try re-installing stock recovery in fastboot.
Click to expand...
Click to collapse
Yeah. The quickest, sure-fire way to get in a position to take the OTA update is to flash back to stock (stock files available here). You can use RSD or MythTools, whatever works for you. Doing this will also put you back on stock recovery.
I had to do this, too, before I could take the OTA. But in my case I had modified/removed too many AT&T stock apps...
thanks to both of you, yes the phone rebooted itself like about 40 secs from turning on i was able to fix this part by formatting cache from cwm, now im gonna try to flash stock recovery
quasihellfish said:
Yeah. The quickest, sure-fire way to get in a position to take the OTA update is to flash back to stock (stock files available here). You can use RSD or MythTools, whatever works for you. Doing this will also put you back on stock recovery.
I had to do this, too, before I could take the OTA. But in my case I had modified/removed too many AT&T stock apps...
Click to expand...
Click to collapse
so i flashed the stock recovery from the stock rom, but when i go into recovery the android is down with a red exclamation sign and i cant get into the recovery menu :S, did this happen to you by any chance?
maur1c10 said:
so i flashed the stock recovery from the stock rom, but when i go into recovery the android is down with a red exclamation sign and i cant get into the recovery menu :S, did this happen to you by any chance?
Click to expand...
Click to collapse
When the dead Android dude is on the screen, tap the bottom right hand side of screen. Hopefully, a menu will appear.
audit13 said:
When the dead Android dude is on the screen, tap the bottom right hand side of screen. Hopefully, a menu will appear.
Click to expand...
Click to collapse
well i flashed the stock firmware, and the phone works fine but still the same with recovery, nothing happens if i touch on the screen or if i press volume or power button, tried to install the update anyway but it fails, hope i can somehow install KK when it comes
maur1c10 said:
well i flashed the stock firmware, and the phone works fine but still the same with recovery, nothing happens if i touch on the screen or if i press volume or power button, tried to install the update anyway but it fails, hope i can somehow install KK when it comes
Click to expand...
Click to collapse
Which stock ROM did you install? There are 2 versions of 4.1.1.
audit13 said:
Which stock ROM did you install? There are 2 versions of 4.1.1.
Click to expand...
Click to collapse
Blur_Version.98.4.20.MB886.ATT.en.US is the one that my phone already had
I think that is the ROM before the update.
I see another ROM named Blur_Version.98.5.38.MB886.ATT.en.US too.
audit13 said:
I think that is the ROM before the update.
I see another ROM named Blur_Version.98.5.38.MB886.ATT.en.US too.
Click to expand...
Click to collapse
flashed it and works fine except recovery the same issue but its updated so i can go to cwm now, thanks man
maur1c10 said:
flashed it and works fine except recovery the same issue but its updated so i can go to cwm now, thanks man
Click to expand...
Click to collapse
Did you flash 98.4.20 or 98.5.38?
audit13 said:
Did you flash 98.4.20 or 98.5.38?
Click to expand...
Click to collapse
the first time i flashed 98.4.20 the second time 98.5.38 and i have the same problem with recovery in both cases
maur1c10 said:
the first time i flashed 98.4.20 the second time 98.5.38 and i have the same problem with recovery in both cases
Click to expand...
Click to collapse
Strange. Did you flash both ROMs using RSD Lite or Myth? I had to use RSD Lite without Myth to flash 98.4.20.
audit13 said:
Strange. Did you flash both ROMs using RSD Lite or Myth? I had to use RSD Lite without Myth to flash 98.4.20.
Click to expand...
Click to collapse
i used myth (easier to use), could that make any difference?
maur1c10 said:
i used myth (easier to use), could that make any difference?
Click to expand...
Click to collapse
I got a Bell Canada Atrix HD from a co-worker. When I used Myth to flash from stock Bell to stock ATT, it would not work properly. When I used RSD with 98.4.20 without going through Myth, the ATT ROM flashed without any errors. I was able to take the OTA update, flash CWM, and revert to a custom ROM.
Hi Guys,
Im using n950f and recently had bootloop. I tired to flash new stock firmware. But still same, device is still keep on bootloop not able to get home screen.. just samsung welcome logo and restart to the same place. I tried twrp that not responding to touch, i tried different versions but no luck. From the last 2months its in same state, i tried different stock firmwares 3months old,previous security patch..1yr old and current but same.. phone can able to pass odin flash but after this also keep on boot loop. Please help me, this issue happened when it is in use and suddenly went bootloop. And phone not able to get recovery mode using the key combinations..
Are you able to logcat the device during boot?
XDHx86 said:
Are you able to logcat the device during boot?
Click to expand...
Click to collapse
How to get?
abyabrahammathew said:
How to get?
Click to expand...
Click to collapse
Do you have usb debugging enabled? You have to use adb logcat in cmd while the device is connected and is booting.
I tried to install stock rom using twrp but zip is failing.. file is good only, I tried different firmwares..same errors
abyabrahammathew said:
I tried to install stock rom using twrp but zip is failing.. file is good only, I tried different firmwares..same errors
Click to expand...
Click to collapse
You can't flash Samsung stock ROM through TWRP, you need ODIN to do so. You can get your stock ROM from here (SM-N950F).
I tried using odin, it passed and boot loop still there
abyabrahammathew said:
I tried using odin, it passed and boot loop still there
Click to expand...
Click to collapse
That's why you need to logcat the device...