I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://forum.xda-developers.com/showthread.php?t=2559715
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Return to stock
steveh_131 said:
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
Click to expand...
Click to collapse
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
asilva54 said:
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Thank you, didn't see that when I searched last time.
ZOMBIExM4STER said:
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
Click to expand...
Click to collapse
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
steveh_131 said:
Thank you, didn't see that when I searched last time.
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
Click to expand...
Click to collapse
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
ZOMBIExM4STER said:
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
Click to expand...
Click to collapse
I will try, but I am not an expert by any means. I tinker, but hopefully these other more experienced guys will chime in if I say something incorrect.
1. Download odin from here: http://www.firmware-files.com/download.php?id=1&token=QDXtLX5r3hLhxpTt604CYR6zP9twKSmr
2. Extract odin to a folder on your computer
3. Download these four files:
http://www.firmware-files.com/download.php?id=8&token=1QMc777QYjZgceInVMKs1HlcxAWv2wrU
http://www.firmware-files.com/download.php?id=7&token=6AfQkrv4S1mjr2oClQdwHp62lZpT8BK5
http://www.firmware-files.com/download.php?id=6&token=rXopUUlOTAGrBAQfksBLl1lKu52xIjl0
http://www.firmware-files.com/download.php?id=15&token=5CYaBqGOCoJSQMM6K7WECGlLDK4NYWTT
4. These four files will be zipped. You need to extract the zip files somewhere onto your computer. Each file should have a .tar.md5 extension once you extract them.
5. Power off your phone. Put it into download mode. To do this:
Power off your phone completely'
Hold down the home button, volume down button and power button all at the same time
When the screen comes on, let go of the buttons
It will give you a warning. Press the volume up button to proceed to download (odin) mode.
6. Run the Odin3 v3.09.exe application (that you extracted in step 2)
7. Now that odin is running and hopefully connected, you need to specify the four files that you extracted to be downloaded. You should end up with a screen that looks 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"
}
8. Click start and let it run until it is finished. Once it is finished, hold down the power button to power off your phone then do the same to turn it back on. The custom icon should be gone.
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Rukbat said:
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Click to expand...
Click to collapse
Doesn't factory reset delete the Xposed framework?
With AT&T you can't do a walk-in exchange after 14 days - pretty scary to mail it in for exchange and risk a $650 charge when they discover you rooted it.
I had the icon turned off with Wanam, but it came back.
steveh_131 said:
Doesn't factory reset delete the Xposed framework?
Click to expand...
Click to collapse
I could probably write an accounting program for an agency as large as the US government (or have fixed the health insurance site - doing something for half a century does pound some knowledge into even rock hard heads like mine), but when it comes to Android, I'm one of the learners, not one of the teachers. You know the answer to this question better than I do. I'd assume it does. I've made a lot of stupid assertions over the years, so ...
I downloaded a course that I may start reading one of these days, so I might yet learn enough to write a "Hello, World" app for Android. (Programmers know what I'm talking about - the difference between being able to develop a program and being able to code something to run in a particular environment - and the only internal environment I know in Android is where the battery and cards go.)
With AT&T you can't do a walk-in exchange after 14 days
Click to expand...
Click to collapse
SSSSSSHHHHHHHH!!!!!!! You weren't supposed to tell them that. I hope they didn't read this thread, and I hope the very nice lady who gave me the phone I'm using now doesn't get into trouble. (I'm not talking about walking in and saying "I don't like this phone, may I have a different one, please?" I'm talking about walking in during the warranty period and saying "could you please make my phone work?" and being told that they'll have to give you another phone. The only thing I'd trade my N3s for is N3s with unlocked bootloaders. I just want to see something other than comets revolving around Samsung's name.)
I had the icon turned off with Wanam, but it came back.
Click to expand...
Click to collapse
Mine stayed off - for the 3 or 4 days that the hardware didn't die on me. Then ... well, maybe Samsung has a way to read melted silicon, or whatever it did to make itself electrically invisible, but I'm not going to worry about it.
Wanam will keep the icon hidden but once you factory reset the phone I believe it deletes the xposed framework and the icon comes back.
I could be wrong about that, but that is my understanding.
I don't think you'd ever fool the warranty department that way, unfortunately, which is why I used this method.
Sent from my SAMSUNG-SM-N900A using Tapatalk 2
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
ryant100 said:
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
Click to expand...
Click to collapse
No custom and no lock. I didn't run a root check, not even sure how.
The files are small because you're not flashing an entire ROM. My ROM was still stock.
Related
WARNING
DO NOT FLASH ON BELL ATRIX
If you appreciate this guide, please visit my website (maybe check out my sponsors!), subscribe on Twitter, press the thanks button below, or donate to Fixter, DesignGears, Fenny and other great helpers/devs for the Atrix 4G.
Download
1.2.6
http://bandbinnovations.com/Atrix.7z
Password: atrixbl
1.5.2
HTTP (Rename from .rar to .gz)
HTTP (Rename from .rar to .gz)
MultiUpload
Hotfile.com
DepositFiles
UPDATE: Linux SBF guide here --> http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html --> Thank you "relaxed"
Flash Guide (Instructions)
Prerequisites
Download RSDLite 5.0 (MediaFire mirror)
Install the program
Download SBF file from above links
Bricked phone or test device
Fully charged device
Drivers installed (if you rooted your phone, your computer has the necessary drivers)
32-bit
64-bit
Problems
Some users experiencing WiFi connectivity weirdness
SIM-unlocked devices may still have WiFi problems
Market might not show all applications (easy fix on the way)
Do not flash this file unless absolutely necessary. It will help those who’ve bricked their device to recover, but this is not for flashing just for fun. BriefMobile cannot be held responsible for device damage due to this guide.
Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .gz file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Congratulations!
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
designgears said:
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
Click to expand...
Click to collapse
Good tip! Didn't know that!
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
tianqi said:
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
Click to expand...
Click to collapse
Yes. This isn't a confirmed issue, but others have experienced WiFi problems with this SBF flash over their SIM unlocked devices.
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
cellzealot said:
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
Click to expand...
Click to collapse
That's very odd. Mine most definitely shows as "NS Flash Olympus."
im a noob sorry, but what does this actually do?
fRenZy-_- said:
im a noob sorry, but what does this actually do?
Click to expand...
Click to collapse
If you mess around with your device and break it, this can save your life by unbreaking it!
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
kennethpenn said:
That's very odd. Mine most definitely shows as "NS Flash Olympus."
Click to expand...
Click to collapse
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
cellzealot said:
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
Click to expand...
Click to collapse
Thanks for the info! Duly noted... editing the post.
jimmydafish said:
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
Click to expand...
Click to collapse
100% positive I purchased my device retail. I'll screenshot the RSD Lite for you in a moment when I recover from my soft brick (screwed up framework-res).
RSD Lite reports "NS Flash" for me too
{
"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"
}
purchased through Amazon
kmiller8 said:
RSD Lite reports "NS Flash" for me too
purchased through Amazon
Click to expand...
Click to collapse
Perhaps "NS Flash" does not mean developer phone on the Atrix?
kennethpenn said:
Perhaps "NS Flash" does not mean developer phone on the Atrix?
Click to expand...
Click to collapse
Or maybe we both got incredibly lucky is there any way to further verify if RSD Lite is reporting incorrectly?
Also off topic, why is the "Start" grayed out for me?
mine also says NS, purchased directly from AT&T
start is greyed out if there is no file/an incorrect file to flash, notice that the file properties pane is blank, it has not actually loaded the file in the select box in that screenshot
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
Mainly just recovers you from a soft-bricked or improperly hacked device. It flashes you back to stock (or as close to stock as we have right now.)
No new features. No bug fixes. Nothing different from stock except a few new possible issues.
tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
It changes some stuff, but I can hardly see anything different at face value.
First few things: I've searched already, can't find any similar threads that actually help. I have the international version. I was running the CM10.2 Rom prior to 'the accident'. I will put a bounty on this if I have to.
There's a bit of a story to this so I'll go over it all - not sure what's relevant.
I've been running out of storage for days, a 64GB SD card is in the mail. I currently have an 8GB one as well as the internal 16GB, both of which were near full, but the external one had relatively more than the internal one, so I decided to use foldermount and link2SD to move some space over. That all went fairly well.
This morning I got invited to the Aviate Beta launcher, which looked interesting. Tried to install, didn't have enough space. So I decided to make a backup of Nova, go into the play store, uninstall nova to free up space and then install Aviate without leaving the playstore. It worked, turns out I don't like Aviate much, so I worked backwards. Uninstalled Aviate, went to install Nova. Not enough space (idk how). Uh oh.
So I deleted some less-necessary apps that I could reinstall later. Not enough storage. Notification comes up in the bar along the lines of "storage critically low, device may malfunction". Now whenever I attempted to enter settings, the process crashed. Great. Simple fix, flash a NANDroid back-up in CWM. I can't remember what the message was, but there was something wrong with the back-up.
Wiped everything and tried to flash CM10.2 from the external SD Card but it wouldn't mount. Data also wouldn't mount. I tried several SD Cards ( ie about 10, different brands, sizes, classes, etc out of hope). So I decided I'll open up and Odin and just re-do everything per /showthread.php?t=2387980.
Turn the phone back on, stock Jelly Bean lockscreen was there, and once unlocked only the notification bar was there (no launcher). So I used different versions of Odin, different cables, downloaded the image several times, etc etc. Nothing fixed it. In fact, it's worse now. after booting past the Samsung logo, the screen just goes black now. smh
Can anyone help? It would be extremely appreciated. It's also a time sensitive issue as I need the device for work on Monday.
Sorry if I've missed anything. Yes I'm a noob, but you great people at XDA have helped a lot of people out before so I'm hoping you can help me.
Thanks!
Sorry to bump...
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
tiskael said:
... getting pretty desperate. $50 for anyone who can provide information that leads to the fixing of the device by the end of the day (AEST). Paypal or bank transfer. PM me or post below.
EDIT: 101 views and no-one knows anything? If you know it's unrecoverable, please say so.
Click to expand...
Click to collapse
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Devo7v said:
I'm going to assume you have the i9295, but have you tried Kies? I want aware that there was an Odin package for your phone.
Click to expand...
Click to collapse
Yes, the i9295 - the international version. The Odin md5 can be found on this thread: /showthread.php?t=2387980.
Sorry if this sounds rude (it's not, I just don't know how to use kies) but what's that supposed to do? I can't find a way for Kies to fix anything... I tried this thread: /showthread.php?t=1984717 but when I have to enter my phone model (GT-i9295) it says "Please check the model name and enter it" and closes the pop-up window within kies. Any more help?
Thanks for trying so far.
Sorry for bumping but i need this fix. $100 to the first person who can fix this by Monday.
I can't possibly believe that no-one knows how to fix this, or at least whether it's fixable or not. Is anyone willing to answer my question?
Check this threads or ask the guys who helped me there, they are Awesome
So after boot you get an totally black screen? Only theorigial Samsung boot logo before it turns dark?
I had this problem twice, but can you tell me if you start the phone after the dark screen do you have sound (like the phone still works, but only no screen) or nothing?
The first time i had sound, need to say that i never solved this problem, re-installed stock firmware, (recovery still works, you only need to know wat to puch) Unrooted my phone, and send it in for waranty, They send me a new phone, never know what was the problem, it can be o broken screen, but i never believed it totally... check this thread for that: http://forum.xda-developers.com/showthread.php?t=2363185&page=9
The other time i had this i installed a other CWM Recovery Version, i had one installed, but some problems with it, installed an other version, after Reboot the Same Samsung Logo...Dark screen, installed this CWM: http://forum.xda-developers.com/attachment.php?attachmentid=2464887&d=1387533161
Good Luck with it M8
Here is something that could/couldn't help you...
I am not sure/not tested this so i am not responsible for anything that happenes to your phone
1.DOWNLOAD A STOCK FRESH SAMMY ROM FROM SAMMOBILE
2.Use odin3.7
3.Open ODIN AND CHOOSE PDA THEN CHOOSE THE FIRMWARE YOU EXTRACTED /DOWNLOADED
4.Now flash the firmware
5.When reached at the state you previsouly in reboot to download mode again and do step 3 again
6.Now download the pit file from HERE
7.In odin screen make sure 3 buttons are checked F.rest time , auto reboot , REPARTITION
8.Now choose frimware in pda
9.CHOOSE THE FILE YOU HAVE ALREADY DOWNLOADED FROM ATTACHMENT IN SIDE THE PIT BOX LIKE THE PICTURE UNDER
{
"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"
}
10.hit start and let the device flash like normal
11.it will auto reboot ...hope this fixes your issue
THE PIT FILE IS CALLED i9295.pit and is from here
HERE IS SOME INFO ABOUT PIT FILES
What are pit files ?
A pit file is a kind of file often used in samsung phones / tablets , these files contain partition tables of the device and the spaces of them with the arragment of each partition with there corresponding mount points ; these files can difenitly dangerous and can kill your tab/phone with a breeze if not used with care
Click to expand...
Click to collapse
What do pit files really do ?
Pit files can help in fixing a broken mmc for ex:
Click to expand...
Click to collapse
NOTE: I AM NOT RESPONSIBLE IF THIS WILL MAKE THINGS EVEN WORSE
make a try and let me know
try this too..
When my DATA is not mounting, i feel bad as well for in my case, i can't do what mythi's solution by flashing PIT file and stock rom using odin, coz my usb port isn't functioning anymore.. in short, my phone is just charging and not syncing to PC anymore... what i did is go to cwm, tried to mount /data there but gives me an error... what i did next is format /data and /data/media (/sdcard) then flash the new cm11 KITKAT they just finished building... reboot, waited for 2 min or so, boom my phone is back to life..
I thought I should share my findings regarding the downgrade process.
It's a long tutorial, but I listed every step for newbies too.
Biggest issue I had with it - is that the phone constantly downloaded the LL update, no matter what. So here is the solution:
I have used my phone with this setup for the past few days, and it did not download the LL update.
Now I can use my phone on trip, during work, and only lose a few %. Back with LL I lost all my battery even with a few hours of use.
The battery life is pure GODLY now.
Downgrading does NOT trip Knox!
Preparation...
- Download ODIN 3.09 and the latest KitKat firmware for your variant from Sammobile.com.
- Uncompress the firmware file.
- Do a full backup of your phone and your SD card files by copying over everything to your PC and by using Super Backup app. No promo, I just used this one and it works wonderful. (For Contacts, SMS, etc.)
Install phase ONE...
- Power off your phone.
- Enter Recovery Menu, by holding VOLUME_UP + HOME + POWER.
Once you see the Samsung logo, release Power, keep holding the other two.
An Android mascot will pop up.
- Navigate with volume keys, and power. (power is "ok", volumes are up and down.)
- Go into "Wipe Data", wipe.
- Press reboot, then turn off your device once it boots.
Install phase TWO...
- Remove your back cover, remove SD card (just in case), remove SIM card.
- Keep battery, of course (lol).
- Boot phone in DOWNLOAD mode by holding VOLUME_DOWN + HOME + POWER.
- Connect your phone to PC, launch ODIN, load the unpacked firmware with the "AP" button.
Do not touch other buttons and switches.
- Press "Start", wait until your phone reboots.
Install phase THREE...
- After your phone booted, DO NOT CONNECT TO WIFI or INSTALL YOUR SIM CARD.
- Turn off wifi, make sure it DOES NOT CONNECT and DID NOT CONNECT TO ANY WIFI NETWORK!!!
- Go into Settings -> About Phone -> Software Updates. Untick "check for updates".
- Turn off your phone.
- Add a DATA SIM CARD. That can connect to mobile networks.
- Boot phone.
- Once it is booted, you will see that the phone will check for updates.. (yeah, to hell with our settings)*
- Open the notification, and you can find an option "NEVER REMIND ME".
* If it does not check, you can do it manually BUT ONLY IF YOU HAVE A DATA SIM CARD INSTALLED!
Then you can see what update you have, and whether you want to download it. Some people reported there are patches for KitKat on some regions.
DONE. You just outsmarted the evil Samsung. Good job.
- If you have your sd card installed, everything in place, you can now connect to wifi.
- Install/recover stuff, set up things, etc. You are good to go.
Ps.: If you are a Samsung employee, please, don't screw us over by force shipping some sneaky OTA to our devices. We do like to have choice what / which version we run, etc. Forcing crap down our throats is not really a nice way to treat customers.
... Reserved ...
h8Aramex said:
I thought I should share my findings regarding the downgrade process.
It's a long tutorial, but I listed every step for newbies too.
Biggest issue I had with it - is that the phone constantly downloaded the LL update, no matter what. So here is the solution:
I have used my phone with this setup for the past few days, and it did not download the LL update.
Now I can use my phone on trip, during work, and only lose a few %. Back with LL I lost all my battery even with a few hours of use.
The battery life is pure GODLY now.
Downgrading does NOT trip Knox!
Preparation...
- Download ODIN 3.09 and the latest KitKat firmware for your variant from Sammobile.com.
- Uncompress the firmware file.
- Do a full backup of your phone and your SD card files by copying over everything to your PC and by using Super Backup app. No promo, I just used this one and it works wonderful. (For Contacts, SMS, etc.)
Install phase ONE...
- Power off your phone.
- Enter Recovery Menu, by holding VOLUME_UP + HOME + POWER.
Once you see the Samsung logo, release Power, keep holding the other two.
An Android mascot will pop up.
- Navigate with volume keys, and power. (power is "ok", volumes are up and down.)
- Go into "Wipe Data", wipe.
- Press reboot, then turn off your device once it boots.
Install phase TWO...
- Remove your back cover, remove SD card (just in case), remove SIM card.
- Keep battery, of course (lol).
- Boot phone in DOWNLOAD mode by holding VOLUME_DOWN + HOME + POWER.
- Connect your phone to PC, launch ODIN, load the unpacked firmware with the "AP" button.
Do not touch other buttons and switches.
- Press "Start", wait until your phone reboots.
Install phase THREE...
- After your phone booted, DO NOT CONNECT TO WIFI or INSTALL YOUR SIM CARD.
- Turn off wifi, make sure it DOES NOT CONNECT and DID NOT CONNECT TO ANY WIFI NETWORK!!!
- Go into Settings -> About Phone -> Software Updates. Untick "check for updates".
- Turn off your phone.
- Add a DATA SIM CARD. That can connect to mobile networks.
- Boot phone.
- Once it is booted, you will see that the phone will check for updates.. (yeah, to hell with our settings)
- Open the notification, and you can find an option "NEVER REMIND ME".
DONE. You just outsmarted the evil Samsung. Good job.
- If you have your sd card installed, everything in place, you can now connect to wifi.
- Install/recover stuff, set up things, etc. You are good to go.
Ps.: If you are a Samsung employee, please, don't screw us over by force shipping some sneaky OTA to our devices. We do like to have choice what / which version we run, etc. Forcing crap down our throats is not really a nice way to treat customers.
Click to expand...
Click to collapse
Very well explained. I will keep this in mind if Lollipop doesn't start to get any better in the next update... ARG SAMMY WHY DID YOU DO THIS!
good write up. In addition, in your "Install phase THREE..." go to settings>applications manager> disable the "software update". - the one with green icon... this will stop the phone from upgrading to LP.. and you can skip the last part of your tutorial.....
{
"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"
}
xdm9mm said:
good write up....
Click to expand...
Click to collapse
I tried this one, but the update still showed up.
The only way was for me, is to tap on that "never remind me again" thing.
Oh well, if you had luck this way, that's fine too (at least we have a workaround handy if the original tutorial does not work for someone.)
Ps.: I hope the 5.1. update will fix all the issues (especially battery wise).
Though... the S6 5.1 update was a let down.
Perfect tutorial man for those beginners. But I thought you might want to add in one thing. When you originally flash KK there will be a small 100+MB update that needs to be done. As it was said in the XDA TV video its for a battery issue. Once that downloads and reboots to install, go right back into the Settings->About Phone->Software updates and uncheck auto updates.
Well. I was really tired when I read your reply and I could not remember if I ever updated adter the flash. Turns out I did, and now I have L coming down once again. Oh my.
Did a Nova backup, Super Backup, and I will reflash on the weekend. And now I will have to charge my power bank, and prepare a mobile charging cable too. Oh good times...
h8Aramex said:
Well. I was really tired when I read your reply and I could not remember if I ever updated adter the flash. Turns out I did, and now I have L coming down once again. Oh my.
Did a Nova backup, Super Backup, and I will reflash on the weekend. And now I will have to charge my power bank, and prepare a mobile charging cable too. Oh good times...
Click to expand...
Click to collapse
Sorry about that, I know the feeling, I did that a few weeks ago myself. Hoping there was a 5.1.1 update, But turns out I couldn't dismiss the update once it checked.
Guys 'coming stupid question'
If I want to downgrade ti kk do I nedd zo check or unchek re-partition? And what about Bootloader?
Thanks..My lolipop have too much lags and battery drop too fast...
Jovan1997 said:
Guys 'coming stupid question'
If I want to downgrade ti kk do I nedd zo check or unchek re-partition? And what about Bootloader?
Thanks..My lolipop have too much lags and battery drop too fast...
Click to expand...
Click to collapse
I just do a factory reset in L, then keep the stock options on ODIN. That worked for me.
cash2387 said:
Perfect tutorial man for those beginners. But I thought you might want to add in one thing. When you originally flash KK there will be a small 100+MB update that needs to be done. As it was said in the XDA TV video its for a battery issue. Once that downloads and reboots to install, go right back into the Settings->About Phone->Software updates and uncheck auto updates.
Click to expand...
Click to collapse
Ok, so since I had to reinstall the phone, I tried what you said.
Well, I only get the L update, after it checks for updates... No small update or anything.
I used this firmware: http://www.sammobile.com/firmwares/download/44754/N910CXXU1BOC3_N910COXX1BOC1_XEH/
N910CXXU1ANK5_N910COXX1ANK2_N910CXXU1ANK5_HOME.tar.md5
Maybe some regions do have small patches for battery issues (even on Kitkat)... or some regions don't have this "latest KK" as md5 file.
Could be the difference in versions your right.I used this one to go back to 4.4.4. It's the AOA1 build for my carrier
http://www.sammobile.com/firmwares/download/42501/N910W8VLU1AOA1_N910W8OYA1AOA1_ESK/
I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?
ucallmebobby said:
I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?
Click to expand...
Click to collapse
Yes, I have read the Sprint forum (I was searching for something else on Google), and some people did complain about that.
It's the bootloader or something.
Well, I am pretty sure it's possible to downgrade... somehow.
(The S4 Mini got the same problem. Once you are on 4.4, you cannot downgrade, it will just fail at the end of the process.
For God knows what reason.)
Uhm... make a thread in the Sprint forum, and if someone got his Knox tripped, he can try the reformat and other options to flash the KitKat rom back. (Well, even if he succeeds, we won't know whether those checkboxes will trip knox or not. There is just no way to tell. Knox should _not_ be tripped when flashing official firmwares.)
ucallmebobby said:
I saw someone else post on another thread that you can't downgrade from BOF5.
This is on Sprint.
Is that true?
Click to expand...
Click to collapse
Please dont make another thread in the Sprint forum pertaining to downgrading to KK after being on OE1 bootloader and up.
Theres too many already and its been answered numerous times when OE1 first came out. I replied to your Question in the other thread about going to KK from LP and with you being on OF5, as of right now, its not possible and Odin will prevent you from bricking your phone, giving you an auth error.
hi my friend, i am in 5.0.1 lollipop with DBT Firmware CSC N910FXXU1BOC3. It is save to downgrade without trip Knox counter? Can you tell me the kitkat version who download?
I did this to my Note Edge too....LP is garbage and people praise it? I guess newer is not better...great tutorial though. Its people like you that take the time and do things like this that makes the world a little better place.
I'm only getting a NAND write start /fail error message. My phone has been doing some goofy stuff lately. Screen locks up (blank) and nothing responds. I get the menu lights for a sec and then they are gone. Plug the phone into the pc leave it for a few minutes and everything comes back. Dunno if that is a software or hardware issue.
Hi again,
it's impossible to downgrade to 4.4.4 from 5.1.1 AFAIK (in N910C)
thanks sammy for your locked bootloaders...
amd-dude said:
I'm only getting a NAND write start /fail error message. My phone has been doing some goofy stuff lately. Screen locks up (blank) and nothing responds. I get the menu lights for a sec and then they are gone. Plug the phone into the pc leave it for a few minutes and everything comes back. Dunno if that is a software or hardware issue.
Click to expand...
Click to collapse
so, it is success to flashing the 4.4?
could you please advise about it?
thanks
After a series of poorly judged flashes and (eventually) factory resets in the name of acquiring root, I am left with a stock S6 that gets no service whatsoever. Knox is tripped. The phone shows 5 bars but will not connect to 4G, GSM, CDMA, nor will it send/receive anything unless it's connected to Wifi and uses wifi calling.
I've been trying to fix this since 11pm last night and I am extremely frustrated. I would love to pay someone who has a clear understanding of these things to hold my hand through getting this thing working again. I have passed the point where my skills can help me.
Hi do you have facebook
Sent from my SM-G800H using Tapatalk
Have you put in your phone companies apn settings ?
Have you tried to Odin back to stock? It sounds like you flashed a custom recovery; what exactly did you do?
Yes, the APN settings are correct. I entered them manually in a second profile, but they were prepopulated as well. Neither makes a difference. I get "Not registered on network" when I try to make a call. When I try to have the phone detect TMobile's network, it says "Unable to select network. Select automatically".
The big issue is, I'm fairly certain the first thing I flashed was not meant for this phone...smh. I was able to Odin back to stock. Before and after multiple factory resets and cache wipes (though no settting for Dalvik cache in recovery...does this mean anything?) everything works fine except I have no service.
Try and toggle Airplane mode on and off? Also if you were on Wifi with Wifi calling disable both of those for the time being. Last case would be to odin factory firmware.
yes, i've tried that. i've tried removing the sim card for a few minutes to no avail.
with wifi and wifi calling on, the phone functions as normal but as soon as that's off, everything stops working.
I don't trust Odin to wipe everything it should.
Download a rooted stock rom. Then go into recovery, mount /system and wipe /system, cache & data, then flash the rom. Finish the setup wizard and try to make a call without wifi. If you cannot, verify APN is correct.
You could have a bad sim card. Sim cards die just like any other piece of electronics. Go to T-Mobile and swap sim cards, they should do it for free.
Edit: I just realized you are probably still on stock recovery. Root your system, flash twrp, then nuke the phone in recovery and start from scratch.
I assume you already tried restoring a nandroid. If that doesn't work and you can't make calls after restoring via Odin or flashing another rom, then you may have corrupted the EFS partition. The only way to recover from that is if you backed up your original EFS partition. A lot of people don't bother, but it is a critical step before flashing your first mod.
..
thank you so much for the advice. i'm trying this now.
OMGitsAlize said:
Have you put in your phone companies apn settings ?
Click to expand...
Click to collapse
socal87 said:
Have you tried to Odin back to stock? It sounds like you flashed a custom recovery; what exactly did you do?
Click to expand...
Click to collapse
Saafir said:
Wouldn't hurt to give Update Profile a go under System Update too.
Click to expand...
Click to collapse
this option does not exist for me
sublimaze said:
I don't trust Odin to wipe everything it should.
Download a rooted stock rom. Then go into recovery, mount /system and wipe /system, cache & data, then flash the rom. Finish the setup wizard and try to make a call without wifi. If you cannot, verify APN is correct.
You could have a bad sim card. Sim cards die just like any other piece of electronics. Go to T-Mobile and swap sim cards, they should do it for free.
Edit: I just realized you are probably still on stock recovery. Root your system, flash twrp, then nuke the phone in recovery and start from scratch.
I assume you already tried restoring a nandroid. If that doesn't work and you can't make calls after restoring via Odin or flashing another rom, then you may have corrupted the EFS partition. The only way to recover from that is if you backed up your original EFS partition. A lot of people don't bother, but it is a critical step before flashing your first mod.
Click to expand...
Click to collapse
okay, i do think it's possible that i corrupted the EFS partition. however, in download mode, the IMEI number it displays is correct.
i am able to get the phone rooted and twrp installed, but once i try to flash the rooted stock rom, i get a "error executing updater binary in zip". not sure how to proceed.
i may abandon the phone altogether and just order an insurance replacement :-/
postmastergeneral said:
okay, i do think it's possible that i corrupted the EFS partition. however, in download mode, the IMEI number it displays is correct.
i am able to get the phone rooted and twrp installed, but once i try to flash the rooted stock rom, i get a "error executing updater binary in zip". not sure how to proceed.
i may abandon the phone altogether and just order an insurance replacement :-/
Click to expand...
Click to collapse
With knox tripped gooood luck. Also, did u have an EFS backup?
That error message means the rom zip is looking for a different device code than the one you are trying to flash it on. Where did you get the rom file? Are you sure it is correct for your S6?
dial *#0011# and post a screenshot for me. I can help you.
Sunderwear said:
dial *#0011# and post a screenshot for me. I can help you.
Click to expand...
Click to collapse
{
"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"
}
THANK YOU
Pm. I'll help you
Any resolution? I am curious to know what exactly happened and what fixed it.
sorry for not PMing you. i got frustrated and stubborn and just ordered a new phone.
postmastergeneral said:
sorry for not PMing you. i got frustrated and stubborn and just ordered a new phone.
Click to expand...
Click to collapse
I feel bad for you - but very curious about one thing - I thought I read the thread carefully and never noticed a response to the question - "Did you try to odin back to Stock?"
Samsung phones are amazingly resilient - and under most conditions (unless you the phone is really totally FUBARed ) odining back to stock cures 99% of all problems - at least that I have seen. And except in one instance with the NOTE 3 (after it's initial release) Odining the stock rom usually fixes the problem every time. The note three was an unusual circumstance in my memory - and it happend to a bunch of people - I actually screwed up two phones and returned them both to get replacements - Odin would not fix the problem because one of the particians or maybe all of them had been corrupted) but you had an IMEI where I did not - so I don't think that was your issue (although, I may be wrong)
anyway, I can understand your frustration - I have been there my self - but usually cooler heads (the people at XDA) have helped me to find the solution that eventually worked - did you try to ODIN back to Stock? If that did not work then returning the phone may have been your only option - but I would love to know if you did try that option?
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
BLU R1 HD
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@bullet25
@triggerlord
@jasonmerc
@ColtonDRG
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for BLU R1 HD
[Index] BLU R1 HD - Amazon and OEM Variants
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]BLU R1 HD[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: Can I root the BLU R1 HD?[/SIZE]Yes. for the Amazon Variant please see these posts:
Original Root Post Here (Includes TWRP)
Or Step-by-Step Root Here (Includes TWRP)
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)[SIZE=+1]Q2: Can I unlock the bootloader?[/SIZE]Yes for the Amazon Variant please see this post:
Bootloader Unlock
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)*Forum Rules | New Users Guide | XDA Tour | Report PostsA special thanks to everyone who contributed to the production of this FAQ
revered #2
Yo, I'll help. I'm stalking these forums 24/7 anyway.
Manual Camera Compatibility
Does it fully support the Camera2 API for use with manual camera apps?
TorrentialTech said:
Does it fully support the Camera2 API for use with manual camera apps?
Click to expand...
Click to collapse
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind
jasonmerc said:
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind
Click to expand...
Click to collapse
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it
TorrentialTech said:
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it
Click to expand...
Click to collapse
Doesn't look too pleasing.
jasonmerc said:
Doesn't look too pleasing.
Click to expand...
Click to collapse
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone. Hopefully it would work with a simple build.prop edit like the Redmi Note 3 or the Moto X Style.
TorrentialTech said:
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone.
Click to expand...
Click to collapse
There's always other alternatives that use their own camera drivers rather than manufacturer-bundled ones. Open Camera for one is a very good app that does not depend on device bundled camera drivers. It is very feature-rich and can be a powerful camera app if used in the right hands. Open Camera might be able to do what you're looking to do:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....
ariesgodofwar said:
Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....
Click to expand...
Click to collapse
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....
Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!
brockwitting said:
Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!
Click to expand...
Click to collapse
I know with other phones you can do encryption with an unlocked bootloader, I don't know about this one. Either something is wrong with the phone's encryption or I honestly don't know. I'll try encrypting mine when I get a chance.
@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.
bullet25 said:
@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.
Click to expand...
Click to collapse
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?
brockwitting said:
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?
Click to expand...
Click to collapse
Open the SuperSU app, go to settings and there's an option for Full Unroot. Select that, reboot, then do the device encryption. After you verify its working okay reboot back into recovery and flash SuperSU again. TWRP will ask for your password, just enter your password/pin when it does.
bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
So, just wanted to close the loop in the event anyone else runs into this. After 7 hours of rebooting every 3 seconds, the battery ran out. The phone then turned on just fine when I attempted to restart it.......... very odd, but all seems well.
ariesgodofwar said:
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....
Click to expand...
Click to collapse
Well spft is still an option. At the point of power off to power on there is a pause on Android that spft uses to inject a DA program of sorts (download assistant). So try to do a readback of the first like 5mb. The read back information dosent matter itbis the DA injection your looking for. If it works the on off cycle should stop. Then unplug and phone should be off