Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy J3 (SM-J320P) msm8916 variant running 5.1.1 (Lollipop).
Tested Safely on following devices.
Samsung Galaxy J3 (SM-J320P)
Why use TWRP ? Why not just use some rooted firmware which keeps my warranty safe?
TWRP is a custom recovery. Thus, it has many more features than stock recovery, such as making full NAND backups, flashing zips through recovery, ADB sideload, and more! Plus, if something goes wrong while flashing something, you can always restore from a backup using TWRP, meaning you're much safer when flashing new ROM's, etc!
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
Follow the instructions carefully.
DOWNLOAD LINKS ARE UNDER THE "WITH PC" INSTRUCTIONS. A SEPARATE DOWNLOAD LINK IS PROVIDED UNDER "WITHOUT PC" FOR THE .IMG FILE YOU NEED FOR THOSE INSTRUCTIONS
WITH PC:
Step 1 :
Install Samsung Drivers and connect your device to PC. Let it install the drivers and any updates that may be required. The device drivers should install without failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery ---- Google Drive Mirror for TWRP
(DISCLAIMER: I HAVE NOT USED GOOGLE DRIVE EXTENSIVELY FOR FILE SHARING, SO THERE MAY ALSO BE A BANDWIDTH/DOWNLOAD NUMBER LIMIT PER DAY, SO IF YOU ARE UNABLE TO USE EITHER LINK, TRY AGAIN THE NEXT DAY FOR THE TIME BEING UNTIL WE DECIDE ON A BETTER FILE HOSTING SERVICE.)
Step 3:
Power down your device, then when turning it on hold [ Vol down + power + home button (all at the same time) ] in order to boot the phone into Odin mode. Release it when you see the warning about entering "Download Mode".
Press vol up to confirm
Step 4:
Now that you are in Odin Mode, connect your device via USB cable.
Now open Odin 3.09 or 3.07 that you have downloaded.
If there is a pop-up regarding Installing ADB drivers let it finish, it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so don’t worry about it, just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing else. Very important! Double check that only these are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
OR
WITHOUT PC:
Instructions:
1. Make sure you have temp root available (Yes, this means likely using Kingroot one more time).
2. Download the recovery.img file (essentially what is in the Odin flashable .tar file) from here. Make sure you are aware of it's download path to find it with Flashify.
3. Download Flashify from the Play Store.
4. Open Flashify, grant root access, and click Recovery Image. Navigate to where you downloaded the .img file and select it.
5. A dialog should pop up asking if you want to continue with flashing the recovery. Click "Yup!" and wait for it to finish. Afterwards if it doesn't ask you to reboot, do so yourself into recovery (Vol-UP+Home+Power in case you forgot). If things went right, you should boot into TWRP smoothly!
A few helpful things for the "just in case" moments(most of these require a PC with Odin, unfortunately):
* Stock Recovery Odin flashable .tar
* Stock Boot Odin flashable .tar
* Both of the above are flashed the same as the instructions above detail flashing TWRP. Use either depending on what you've flashed/messed up, or flash both if you aren't sure. These are NOT a replacement for flashing full stock firmware through Odin in case of a thorough brick (I.E. combinations of boot/recovery/system/etc being corrupted together). Use these when you're flashing TWRP or the root zip, as it's faster and you shouldn't need to flash full firmware if you didn't brick your device in some other way.
* Raw kernel source for anyone wanting to start their own project for this device.
Credits:
TWRP Team i.e. @Dees_Troy for his awesome recovery!
@androidlover5842 for compiling TWRP, and for creating the flashable supersu.zip to give us PERM ROOT!
@darknaio for testing recovery!
*** IMPORTANT UPDATE: WE HAVE SOLVED THE ROOT PROBLEM ***
We have a working permanent root solution available for testing by anyone who would like to give it a try and get back to me with your results. So far on my device root has persisted through several reboots. Make sure you pay attention to the instructions when you flash it, and you should be good to go! Download the following file and flash it through TWRP, and make sure you DON'T let TWRP flash it's own supersu when you reboot. SuperSU TWRP Flashable ZIP
Source Code: https://github.com/Grace5921/android_device_j3ltespr
ROM OS Version: 5.1.x Lollipop
Twrp version: 3.0.2 Lollipop
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod
Version Information
Status: Stable
Created 2016-04-11
Last Updated 2016-04-11
Will tbis make root stick on my device
turboxsloth said:
Will tbis make root stick on my device
Click to expand...
Click to collapse
We're working on it, currently flashing supersu through TWRP still causes a bootloop similar to when using super sume to get rid of kingroot. More work is going to be done on it tomorrow, and hopefully we will solve the issue with either custom kernel, or he was maybe porting CM13 to here and thatd fix it straight away.
In short dont let twrp flash supersu just yet. And have odin backups just in case. Might see if we can link to the stock files later.
Ok sousnds good
Hey sorry noob question where is the recovery file I have to download?
gsprague15 said:
Hey sorry noob question where is the recovery file I have to download?
Click to expand...
Click to collapse
The download links are under the With PC Instructions. Click the Show Content button to show the instructions, and you'll see the link for TWRP Recovery in the directions. Let me know if you have trouble finding the link.
Ah okay I see thanks man! And thank you for putting up no pc instructions and thank you Androidlover5842
gsprague15 said:
Ah okay I see thanks man! And thank you for putting up no pc instructions and thank you Androidlover5842
Click to expand...
Click to collapse
Glad to do it! It actually got me to stop being lazy and clean up the thread in general, plus I want to make this available to as many people as possible, since this is the FIRST real progress on this device, I want everyone to hear about it! Too many owners of this device have probably given up hope on root solutions so far, which is just tragic for what is a genuinely good device.
darknaio said:
Glad to do it! It actually got me to stop being lazy and clean up the thread in general, plus I want to make this available to as many people as possible, since this is the FIRST real progress on this device, I want everyone to hear about it! Too many owners of this device have probably given up hope on root solutions so far, which is just tragic for what is a genuinely good device.
Click to expand...
Click to collapse
I admit, I had given up but now seeing this gives me some hope. Thanks!
triiuzii said:
I admit, I had given up but now seeing this gives me some hope. Thanks!
Click to expand...
Click to collapse
Glad to hear it! We're working hard to finish things up, once we get custom ROM working things will be so much easier with this device!
Hey! So I followed the instructions for hooking it up with no pc. But after I typed reboot recovery it rebooted to the J3 logo and then to a black page with a big yellow triangle sign that had "!" in it and on the top it said something like: custom binary has been blocked by FRC. so I flashed the stock rom back into it (had to go to someone's house to use their pc). Didn't lose any data though after it recovered everything was still there on my phone.
gsprague15 said:
Hey! So I followed the instructions for hooking it up with no pc. But after I typed reboot recovery it rebooted to the J3 logo and then to a black page with a big yellow triangle sign that had "!" in it and on the top it said something like: custom binary has been blocked by FRC. so I flashed the stock rom back into it (had to go to someone's house to use their pc). Didn't lose any data though after it recovered everything was still there on my phone.
Click to expand...
Click to collapse
That's odd, we didn't run into that on my device, but I was using a pc and Odin, though there shouldn't be any difference. Would you be able to borrow that person's PC again to try to flash it with the .tar file through Odin? AL is asleep atm but I'll direct them to this post when they wake up.
darknaio said:
That's odd, we didn't run into that on my device, but I was using a pc and Odin, though there shouldn't be any difference. Would you be able to borrow that person's PC again to try to flash it with the .tar file through Odin? AL is asleep atm but I'll direct them to this post when they wake up.
Click to expand...
Click to collapse
It was my moms I just ran over there to fix it real quick cause I need my phone for work. Her computer is all screwed up with viruses for some reason and she also hates me lol but I'm going to see if my buddy will let me use his.
---------- Post added at 12:12 AM ---------- Previous post was at 12:11 AM ----------
I'll let ya know
gsprague15 said:
It was my moms I just ran over there to fix it real quick cause I need my phone for work. Her computer is all screwed up with viruses for some reason and she also hates me lol but I'm going to see if my buddy will let me use his.
---------- Post added at 12:12 AM ---------- Previous post was at 12:11 AM ----------
I'll let ya know
Click to expand...
Click to collapse
Eek, that doesn't sound fun! Alright, keep me posted as to your success with doing it through Odin if you are able to. Hopefully in a few hours AL will be up and I can mention it to them.
Awesome thanks I'm sure it will work itself out. Could be that I did something wrong while using the console although I'm not totally sure
hmmmmmmmmmmmmmm this is so weird. I tried the PC method with odin and on my phone screen where it says in the small text what Odin is doing, I'm still seeing "Blocked by FRC". weird. I might have to do a factory reset and then try again or something. what does FRC mean?
---------- Post added at 07:14 PM ---------- Previous post was at 06:31 PM ----------
Ok! I figured it out. Turned on OEM unblocking flashed it and it worked. But I accidentally forgot to untick auto reboot (whoops!). It booted up fine but now I am worried. What happens if you forget to untick that?
gsprague15 said:
hmmmmmmmmmmmmmm this is so weird. I tried the PC method with odin and on my phone screen where it says in the small text what Odin is doing, I'm still seeing "Blocked by FRC". weird. I might have to do a factory reset and then try again or something. what does FRC mean?
---------- Post added at 07:14 PM ---------- Previous post was at 06:31 PM ----------
Ok! I figured it out. Turned on OEM unblocking flashed it and it worked. But I accidentally forgot to untick auto reboot (whoops!). It booted up fine but now I am worried. What happens if you forget to untick that?
Click to expand...
Click to collapse
Good to hear! I dont think its absolutely necessary to untick that, I didnt when I first flashed it through Odin, just reboot into recovery to make sure that it worked (Turn phone off, then turn it back on holding power + vol up + home) and you should boot into TWRP if it worked correctly.
darknaio said:
Good to hear! I dont think its absolutely necessary to untick that, I didnt when I first flashed it through Odin, just reboot into recovery to make sure that it worked (Turn phone off, then turn it back on holding power + vol up + home) and you should boot into TWRP if it worked correctly.
Click to expand...
Click to collapse
Yup! Everything works great
gsprague15 said:
Yup! Everything works great
Click to expand...
Click to collapse
Awesome! Make backups and restore from them if you wamt to test its functionality. And remember not to flash supersu yet.
darknaio said:
Awesome! Make backups and restore from them if you wamt to test its functionality. And remember not to flash supersu yet.
Click to expand...
Click to collapse
Thanks so much for doing this!
Before I jump in, I want to make sure I have the proper firmware to restore the unit via Odin, just in case. I was able to download the file "J320PVPU1AOL2_J320PSPT1AOL2_SPR.zip" from a source (with a MD5 value of 008D7C9916FCAF885C811ABC3E55F01A), which when unzipped shows: "J320PVPU1AOL2_J320PSPT1AOL2_J320PVPU1AOL2_HOME.tar.md5" (with a MD5 value of 2C92F5AED197619F6AE8A86DBCB76B8E). Is this the correct firmware to restore a Virgin Mobile Galaxy J3 (SM-J320P)?
If this is not the proper firmware to restore this phone with Odin, can you please indicate where I might download it?
Related
Hi everyone, I post this tutorial in order to help people (like me) want to revert to stock state, including the "famous" flash counter, and Stock Recovery, in order to install update by official methods.
WARNING
I'm not responsible malfunctions, bricks and other by make these actions.
All actions described were tested by me in the same order in a Galaxy Tab 2 Wifi-only P5110
However, it should work on any Galaxy Tab 2 model.
Requeriments:
You have permission of superuser
Recomendations:
Use Titanium Backup in order to backup your apps & apps data
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Remember, Mobile Odin NOT increase your flash counter!!!
And enjoy your device with stock state!!
Don't forget press the :good:"Thanks button" !!!
It should work on every gtab 2 , nice work.
Yes, it should work or any Galaxy Tab 2.
I really hope someone can help. I have a GT-P5113 and have rooted and put CM10 on it. The touch screen is broken now and I need to send it in for warranty (broken as in not working not shattered or cracked) and need help! I can still use the power and volume buttons so getting the new firmware on it isn't the issue, its resetting the flash counter. PLEASE HELP!!!
I think you need usb otg cable (so cheap) ,then connect usb mouse (better) or keyboard ,then download triangle away 1.90 app from market (paid) or xda forums (free) ,then use to reset counter ,then boot to download mode by long press power then reboot/download (better) or power off then volume down+power ,then connect to computer ,then flash stock firmware from www.samfirmwsre.com or so via odin
Sent from Galaxy S2 or Galaxy Tab2
smileygui said:
I really hope someone can help. I have a GT-P5113 and have rooted and put CM10 on it. The touch screen is broken now and I need to send it in for warranty (broken as in not working not shattered or cracked) and need help! I can still use the power and volume buttons so getting the new firmware on it isn't the issue, its resetting the flash counter. PLEASE HELP!!!
Click to expand...
Click to collapse
You can prove this tutorial using a mouse with a USB OTG cable for Galaxy Tab 2. You can buy it on eBay or other online shops.
ok, so I am waiting for my OTG adapter to get here to try that out and hopefully that works for getting back to stock. Here is my next big question. I am going to try to send this back to samsung for warranty because the touch screen doesn't work and the lcd is very dark along the left side from top to bottom. I was removing dust that somehow got caught between the front glass and the lcd and in doing so i cut the ribbon cable for the digitizer. (lcd was already really dark before hand, that is a factory defect) being that one would have to cut the seal to see that, is that something that samsung would be able to know? I've reassembled the tablet and you would never even know it was apart, i didn't see any void stickers or even watermark stickers. any thoughts?
Anybody? Please?
smileygui said:
Anybody? Please?
Click to expand...
Click to collapse
Even if they find it they probably won't care. This is from experience with Samsung phones and them not really giving a crap. They'll probably send you a refurb with no questions asked. Can't hurt to try, anyways.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
smileygui said:
ok, so I am waiting for my OTG adapter to get here to try that out and hopefully that works for getting back to stock. Here is my next big question. I am going to try to send this back to samsung for warranty because the touch screen doesn't work and the lcd is very dark along the left side from top to bottom. I was removing dust that somehow got caught between the front glass and the lcd and in doing so i cut the ribbon cable for the digitizer. (lcd was already really dark before hand, that is a factory defect) being that one would have to cut the seal to see that, is that something that samsung would be able to know? I've reassembled the tablet and you would never even know it was apart, i didn't see any void stickers or even watermark stickers. any thoughts?
Click to expand...
Click to collapse
The only thing you can do is try sending it in for warranty. Bte, you can just flash the stock rom via Odin using a laptop or desktop. Flashing stock does not increase your counter.
frankdrey said:
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
Click to expand...
Click to collapse
mine too. P5100 with CM10.1. also using Mobile Odin lite. Also stuck on boot logo. Wipe data n factory reset done. back to stock...
:laugh::laugh::good::good:
If I only wanted to reset my flash counter but I am running CM10.1 on my GT-P5113, triangle away will work correct? Or would I expect problems after resetting counter? Tab is running perfect, just want to fix counter
Edit: so I got a response for this in the thread for the CM10.1 nightly build and TA is safe for my device/rom combination.. So I ran TA, and after I run, it went from 10 to 0. Perfect, rebooted into DL mode, and it says 1.. Relaunched TA, sure enough, it said 1 again, so I reran, it says 0, but when I reboot, I should expect to see 1 again? (I thought I remembered reading that it would do this, but didn't remember where, I reread this OP)
This is after using TA to reset the flash counter from 10 to 0, notice it says "0" and "Official binary":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is after only rebooting, nothing else was done, its like a kernel gets flashed on reboot:
I have a jig too, and I just got some converters to "adjust" the USB port configuration.. I'm thinking about plugging in the usb that came with my tab, converting the reg USB (male) to micro USB (female) and then plugging in the jig. The only thing I would need to know though is if the jigs are device dependant and os version dependant.. (After thinking about it, in order to actually use the jig on an E4GT, I have to restore it to EL26 or 29..) So I guess it prolly won't work on a GT-P5113.. :/
sj
Sent from my pimped out E4GT on WftN_CM10.1 - 1/25 with [email protected] Pro 2.4.10
sjsharksfan420 said:
If I only wanted to reset my flash counter but I am running CM10.1 on my GT-P5113, triangle away will work correct? Or would I expect problems after resetting counter? Tab is running perfect, just want to fix counter
Edit: so I got a response for this in the thread for the CM10.1 nightly build and TA is safe for my device/rom combination.. So I ran TA, and after I run, it went from 10 to 0. Perfect, rebooted into DL mode, and it says 1.. Relaunched TA, sure enough, it said 1 again, so I reran, it says 0, but when I reboot, I should expect to see 1 again? (I thought I remembered reading that it would do this, but didn't remember where, I reread this OP)
This is after using TA to reset the flash counter from 10 to 0, notice it says "0" and "Official binary":
This is after only rebooting, nothing else was done, its like a kernel gets flashed on reboot:
I have a jig too, and I just got some converters to "adjust" the USB port configuration.. I'm thinking about plugging in the usb that came with my tab, converting the reg USB (male) to micro USB (female) and then plugging in the jig. The only thing I would need to know though is if the jigs are device dependant and os version dependant.. (After thinking about it, in order to actually use the jig on an E4GT, I have to restore it to EL26 or 29..) So I guess it prolly won't work on a GT-P5113.. :/
sj
Sent from my pimped out E4GT on WftN_CM10.1 - 1/25 with [email protected] Pro 2.4.10
Click to expand...
Click to collapse
It's because you have a custom rom and recovery
It detects that and bumps up the counter to 1
Sent from my GT-P5110 using Tapatalk HD
frankdrey said:
It's because you have a custom rom and recovery
It detects that and bumps up the counter to 1
Sent from my GT-P5110 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the post.. I just wanted to be sure I wasent missing something.. if that's expected as the outcome due to my rom/recovery configuration, then I totally understand
sj
Sent from my PimpedOut GT-P5113 on CM10.1 - 1/28 Nightly using [email protected] Pro 2.4.10
chapitron said:
Hi everyone, I post this tutorial in order to help people (like me) want to revert to stock state, including the "famous" flash counter, and Stock Recovery, in order to install update by official methods.
WARNING
I'm not responsible malfunctions, bricks and other by make these actions.
All actions described were tested by me in the same order in a Galaxy Tab 2 Wifi-only P5110
However, it should work on any Galaxy Tab 2 model.
Requeriments:
You have permission of superuser
Recomendations:
Use Titanium Backup in order to backup your apps & apps data
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Remember, Mobile Odin NOT increase your flash counter!!!
And enjoy your device with stock state!!
Don't forget press the :good:"Thanks button" !!!
Click to expand...
Click to collapse
That's great to restore stock state for P5110.
chapitron said:
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Click to expand...
Click to collapse
Hi, i tried to return to stock with your Tutorial (thanks btw) but it didnt work for me. I configured MobileOdin and taped "flash firmware", everything went very fast and the GalaxyTab2 Bootlogo appeared. A few seconds later there is the blue Mobile Odin Logo and on the left side of the screen it says "Wipe.....done flash.....done, kernel....done its too fast to read any word exactly and then: BOP - Samsung Bootlogo again and again mobile odin and again Bootlogo and so on. CWM doesnt work anymore but Odin-Mode (Download-Mode?) still works.
Is it possible to flash the stock rom with Odin PC in Odin-Mode on my tablet? And is it possible that i downlaoded the wrong Stock-Rom? Im from Germany, using a P5110 and downloaded this one: P5110XWALD2 (4.0.3) - Netherlands April 2012 (Official).
pls help if somebody can help
thanks in advance
edit: ok first i'll try the 4.0.4 Stockrom from the first post via Odin on PC, see if it works...
edit2: WORKS! Even if no one helped (no reproach!): thank you guys, i appreciate your work and time you all are spending for ous!! This is the greatest community
Flash count question
frankdrey said:
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
Click to expand...
Click to collapse
I was wondering, and probably a noob question. Does the flash count increase when installing official Samsungs update OTA? Such as from 4.0.4 to 4.1.1?
BrooklynSpartan said:
I was wondering, and probably a noob question. Does the flash count increase when installing official Samsungs update OTA? Such as from 4.0.4 to 4.1.1?
Click to expand...
Click to collapse
No...OTA is official...flash official ROM using Odin also will not increase your binary....as long its official..its good to go...cheers...
Done!
I followed the steps, and was able to go from CWM recovery + CM10.1 to full stock.
Only issue was after it flashed, the boot sequence continued (samsung logo) in infinite loop without responding to any key press, off switch etc. Finally I removed the micro-sd card and tried, it rebooted, now it works fine! Had some tense moments..was that step required? when it is on infinite reboot loop, what is the correct way to reset?
Everything works fine or seems to..thanks very much. The counter too showed zero after I reset it. Now when I go to download mode, dont see any counter stat.
BTW, if the Device status message shows NORMAL that means the counter is zero?
Tks
DDLF2 Full (PIT,BOOTLOADER,PDA,PHONE,CSC) Orignal Firmware.
Imported From Samsung Service Center Directly, Ultra Compressed 200 MB Only Uploaded By Me "Sgatechwork". :good: :laugh: :victory: Enjoy ... Don't forget PRESS "THANKS BUTTON" :good: :good:
You Can Directly Flash This On your i9003 no need to flash any thing before this. Because its a full pack firmware.
For cm 10 10.1 or any other based on these if you are from india or if you want your baseband Version to I9003DDLE1 Than just download modem.zip (ultra Compressed) from attachment Extract zip take modem.bin and push it in /radio 0664 which is rw-rw-r--
Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Only Modem.bin View attachment modem.zip
Resumable Links
Download Now
Mirror
Mirror Download
Edit:
Confirmation
Installation instructions:
1:Turn Off Your Phone
2ress Vol Down+Home + Power Until Downloading Screen Comes...
3:Than Start Loading Files in
Code:
PIT =latona_20110114.pit
Bootloader =APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PDA=CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
Phone=MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC=GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
For CF Root Open Odin 1.85 Load Only PDA=DDLF2-CFROOT-30-06-2012.tar
For Root And ClockWorkMode Recovery
CF Root LF2 (PDA only with Odin) Download Download CF Root Link
Download Odin 1.85 Download Now
Than Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update Than Press Start When it says PASS In a green Box wait Till reboot is done than remove the cable enjoy...
Does this mean that we can flash DDLF2 directly instead of starting from xxkpe as this new uploaded firmware contain all necessary files??
probably. but still a confirmation would be great.
Sent from my GT-I9003 using xda app-developers app
Yeeh does that mean full clean begin from it .. We need confirm about these thing ..
Thanks very much ..
Sent from my GT-I9003 using xda premium
Tested.Works like a charm.And yes it makes a full wipe.
I suggest you add a guide on how to flash this if its proven that this does not need xxkpe to start with. This is really great. Flashaholic members will no longer have a hard time doing a clean flash.
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
devilhell007 said:
Tested.Works like a charm.And yes it makes a full wipe.
Click to expand...
Click to collapse
You flashed directly? Wow. Have you included the bootloader? your from what base rom?
marshygeek said:
I suggest you add a guide on how to flash this if its proven that this does not need xxkpe to start with. This is really great. Flashaholic members will no longer have a hard time doing a clean flash.
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
You flashed directly? Wow. Have you included the bootloader? your from what base rom?
Click to expand...
Click to collapse
Yeah I flashed it directly.I did not include the bootloader.Iwas on CM 10.1 Alpha 4.Just wanted to make a clean install so tested it.
devilhell007 said:
Yeah I flashed it directly.I did not include the bootloader.Iwas on CM 10.1 Alpha 4.Just wanted to make a clean install so tested it.
Click to expand...
Click to collapse
Great news! :thumbup:
Thanks a lot for the confirmation!
Sent from my GT-I9003.
Good news bro
easy clean now !!!
Tested just now I will review all the installation instructions thank you for this easy clean
With Odin 1.85
- Full LF2 reset odin then remove cable and battery after bootanimation
PIT =latona_20110114.pit
Bootloader =APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PDA=CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
Phone=MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC=GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
Click to expand...
Click to collapse
- CF LF2 (PDA only with Odin) reset odin then remove cable and battery after bootanimation
- jellymystery A4 reboot automatic recovery works fine now !!!
- jellymystery A4 again with new recovery
- Wip cache and dalvik cache
time of need to put this topic in post-it
can you add link CFroot LF2 also
- CF Root LF2 (PDA only with Odin)
enjoy...
thanks bro :good:
thanks.
using xwlf2 as a base (eastern europe), but I guess that will do
I never checked "Phone Bootloader Update" in Odin. Is it necessary for this full DDLF2 ?
Currently I'm using same old DDLF2 over XXKPE method without using "Phone Bootloader Update" option
Please confirm.
yes bootloader no need after froyo
just for froyo upgrade (to GB HONEY ISC JB uses the same bootloader) no need updating this !!!
it is even not recommended to put bootloader because it is often responsible for Brick
Bootloader is the first step in flash, if you have a conflict on your computer
avoid process, samsung kies, adb, antivirus internet security software and others scan stuff before flash !!!
@LoLaTiOn!
That what i thought so and read everywhere but was bit confused about checking that option. Thanks! for confirming
I would like to go back to GB from Jb only because of the battery.
Im currently in Qwerty
can someone post every single step in a noob (me) friendly way,please?
From what i've read:
1) you need odin 1.85 installed on your pc
2)Start the phone while pressing Vol down+home+power to start in download mode (these has to be with the phone connected to the pc via usb cable or you can plug it in later?)
3)Fill every file category with the corresponding file in odin.
4)Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update
5)Press Start
7)When it says PASS In a green Box wait Till reboot is done ....
8)thee remove usb cable from phone
Am i missing something? devilhell007 says that you dont need the bootloader file? Is this file necessary only with certains roms? which roms would that be?
and finally, i've read that some roms, change the file system of the phone, and returning to stock bricks it, does this method prevents and reverts that?
sorry for the noobish questions, big thanks in advance!
Load all the files as i mentioned... and flash it... than after paas ur done...
Sent from my GT-I9003 using xda premium
felaipes said:
I would like to go back to GB from Jb only because of the battery.
Im currently in Qwerty
can someone post every single step in a noob (me) friendly way,please?
From what i've read:
1) you need odin 1.85 installed on your pc
2)Start the phone while pressing Vol down+home+power to start in download mode (these has to be with the phone connected to the pc via usb cable or you can plug it in later?)
3)Fill every file category with the corresponding file in odin.
4)Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update
5)Press Start
7)When it says PASS In a green Box wait Till reboot is done ....
8)thee remove usb cable from phone
Am i missing something? devilhell007 says that you dont need the bootloader file? Is this file necessary only with certains roms? which roms would that be?
and finally, i've read that some roms, change the file system of the phone, and returning to stock bricks it, does this method prevents and reverts that?
sorry for the noobish questions, big thanks in advance!
Click to expand...
Click to collapse
LoLaTiOn said:
yes bootloader no need after froyo
just for froyo upgrade (to GB HONEY ISC JB uses the same bootloader) no need updating this !!!
it is even not recommended to put bootloader because it is often responsible for Brick
Bootloader is the first step in flash, if you have a conflict on your computer
avoid process, samsung kies, adb, antivirus internet security software and others scan stuff before flash !!!
Click to expand...
Click to collapse
As you can see LoLaTiOn said the same thing.
And bootloader might even brick your phone.So please refrain from doing so.
I hav no idea about it in samsung service center offically.. they use all the files to flash including bootloader even me my self always flashed my phone with all files never bricked... infact with my previous phone i always used bootloader and all files... els u c
Sent from my GT-I9003 using xda premium
the first galaxysl and comes with froyo
That is why we must put the bootloader for an upgrade to gingerbread
after the upgrading not a time of need for clean
understand all ?
if a person is on froyo and does not put the bootloader it will encounter a bootloop only ^^
i totally understand and agreed with you
LoLaTiOn said:
the first galaxysl and comes with froyo
That is why we must put the bootloader for an upgrade to gingerbread
after the upgrading not a time of need for clean
understand all ?
if a person is on froyo and does not put the bootloader it will encounter a bootloop only ^^
Click to expand...
Click to collapse
i totally understand and agreed with you but i am just saying what Samsung engineers thought to there service center technicians and instructed to do as per proper procedure, load all the files and flash it they do this for all the device any Samsung phone down grade up grade or same reflash they do the same sorry if am wrong but am just saying in the official way rest all on us...
I have this phone which has the GB obtained from Samsung web site. I then rooted with J Scott option 2. Since then I dont have messaging. What can I do to get this back? I have an app that I use but not really satisfied with that. Can I go back to Aroyo, or try to download GB again. I tried Kies again, but it doesn;t give me any option to download again. I have read hundreds of pages w/o an answer, followed many links only to have spam loaded to my computer. Thanks for any help.
[email protected] said:
I have this phone which has the GB obtained from Samsung web site. I then rooted with J Scott option 2. Since then I dont have messaging. What can I do to get this back? I have an app that I use but not really satisfied with that. Can I go back to Aroyo, or try to download GB again. I tried Kies again, but it doesn;t give me any option to download again. I have read hundreds of pages w/o an answer, followed many links only to have spam loaded to my computer. Thanks for any help.
Click to expand...
Click to collapse
Get goo app then install cwm or twrp recovery from that. Then download a rom and flash it. First flash an ICS ROM then a JB ROM in that order
Sent from my SAMSUNG-SGH-I317 using Tapatalk
eZdubzitmk4 said:
Get goo app then install cwm or twrp recovery from that. Then download a rom and flash it. First flash an ICS ROM then a JB ROM in that order
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
This is all new to me, but I'll give it a try. I dont see cwm or twrp on Goo? Can you recommend ICS and JB ROM I dont want anything fancy, just a working phone, but then I might want to get fancy. Thanks for your reply.
[email protected] said:
This is all new to me, but I'll give it a try. I dont see cwm or twrp on Goo? Can you recommend ICS and JB ROM I dont want anything fancy, just a working phone, but then I might want to get fancy. Thanks for your reply.
Click to expand...
Click to collapse
Can anyone help with this please? Thanks
[email protected] said:
Can anyone help with this please? Thanks
Click to expand...
Click to collapse
You can go back to Froyo using GTG's Unbrick. Link in my sig. And then you can get Gingerbread here. I recommend option C. If you prefer Heimdall to Odin, there are links to those packages in the ISET thread.
Thank you. I'll let you know what happens.
[email protected] said:
Thank you. I'll let you know what happens.
Click to expand...
Click to collapse
I did the unbrick and messaging appears to be working. SU icon is in the apps but I don't think it is working. I tested with root test from apps store and it said it was rooted. What should I do next? Do I still need to do the second thing suggested above? Thanks again
[email protected] said:
I did the unbrick and messaging appears to be working. SU icon is in the apps but I don't think it is working. I tested with root test from apps store and it said it was rooted. What should I do next? Do I still need to do the second thing suggested above? Thanks again
Click to expand...
Click to collapse
If you're on Froyo and root was successful, then you can stay there. Do the second step if you want to move up to Gingerbread.
jkakkanad said:
If you're on Froyo and root was successful, then you can stay there. Do the second step if you want to move up to Gingerbread.
Click to expand...
Click to collapse
No, I'm still on GB, root is not working to remove the AT&T bloat, and I would like to move up to JB if possible?
[email protected] said:
No, I'm still on GB, root is not working to remove the AT&T bloat, and I would like to move up to JB if possible?
Click to expand...
Click to collapse
Follow the instructions in this thread to move up to ICS or JB. Some of the ICS roms and all JB roms (I think) use the MTD file system so make sure you backup your EFS before making the move upward. There are instructions in the linked thread for making an EFS backup. Make sure to read carefully before you attempt anything.
Of course, the first step is to see if you have a custom recovery. It will be your launch pad to sweeter future.
jkakkanad said:
Follow the instructions in this thread to move up to ICS or JB. Some of the ICS roms and all JB roms (I think) use the MTD file system so make sure you backup your EFS before making the move upward. There are instructions in the linked thread for making an EFS backup. Make sure to read carefully before you attempt anything.
Of course, the first step is to see if you have a custom recovery. It will be your launch pad to sweeter future.
Click to expand...
Click to collapse
How do I find if I have custom recovery?
[email protected] said:
How do I find if I have custom recovery?
Click to expand...
Click to collapse
Power down the phone. Then hold Vol+, Vol-, and the Power button when you turn it back on. Once white SAMSUNG comes up, release the power button. This will take you into recovery. At the top, it will tell you which recovery you have: Android 3e (secure) or red CWM (custom).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----edit----
If you still have stock recovery, then following the link in post #5 and use Odin to flash option C. This will give you GB with root, red CWM, and AT&T bloatware removed.
jkakkanad said:
Power down the phone. Then hold Vol+, Vol-, and the Power button when you turn it back on. Once white SAMSUNG comes up, release the power button. This will take you into recovery. At the top, it will tell you which recovery you have: Android 3e (secure) or red CWM (custom).
----edit----
If you still have stock recovery, then following the link in post #5 and use Odin to flash option C. This will give you GB with root, red CWM, and AT&T bloatware removed.
Click to expand...
Click to collapse
Nothing comes up, it goes on to load the AT&T rethink possible. So I dont have stock recovery?
[email protected] said:
Nothing comes up, it goes on to load the AT&T rethink possible. So I dont have stock recovery?
Click to expand...
Click to collapse
My instructions were a little unclear the first time around. Try again with the instructions below.
1) Power down the phone
2) Hold Vol+, Vol-, and Power
3) When the white SAMSUNG logo comes up, let go of the Power button only. Continue to hold down Vol+ and Vol-.
This should get you into recovery.
jkakkanad said:
My instructions were a little unclear the first time around. Try again with the instructions below.
1) Power down the phone
2) Hold Vol+, Vol-, and Power
3) When the white SAMSUNG logo comes up, let go of the Power button only. Continue to hold down Vol+ and Vol-.
This should get you into recovery.
Click to expand...
Click to collapse
No your instructions were clear to me. I did it again, same result. Thank you for your time.
[email protected] said:
No your instructions were clear to me. I did it again, same result. Thank you for your time.
Click to expand...
Click to collapse
No problem. I'm not sure why the phone won't boot into recovery. I can only speculate but I'm sure there's someone who can shed some light on the issue. If this was my phone, I would flash the UCBL3 Unbrick in Odin b/c it'll re-establish the original partitions, give you GB and root at the cost of losing all the info on your phone. Then you can use flash a custom kernel to get red CWM. From there, you can move on to ICS or JB. Let me know how things turn out.
jkakkanad said:
No problem. I'm not sure why the phone won't boot into recovery. I can only speculate but I'm sure there's someone who can shed some light on the issue. If this was my phone, I would flash the UCBL3 Unbrick in Odin b/c it'll re-establish the original partitions, give you GB and root at the cost of losing all the info on your phone. Then you can use flash a custom kernel to get red CWM. From there, you can move on to ICS or JB. Let me know how things turn out.
Click to expand...
Click to collapse
The last thing I did was the UCBL3 unbrick in Odin, so should I do it again or flash the custom kernel to get red CWM? Thanks
[email protected] said:
The last thing I did was the UCBL3 unbrick in Odin, so should I do it again or flash the custom kernel to get red CWM? Thanks
Click to expand...
Click to collapse
Flash a custom kernel
jkakkanad said:
Flash a custom kernel
Click to expand...
Click to collapse
I bet you knew I was going to say this ....... How do I do that? Thanks
I really do think these videos should be sticky'd in the forums
Simple search on Youtube ''How to root the samsung infuse 4g''
This video showing how to upgrade to stock 2.3.6 rooted with a custom recovery
This video showing how to upgrade from 2.3.6 to 4.0.4
This video showing how to upgrade from 4.0.4 to 4.1 and up
There is also this Super Everything thread from a while ago with links to everything needed to root and install recoveries with instructions. I highly recommend reading ALL OF IT before proceeding as it answers almost any question you could have and then some
Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.
Code:
*** Disclamer
-- * Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BeanStalk 7
CyanogenMod 14.1 based
Quicker system animations
Trimmed down fat and excess bloat
Option to enable all widgets
Numerous extra lockscreen options
LCD Density
Custom original BeanStalk Wallpapers by skyliner33v
Custom BeanStalk bootanimation by skyliner33v
3-minit battery support
Clock and date options
Contextual Header - Original and Polygraphic
Battery styles - Includes specific colors and styles. Also includes battery bar
Do not disturb option
Show notification count
Recent screen options
Customizable navigation bar
Use Omniswitch as default recents
Built-in screen record
Toast animations
App Circle bar
Gesture Anywhere
Disable FC warnings
Disable Immersive message
Force expanded Notifications
Configure scrolling cache
Build.prop MOD options to enable/disable tweaks as preferred
Less frequent Notification sounds options
CRT screen off/on options to specify how the animation shows
Enable/disable wake up on charge option
Superuser fully embedded into the build and accessed from settings menu
CM Performance options and features
Hide superuser icon
Developer options and advanced reboot enabled by default
Numerous cherry-picks and improvements throughout the build, baked into the
awesomeness of existing CM layout.
Numerous other options hiding throughout the build.
Magisk
Click to expand...
Click to collapse
Bugs
Same as LOS.
Click to expand...
Click to collapse
Installation instructions
* -- Flash rom zip from twrp.
* -- Flash opengapps zip from twrp.
* -- Reboot and wait for a while.
Click to expand...
Click to collapse
Download
Here
Click to expand...
Click to collapse
GAPPS
Open Gapps
Click to expand...
Click to collapse
Changelog
Code:
5/13/17 - New update. May security updates!
4/21/17 - Weekly update. May be switching to an every other week or monthly build schedule.
4/15/17 - Updated to 7.1.2, april security patches.
4/14/17 - Weekly update.
4/9/17- Weekly update.
4/1/17 - Initial release.
Thanks To/Credits
Code:
LOS: https://github.com/LineageOS
Beanstalk: https://github.com/scotthartbti
XDA:DevDB Information
Beanstalk, ROM for the AT&T LG G3
Contributors
redbeard1083
ROM OS Version: 7.x Nougat
Version Information
Status: Beta
Beta Release Date: 2017-04-01
Created 2017-04-01
Last Updated 2017-05-13
Click to expand...
Click to collapse
mine
Reserved
Mine Mine Mine!
Has anyone flashed this rom yet and if yes do ya have any feedback for the rest of us
Sent from my LG-D850 using Tapatalk
Ive installed and been using this ROM. Pretty smooth so far
Have created a telegram group to discuss the features and future improvements in this ROM. Please feel free to join
https://t.me/joinchat/AAAAAAybqlHeCOdDa7TThw
I couldn't find the CRT screen off/on option. Where is it?
new build is up.
new build is up.
whats in the new build, any changelogs please?
I can't make a new post in the troubleshooting and help section in XDA so I'm hoping someone can help me out.
I am stuck on a rom and have no root, recovery or Sim.
I flashed a rom last week being a 7.1 rom and without thinking, I used Aroma Installer and I ended up losing root, recovery and my phone isn't reading my sim. I've tried using Kingroot as well as Kingoroot but to no avail. So pretty much my phone can only be used as a wifi device.
I have tried using ADB and Fastboot, both will respond to commands, but won't read my device....I do have the latest driver's installed...But when I connect my phone to the computer I get a notification telling me that the drivers weren't installed properly..And when I go into device manager I see that the device is there but with an exclamation mark with it...Now what doesn't make sense is the fact that it can read the internal storage and DCIM on the phone (D850) but I can't get it recognize Fastboot or ADB.. even when I tried a couple of root programs it still didn't even read my phone. Am I not doing something wrong? Now it's not my computer, it's my wife's and I don't want to install things and mess with her system settings just to get my phone to read right hopefully someone can point me in the right direction, I hope I can get Fastboot somehow working and possibly just flash the D850 radio.img so I have cell service again.
Any help with this would be greatly appreciated.
I have tried stump root, which won't work because I'm on a 7.1 rom and not completely stock.
My phone works fine, except I don't have data nor root or twrp, so flashing back to my last backup won't work...
I would really like to get my radio back..If I can somehow flash that in some sort of way I would be happy with that and I can figure the other things later. I just need a working phone so I can call and text. Is there a way I can copy and paste a radio image into a system directory without root?
If so, which directory would I need to paste it to?
Excavator2015 said:
I can't make a new post in the troubleshooting and help section in XDA so I'm hoping someone can help me out.
I am stuck on a rom and have no root, recovery or Sim.
I flashed a rom last week being a 7.1 rom and without thinking, I used Aroma Installer and I ended up losing root, recovery and my phone isn't reading my sim. I've tried using Kingroot as well as Kingoroot but to no avail. So pretty much my phone can only be used as a wifi device.
I have tried using ADB and Fastboot, both will respond to commands, but won't read my device....I do have the latest driver's installed...But when I connect my phone to the computer I get a notification telling me that the drivers weren't installed properly..And when I go into device manager I see that the device is there but with an exclamation mark with it...Now what doesn't make sense is the fact that it can read the internal storage and DCIM on the phone (D850) but I can't get it recognize Fastboot or ADB.. even when I tried a couple of root programs it still didn't even read my phone. Am I not doing something wrong? Now it's not my computer, it's my wife's and I don't want to install things and mess with her system settings just to get my phone to read right hopefully someone can point me in the right direction, I hope I can get Fastboot somehow working and possibly just flash the D850 radio.img so I have cell service again.
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
Download your stock TOT or KDZ rom download LG flash tools and try to restore your phone! If that will not work this method will BUT follow instructions to a T and be careful I use this method on phones that have the anti roll back so can downgrade to root
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
The computer won't read my device in download mode...But it reads ADB with the phone turned on and on the home screen. .
Excavator2015 said:
The computer won't read my device in download mode...But it reads ADB.
Click to expand...
Click to collapse
try installing twrp with the official twrp app from playstore and if it works try to flash super user thru twrp might help but cant hurt or try stump root
1. Go Here
2. Download and install Stump root
3. Run Stump root - you are now rooted
4. Go to playstore and downlaod SuperSU
5. Install Super SU
6. Uninstall Stump Root
You now have root!!
To check,
Download root checker from play store and check for root
twrp with the official twrp app from playstore and if it works try to flash super user thru twrp might help but cant hurt
I've tried Kingoroot, and Kingoot...To no avail I'm stuck on Cosmos Os. Is there any way I can install SuperSu through ADB? Now remember ADB nor fastboot work through download mode...The computer doesn't see it.
Stump root doesn't work...I can't install super su thru twrp app..I'm not rooted.
rogerssnpy said:
Download your stock TOT or KDZ rom download LG flash tools and try to restore your phone! If that will not work this method will BUT follow instructions to a T and be careful I use this method on phones that have the anti roll back so can downgrade to root
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
Where can I get the KDZ Rom for beanstalk 7? Or can I just pull my TWRP backup from my phone and just restore it that way? Will I need to create a zip for that, I'm not sure how the backup is configured...I have looked at the folder that my backup is in...But when I open it up there's multiple files in it...Including user data recovery and whatnot. Now if I have to make a zip for the restore how do I do it?
And lastly, will I have to have download mode working? As I can't get it to work while I am in download mode, I can send commands in ADB like rebooting bootloader, but when I go into fastboot and trying to send commands, it says waiting for device. I'm lost with this thing...I should have just flashed the micro open gapps and been done with it.
I'm hoping you can help me out, maybe there's a way around this without pulling my phone apart to do this.
Need to download your phones factory rom using lg flashtools
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
I'll explain when get home at work atm should be around 9pm est
rogerssnpy said:
Need to download your phones factory rom using lg flashtools
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
I'll explain when get home at work atm should be around 9pm est
Click to expand...
Click to collapse
How can I get a working lg flashtool...Everytime I've used that thing..It opens with something about a username and password...It won't open straight into the tool.
Can you provide me with a working file? Or at least direct me to a site with a working file without the username and password version? Will download mode have to work? The computer doesn't see the device when it's in dl mode...It tells me after trying to install the drivers that they weren't downloaded properly.
---------- Post added at 02:01 AM ---------- Previous post was at 01:51 AM ----------
rogerssnpy said:
Need to download your phones factory rom using lg flashtools
---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------
I'll explain when get home at work atm should be around 9pm est
Click to expand...
Click to collapse
Ok sounds good, the wife and I are going out to see a movie, if you can, can you just PM me directly? And when I get home I will see your message. Thank you man!
as this thread is clearly more useful as a troubleshooting section and there's little interest in the rom, i'm going to switch maybe monthly builds on this. we'll see how it goes.