Related
Hi! Sorry about this rude way but I am in an emergency situation.
I have a ZTE RACER with Android 2.2.2 (official ZTE Frimware) which it keeps rebooting at the splash screen.
Before that, I did a root using SuperOneClick 2.3.3 by Shortfuse. After following the instructions (USB debug, plug-in, root) I've rebooted the phone normally (NOT with adb), and when it got after the ZTE Logo (the first one, not the splash screen and not the Android logo). The animation goes a little and freezes for a few seconds, then restarts automaticly (but not entirely, just repeats the splash screen) and reboot. Rance and repeat! I tried to unroot, but the app hangs, restarting with adb and nothing happens. adb restart command doesn't help that much. What should I do to fix it?
Additional info:
Phone recives adb commands normally.
Possibly Superuser app was leftover before unrooting and rooting again (yes I already did root, but superuser stoped working properly afer app and su files update)
Can't go to FTM Mode, ROM Manager gave me a broken CWM.
Unsure If I can install CWM manually since SD doesn't seem to get mounted.
Phone Info:
ZTE-RACER
Android 2.2.2 (FROYO_P2XXGV_V1.0.0_B2)
CWM 5.0.x (Installed with ROM Manager. Broken.)
Carrier: GR COSMOTE (that's unknown carrier for you.)
Thanks for any help.
P.S.: Does anyone here is greek and has a ZTE RACER with the official 2.2 upgrade? I need the FTM Mode.
From what you have said, it seems like you are in a soft brick not a hard one. This means that there is chance of recovery but you have to be very careful.
You weren't rude so don't worry bout that.
You may want to try a hard reset.
Now that we have identified the problem, you have the ability to try and find it yourself at least.
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Deftone said:
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Click to expand...
Click to collapse
For the first one, I don't know how since the only way I had was to reflash it with the 1-Click Update (I did that on my ZTE MF636 3G Modem).
About the second, you mean that I must use the adb command, or I just hold it down without connecting it (I am newbie to the Android), but thanks for the help. I'll keep you posted for the results.
(NOTE: 1-click update is the offline frimware updater made by ZTE.)
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
rivas1981 said:
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
Click to expand...
Click to collapse
Logo appears but... I still don't get it.
Was that for CWM? Or for the phone?
CWM is broken by the ROM Manager. After installing, I tried to get in, but it got frozen to the Android logo + the red led is on. (Temporal brick).
Should I flash a working CWM to the phone?
Anyone?
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
post-mortem said:
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
a) I am not sure if it works but for sure it doesn't come from ROM Manager.
b)Where do I find fastboot and what's the command?
Anyone, please?
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
post-mortem said:
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
This command doesn't work. Is it fastboot flash recovery [image_file]?
Will somebody please help me out!
Here is the thread for Android Flash Recovery:
http://forum.xda-developers.com/showthread.php?t=1827723
Doesn't work! It does detect it, but it can't flash it (on normal boot only. On recovery/bootloader it just getting bricked). Any other options? Or I have to send it for reflashing?
Hi guys,I am new here
Today I flashed my vision with custom rom (2.3.7+root) from a Russian forum.Everything was OK,then I installed the Beats app and restarted.Now the phone is constantly rebooting.How can I fix it? ?Please help
PS: I try to get in recovery menu,but I cant
do you have backup? if you have
try to get recovery via adb
type ' adb reboot recovery '
and then restore
I dont have backup.I managed to get into recovery and made factory defaults, but nothing.It keeps restarting.I uploaded the rom to my sd card.And I saw "download rom from sd card" in the recovery menu.If I click it,would it flash the rom?
And another thing is that i cant remove the battery and that is why it is so hard to get into recovery
PS How it is possible to get into recovery mode when the phone is constantly restarting and I cant remove the battery?
Infoto said:
I dont have backup.I managed to get into recovery and made factory defaults, but nothing.It keeps restarting.I uploaded the rom to my sd card.And I saw "download rom from sd card" in the recovery menu.If I click it,would it flash the rom?
And another thing is that i cant remove the battery and that is why it is so hard to get into recovery
PS How it is possible to get into recovery mode when the phone is constantly restarting and I cant remove the battery?
Click to expand...
Click to collapse
use adb to get recovery, when the phone boots, quickly type 'adb reboot recovery'
Huawei U8850 keeps rebooting
Mine already brick...
Infoto said:
Hi guys,I am new here
Today I flashed my vision with custom rom (2.3.7+root) from a Russian forum.Everything was OK,then I installed the Beats app and restarted.Now the phone is constantly rebooting.How can I fix it? ?Please help
PS: I try to get in recovery menu,but I cant
Click to expand...
Click to collapse
1. Hold the Vol (+) and Power button and hold it until the screen is black. Count to 10 seconds. (Hard reset)
2. Remove a second finger from the Power button and return back to Power button (Quickly release and immediately press it back.) Huawei logo should appear just for a second and then it will turn off. Count to 10 seconds.
3. Remove your fingers and wait for the phone to turn on again, if not then good, if on then do it all over again.
4. Enter recovery mode
5. Flash it back using SUT L3.
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
I have same PROBLEM, anny help?
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
rspilot1 said:
Had a problem. Hope someone with experience can give me a few answers.
Nave new t-mobile Note 3, SM-N900T. Stock 4.4.2 KitKat Touchwiz rooted.
Rooted to enable SDFix to use SD card as I want to use it.
Everything great! No problems.
Thought it would be wise to have a Nanoid backup.
Opened Rom Manager and made One change in prefrences. I set it for external SD card storage. (mistake?)
Went to 'Backup current Rom' in Rom manager, started it and it started to reboot. Shut down and restarted in a 'Recovery' boot loop??
No matter what I did, Tried holding power, up volume and home button, nothing. Boot loop continued. Removed battery, waited, as soon as I re-installed battery it instantly went back into recovery boot loop.
I don't know what I did, I kept removing battery and trying again and again and all of a sudden, it booted up back to KitKat and now everything is working great again. No problem on any standard reboot.
What happened? I have used this same set up on my S3 and never had a problem.
I would like to backup the current setup for any future problems. But now, I'm afraid to even try.
I removed Rom Manager and re-installed. Made sure that the storage location was reset to internal and it should be OK??
What did I do when I got out of the Recovery boot loop??
So, afraid to try again. Don't want the boot loop again.
Click to expand...
Click to collapse
Hi. What recovery are you using?
If you haven't installed a custom recovery, then that explains your issue. Basically, the app scheduled a custom recovery script which kept failing in the stock recovery. You should normally be able to reboot into the system holding the power button, thus skipping going to recovery. This also resets the recovery script so everything is back to normal.
Nandroid is normally only possible using a custom recovery like TWRP or CWM.
I saw that you might be able to perform a Nandroid without restarting the phone (so without a custom recovery) using this app: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en
I have never tried it. Looks promising though.
But please note that you won't be able to restore the backup without a custom recovery.
EDIT: If you do have a custom recovery, why not boot in recovery mode and make the backup from there?
Cheers
Recovery Boot Loop Problem
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
rspilot1 said:
I have CWM installed. Setup thru Rom Manager as I have done before on other phones.
Tried it again, same thing. Over and over. Constant reboot. Dosen't matter if I hold the power button or try different ways, same thing.
It says: Recovery booting
Recovery is not seandroid enforcing
Set warranty bit:recovery
If I remove battery and wait a couple of minutes, I can install battery and it dosen't start till I hold power button.
So I held volume down, home button and power button and booted into download mode. From there I cancelled and it rebooted normally.
Everything I've read on boot loops always say 'boot into recovery'. I only wish I could. That's the bootloop.
Any idea on what's wrong?
Thank you for your time and trouble.
Click to expand...
Click to collapse
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
Have you tried booting directly into recovery?
So just shut off your phone and then open it by holding volume up + home + power. It should boot into recovery. If it doesn't, I recommend installing cwm or TWRP using Odin instead of Rom manager.
Might be a problem with your current recovery.
Sent from my GT-I9505
Click to expand...
Click to collapse
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
rspilot1 said:
Yes, I tried. Does the same thing.
I've never used Odin. All the info I've read mentioned downloading USB drivers and using different .tar files. Checking this and that.
Nothing I've ever done.
No experience with it.
Never had a reason before to use it.
Every instruction website I've read all seem to be different.
I'm gonna have to find out, huh? lol
I've got Odin on my computer, and have the CWM 6 zipped file.
Will do some research.
Thanks
Click to expand...
Click to collapse
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
No problem.
A few tips with odin:
-If you have Kies installed, you don't need to install other drivers.
-The file you flash with Odin should have tar or tar.md5 extension
-you have to activate USB debugging from developer options.
-boot your phone into download mode
-run Odin as administrator
-connect your phone. you should see the text Added in Odin. If don't see it, you need drivers.
-you should make sure only auto reboot and f. Reset time are checked
-you should put the file in Pda or Ap(if using latest version)
Click start and wait until it finishes. It will restart itself if you checked auto reboot.
That's about it. It's very safe and easy to use.
Watch some videos on YouTube. You will definitely find some.
Cheers
Sent from my GT-I9505
Click to expand...
Click to collapse
Thank you, that answered some questions.
you've been a great help.
Recovery Boot Loop Problem
rspilot1 said:
Thank you, that answered some questions.
you've been a great help.
Click to expand...
Click to collapse
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
rspilot1 said:
Update: The install of CWM with Odin seemed to be successful. Still have same problem.
I believe the problem must be somewhere else.
Something is stopping the recovery boot. More research ahead.
When I find out more, will post here and give update.
Click to expand...
Click to collapse
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Recovery Boot Loop Problem
andreiav said:
Strange. You could try TWRP instead of CWM. I use TWRP and really like it:
Here is the download link for your device: http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
This is the Odin flashable recovery.
Here is TWRP page: http://teamw.in/project/twrp2/
EDIT: One more thing. Are these the exact steps you are following when booting into recovery?
"To access recovery mode on your Note 3, turn off the device and press Volume Up+Home+Power buttons at the same time for about 4-6 seconds. When the screen lights up and you see the Samsung logo, release the Power button but keep Volume Up+Home keys pressed until you see the recovery menu screen"
Cheers
Click to expand...
Click to collapse
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Recovery Boot Loop Problem
rspilot1 said:
Yes, if I use the buttons, the download mode comes up saying 'Boot failed'. That's holding the vol. button 'up'. If I hold vol. down, it loads download mode correctly.
If I try to enter recovery thru Rom Manager, Recovery tries to start and the boot loop starts. ??
I may try TWRP. I've heard a lot about it.
Thanks for the links.
Click to expand...
Click to collapse
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
rspilot1 said:
Is changing over to TWRP as simple as installing CWM on Odin??
Just install and try?
Click to expand...
Click to collapse
Yep. 5 minutes process at most
Sent from my GT-I9505
Recovery Boot Loop Problem
andreiav said:
Yep. 5 minutes process at most
Sent from my GT-I9505
Click to expand...
Click to collapse
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
rspilot1 said:
Success!! TWRP works!!
Installed with Odin and it started up fine. Backed up system on my Ext. SD card and rebooted back to OS.
Perfect!
Don't know what happened to CWM but problem is solved thanks to your help.
If your ever in Winter Haven, Fl area, I'll buy you a steak dinner.
Thank you.
Click to expand...
Click to collapse
Awesome! Really glad it worked.
Cheers!
Sent from my GT-I9505
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
When i boot or reboot my rooted my Samsung galaxy grand prime g530h it directly enters in recovery mode , WHY ?
Due to this problem my mobile does not show battery percentage while charging switched off mobile.
Even when i have not installed any rom , why does this problem occur ?
The only thing i did was just rooted my mobile using odin .
But , I do have custom recovery CWN
Why does it boot or reboot in recovery mode ?
What should i do to solve it ?
Need an quick answer .
Depends on the situation on why it boots to recovery. Probably would need more information. Do you have a custom recovery and if so what one? What were you doing before this behavior came into play. Please give as much detail as possible and I might be able to help you. Or someone else can.
AcidicTyranny said:
Depends on the situation on why it boots to recovery. Probably would need more information. Do you have a custom recovery and if so what one? What were you doing before this behavior came into play. Please give as much detail as possible and I might be able to help you. Or someone else can.
Click to expand...
Click to collapse
I just rooted my mobile using odin and Yes, i do have custom recovery CWN
Please help me with this.
Iqrama Vasta said:
I just rooted my mobile using odin and No, i do not have custom recovery or rom.
Please help me with this.
Click to expand...
Click to collapse
Wow. Sounds to me in my opinion that u soft bricked your device. But have no fear. Samsung devices are virtually impossible to perm brick as long as you operate Odin correctly. First thing your going to have to do is find an custom recovery to put on the device. In my opinion as soon you rooted you should of done it because people do make mistakes.
I do not own a Samsung device personaly my wife does but she won't let me touch it LMAO. Try searching on Xda for Samsung galaxy grand prime g530h softbrick
I apologize for a late reply.
Try this credit goes to owner.
http://forum.xda-developers.com/grand-prime/general/guide-flashing-stock-rom-t3039167
correction
Iqrama Vasta said:
I just rooted my mobile using odin and No, i do not have custom recovery or rom.
Please help me with this.
Click to expand...
Click to collapse
I do have custom recovery which by mistake I mentioned I didn't have . But I didn't have installed any rom.
AcidicTyranny said:
Wow. Sounds to me in my opinion that u soft bricked your device. But have no fear. Samsung devices are virtually impossible to perm brick as long as you operate Odin correctly. First thing your going to have to do is find an custom recovery to put on the device. In my opinion as soon you rooted you should of done it because people do make mistakes.
I do not own a Samsung device personaly my wife does but she won't let me touch it LMAO. Try searching on Xda for Samsung galaxy grand prime g530h softbrick
I apologize for a late reply.
Try this credit goes to owner.
http://forum.xda-developers.com/grand-prime/general/guide-flashing-stock-rom-t3039167
Click to expand...
Click to collapse
I do have custom recovery CWN
Need a quick reply
Iqrama Vasta said:
Need a quick reply
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here