Hello all,
New user and made a stupid mistake. I have a note 4 and i tried rooting it via odin. Problem is i knocked my phone off during it and it unplugged. Now i try turning the phone on and it bootloops from the samsung logo to the sprint logo and then restarts. I have tried factory resets and everything. My phone will not detect in odin in the download mode. when i go in to recovery booting i get a the message dm-verity verification failed.... Please help me I am stupid for doing this and think i have lost about 1000 pics of my newborn son .
mullen5160 said:
Hello all,
New user and made a stupid mistake. I have a note 4 and i tried rooting it via odin. Problem is i knocked my phone off during it and it unplugged. Now i try turning the phone on and it bootloops from the samsung logo to the sprint logo and then restarts. I have tried factory resets and everything. My phone will not detect in odin in the download mode. when i go in to recovery booting i get a the message dm-verity verification failed.... Please help me I am stupid for doing this and think i have lost about 1000 pics of my newborn son .
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Sprint Samsung Galaxy Note 4 at http://forum.xda-developers.com/note-4-sprint which would be a good starting place . I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/note-4-sprint/help where the experts familiar with your device will be best able to guide you.
Good luck!
Related
Hello, i'll explain my case and hope can find some help.
A month ago, I flashed my S3 Mini I8190 with CyanogenMod 12.1 (Lollipop) and everything went well.
4 days ago, the phone died. I had it on my pocket and when I was going to use it, the phone was off and won't turn on. It won't respond, vibrate, even when connecting it to the charger.
Anyways, a friend told me that it may be a problem with battery and I should let phone plugged to the wall charger for 24 hours, and it worked (at least phone wasn't dead)
The phone responded, it turnedon but won't boot. It reach until model name screen (before Samsung Logo, or in this case, CM logo) and then starts to reboot. I tried to flash it again with CM and didn't worked. I flashed it with Stock Rom and didn't worked.
I flashed it with Param file and didn't worked.
The problem persists, it only reachs the model name screen and the reboots.
[!] I can't enter into Recovery Mode, only Download Mode. I tried flashing TWRP Recovery, ClockworkMod Recovery but still can't enter into Recovery Mode.
So, anyone knows how to fix this? I want to try a final thing before taking the phone into a JTAG Service.
Sorry for bad english.
Hello and thank you for using XDA Assist,
Please create an account, so you can post in other sections. Then I will have your thread moved to the Galaxy S3 Mini Q/A. Please create an account and post in this thread.
Experts there may be able to help you there.
Kind regards
Trafalgar Square
XDA Assist
Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
androcrazy24 said:
Hello guys,
A few months ago, I rooted my phone using kingroot. After a few weeks, i tried to install TWRP custom recover to unlock bootloader. I accidently downloaded a wrong version of it and flashed it using flashify app, after which i booted into recovery to check the new recover mode. But, something awkward happened. THE BOOT MODE DIDN'T OPEN AND THE SCREEN GOT STUCK AT "Booting into recovery". I read on the internet and realised that my device has got soft-bricked. Also, phone wasn't rebooting. So, i found a solution atleast start my phone. I took out my battery, pressed the buttons for download mode and then placed the battery back in and pressed the buttons for download mode and somewhow rebooted my phone (i read about this technique in xda forums). Now, although my phone works but i cannot access the recovery mode as it has got soft-bricked. Thus, i cannot perform a hard reset as it gets caught in that "recovery booting stuck cycle". So, can anyone tell me how to fix this? PLS QUICKLY. aLSO, i don't know much about ADB, so pls explain that too as my friend suggested me to use ADB to fix softbrick but im not sure!!
Click to expand...
Click to collapse
Hi androcrazy24
Thanks for using XDA Assist.
Could you please state the Manufacturer & Model of your device so we would better approach your issue guiding you to the appropriate experts? Your last post from November 2015 is referring to the S III. It is still that?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
my phone is samsung galaxy s4 mini DUOS GT-I9192, OBVIOUSLY BY SAMSUNG..........
Kdio said:
Hi androcrazy24
Thanks for using XDA Assist.
Could you please state the Manufacturer & Model of your device so we would better approach your issue guiding you to the appropriate experts? Your last post from November 2015 is referring to the S III. It is still that?
I will be waiting for your reply within the next 2 days.
Nice regards.
.
Click to expand...
Click to collapse
"mY phone is samsung galaxy s4 mini duos GT-19192 RUNNING ANDROID 4.4.2
androcrazy24 said:
"mY phone is samsung galaxy s4 mini duos GT-19192 RUNNING ANDROID 4.4.2
Click to expand...
Click to collapse
Hi androcrazy24
Thank you for your answer
Our experts at the below forum should be able to help you. Please be welcome to ask in there.
Galaxy S 4 Mini Q&A, Help & Troubleshooting
Nice regards and good luck.
.
I had this phone rooted for about a month or so using KingRoot. at first it worked as it shouldve, now recently my phone has died and upon charging it i get the message "Boot Verification Failed, Mismatch_sig_len" i cant go into download mode, safemode or anything. i need help with this as iam a novice in the rooting community :crying:
shadowtech27 said:
I had this phone rooted for about a month or so using KingRoot. at first it worked as it shouldve, now recently my phone has died and upon charging it i get the message "Boot Verification Failed, Mismatch_sig_len" i cant go into download mode, safemode or anything. i need help with this as iam a novice in the rooting community :crying:
Click to expand...
Click to collapse
Hi, Thanks for using XDA assist.
It looks like there is no dedicated forum for your device, however
There is a general forum for android here http://forum.xda-developers.com/android/help where you can try to ask to get expert's help.
Good luck
I tried to root my device and it went quite well. Then I tried to flash a custom rom (Darkwolf S7 edge port) on my phone but I ended up in a bootloop where it was stuck on the samsung logo for hours. I tried different stuff to get out of it but nothing worked so I decided to flash the stock rom onto my phone and at the odin status I get "FAIL". And on my device it shows "Volume Size is too big 4620289 < 4718599. And my phone is unusable. I need some help asap to fix it.
XDA Visitor said:
I tried to root my device and it went quite well. Then I tried to flash a custom rom (Darkwolf S7 edge port) on my phone but I ended up in a bootloop where it was stuck on the samsung logo for hours. I tried different stuff to get out of it but nothing worked so I decided to flash the stock rom onto my phone and at the odin status I get "FAIL". And on my device it shows "Volume Size is too big 4620289 < 4718599. And my phone is unusable. I need some help asap to fix it.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please have a look at the Note 3 homepage:
http://forum.xda-developers.com/galaxy-note-3
If you create an XDA account, you can ask the experts for help, here:
http://forum.xda-developers.com/galaxy-note-3/help
Good luck and welcome to XDA!
i was trying to root my samsung galaxy s7 and i tried to flash supersu and my phone rebooted a couple times. then it was just stuck rebooting and I cant get back into android. please help. (im a noob to rooting)
l1me_ said:
i was trying to root my samsung galaxy s7 and i tried to flash supersu and my phone rebooted a couple times. then it was just stuck rebooting and I cant get back into android. please help. (im a noob to rooting)
Click to expand...
Click to collapse
Greetings and welcome to assist. I can see you have already asked your question in the correct place here
https://forum.xda-developers.com/showthread.php?p=71149330#post71149330
and the experts there are guiding you so I'll close this one up
Regards
Sawdoctor