Phone Not booting after build.prop changed - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I have Samsung Galaxy s3 ATT rooted - clockworld mod v-6.0.1.2. I was trying to install google wallet.
One of instructions was to change the following in the build.prop file.
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
I changed it. Installed custome google wallet. Reboot my phone and it gets stuck in the samsung logo, and then the screen blanks out.
What do I do?
Thanks
:crying:

Restore the cwm backup you should've made before editing the file.
Sent from my Motorola DynaTAC 8000X

mitchdickson said:
Restore the cwm backup you should've made before editing the file.
Sent from my Motorola DynaTAC 8000X
Click to expand...
Click to collapse
Unfortunately the backup I had done was a long time ago. And I had deleted the backup.

pkirangi said:
Unfortunately the backup I had done was a long time ago. And I had deleted the backup.
Click to expand...
Click to collapse
I'm thinking you need to find the stock at&t Rom put your phone in download mode and flash through Odin.
Sent from my SGH-I747M using xda premium

kojobaafi said:
I'm thinking you need to find the stock at&t Rom put your phone in download mode and flash through Odin.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Thanks. Where would I get the stock ROM?

pkirangi said:
Thanks. Where would I get the stock ROM?
Click to expand...
Click to collapse
I was able to download the boot-stock-att-sgh-i747.tar and flashed it using ODIN.
But still the same affect. After the samsung log, screen blanks out.
Thanks

pkirangi said:
I have Samsung Galaxy s3 ATT rooted - clockworld mod v-6.0.1.2. I was trying to install google wallet.
One of instructions was to change the following in the build.prop file.
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
I changed it. Installed custome google wallet. Reboot my phone and it gets stuck in the samsung logo, and then the screen blanks out.
What do I do?
Thanks
:crying:
Click to expand...
Click to collapse
Are you sure you didn't accidentally delete it? I've booted a bunch of times with wrong build prop info but I doubt phone would be boot if build prop didn't exist
Sent from my Nexus 7 using Tapatalk 2

mobilehavoc said:
Are you sure you didn't accidentally delete it? I've booted a bunch of times with wrong build prop info but I doubt phone would be boot if build prop didn't exist
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I dont think I have deleted it. But how do I verify that..?

Go here... http://forum.xda-developers.com/showthread.php?t=1927198
This will tell you how to fix your build.prop so that your phone will boot again

ibanezbass said:
Go here... http://forum.xda-developers.com/showthread.php?t=1927198
This will tell you how to fix your build.prop so that your phone will boot again
Click to expand...
Click to collapse
Thanks I did try it. I am getting another issue. When I try the "adb shell" command as pointed by thread above - it throws a error - device not found. I have installed my drivers multiple times - but does not seem to be helping. when I connect the phone to the laptop - it is in clockworld recovery mode with the initial set of options.

That sounds all correct. Go back into the SDK manager and under extras there are a few drivers. Check and install those. Try it again.
If that doesn't work, I'll send you the necessary drivers as soon as I get a chance.
Sent from my Galaxy SIII using xda app-developers app

ibanezbass said:
That sounds all correct. Go back into the SDK manager and under extras there are a few drivers. Check and install those. Try it again.
If that doesn't work, I'll send you the necessary drivers as soon as I get a chance.
Sent from my Galaxy SIII using xda app-developers app
Click to expand...
Click to collapse
Thanks ibanezbass. From the extras I downloaded Google USB drivers/Web drivers. But still no avail. I have the latest drivers from ATT downloaded. But for some reason, the phone wont recognized when I do the "adb shell" .

pkirangi said:
Thanks ibanezbass. From the extras I downloaded Google USB drivers/Web drivers. But still no avail. I have the latest drivers from ATT downloaded. But for some reason, the phone wont recognized when I do the "adb shell" .
Click to expand...
Click to collapse
I was able to flash my SG3 with stock ROM using ODIN in download mode. So back in shape. Thanks for everybodies suggestion on this.
As a bonus, AT&T had a RMA and were ready to exchange it for a new phone, which I am declining now.

Ah, I'm sorry to hear that you had to use ODIN and wipe all your data. I solved your driver problem. I apologize about the length of time it took. If you ever need to fix the build.prop again, I've updated my OP to include the driver section. Happy modding!
ibanezbass

ibanezbass said:
Ah, I'm sorry to hear that you had to use ODIN and wipe all your data. I solved your driver problem. I apologize about the length of time it took. If you ever need to fix the build.prop again, I've updated my OP to include the driver section. Happy modding!
ibanezbass
Click to expand...
Click to collapse
No Worries. Thanks for your help.

got a major problem
Hi guys I have yet another crazy issue I am faced with
My Samsung galaxy tab p3110 model has just got the black screen of death after having replaced build.Prop file however I did create a backup of the build. Prop file only its inside the root folder of the tablet at stake. I only seem to have access to Odin mode and I need a way of moving the original built.Prop file back in its place. Does anyone here have any ideas of how I may go about doing this without risking screwing up my tablet further
Any help is greatly appreciated

Gloftking said:
Hi guys I have yet another crazy issue I am faced with
My Samsung galaxy tab p3110 model has just got the black screen of death after having replaced build.Prop file however I did create a backup of the build. Prop file only its inside the root folder of the tablet at stake. I only seem to have access to Odin mode and I need a way of moving the original built.Prop file back in its place. Does anyone here have any ideas of how I may go about doing this without risking screwing up my tablet further
Any help is greatly appreciated
Click to expand...
Click to collapse
You're in the i747/i747m Galaxy S3 forum, so use anything you find here with care. You might want to consult the Galaxy Tab forum for more device specific advice; however, fixing a build.prop brick should be a pretty generic procedure for an android device.
Here is a guide for fixing build.prop errors using adb. You'll probably have to track down different drivers than the ones linked to that thread for your device unless they happen to be generic Samsung drivers. Here's a minimal adb installer so you don't have to mess with the whole Android SDK, just to use one tiny tool
If you have a custom recovery or wouldn't mind using Odin to install one (again, consult your device's forum for specific issues - this may or may not be safe depending on your bootloader), you could just use the file tools built into TWRP or Aroma file manager to replace your modified build.prop with your backup. Be sure to set permissions to 644 after moving the file or you might still be bricked. This might be easier than getting adb working or it might not, depends on your comfort level with Odin and how tricky your device is to mod safely. I see custom ROMs in the Galaxy Tab forum, so it definitely can be done.

Slightly confused
Thanks for your quick response
However I am still a bit confused. Does flashing TWRP recovery through odin mean that all the data and apps currently installed on the tablet will be wiped

Gloftking said:
Thanks for your quick response
However I am still a bit confused. Does flashing TWRP recovery through odin mean that all the data and apps currently installed on the tablet will be wiped
Click to expand...
Click to collapse
Your data and apps will not be affected by flashing TWRP; that Odin package will just be a recovery, not a full firmware update like they are a lot of the time. It will just replace your stock recovery with a custom recovery that has more functionality.
TWRP basically gives you a mini operating system on your phone for creating backups or flashing ROMs. TWRP also has some file tools in its Advanced tab you could use to copy your build.prop backup to /system and set the permissions, so you should be able to use it to fix your soft brick. It is independent of your ROM, so it will unaffected by your main system's build.prop error. There should be a hardware key combo you hold with the tablet off to boot into recovery. A lot of the time its vol up + power (i747 has a physical home button and recovery boot is vol up + home + power).

Thanks
jason2678 said:
Your data and apps will not be affected by flashing TWRP; that Odin package will just be a recovery, not a full firmware update like they are a lot of the time. It will just replace your stock recovery with a custom recovery that has more functionality.
TWRP basically gives you a mini operating system on your phone for creating backups or flashing ROMs. TWRP also has some file tools in its Advanced tab you could use to copy your build.prop backup to /system and set the permissions, so you should be able to use it to fix your soft brick. It is independent of your ROM, so it will unaffected by your main system's build.prop error. There should be a hardware key combo you hold with the tablet off to boot into recovery. A lot of the time its vol up + power (i747 has a physical home button and recovery boot is vol up + home + power).
Click to expand...
Click to collapse
BTW is there a default recovery partition that your supposed to be able to access because when I press and hold "power + volume up" the tab just restarts and shows the Samsung logo over and over again. Also I could swear that I did install TWRP at the time when I rooted but there is no sign of it.

Related

Sprint Restore To Stock! (Nandroids CWM+TWRP & Recovery IMG)

Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Updated with CWM Nandroid and Stock Recovery Image
Sweet thanks
Sent from my Galaxy Nexus using Tapatalk 2
thanks to raiderep for giving me the stock recovery
Well Thanks Let the flashing begin ;P
Here is a link for the drivers from Samsung as well maybe helpfull
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
its the exe file and works well
thanks.. ill get how to videos up soon
qbking77 said:
thanks.. ill get how to videos up soon
Click to expand...
Click to collapse
You a good guy, so is OP.
added thanks to all the guys over on the IRC channel
shabbypenguin said:
thanks to raiderep for giving me the stock recovery
Click to expand...
Click to collapse
Glad to help when I can as always, go android!
Sent from my Galaxy Nexus
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
malibu_23 said:
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
We do the CWM for the verizon version is the one that works......
What if...
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
Click to expand...
Click to collapse
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same here...says "no sim card"...WTF...
Try doing a factory data reset. Just a shot in the dark...
turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same thing has happened to my phone but not with this immage what happened is i accidently flashed a image from a verizon phone to the sprint phone and now is all kinds of messed up
my friend is currently trying to fix it for me (hes a hell of a lot smarter than i am)
ill let u know the results
Same Song.. Several Verses Later
I would really like to find out if any of you figured this out??
I find myself in the same position as I'm finding that many have on here as well. I found this thread interesting because it is dealing with the Sprint Galaxy in particular. I have hosed the radio and the baseband on the Galaxy - likely the EFS parition, not sure.. at this point. It needs to be made very clear to everyone that even has a thought of flashing with this phone to make triplicate backups of the EFS partition before they turn the phone on (exxageration for affect).
That being said - I don't think that gets the rest of us anywhere. I'm a OG owner and a Bionic owner - and the first 72 hours of Samsung ownership has felt like non-stop triage to me..
I have this here.. but this really isn't the specific image for the Sprint the phones...
The link below points to a post for the IMM761 GSM+HSPA - which I believe these phones to be identical.. and since Sprint had locked code for the CDMA versions - is this one the same - in other words, is there an image out there that can be downloaded, flashed, and from there we can we can either fix the EFS and restore IMEI folder and baseband function or at least call warranty?
At this point - I can't reset the counter on the phone, I can't take it to the store (as if the 7 iployees would know what I was talking about) and I'm not about to pay $800 to learn that the EFS partition is the "short" in the term "got you by the short hairs"..
androidforums -
Heat57 says:"
It sounds as so you are on the GSM "maguro" device. In that case I suggest you download the complete ICS 4.0.4 factory image from Google at ... file. Beware! if you have a Windows PC the original download with a .tgz extension will be renamed by Windows automatically to a .tar file, which means that you'll have problems extracting it. In that case simply rename the file by changing the extension to .tgz and all will be well. Note: you'll need the Galaxy Nexus bootloader unlocked in order to flash a factory image and at the end of the procedure you can leave it unlocked and flash a Superuser file to root, if so desired. You'll need the Android SDK installed on your PC and then copy the bootloader, radio and image .img files to your ...android-sdk\platform tools-tools folder and run the adb commands in the windows command shell (note: you must flash each image in this order and wait until each image is flashed completely >bootloader >radio > image). Finally, flash the "image-soju-imm76d.zip" through your cwm recovery. You should end up with a healthy Galaxy Nexus on ICS 4.0.4 and everything working"​
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Click to expand...
Click to collapse
I think you are right but I do have cwm Also when I followed techfanatic's vid to unroot it said my phone was unrooted but the radio failed error came up. Also I am still on codeandroid. can I actually be unrooted and still be on that? Must I root again? Thanks.

[Howto] Install a Recovery

NOTE: If anyone has any further questions about recoveries on the S3, please note that I have moved on to another device. Sorry!
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.
Using mskip's Toolkit CWM [link]
Follow the instructions posted in his thread, and if you have any problems, direct them there as well!
Using ROM Manager CWM [link]
For some reason, ROM Manager doesn't always offer the correct list of devices to flash a recovery for and you won't see the SGS3 (AT&T) in the list. If that happens, force-close the app from Settings > Applications and try again. If this method just won't work for you, move on to option 4.
Using GooManager TWRP [link]
If you've been looking at ROMs, you may have noticed Goo.IM is a popular hosting website for Android developers. It's so popular, in fact, that they have produced an Android app that searches their website for updates for your ROM, and can even install TWRP with only a few simple clicks! Just open up GooManager, tap Menu, and tap "Install OpenRecoveryScript". You will be guided step-by-step from there by the app.
Note: Some people (myself included) have reported issues with this method, where the app claims to have installed the recovery, but when you reboot into recovery mode, nothing has changed. This issue may have been resolved in newer versions; I was able to successfully install TWRP using this method on Sept 26 2012.
Manually via ADB or Terminal Emulator CWM or TWRP [Terminal Emulator link]
If the other options just won't work for you, or if you would rather do an install by hand to ensure you're getting the latest version, read on...
Manually Installing a Recovery​
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
Now, transfer the ".img" file you downloaded onto your device. I'd suggest somewhere with a nice short path, like "/sdcard/<file>.img" (you'll thank me later, especially if you're using terminal emulator on the device)
Now, let's back up your existing recovery. If things go wrong, you can use this backup to get back to where you started.
Code:
$ su
# dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery-backup.img
That should have created a "recovery-backup.img" on your phone's internal storage.
Here's the part you've been waiting for: Flashing the new image, which installs it as your recovery system. You do this from either an ADB shell or inside Terminal Emulator.
Code:
$ su
# dd if=/sdcard/[B]<file>[/B].img of=/dev/block/mmcblk0p18
You're done. Reboot into your new recovery by holding VolUp and Home while you power on your device.
If you need to return to the stock recovery, that IMG can be downloaded here: stock-recovery.img - 10.00 MB
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Please remember to click/stick/lick/kick the "Thanks" button if you found this guide helpful!
How bout a 4th method for TWRP?
This should come in handy for some of the newer users
Well, the other TWRP method assumes that you already have a custom recovery installed to flash the ZIP from... If you've gotten that far already, I don't think you should need me to tell you how to flash a ZIP.
theres also GooManager from the market. its how I installed TWRP just download the app open it hit menu you'll see some options come up hit "install Open Recovery Script" it will ask if your sure hit ok and your done the whole process will take 30secs
Moved to General so new members can post questions
and stuck
FNM
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
Where'd you get it from? I'll add it to the OP.
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
tonymtl said:
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
There sure is! One of the benefits of manual installation is that you can find exactly what you want to use, and not rely on ROM Manager or other tools to make the decision for you!
Sent from my SAMSUNG-SGH-I747M
dstruct2k said:
Where'd you get it from? I'll add it to the OP.
Click to expand...
Click to collapse
+1. I am also looking for stock recovery...
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
nekkidtruth said:
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
Click to expand...
Click to collapse
That's a known issue with any recovery on the SGS3, it seems that the hardware clock cannot be accessed by the recovery no matter which recovery you use.
Did you happen to make a backup of your stock recovery? If so, I'd like to get a copy of it to add to the OP.
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
zmore said:
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
Click to expand...
Click to collapse
I could never get that to actually work in the past, so I guess I forgot about it. I just tested it now, and it worked fine, so I've updated the OP. Thanks!
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
See my Index for flash back to stock. There is a great vid tutorial.
PS dstruct2k I have added this thread to the INDEX. Nice work
Thanks, just flashed latest CWM Touch. External SD Card support rocks
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Then you're skipping a step, or typing something incorrectly. Once DD is done its work, you should get a response saying "Copied 10MB OK" or something similar. If it says that, then the stock recovery no longer exists.
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Please visit this post and follow from step 11-15. Shows kind of messed up on the XDA app so view it on your desktop. Very detailed guide for those who are confused. Thank you.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747
I followed those same steps but from a different thread and it still wasn't upgrading my clockwork recovery and kept getting status 7 when trying to flash cm10. Now I installed touch version hoping I would be able to get cm10 installed but still getting status 7. Any help appreciated
Sent from my SGH-I747M using xda app-developers app

AOSP 2.99 beta5 (five) Reboot loop! bricked

The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you
Go back to stock and start fresh.
Sent from my i9250
bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.
Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.
1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .
Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck
It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

[q] please help asap rooting problem

http://forum.xda-developers.com/showthread.php?t=2026569
I followed all of the instructions on the above link and after using odin my phone won't boot in clock work mod recovery. it only boots in the android system recovery and I didn't realize it at first and ended up clicking apply update from external storage and then chose the "CWM-SuperSU-v0.97.zip and when my phone rebooted it was wiped.
Odin passes so why is clock work mod recovery not working? please help
I also followed these instructions:
http://video.search.yahoo.com/video...c=2&sigr=11a718jq9&sigt=116j41687&age=0&&tt=b
rebecca928 said:
http://forum.xda-developers.com/showthread.php?t=2026569
I followed all of the instructions on the above link and after using odin my phone won't boot in clock work mod recovery. it only boots in the android system recovery and I didn't realize it at first and ended up clicking apply update from external storage and then chose the "CWM-SuperSU-v0.97.zip and when my phone rebooted it was wiped.
Odin passes so why is clock work mod recovery not working? please help
I also followed these instructions:
http://video.search.yahoo.com/video/play;_ylt=A2KLqIRlQI5SphoAIkX7w8QF;_ylu=X3oDMTByN2RnbHFoBHNlYwNzcgRzbGsDdmlkBHZ0aWQDBGdwb3MDMw--?p=how+to+root+galaxy+note+2+att&vid=2388eab99f70408a6b22d9a0083af7d6&l=8%3A24&turl=http%3A%2F%2Fts2.mm.bing.net%2Fth%3Fid%3DV.5053124652827001%26pid%3D15.1&rurl=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw7zGq_-gFlE&tit=How+to+Root+the+AT%26amp%3BT+Galaxy+Note+2&c=2&sigr=11a718jq9&sigt=116j41687&age=0&&tt=b
Click to expand...
Click to collapse
If you don't have root do this first,
http://forum.xda-developers.com/showthread.php?t=1980644
Then do this to install CWM
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
jibust said:
If you don't have root do this first,
http://forum.xda-developers.com/showthread.php?t=1980644
Then do this to install CWM
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
Click to expand...
Click to collapse
I followed all of the instructions here
http://forum.xda-developers.com/showthread.php?t=1980644
and then installed root checker and it still says I am not rooted :-/
rebecca928 said:
I followed all of the instructions here
http://forum.xda-developers.com/showthread.php?t=1980644
and then installed root checker and it still says I am not rooted :-/
Click to expand...
Click to collapse
I followed them to the letter and was rooted in 1 minute.
See if there is something you are skipping,make sure you have the latest PC drivers
Your not rooted. Reroot using odin 3.0.9 you might need to reinstall stock rom. If you read skynote thread your answer is there as well as download links... your welcome
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I re-ran odin and I am now rooted, my phone wasn't in debug mode... and the instructions didn't say that but I tried it and it worked.
Now my problem is when I try to start my phone in recovery mode the galaxy note logo flickers up and down the screen and the phone completely goes dead and i have to take out the battery to get it to start again. I have followed both sets of instructions to a T for clock work mod recovery and it hasn't worked.
And on the clock work mod recovery instructions, now when I click to download it it says failed download error...
http://forum.xda-developers.com/showthread.php?p=34039100#post34039100
I re-installed clock work mod recov 4 times and still when I try to start in recovery mode the screen flickers n theres lines across the screen n then the phone goes dead and I have to pull the battery to restart.
rebecca928 said:
I re-installed clock work mod recov 4 times and still when I try to start in recovery mode the screen flickers n theres lines across the screen n then the phone goes dead and I have to pull the battery to restart.
Click to expand...
Click to collapse
Try it with TWRP
http://tinyw.in/16LP
I installed that but it is an image file and odin will not open an image file?
Is it the same instructions to run this as it is to run cwm?
It says it needs to converted to a .tar file. How do I do that?
rebecca928 said:
I installed that but it is an image file and odin will not open an image file?
Is it the same instructions to run this as it is to run cwm?
Click to expand...
Click to collapse
The link I provided is for the tar file. If you downloaded it do not extract it.
Look here, end of the page
http://teamw.in/project/twrp2/124
Maybe this doesn't apply to you, or maybe it's too late, but some flavors of Samsung Android 4.x have a file to restore stock recovery at boot.
With the phone rooted and a root capable file explorer like Root Explorer or ES File Explorer look in the /etc directory. If there is a file in there called install-recovery.sh rename it and then try re installing cwm or twrp.
oldnoob said:
Maybe this doesn't apply to you, or maybe it's too late, but some flavors of Samsung Android 4.x have a file to restore stock recovery at boot.
With the phone rooted and a root capable file explorer like Root Explorer or ES File Explorer look in the /etc directory. If there is a file in there called install-recovery.sh rename it and then try re installing cwm or twrp.
Click to expand...
Click to collapse
I tried this and I still have the same problem. When I try to start in recovery mode the samsung galaxy logo flickers and the phone shuts off n then I have to pull the battery to reboot.
:-/
jibust said:
The link I provided is for the tar file. If you downloaded it do not extract it.
Look here, end of the page
http://teamw.in/project/twrp2/124
Click to expand...
Click to collapse
I clicked on the link and then went to end of the page to download for Odin, but when you click on that link there are a million different files, I just want to make sure I am clicking on the right one. Dont want to brick my phone. Is there a difference between all of the different files?
openrecovery-twrp-2.6.3.1-t0lteatt.img.tar.EjYLF6
is that the correct file?
Ok so I got TWRP installed.
Next question, I have been out of the loop for a few years so how do I get the latest firmware? Right now I have Android Version 4.1.2 and baseband version I317UCAMH3.
Is that the latest for the galaxy note 2? I have att and its the SGH I317
I didnt even plan to f with my phone but the other day my phone glitched and erased 300 pictures and videos from my newborn daughter that I just had and I was so upset and trying to find a way to recover them, someone told me to root my phone and try disk digger... so far I have had no luck at all with recovering anything... totally sucks and I am soooo upset!
rebecca928 said:
Ok so I got TWRP installed.
Next question, I have been out of the loop for a few years so how do I get the latest firmware? Right now I have Android Version 4.1.2 and baseband version I317UCAMH3.
Is that the latest for the galaxy note 2? I have att and its the SGH I317
I didnt even plan to f with my phone but the other day my phone glitched and erased 300 pictures and videos from my newborn daughter that I just had and I was so upset and trying to find a way to recover them, someone told me to root my phone and try disk digger... so far I have had no luck at all with recovering anything... totally sucks and I am soooo upset!
Click to expand...
Click to collapse
4.1.2 is the latest OFFICIAL AT&T build. There is an unofficial leak in the Android Development section, but I honestly don't know how it performs as I only run AOSP roms.
thanks

Please help - bricked phone?

Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
doctadocta said:
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Spaceminer said:
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Click to expand...
Click to collapse
Thanks for the response, Spaceminer!
When I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folders/1brK12SaoQ4gRbhuqLm7k0ZaW_iiaqfde
I get stuck on the Samsung Galaxy A50 screen.
I am basically trying to follow the directions here:
https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
doctadocta said:
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
Click to expand...
Click to collapse
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Spaceminer said:
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Click to expand...
Click to collapse
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
doctadocta said:
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
Click to expand...
Click to collapse
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
As I just spent like 8~hours getting my device out of bootloop.. (after trying to root + twrp...) I might as well take the time to post how I got it working.
DISCLAIMER: Only do this if you are desperate - I have no idea why this worked for me to be honest..
Here is how I managed to get my phone(A505FN btw) to boot again it:
download currently used firmware
extract boot.img + place it on external sd
Flash TWRP.tar (see roms&kernels forum section)
hold up + power while flashing until you are in TWRP
now flash boot.img for bootloader
reboot to system
IT BOOTS (I never got it passed samsung logo + text complaining about non offical firmware)
//edit
RIP it installed on SD card, anyone got any tips on how I move it onto internal?
It doesn't show internal storage anymore..
Shout outs to all the non english youtube videos about flashing android phones lmao
Im having kind of same issue but i only tried to install twrp via odin but then it got stuck on samsung logo boot loop. Later i tried creating recovery tar file and tried flashing it in odin but it wont go to the recovery mode although it came as Pass in odin and now im stuck on downloding screen fml any help is appreciated. can some please suggest my next course of action? is my phone gone>?
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Spaceminer said:
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
Click to expand...
Click to collapse
The twrp gives problems but since I rooted with just the patched bootloader in magisk and flash it with Odin. It works stable and I don't have issue's.
ebayusuff said:
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
i tried but stucked at modem_debug.log. can't proceed further. go back to SC to restore the default rom.
Thinking on having magisk but not TWRP. as TWRP may cause many malfunctioning.

Categories

Resources