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
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?
Hello,
I'm new to tablets and their operating systems. I was wondering if anyone knew how to root the dopo D7020 tablet. It was gift for my children and I would like speed it up so my kids don't come up to me 5 minutes telling me that it's froze.
Thanks and any help is appreciated,
Jon
Rooting won't fix your problem. A custom rom is needed and it's hard to find these for such tablets.
I'd recommend using a lightweight launcher so you have more free RAM.
Stuck in CWM 5.5.0.4 No ADB DOPO D7020
So I rooted the device no problems , and I used a generic CWM recovery for RK2918 devices, since I thought thats what it's running
Livesuit Shows no Rockchip device , it is now detecting a A10 device and I cannot load a Rockchip driver for the life of me , in the CWM recovery mode.
1. Is this device rockchip or not?
2. I have no control with volume controls can only press power which reboots right back to CWM
3. Is there a proven recovery technique for this issue?
4. Does anyone have a backup <--- I was installing CWM to do this I belive I may have put the wrong on or
5. The factory firmware image <----- Double powertech site does not even list this tablet.
6. Is there a way to get the device out of CWM recovry mode? Yes I have done a hard reset via the reset button still CWM recovery.
Device is a DOPO 7020 it detect under windows as a D7016 though
Im not sure how to get out of this if I could even gain control of the menu up down to apply an update from zip this would be fine. I can work in WIN. MAC, Linux dont matter just need to get it working agin for my kid. Any help wold be appreciated.
protocol2 said:
So I rooted the device no problems , and I used a generic CWM recovery for RK2918 devices, since I thought thats what it's running
Livesuit Shows no Rockchip device , it is now detecting a A10 device and I cannot load a Rockchip driver for the life of me , in the CWM recovery mode.
1. Is this device rockchip or not?
2. I have no control with volume controls can only press power which reboots right back to CWM
3. Is there a proven recovery technique for this issue?
4. Does anyone have a backup <--- I was installing CWM to do this I belive I may have put the wrong on or
5. The factory firmware image <----- Double powertech site does not even list this tablet.
6. Is there a way to get the device out of CWM recovry mode? Yes I have done a hard reset via the reset button still CWM recovery.
Device is a DOPO 7020 it detect under windows as a D7016 though
Im not sure how to get out of this if I could even gain control of the menu up down to apply an update from zip this would be fine. I can work in WIN. MAC, Linux dont matter just need to get it working agin for my kid. Any help wold be appreciated.
Click to expand...
Click to collapse
How did you go about rooting?
No expert but I can suggest ADB...
protocol2 said:
So I rooted the device no problems , and I used a generic CWM recovery for RK2918 devices, since I thought thats what it's running
Livesuit Shows no Rockchip device , it is now detecting a A10 device and I cannot load a Rockchip driver for the life of me , in the CWM recovery mode.
1. Is this device rockchip or not?
2. I have no control with volume controls can only press power which reboots right back to CWM
3. Is there a proven recovery technique for this issue?
4. Does anyone have a backup <--- I was installing CWM to do this I belive I may have put the wrong on or
5. The factory firmware image <----- Double powertech site does not even list this tablet.
6. Is there a way to get the device out of CWM recovry mode? Yes I have done a hard reset via the reset button still CWM recovery.
Device is a DOPO 7020 it detect under windows as a D7016 though
Im not sure how to get out of this if I could even gain control of the menu up down to apply an update from zip this would be fine. I can work in WIN. MAC, Linux dont matter just need to get it working agin for my kid. Any help wold be appreciated.
Click to expand...
Click to collapse
Using windows or linux, please try to boot into CWM (since it only does that I'm sure that's automatically) and then use ADB to push, pull or even restart in bootloader or recover mode if I"m not mistaken. The commands are "adb reboot-bootloader" and "adb reboot recovery" without quotes. This should allow you to work with your phone. Use ADB to reboot into the bootloader (fastboot mode) and then use fastboot to flash whatever you may need. Hope this helps. I spent a lot of time working on my kids Tablet too and ended up in a similiar situation.
-Q
Cheers! Good luck.
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?
now i was looking for how to root my j2 prime because its what i use to login with my vpn then i use a proxy server on it to route all traffic connected to it while its in hotspot mode but it seems proxy servers have their limitations and so im forced to root so i can just hotspot the vpn directly with an app, but after searching i found 3 methods all using superSU which im not comfortable with anymore, all with many steps but in my experice since this phone has got nothing to lose i decided to experiment and boom it worked...
what you need
latest Magsisk - v17.1 at this time of posting
latest SAMSUNG USB DRIVERS
ODIN
and TWRP by
ashyx said:
STEPS
1. BOOT PHONE IN DOWNLAOD MODE (power+vold-down+home)
2. FLASH TWRP in the AP OPTION in ODIN (untick auto reboot;very important) then after flash succeeds
3. Pull out battery and boot to recovery (power+vol-up+home)
4. FLASH MAGISK.zip from your SDCARD (Recovery wont be able to mount internal storage so make sure to put the MAGISK.zip in your SDCARD)
5. Reboot and Hello systemless root
credits to this thread where i was searching for root, includes link to 3 methods but mine is the shortest and easiest
Click to expand...
Click to collapse
I'm unable to start recovery mode. I pull out the battery and after pressing the keys the phone simply goes off. Also I'm unable to enter recovery mode anyway (after turning it off and not flashing anything). That's it, I can't enter stock recovery either.
I tried all button combinations and it just doesn't enter recovery mode.
Never mind, it was probably a faulty button. Pressing with force did the trick. I however employed a bit different path (or perhaps I wrote it down more detailed), which come out more noob like, I'll leave them here for anyone that might use them
Noob, baby steps to root the Samsung Galaxy J2 Prime SM-G532M:
1. Enable developer mode and selected OEM unlocking and USB debug, dunno if it's needed but I did it because in all roots I have seen this is a must.
2. Put the Magisk zip onto a SD card (currently Magisk-v18.0) and put the SD card into the phone. Then I turned off the phone.
3. Turn on the phone into download mode (power+vold-down+home), connect the phone to the PC.
4. Open ODIN and FLASH TWRP file using the AP button (VERY IMPORTANT, uncheck the auto reboot in options, otherwise the recovery goes back to stock I think and the phone will boot into the regular OS, and you'll have to flash TWRP again), wait a few seconds to the flash to finish (odin says PASS! in green).
5. From this screen without touching anything reboot the phone into recovery mode (power+vol-up+home) (just in case press hard the vol+ key). If it boots the phone in regular mode, do steps 2 , 3 and 4 again.
6. FLASH MAGISK.zip from the microSD. When finished wipe Delvik/Cache.
7. Reboot the system. Open the Magisk app (you might have to wait a few seconds for it to appear among on the apps) then press yes when prompted to finish installation as many times (2 times I think). And done, you have your phone rooted.
PD: Magisk can be found here: https://github.com/topjohnwu/Magisk/releases/
As for the TWRP file (twrp_3.1.0-1_sm-g532_5617b.tar), use the one in the link on the OP.
LordBaal19 said:
6. FLASH MAGISK.zip from the microSD. When finished wipe Delvik/Cache.
7. Reboot the system. Open the Magisk app (you might have to wait a few seconds for it to appear among on the apps) then press yes when prompted to finish installation as many times (2 times I think). And done, you have your phone rooted..
Click to expand...
Click to collapse
why am i getting an error? it says
"Updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v17.1.zip' "
can i get some help here?
Good day!
Is disabling dm-verity and force encryption included in the process?
And also, everything works fine but how is that i cannot delete system apps manually? They're returning back after reboot.
Thanks.
Unable to detect the phone -win nor Lin
Hello guys
Something really extrange is happening.
My j2 prime -532G- can't be detected by Windows nor Linux.
The usb is working because it charges the phone, but I can't access the phone at all. I checked all the drivers in Win -google/adb and samsung- and in Linux libmtp/heimdall/etc.
I have tryed different usb -not the original one since i lost it-
Even when i start the download mode, nothing happens.
it there a way to root the phone without a PC? i have tryed also kingroot apk but it is useless.
Thanks
LordBaal19 said:
I'm unable to start recovery mode. I pull out the battery and after pressing the keys the phone simply goes off. Also I'm unable to enter recovery mode anyway (after turning it off and not flashing anything). That's it, I can't enter stock recovery either.
I tried all button combinations and it just doesn't enter recovery mode.
Never mind, it was probably a faulty button. Pressing with force did the trick. I however employed a bit different path (or perhaps I wrote it down more detailed), which come out more noob like, I'll leave them here for anyone that might use them
Noob, baby steps to root the Samsung Galaxy J2 Prime SM-G532M:
1. Enable developer mode and selected OEM unlocking and USB debug, dunno if it's needed but I did it because in all roots I have seen this is a must.
2. Put the Magisk zip onto a SD card (currently Magisk-v18.0) and put the SD card into the phone. Then I turned off the phone.
3. Turn on the phone into download mode (power+vold-down+home), connect the phone to the PC.
4. Open ODIN and FLASH TWRP file using the AP button (VERY IMPORTANT, uncheck the auto reboot in options, otherwise the recovery goes back to stock I think and the phone will boot into the regular OS, and you'll have to flash TWRP again), wait a few seconds to the flash to finish (odin says PASS! in green).
5. From this screen without touching anything reboot the phone into recovery mode (power+vol-up+home) (just in case press hard the vol+ key). If it boots the phone in regular mode, do steps 2 , 3 and 4 again.
6. FLASH MAGISK.zip from the microSD. When finished wipe Delvik/Cache.
7. Reboot the system. Open the Magisk app (you might have to wait a few seconds for it to appear among on the apps) then press yes when prompted to finish installation as many times (2 times I think). And done, you have your phone rooted.
PD: Magisk can be found here: https://github.com/topjohnwu/Magisk/releases/
As for the TWRP file (twrp_3.1.0-1_sm-g532_5617b.tar), use the one in the link on the OP.
Click to expand...
Click to collapse
I can't seem to get this phone to go into recovery after flashing TWRP. It always goes into a normal reboot no matter how hard i press the button combination.
Any idea about how to make it reboot to recovery any other way
BTW I was aable to make it go to TWRP Once but forgot to insert the SD card that time and had to repeat the process again and haven't been able to see that TWRP screen agin
Any ideas
mbalino said:
Win -google/adb and samsung- and in Linux libmtp/heimdall/etc.
Click to expand...
Click to collapse
Hello mbalino I am new to XDA forums
Where did you checked the drivers in the phone or the PC? what drivers are they?
mbalino said:
My j2 prime -532G- can't be detected by Windows nor Linux.
The usb is working because it charges the phone,
Click to expand...
Click to collapse
Did the phone trigger an Autoplay window (to ask you if you want "view files", "import media", etc.)
Did the phone appear in the file explorer (as a media player device?) with storage(s)?
Hi I have tried so many times using the instructions all over the internet that says you have to use power volume up to get into recovery for flash mode but it never works just keeps loading into Android. Am I doing it wrong or is there a video or other way to get to stock recover. need to do this so I can install custom recovery and rom
Thanks
Hardware button recovery.
squigsie said:
Hi I have tried so many times using the instructions all over the internet that says you have to use power volume up to get into recovery for flash mode but it never works just keeps loading into Android. Am I doing it wrong or is there a video or other way to get to stock recover. need to do this so I can install custom recovery and rom
Thanks
Click to expand...
Click to collapse
No you didnt do anything wrong. Some h/phone models do not respond to Vol+/- + Power. Out of the 11 device I owned my latest MTK powered phone do not respond to the hardware button.
But you did not describe your phone completely.
What SoC? Kirin, Exynos or MTK? (I assume it is MTK)
Are you rooted?
Do you want to access customs recovery or stock recovery?
If you are not rooted and on stock recovery, you can only access (for these problematic models) via "fastboot recovery"
command. It is not hard install adb driver on your PC, and your device driver. search for "fastboot adb" installer from the web. It is less than 1 Mb size and your USB cable from PC to device. End users cant do much when facing this problem.
If you are rooted and on customs recovery all you need to do is to install "Rebooter" from Playstore and click the rebooter from Android homescreen to get into TWRP recovery. (this doesnt work if you dont have root and on stock recovery).
I rooted , install customs recovery, by using fastboot and my device ROM flasher everything works well for me. And I enter TWRP via "Rebooter" and clear my dalvik and cache. Try it.