Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !
Sanjuujosephh said:
Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !
Click to expand...
Click to collapse
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.
Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !
Sanjuujosephh said:
Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !
Click to expand...
Click to collapse
After I flash the firmware it automatically goes to a recovery screen, a progress bar gets filled then opens the Android system normally. After that when I try to go to recovery mode again it goes back to download mode again with the error text "Could not do normal boot".
Problem.... Fixed? .___.
Well for some reason on the third (and thought it's hopeless) attempt to flash the firmware again, I managed to open recovery mode after it, I was kissing the Reset Factory button.
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.
citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
---------- Post added at 06:49 PM ---------- Previous post was at 06:46 PM ----------
citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
اقرأ الموضوع اللي كتبته خصوصي للجراند 2 بنظام كت كات
رسالة Could not do normal boot طلعت بسبب استخدام ريكفري قديم ع الكت كات
الموضوع الجديد فيه ريكفري جديد.
Help me plzz
hey.... wht did u do evn i m stuck there??? plzzz help..got KitKat on my Grand 2 got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot"
citBabY said:
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.
Click to expand...
Click to collapse
i think you should reset your phone
and if it doesn't work then try another country's rom
thankyou
hey bro, I have problem same to u..
Bro...I have same problem..?? I cant go to recovery mode showing Could not boot normally...etc..This happened after I tried CWM using Odin ..I always go download mood and...when i pressed factory reset button ..it didnt rest and go download mode again...plz help me bro...thanks
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.[/QUOTE]
Bro, please don't use king root or any other root.
Solution
Please download the stock firmware and then go to download mode flash the stock firmware and root your phone again. Then recovery mode will work.
Thank you
Sorry for errors.
Sent from my SM-G900H using XDA-Developers mobile app
I'm a newbie but I fixed mine...
I've had this happen and it is frustrating to say the least. But I fixed it though. This is what I did: CAVEAT: Please read up all the FAQs, search the right firmware for your phone and the appropriate versions, KitKat vs Jelly Bean, etc. otherwise if your phone is bricked...don't blame me.
I have a 2nd-hand Galaxy Grand 2 and so warranty issues are a non-issue for me. All the files I've found were downloaded on this forum. I flashed ROM with my PC with Odin program installed.
I used Odin3 (v.3.07). (To install Odin program search the this forum). I also reflashed the recovery TWRP file "twrp_ms013g-build2.tar" Including the firmware G7102 Stock. My file was: G7102DDUBOB1_G7102ODDBOB1_G7102DDUBNK1_HOME.tar.md5. (Search for it.) Oh, you may want this file: CF-Auto-Root-ms013g-ms013gxx-smg7102.tar.md5 which may help with rooting your phone if you haven't already done so.
I did the Recovery 3-button Samsung phone groping procedure (you know what I'm talking about Volume Up/Down button + power + home button)... but to no avail...I keep getting that boot loop (Unable to normal boot...etc). You know that stupid "Downloading" Android logo (with the blue worded script on the top left-hand corner) with message ..."Downloading ...Do not unplug source..." Well, I plugged the USB cable to the phone to my computer and Odin program recognized it (it'll read "Added"). The phone didn't give any indications that it was doing anything. Btw, if your Odin program doesn't recognize your device then you should find out why it doesn't. If it recognized it before and you flashed with the Odin program before, I don't see why it won't recognize it now? Some say it's the USB cable but I can't logically accept that kind of superstitious BS. Come on, it's a copper/aluminum wire cable wrapped in pvc -- not a script. A cable is a cable is a cable. If it worked before, it'll work again unless it's cut inside the pvc tubing. You can use a digital multimeter to easily test that for continuity (albeit with really tiny leads to be able to connect to the mini USB side). Anyways, if your Odin program won't recognize your phone, maybe try using a lower version, or re-installing, or another similar type of program that will work. I'm assuming you did install the Samsung USB driver for your PC (e.g. mine is -v1.5.61.0 -search for your appropriate version) so that your computer will recognize your phone when cable is hooked up.
DON'T FORGET TO have the "Auto Reboot" and "F. Reset Time" boxes checked on the Odin program. Then select PAD button and browse for your TWRP file (above) and hit "Start." The Odin will flash it and you'll see a light blue bar under the Android logo (on your phone) that will go from left to right and when finished....whooooohooo the phone auto restarts back to your last OS state without losing any info on the phone. At least it worked for me. Hope that helps. Sorry for the long post.
hi i am in official android 4.3 on my g7102 and i wanna install a recovery file. but every recovery file i tested dosnt work on android 4.3. can you help me?
If u have knox bootloader do not try to downgrade just get kitkat one and in odin check phone bootloader update
Seems like u really guys screwed up the recovery. Somehow on my first try of flashing a zip file (recovery), i got stuck on download mode and wont boot normally. When I fixed the problem, the phone boots normally but the recovery is the only problem I got. I fixed this problem for about 10 days ago, all i did was to reflash the recovery again, orrr flash other version of the recovery (if the downloaded recovery version didnt work) or flash other recovery if the another recovery didnt work. Make sure the recovery is working on the version of you're phone (jelly, kk, lollipop, marshmallow or nougat) and working also on the model version.
I know this is an old thread but I hope this reply helped
hello guys.
first i will start with the beginning. i have a grand 2 duos g7102 phone. i rooted the phone and installed CWM recovery in order to flash custom rom CM 12.1 Lollipop 5.1.1 everything was running well until i upgraded to CM 14 Nougat 7.0 COSMO, i didn't like it and when i wanted to get in recovery mode again it stopped working. Now i can't boot in recovery mode at all. Not showing CWM recovery like before only recovery booting for few second and after that the dead android and No command and there is more writing down the screen like Supported API: 3 but it is hard to read because the screen is always flashing.
i someone faced this problem before please help !!!
thanks in advance
Guys guys i had the same problem with my grand 2 7102.
I rooted my phone and flashed a recovery via odin.
But as i press the button combos it says. Could not do normal boot.
So, i found a solution for it.
Downloaded flashify for play store.
Extracted img. File of twrp recovery provided in the grand 2 thread 😬,
Flashed it with flashify
And guess what i was in the recovery and after that no problem came with the recovery flashing 🙂
If you guys keep having problems with no-pc flashing, try the pc flashing cause this is the better way of flashing other than apps.
I had the could not do normal boot problem
Do this ...
Google cwm test 4.4 ms013g.tar and download it
Put it in PA or PDA uncheck autoreboot keep freset time checked
Flash the file then when you get pass message in odin , remove battery and reinsert it and go to recovery mode directly with vol up + power button.
NOTE : Don't try to normal boot to system
Short version: Phone is boot looping at LG logo and when I try to volDown+power into recovery it gets to the factory reset prompt and I press power twice but nothing ever loads and the backlight just stays on. I'm guessing I no longer have a functioning download mode either because of the way these flashable bootstack zips we've been using on the VS980 ROMs mention that they disable download mode, so I probably can't use LG Flash Tool either. Bricked?
I had been on CloudyRom 1.3. I switched back to xdabbeb's VS980 ROM, the newest version with the 25B bootstack. As many people ran in to, for some reason after coming off of Cloudy, KnockOn doesn't work on other ROMs. I had tried to do this hidden menu trick to update the touch screen firmware which some people reported got the KnockOn working again. Long story short I was having trouble getting the hidden menu trick working while on the xdabbeb ROM, I went back to Cloudy ROM and tried to do it but that didn't fix it either. I saw people having success by going back to a purely stock ROM and doing the hidden menu trick from there.
Here is where I probably messed up, I had a backup from April of this year that I didn't have labelled/named well but I was certain it matched up with the last time I had probably been on a purely stock ROM when the VS980 finally got KK earlier this year, a backup I had made for the convenience of ever having to return to stock. I tried to restore this and that's where the trouble happened. At the time I figured worst case scenario would be that the baseband wouldn't match up and I wouldn't get a signal, but in hindsight I'm guessing it wasn't safe to try to restore this after updating to different bootstacks. Original KitKat rom was 24a I believe but I had just recently updated to 25B to use the newest xdabbeb ROM.
I saw a small ray of hope when I calmed down enough to remember the voldown+power sequence to get into recovery, but after reaching the factory reset prompt and pressing power twice to continue, nothing ever loads and the backlight just stays on, like my recovery is gone now too I guess.
And in a comedy of errors I'm guessing I no longer have a download mode that would allow me to use the LG Flash Tool through PC because these flashable bootstack files always mention that they disable download mode and I never worried about restoring it.
So, bootloop, can't get into recovery, probably can't get into download mode to work with LG Flash Tool.
Screwed? :crying: :crying: :crying:
Yeah, volUP + plug into PC just gets me fastboot mode.
Don't really understand why my recovery is gone, thought the button sequence to get back into recovery was the safety net to this entire thing and why I wasn't too worried. Was running TWRP.
I'm at the mercy of checking the internet when I have access to another computer because my phone was also my internet access on my home PC. Hoping someone can help. : (
Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Which TWRP are you flashing? I recommend using version 3.0.1-0 from here, as version 3.0.2-0 has been known to have some problems in the past.
https://forum.xda-developers.com/showthread.php?p=66266209
Maybe try making sure Allow OEM unlock is switched on in Settings-->Developer Options before you flash it too. Obviously make sure your device is being recognized properly by ODIN as well. You should see a little blue box light up in the top left of the ODIN window when you connect the device. Make sure you're flashing it in the AP slot and no other. Also, make sure you have the current Samsung drivers installed for the SM-G360T1 from here:
http://www.samsung.com/us/support/owners/product/galaxy-core-prime-metro-pcs
Hope this helps! Have a good day.
I've honestly tried just about every version here and on the website. Started with 2.8.7 as a ROM I was interested in recommended it, however I am willing to use any that will work at this point I really only wanted my device rooted for one simple task.
My drivers appear up to date -
USB debugging and Boot unlock are both enabled -
Odin shows PASS and reboots my phone on flash -
Everything seems like it's working right, but it's not replacing my recovery. When I reboot it just takes me back to the warning/download screen. Is it possible I might need to downgrade to the original Lollipop that came with this phone first?
Edit -> I tried TrapKernel as well, that disabled my wifi entirely (on/off button would not stay in on position)
Edit -> Tried downgrading to the original Lollipop that came with my phone and it reboots itself as soon as it gets in to Android. Gonna try flashing it again before returning to current Android. :/
OutlawStarX said:
Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Click to expand...
Click to collapse
Pull out the battery after the phone comes up on the boot logo when the flash is complete. After that put it back in and press VOL UP + HOME + POWER and it should take you to the TWRP recovery. You do this because the phone will recognize that is not a original recovery, so it replaces with the original one. Make sure to put a custom rom with root in it so it doesn’t replace the recovery again.
it's been a week that i'm searching for a solution and i couldn't find anything and even any thread that could solve my situation probably becouse it's specific and with various weird problems.
frist of all i have a rooted rom for the SM-G531FX (android 5.1.1) and i can't remember wich model was before rooting it but i was a very similar code changing probably from G531FX to G530F?. but everything was ok i rootend my phone with no problem.
the real problem started like this:
i've changed the dpi of my phone using Root Essential changing it from 240 to 180.
immediatly after changing it the screen became with only the default background and nothing else, no icons, no notification bars, nothing, just a popup that said "unfortunately settings has stopped working".
the only thing i could do was swithing off the phone, (obviously the "reset" "switchoff" "airplane mode" was at loer dpi)
restarting it changed nothing and the phone still remain with the background with only the possbility of swithing it off.
the volume popup won't display but i could tell that the phone still works perfectly under the display becouse i recived messages (from telegram and whatsapp not normal messages becouse i couldn't use the display so i can't put the pin code to enter the phone so i removed the simcard) and also the volume controllers works.
so i decided to searching how to change the dpi from the pc.
i found that Adb could do it so i plugged in but unfortunately not worked, the phone remained in "unauthorized" state and i could not change the build.prop.
i started panic a bit so i wiped the cache from recovery mod.
After doing it i realized that i did a big mistake, now i can't connect usb in debug mod becouse of that.
i decided to reflash the rom i had use to rooting it thinking that could solve the problem.
midflashing odin had an error and the rom din't finished, it was stuck and i unplugged the phone from the pc and obviously the phone gave me an error in download mod (don't remember the error but was the one talking about Kies to solving the problem)
panic increasing couse i never had those types of problems.
i decided to flash the rom in Bootloader instead of AP in odin, that solved the problem of the error (later i found out that even in AP would have solved the problem)
i thought that wiping everything could have been the solution at that point so i restarted in recovery the phone but i could not access it probably becouse the previous BL flash, the phone stay with the Galaxy grand prime logo and on top in red "recovery is not seandroid enforcing". well done me
so i thought about reflashing a stock rom and found a rom w ww. sam mobile. co m / firmwares/galaxy-grand-prime/SM-G530FZ/WIN/download/G530FZXXS1BQC2/131851/ that pretty much fits my phone as i remembered the phone model, it was also an italian rom (i'm from italy) and with my very same phone company (WIND).
and finally odin fail flashing the rom so i remain with a phone with no acces to recovery, that boots normally but can't use the display becouse of just a value.
hope you could help me
thanks
Try to flash stock ROM of your phone with AP on Odin and the problem will be gone
Sent from my Redmi Note 3 using Tapatalk
Messed up everything first of all remove backcover and find what exact model it is..and find if you can go to download mod
Hey, so I have had my phone rooted for a long time. I have a Galaxy S5 6.0.1 Marshmallow.
I decided I wanted to get Framework installed so I downloaded the right files and flashed it in TWRP.
My phone took way longer than 10 min to reboot into system so I thought I was stuck in a bootloop and decided to run my phone through TWRP again.
I tried rebooting but that didn't work. I have my phone's backup saved onto a micro SD so I did a factory reset and then tried rebooting.
I got past the rebooting logo and actually got to my lock screen where it asks for my password.
From there, I've been getting spammed with 3 different messages, one saying that IMS service is down, com.sec.vsimservice is down, and WfcService is down.
After I press ok to all 3 of the messages, my phone is still in the lock screen asking for my password but the phone doesn't recognize that im touching the screen to type. After letting the phone stay like that for a few minutes, the lock screen that asks for my password goes away and all I can see is my wallpaper background (no notification panel either) but now the phone recognizes me touching the screen ( I know that because the LED lights up for the windows button and back button )
So basically I decided to go into TWRP and flash my recovery that I had saved on the microSD.
After that didn't work, I've just been going through a series of factory resetting my phone and wiping Dalvik files and then flashing my recovery. My phone is getting unrealistically hot too.
Btw I never downloaded the Exposed Uninstaller from the forum so I tried downloading it onto my pc and then sending the file over to my phone through download mode using Odin so that I could flash the uninstaller through my TWRP but that didn't work because the PDA in Odin does not recognize the uninstaller file.
Please, I really need help and thanks to anyone who tries, it would mean a lot if someone could figure out what I can do. Thanks.
Since you've tried restoring your backup and everything seems to have failed (it sucks, I know) you should try to install a completely stock firmware which you can download from here: http://live.samsung-updates.com/index.php?device=SM-G900I Just make sure you select your exact phone model from the dropdown menu at the top right side as you didn't mentioned which of the 40 S5s you have lol. And after you flash stock firmware and successfully boot up try to restore your backup. If it's still bugged - flash stock again and start off fresh. Let me know how it turns out. I'll help with installing xposed later as well, first let's get your phone running again