Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Vikings09876 said:
Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Click to expand...
Click to collapse
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Vikings09876 said:
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Click to expand...
Click to collapse
You'll have to flash a copy of your stock recovery or your stock firmware, if you can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You'll have to flash a copy of your stock recovery or your stock firmware, if up can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm just gonna leave it as is rn because the phone works tbh, I just don't have a working recovery. The stock ROM doesn't seem to be available atm as the phone was just recently released. I'm sure it will be released at some point, and I'm not too worried about it. If anything, I can just pay it off and upgrade to a different phone.
Use crom apk by Samsung to unlock your bootloader.....till the files come out that's as far as me or ne of us r getting
Update twrps have been tried to compile with no success till Ashyx (our luck to have his services) recieves the kernel source
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
There is a rooted boot.img that ill be testing since i havbe access to exclusive stock firmware and have recourse should ne th ing be wrong....ie a brick.
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
Kindly redirect to this thread
Related
I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?
Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app
I have my tablet still on ICS, locked, all stock ROM, except I used a root exploit for ICS to have root.
What I would like to know; what is the best method for me to be able to happily try out different ROM's without fluffing up and bricking my tablet?
I know I need to unlock, install customer recovery. Is NVFlash backup necessary?
I've also got a HTC Desire HD which I've flashed with many ROM's without ever running into issues.
The Asus TF300 seems different and I've seen too many posts where people have bricked their devices.
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
psjw12 said:
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
Click to expand...
Click to collapse
Yes flashing a rom on a 4.2 bootloader that was made to work on a 4.1 bootloader will most likley cause a bootloop or a softbrick but should be able to be recovered in most cases.
The main cause of bricked devices atm is flashing the incorrect recovery for your bootloader version. This is flashing a non-4.2 recovery on a 4.2 bootloader, causes a fastboot flash brick - more info on this in my how-to in sig below.
I'm not sure about bricking your devices using wipes in recovery but the wipe data option in the bootloader menu will in most cases brick the device.
Not sure what the best method is but I pefer using the fastboot method over the twrp method but it's up to you, however the fastboot method does seem to work even with a locked device (but try at own risk).
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
pjc21 said:
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
How is a fastboot flash brick caused?
pjc21 said:
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
Click to expand...
Click to collapse
Thank you. I understand what to do but I don't feel confident. I've been happy flashing my HTC Desire HD for a long time and never had issues but I've seen so many bad stories on these forums it's really making me uncomfortable. I really want to go ahead and flash my device as it's slow and keeps crashing, and I want to be able to flash different ROM's without breaking a sweat. But I'd rather have a slow crashing device than a bricked one.
pjc21 said:
ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
EndlessDissent said:
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
Click to expand...
Click to collapse
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
I agree with you that as long as you can boot to apx and have nvflash backup and don't brick during nvflash restore then you should be able to unbrick from any brick.
Sorry for any confusion here.
pjc21 said:
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
Click to expand...
Click to collapse
Where? I went through the thread backwards from the last page back to page 7 or 8. Only one person even mentioned NVFlash, and he was asking if he could use NVFlash backups from a different tablet because he didn't have any of his own (that's not possible because of the way the bootloaders are signed). I also didn't see anyone actually tell him it wasn't possible. He was the third to last post in the thread.
So nobody in that thread (after page 7, anyway) said anything about NVFlash let alone that it doesn't work. NVFlash should work just fine to fix the fastboot bricks, just like any other brick.
Edit: So one other guy in a random post just kind of said NVFlash wouldn't work, nothing else - no details at all. A couple people asked him for details and proof, but he never replied. I have a feeling he meant NVFlash couldn't help because he didn't have any backups. If you have the NVFlash backups, you can recover from pretty much any brick.
Thank you guys for your help.
So does the following plan sound safe to you?
1. Backup my device (apps, data and sdcard)
2. Unlock with Asus unlock tool (v7 right?)
3. Do NVFlash Backup
4. Do official ASUS upgrade to JB 4.1 (I would do this by extracting the download from their site onto my SD card right? Because once unlocked I won't get offered any updates)
5. Once on JB, flash the correct 4.1 TWRP onto my recovery via Fastboot
6. Get Flash happy with my 4.1 compatible ROM's, do a few data wipes in between.
Sounds good to me. As long as you check version numbers and filenames carefully, there shouldn't be a problem.
What about on an Unlocked device
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
teedoe said:
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
Click to expand...
Click to collapse
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
psjw12 said:
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
Click to expand...
Click to collapse
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
teedoe said:
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
Click to expand...
Click to collapse
Did you remove any apps or system files? If your ROM isn't 100% exactly stock before the update, the update will fail.
It was a simple mistake, I just needed to extract the zip file I downloaded from ASUS one time and then transfer it to my SD card. Worked perfectly after that and I did not lose any data or apps.
Thanks to all on the forums for your advice and help!
How do you unroot the GS3 and get back to stock unrooted? I am currently just stock rooted. I'm just done with flashing and don't want to worry about something happening to my phone while I'm rooted, and am sick of it not being able to take the VZW update on a daily basis. I understand there is an unroot in the superuser app, is it as simple as clicking that and it will unroot by itself? Is there more I need to do? Thanks for your help!
Bump
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
buhohitr said:
Many ways to unroot, you could use SuperSU and select remove root, then uninstall the app then reboot or use universal unroot app from play store.
Click to expand...
Click to collapse
Thank you. Once you perform either or these methods, can you still root again in the future if you decide to?
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Bump
irl5fan said:
Bump
Click to expand...
Click to collapse
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Flash this file:
http://forum.xda-developers.com/showthread.php?t=2795659
With this guide:
http://forum.xda-developers.com/showthread.php?t=2586319
Then you're unrooted and up to date, but you'll erase all of your data. So backup all the pictures and music you want to keep.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
irl5fan said:
None of the links to the files have anything in them. Is there another way? Any other location to find these files?
Click to expand...
Click to collapse
You're right, try to search for it in Google. I didn't bookmark anything.
Sent from my HTC6525LVW using Tapatalk
irl5fan said:
I unrooted through SuperSU. Went to install the VZW update and it went into Teamwin Recovery. When it was trying to update the software and running all the checks, etc. I saw "checking for MD5 file...no MD5 file found." What is this and is this what is causing me to not be able to take the update? Am I supposed to still have Teamwin Recovery? How do I get rid of it? Root Checker said I'm unrooted now.
Where do I go from here? Thanks again!
Click to expand...
Click to collapse
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
Sent From V500
Using XDA App
unroot gs3
LiamAtkins90 said:
Dude.... You shouldn't be rooting if you don't know what TWRP is.... LMAO!
You need to flash stock recovery to take the OTA, you should of backed it up when you first flashed TeamWin to the device and it would of been a simple reflash through Flashify and it would of been good.
Now you need to download Odin (A PC flash tool) and reflash through that programme....
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
irl5fan said:
When did I say I didn't know what TWRP is? So if I flash stock recovery will that get me where I want to be...stock unrooted and able to take OTA updates. I never did flash any custom roms or anything while I was rooted.
Click to expand...
Click to collapse
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
LiamAtkins90 said:
Sorry, I realise my reply come of a little arsey, I will explain.
If you take the OTA in stock recovery it will go through, but as soon as you flash a custom recovery you give up the right to an OTA whilst on said recovery,
Instead you either:
1. Flash a custom ROM, and do updates with there ROM team.
2. Wait for stock ROM to come in a flashable zip for Custom Recoverys.
If you have root and stock recovery and take it, sometime it will go through, sometimes it won't.... Like Samsung Knox for example....
Sometimes it will take but as soon as you boot back up you will have no root.
If you OTA in Custom Recovery it will boot to TWRP and most likely abort straight away and bad things will ocure.
Mixed Partitions no ROM etc...
Now back to your question....
Yeah Stock non rooted you can take OTA (but in Samsung's case, they have a flash counter, that keeps track of system mods)
Best bet would be flash through Odin, to out-the-box firmware and take the OTA from there...to avoid any conflicts with the system.
I do apologise for my earlier post mate, write back if you got it upgraded.
Click to expand...
Click to collapse
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
irl5fan said:
No problem. This has been a long drawn out process over the past few months, so forgive me for all the questions and details of events. This is where I'm at. When I started the unrooting process, as stated above, used triangle away to reset the counter and then I unrooted through SuperSU. According to root checker apps I am unrooted, but I believe my bootloader is still unlocked. And obviously still have TWRP. Phone Info: SCH-I535, Version 4.1.2, Baseband I535VRBMF1.
Given that info, do I still flash the stock firmware (from here?--->) (http://downloadandroidfiles.org/download-sch-i535-vzw-i535vrbmb1-1360821900-zip/) and then flash stock recovery? Does flashing stock firmware re-lock my bootloader? Thanks for your help.
Click to expand...
Click to collapse
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
LiamAtkins90 said:
So you used Triangle Away to clear the flash counter?
Great, so the only thing you need now is the stock recovery image for your device,
I would say just flash the stock recovery image through Odin, but their is that many models
with different numbers, it would be easier flashing 4.1.2 firmware again through Odin.
In future bud if your gonna be messing with ROMs and Recovery files I recommend this:
Flash recovery with this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
(Backup Stock Recovery 1st)
Backup Stock EVERYTHING, Boot, System, EFS, Data etc in Recovery of choice.
Move backup to computer or cloud storage.
Then all you need to do to go back is triangle away, restore stock backup, restore stock recovery, unroot through SuperSU.
And the OTA should work.
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
irl5fan said:
I just want to clarify before I go ahead and do anything and get myself into a pickle. Are you saying to flash 4.1.2 firmware instead of stock recovery? Or am I still flashing both of them? If so, which order? Does that link I posted look like it is the correct firmware to you? Also, I have an older version of Odin on my computer, does that matter or should I get the newer one first?
Click to expand...
Click to collapse
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
My model number is SCH-I535. I have used Odin before, but I'll take a look at the guide just to make sure. Thanks for your help!
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
ShapesBlue said:
I just wanted to say thanks for helping out someone in our forums with the VZW variant, I was going to chime in but I see you had things under control. It's just odd to see so many people in our forums who don't have the version we have
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
No problem, glad I can help.
Verizon edition Models tend to get overlooked as oppose to International variants which is a shame, I think both should get equal recognition. Not just Sammy Verizon, most Verizon models and also Google Play Edition Model Phones/Tablets get pushed aside.... Crying shame.
LiamAtkins90 said:
Stock recovery is in the firmware file mate, when you flash the firmware it flashes the recovery, clears internal SD card (move pictures, videos, music to PC) & Radio, Modem, EFS basically everything on the phone gets flashed to how it is when you buy it from a store. Whats your model number?
And no it shouldn't matter, I've never seen any issues rise with using older Odin Programmes.
Do you have experience using Odin?
If not:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
That guide covers how to use it, where to place the firmware file etc.
Any questions just ask
Sent From V500
Using XDA App
Click to expand...
Click to collapse
Everything worked out great, flashed the stock firmware and was able to take the OTA. Thank you so much for your help, it's greatly appreciated!
Hi xda community.
Maybe I'm blind, but I can't find stock recovery images for the LG Google Nexus 5. I run all my devices rooted, with unlocked bootloader, TWRP and Cyanogenmod 13. However, due to security concerns I would like to flash a stock recovery again and lock the bootloader.
However, I can not really find first-hand stock recovery images. Searching yields only unsigned third party downloads like this one. No way I'm going to flash this.
The official Google developer factory images only contain a bootloader image and a radio (?) image and the hammerhead stock ROM zip archive. But what I'm looking for is the recovery image!
Any idea where to get them first hand and singed or at least check-summed? Thanks!
Ok for some reasons, the factory image contains all images in the zip, including a recovery zip.
However, flashing that renders recovery unusable - little android with a red sign. I don't really worry (yet), but what would be the cause for that?
Is there any issue to run Cyanogenmod with a stock recovery? Should I prefer the CM recovery instead? Is the CM recovery as secure as the stock recovery?
The Android logo with a red exclamation is the stock recovery (recovery.img in the factory images) with its basic features.
You should be able to run CM13 with a stock recovery but locking the bootloader seems enough IMO. Actually I keep it unlocked because it could be my last chance to recover my device without loosing all my data.
Hi, not sure if you still need this but if you check page 1 of this XDA thread under "Nexus 5 Specials", you can find all of the stock bootloaders, radios, recovery, stock/ custom ROMs and stuff like that.
I've flashed a lot from this guys thread and I know the stuff there is legit and reliable. You're right though, only flash what you trust from a Official source.
You should be able to find what you need on that thread, good luck whatever route you choose.
Link to thread: (Page 1: Nexus 5 Specials.)
http://forum.xda-developers.com/goo...gle-nexus-5-roms-kernels-mods-t2475401/page50
Primokorn said:
The Android logo with a red exclamation is the stock recovery (recovery.img in the factory images) with its basic features.
You should be able to run CM13 with a stock recovery but locking the bootloader seems enough IMO. Actually I keep it unlocked because it could be my last chance to recover my device without loosing all my data.
Click to expand...
Click to collapse
Ah, okay. It shows only the logo, no menu or something. Does that sound correct?
The issue with keeping it unlocked is basicly that anyone can recover my device. I use backup synchronization from within android and when the devices fails, I can simply whipe it and start fresh because I have all data synched to my computer (using syncthing).
Rooted Droid said:
Hi, not sure if you still need this but if you check page 1 of this XDA thread under "Nexus 5 Specials", you can find all of the stock bootloaders, radios, recovery, stock/ custom ROMs and stuff like that.
I've flashed a lot from this guys thread and I know the stuff there is legit and reliable. You're right though, only flash what you trust from a Official source.
You should be able to find what you need on that thread, good luck whatever route you choose.
Link to thread: (Page 1: Nexus 5 Specials.)
http://forum.xda-developers.com/goo...gle-nexus-5-roms-kernels-mods-t2475401/page50
Click to expand...
Click to collapse
Thanks, will look into that one.
5chdn said:
Ah, okay. It shows only the logo, no menu or something. Does that sound correct?
The issue with keeping it unlocked is basicly that anyone can recover my device. I use backup synchronization from within android and when the devices fails, I can simply whipe it and start fresh because I have all data synched to my computer (using syncthing).
Click to expand...
Click to collapse
Stock recovery offers basic features: reboot, wipe cache, factory reset...
This is the bootloader.
You have a rooted phone so anyone can install BootUnlocker app to unlock the bootloader without wiping anything.
Primokorn said:
Stock recovery offers basic features: reboot, wipe cache, factory reset.
Click to expand...
Click to collapse
Yeah, I don't have that, it looks like this issue: https://www.youtube.com/watch?v=yoJ_vRTRX7g However, the CM recovery works. Edit, after watching the video, I understand it's a non-issue
Primokorn said:
You have a rooted phone so anyone can install BootUnlocker app to unlock the bootloader without wiping anything.
Click to expand...
Click to collapse
Mind elaborating how _anyone_ can install an app on my phone? No custom recovery, no debugging enabled, bootloader locked, phone encrypted, pin set up. How to access my phone to install a bootunlocker?
5chdn said:
Mind elaborating how _anyone_ can install an app on my phone? No custom recovery, no debugging enabled, bootloader locked, phone encrypted, pin set up. How to access my phone to install a bootunlocker?
Click to expand...
Click to collapse
"Anyone" is excessive for an encypted phone of course
Using a long password was enough to hack Android phones having Lollipop; hacking a 4 digits password can get cracked in minutes with a computer; thanks to the software FROST, security researchers extracted photos, web history and contact lists from locked & encrypted Android phones,...
Anyways, Android is not a secure OS and I never trust those security tools. I don't store precious information on my device and I'm safe from day one lol
Ok so Huawei Ascend XT H1611 ATT. Rooted just fine. Unlock just fine. ATT sends update OTA. Supposed to go from B150 to B160. I tried to avoid it. Started and then froze on reboot. I can run recovery. Can flash recovery. Used every method I can find in the forums. All it will do is run either stock or custom recoveries but no matter how many backups or stock roms I have tried it just hangs on boot. I'm not too new to custom roms and rooting and unlocking, I just would like to know if I should just give up on it. It is not like it's the end of the world, I would just like a second opinion on the matter. Thanks for any advice.
MotoBlack said:
Ok so Huawei Ascend XT H1611 ATT. Rooted just fine. Unlock just fine. ATT sends update OTA. Supposed to go from B150 to B160. I tried to avoid it. Started and then froze on reboot. I can run recovery. Can flash recovery. Used every method I can find in the forums. All it will do is run either stock or custom recoveries but no matter how many backups or stock roms I have tried it just hangs on boot. I'm not too new to custom roms and rooting and unlocking, I just would like to know if I should just give up on it. It is not like it's the end of the world, I would just like a second opinion on the matter. Thanks for any advice.
Click to expand...
Click to collapse
When you flash recovery, have you tried factory resetting and wiping cache in recovery then rebooting?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
When you flash recovery, have you tried factory resetting and wiping cache in recovery then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes. That has been common practice for my other phones. This is the first phone that has had issues like this. Everything was fine until ATT it's update started.
MotoBlack said:
Yes. That has been common practice for my other phones. This is the first phone that has had issues like this. Everything was fine until ATT it's update started.
Click to expand...
Click to collapse
It's best to unroot a device before applying stock updates on most devices. Stock updates usually require you to have stock recovery and an unmodified system partition.
If there is a rooting method for the update then you can try reflashing your stock firmware to get a clean start then apply the update again, then try rooting again after the update is applied.
Sent from my SM-S903VL using Tapatalk