Develop Bugs

Life after simpleroot?

Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.

I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell

Keep at it!
loztboy said:
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
Click to expand...
Click to collapse
0. Please read everything before doing anything. My post is a little chaotic, but you should be fine if you read everything first.
1/2. The usual disclaimer: I'm not telling you to do anything. I'm just providing information. I'm not liable for anything you do to you phone.
1. ROM Manager is definitely the easiest way, though the "real way" is to load your ROM of choice on the SD card and then flash it from Recovery (more on recovery later).
1 & 1/2. By the way, you should install Titanium backup from the market five minutes ago. Yes, it is that important. When jumping ROMs, you often have to wipe everything out. Without Titanium Backup, you could end up having to repurchase apps and redownload all of your free ones, losing progress in games and settings in apps, etc. The free version of Titanium Backup lets you back up easily enough, but you want the donate version to prevent restores from taking a few hours of user interaction (Yes, I said user interaction, meaning sitting there and pressing buttons for hours). Once you throw $4.00-$50.00 (you can pick within that range, you get the same product regardless of amount) at Titanium Backup (and wait a day or so to get the license key file), you can do a restore in 15 min without any interaction beyond hitting start (or, more accurately, begin batch process). This app has saved my life time and time again. I literally did my first backup out of curiosity for the app and then totaled my phone in the next five minuets. It even backs up your home screen layout. GET IT NOW!!! YOU WILL HATE YOURSELF IF YOU DO NOT GET IT!!! At least get the free version, because, as stated above, it does backups fine. You (like me) will be scared into paying when you realize that you just wreaked everything and really don't want to spend the next few hours restoring. However, Titanium backup will not function until you get Superuser app working, as detailed in point 2 below.
***EDIT: I forgot to mention that Titanium Backup should work after running this program. It should even fix clockwork for you***
2. There are three possibilities for that error: 1: You don't have the superuser app installed. It dishes out the privileges. If you don't have it (if you do go on to potential issue number two and be grateful), you can install it by downloading this file and putting it on the root of the SD card. Then boot into recovery (I'm sure there is a tutorial for getting into recovery floating around here somewhere, just search the EVO section) and flash the .zip Presto! Superuser app is installed. If you prefer not to go around flashing random packages recommended by strangers on the internet, you can research and download superuser app at the source 2: If you found the Superuser app in the app drawer (the screen with all the applications where you scroll down in alphabetical order and pick the one you want to use), open it. You may have bumped "never give superuser access to this app" (or words to that effect) the first time you opened ROM Manager. If so, it will be listed in the Superuser app
{
"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"
}
as red. Just have the superuser app forget ROM Manager and then try to flash custom recovery from within the ROM Manager again, being sure to say "Yes!" when it asks for superuser privileges. 3: If you have no recovery to flash superuser from or superuser is installed and ROM Manager is green inside and it still fails, the SimpleRoot failed. If you skipped a step in the rooting process, go back and do that step. If not, just start over and run all the steps from the beginning, Also note that if you accepted the over the air update, you need the OTA version of SimpleRoot, not the original one.
3. Now, about total reversal. I'll be honest: There is probably a way to go back to stock that works without finishing the root process (probably something to do with PC36IMG.zip) files, but I don't know it. The way I would do it would be picking the OTA Stock ROM from this page and flashing it after getting recovery installed at the end of a successful root process. However, then you would have succeed in your original endeavor and would have no need to go back. There is a program here that supposedly does just enough tweaking to the phone to give you the recovery you need to flash back to the stock ROM, but I have not used it myself and therefore cannot vouch for it.
dws51 said:
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Click to expand...
Click to collapse
If you both succeed in the root process (and I encourage you to persevere, the reward is spectacular), I personally recommend Cyanogen Mod 6. I believe that you can get the nightly builds of CM6 from ROM manager, but the release candidate is likely more stable. I use the RC myself and have never looked back. My battery lasts forever and my phone is never unresponsive. And because the CM6 ROM is based of of Android 2.2 (Froyo), free tethering is built in to the OS and done so rather elegantly, meaning no more dirty hacks for tethering. Just know that if you go that route, though you have the best of the best, you will need to tinker a bit to get everything working. Also, 4G, the FM Radio, and HDMI output are flat out not working in the RC (I'm sure they will be fully functional in the final release, and the not-workedness is a software thing, meaning that the hardware is fine and will come online when you again install a ROM that supports it). On the other hand, with this ROM you can force the phone to roam on Verizon's network when Sprint's 3G speeds are less than desirable.
I'm not sure where to put this, so I'm sticking it here. As soon as you get custom recovery working, you want to backup with Nandroid. The easiest way is from ROM Manager. Just hit "Backup ROM". This backs up not only your setup (like Titanium Backup), but also all the crucial bits that lie underneath and keep your EVOs humming, bits very very difficult to replace. HOWEVER, this is NOT a replacement for Titanium Backup, because it can only restore to the same ROM. If you attempt to restore to a different one, it will put the one you had at the time of the backup back on.
Whichever way you go, I wish the both of you luck. You're entering into the wild and wonderful world of devices that you actually own!

that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through

The root of the SD card is the 'directory' you're in when you plug the card into the computer & you see folders like ".Mail" "Android" "DCIM" etc.
It's up to you if you think you can handle rooting. I used SimpleRoot & it was incredibly easy, but i have been familiar with modding phones for awhile now.

jdjozwia said:
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
Click to expand...
Click to collapse
The root of something simply means not in a folder, e.g. on your computer it would be just G:/ (or whatever letter your SD card is mounted to). Just open the SD card and put whichever file you are referencing right there, not in any folder.
By the way, anyone can root, so long as you are willing to learn and willing to take a few risks. As long as you stay well informed, you usually don't break anything. And there is usually a way out, even if you make a train wreak, though it may be ugly. Independent developers (not me; smart people like Cyanogen and Toast who actually make these awesome ROMs and roots) have a better track record for keeping dangerous stuff out than some corporations. ***Cough***McAfee antivirus broke thousands of computers with a defective update***Cough*** Scientia est vox. Knowledge is power. Know what you're doing, and you'll be fine. You will make mistakes (I know I have), but stay sharp and know the consequences, how to go back, who to ask when things go South, and you'll do alright. The community here at XDA is one of the best and most helpful I have ever seen. If you're not totally hosed, someone will pull you out of the fire. It probably won't even be me. I'm no pro. But there is no shortage of pros here at XDA.

so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod

See Above
jdjozwia said:
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
Click to expand...
Click to collapse
If titanium backup works, you have root. As for Clockwork, please see my first post, where I went over it in detail.

OK well i installed titanium back up and busy box and it looks like im rooted? Im going to try to flash that superuser app tmw i left my usb cord at work so in about 12 hours ill probly be back with more questions
thanks for the encouragement the answers and most of all your time

Cut the cord
jdjozwia said:
i left my usb cord at work
Click to expand...
Click to collapse
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?

Techrocket9 said:
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Click to expand...
Click to collapse
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?

jdjozwia said:
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
Click to expand...
Click to collapse
It should complain about being unable to acquire root privileges.
___
An army of pacifists can be defeated by one man with the will to fight.

yeah when i open it it doesnt say that and it says my root access is ok,
I DL astro and when i open it one of the folders is clockwork mod and if i search i find super user app on my sd card when i reboot my phone by holding the down volume it goes to the hboot screen and askes me if i want to update my phone i say no and then when i go to recovery it does not give me the option to flash the super user app. it takes me to android system recovery with four options. At the very bottom it says E: cant open/cache/recovery/command
?

Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.

How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
As for CM6, don't get me wrong, I LOVE CM6, but, Fresh 1.0.1 or the latest Damage Control might be a safer bet. For your first rom CM6 needs more coaxing than you might like. Also tethering is installed by default in the 2.1 roms from those guys and it's (imho) easier and more obvious to use.
Keep at it, there will be times you feel like giving up even after you get past this point, just don't take it too seriously and remember that as long as you are still getting phonecalls your phone is still doing it's primary job, the rest is just icing. Icing that gets more delicious with time, like beer, mmmmmm beer.
Where was I?
Oh yeah, good luck!

Crap, forgot, when someone says "put it on the root of the SD card" the easiest way to do that is hook it up via USB, hit the status tray that says "usb connected" and check the Hard Drive option. Then just copy your file to the new drive that will show up in windows (might pop up automatically depending on your windows settings) and boom, it's on the root of the SD card.
As for the "real" way to flash. Do the above, putting the .zip file containing whatever rom you want (for instance CM6, or Fresh 1.0.1 which you can obtain over in Development forum from their respective posts) on the root of the SD card. Safely remove the device (on windows it will be in your status bar, usually looks like a plug with a green arrow, click it, choose Mass Storage Device and then hit Stop, it will tell you when its done, make sure you have the folder closed before you do this or it will grump at you) and switch back over to Charge Only on your phone. Then power off the phone (hold the power button with the phone unlocked, choose Power Off, then Ok) and hold the volume down button. Then press power, don't let go of volume down but you don't have to hold power, just press it to turn it on. A white screen should come up, let go of the volume button, and one option will be Recovery. Use volume up and down to select it and press the power button to select. It should then boot you into recovery which should have an option to "wipe", you want to wipe dalvik cache, then cache, then factory defaults. Then go back up (in AmonRA that means hitting vol-up and vol-down at the same time), then goto "Flash .zip from sdcard" select it, hit power, select the zip file, power again, power one more time to confirm.
Once it's done you hit Reboot System Now and viola, first boot takes FOREVER so don't fret.

alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse

Techrocket9 said:
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
Click to expand...
Click to collapse
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?

jdjozwia said:
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
Click to expand...
Click to collapse
It is possible. The program I mentioned earlier (unrEVOked) should install a custom recovery for you. I can't put a link in this post because I'm on my phone, but a quick google search should find it.
An army of pacifists can be defeated by one man with the will to fight.

jdjozwia said:
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
If you just did SimpleRoot (i.e. didn't download the android SDK) you probably don't have ADB installed on your PC. So then you'd want to go the terminal route. Search the market for Better Terminal Emulator
Click to expand...
Click to collapse

Firmware upgrade for dummies (from P1000XXJID to P1000XXJK5)

This is my guide for dummies:
INTRODUCTION: I'm an italian user with a standard Samsung Galaxy Tab purchased via Vodafone. I would like to upgade my firmware from P1000XXJID to P1000XXJK5. I search in XDA and in samfirmware and this is the sequence of my upgrade.
1. You need some software.
a. KIES software (from www.samsungmobile.com): download and install
b. P1000XXJK5.rar (from www.samfirmware.com): download and unzip (use WinRar and password is "samfirmware.com")
c. NEW Odin: DOWNLOAD Version 1.7 (from www.samfirmware.com)
2. unzip New Odin 1.7 and run "Odin3 v1.7.exe"
3. Press the [PIT] button and select the "P1_20100909.pit" file
4. Press the [PDA] button and select the "P1000OXAJK5.tar" (which was in the 'P1000XXJK5.rar' file - see 1.b.)
5. Put a cross-chek on 'Auto Reboot' and 'F. Reset Time' (NOT on 'Re.Partition')
6. Now we are ready to flash our Galaxy Tab:
a. power off the device
b. extract SIM and SD card (if you have one)
c. power on the device pushing 'Volume down' + 'Home' + 'Power button'
d. the device will start in dowloading mode (yellow triangle)
7. Connect your usb cable (if you have correctly installed the KIES software, drivers are ok and device is recognized by the PC)
8. In Odin you must see on the left "0:[COM3]" (yellow background), or something like that
9. Press [START] and wait till has finished (4 minutes); Odin will reset the device itself.
10. After boot check if all is ok using *#1234# code
PS: I have found all my apps, no backup/restore needed ! But this is my case...

( trying to update to -> P1000XXJK5 )
Hi,
thx
but I the device gave me an error.
update media, please wait
e:can't mount /dev/block/stl10 (invalid argument)
E:copy_dbdata_media:can't mount DBDATA
your storage is not prepared yet. please use UI menu for format and reboot actions...
any help thats my device before I tried to update
PDA
P1000XWJJ3
Phone
P1000XXJID
CSC : P1000CPWJJ3
Build Time : 2010.10.07
Changelist : 615445

dorenthe said:
( trying to update to -> P1000XXJK5 )
Hi,
thx
but I the device gave me an error.
update media, please wait
e:can't mount /dev/block/stl10 (invalid argument)
E:copy_dbdata_media:can't mount DBDATA
your storage is not prepared yet. please use UI menu for format and reboot actions...
Click to expand...
Click to collapse
No problem, theres two ways to fix this:
1: Flash the full JJ4 firmware with the P1_20100909 file and check partition
Then let it reboot, and flash JK5 after that without the .pit and partitioning on..
2: just flash the dbdata.tar from the end of this post:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
I'd do option #1, I think you need to have JJ4, coming from your older version (pre-JJ4)
This is also for anyone flashing a non-European Tab:
so steps:
3.1 Press the [PDA] button and select the "P1000XWJJ4.tar"
3.2 Put a cross-check on 'Partition', 'Auto Reboot' and 'F. Reset Time'
3.3 Do steps 6-9
.

usa
What benefits does this give us in usa? thx

kevinniven said:
What benefits does this give us in usa? thx
Click to expand...
Click to collapse
Hi, in my european Tab I notice a little better 'scroll speed' between home screens (horizontally scroll). It's the only advantage, IMHO (In My Humble Opinion).
Please remember that for 'usa TAB' you have different firmware; consult www.samfirmware.com

I ran the update on my tab from the UK, specs beforehand were:
PDA XWJJ3
Phone XXJID
CSC CPWJJ3
Click to expand...
Click to collapse
After flashing directly to JK5 it rebooted happily although it basically did a factory reset (formatted the internal SD card - which is a pain as that's where Titanium Backup put its backups)
Firmware specs now are:
PDA XXJK5
Phone XXJK5
CSC XAJK5
Click to expand...
Click to collapse
It does look like there's a number of missing applications, so I'm going to get the full JJ4 package and flash that and then put JK5 over the top of it.
So while it works and does feel a bit snappier, it's not what I'd call a huge success going straight from JJ3 to JK5 I'll get there though.
EDIT: Before I did the flashing, I did a factory reset and the "missing" apps popped up, so while it looks like it's not entirely happy going from JJ3 to JK5, it does appear to work ok.
I'm still going to put JJ4 on there just for the heck of it and then reflash to JK5.
Looks like JJ4 defaults to Russian:
PDA: XWJJ4
Phone: XXJID
CSC: SERJJ2
Click to expand...
Click to collapse
Final Edit:
Nope, no noticable difference having gone from JJ3 to JK5 or JJ4 to JK5, other than having to manually do a factory reset to get everything behaving after having gone from JJ3 to JK5.
Fair warning, I may have done something wrong, but if not, it WIPES your internal user storage when you do the update!
Still, happily on JK5 now, not a big deal to re-transfer my stuff over.

Thank for this thread.
But why would someone not choose to upgrade firmware when Samsung releases it via KIES?

sanderh said:
Thank for this thread.
But why would someone not choose to upgrade firmware when Samsung releases it via KIES?
Click to expand...
Click to collapse
Because Samsung have a history of not releasing official updates.
Plus, we want new stuff NOW

Big thx to you rotohammmmmmmer ...

I suggest to do also the following after the first boot: *#272*your imei# (dial all your imei digits!),then select your original Sales code,in my case for Italy Itv.This allow you to have all the Samsung Apps of your country.
Also the problem with the missing data at boot is because JK5 isn't a full flash.you can also flash the JJ4 with repartition and then JK5 without.
For newbies: Make a Titanium Backup before the 272 code!! (thanks to brunino1967 to remind me, I forgot to mention )
Sent from my GT-P1000 using Tapatalk

knightnz said:
After flashing directly to JK5 it rebooted happily although it basically did a factory reset (formatted the internal SD card - which is a pain as that's where Titanium Backup put its backups)
Click to expand...
Click to collapse
You can change where Titanium sticks it's backups by going to
Preferences/Backup folder name
and change it to
/external_sd/TitaniumBackup
Or if you've got the full version you could have sync'd your backup to Dropbox.

I also have JJ3. I think I will follow the suggestion to install JJ4 first with the repartition and then JK5. If I backup all my system data and apps to the external SD card (or Dropbox) using Titanium Backup, is it OK to restore the system data as well after the upgrade or might there be some conflict with the new version? TBH I don't realy know what the system data is so may you will tell me I only need to restore the apps.
TIA

How languages are included in this ROM? I need Polish.

vahanara said:
How languages are included in this ROM? I need Polish.
Click to expand...
Click to collapse
Yes in P1000XXJK5 there is "polski".

zerocool76 said:
I suggest to do also the following after the first boot: *#272*your imei# (dial all your imei digits!),then select your original Sales code,in my case for Italy Itv.This allow you to have all the Samsung Apps of your country.
Also the problem with the missing data at boot is because JK5 isn't a full flash.you can also flash the JJ4 with repartition and then JK5 without.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Advice for all newbies: please be carefull with this code *#272... etc etc.
because if you apply it, you will have a wiped SGT and it will go back at factory status (I mean that the default apps will be there but no one of your already downloaded apps will be there !). You will have your home screen reset to default too. If you have the fortune, like it has been for me, to see your SGT (after the firmware update) restart as it was before (with all your apps, etc.) don't use this code.
Obviously if your installation is not complete and you wish to have all default/factory installed apps, use this code.

sooooo say u do this and it reboots but gets stuck at the samsung logo and vibrates every few seconds. what does that mean?.....and how do u fix it? i really hope i dont gotta reflash and repartition...if so.....FAAWWKKK!
update:
flashed dbdata.rfs.tar from:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
end of the first post
still waiting for the results.....

Guys did the update but now cant download from market what's happened

Difference from xxjid and xxjk5 ?
Sent from my GT-P1000 using XDA App

brunino1967 said:
Advice for all newbies: please be carefull with this code *#272... etc etc.
because if you apply it, you will have a wiped SGT and it will go back at factory status (I mean that the default apps will be there but no one of your already downloaded apps will be there !). You will have your home screen reset to default too. If you have the fortune, like it has been for me, to see your SGT (after the firmware update) restart as it was before (with all your apps, etc.) don't use this code.
Obviously if your installation is not complete and you wish to have all default/factory installed apps, use this code.
Click to expand...
Click to collapse
Guys, who is doing a flash needs to make backups!!! Use titanium before flashing or apply 272 code and so on. If for example you are flashing with re-partition you will lose not just the apps but also the entire content of your internal sdcard.With 272 code you will lose the apps but no the sdcard content.You can restore everything with Titanium Backup.

norm2002 said:
I also have JJ3. I think I will follow the suggestion to install JJ4 first with the repartition and then JK5. If I backup all my system data and apps to the external SD card (or Dropbox) using Titanium Backup, is it OK to restore the system data as well after the upgrade or might there be some conflict with the new version? TBH I don't realy know what the system data is so may you will tell me I only need to restore the apps.
TIA
Click to expand...
Click to collapse
Sorry to ask again but is there anyone who can help me with this? I am nervous of making a mistake.

Asia Firmware DXJM4

Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."

cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.

Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet

rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?

VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.

I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route

perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job

oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)

This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App

thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T

Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.

ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!

TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.

hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.

try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading

fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks

sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?

KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?

samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?

VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.

[GUIDE] Full Phone Backup without Unlock or Root

Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
Keep in mind this is experimental and not exactly publicized as a feature of ICS, so don't count on this as your only method of backup!
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
1. Connect your device via USB, and open a command prompt.
2. Optionally, type the command 'adb devices' to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
There is a command, 'adb backup' (to be detailed shortly), that will now allow you to create a full system backup.
The command parameters format is:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use* is simply:
adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
* This may not work for every setup. If you get an error such as "adb: cannot open file ./backup.ab", use:
adb backup -all -f C:\backup.ab
Click to expand...
Click to collapse
Or substitute the path of your choice in place of C:\.
To explain the parameters:
-f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
-apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
-shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
-all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
-system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
<packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
adb backup -apk -shared -all -f C:\backup20111230.ab
Click to expand...
Click to collapse
4. You will see a screen like the following:
{
"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"
}
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you will get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your phone returns to the home screen.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
adb restore C:\backup20111230.ab
Click to expand...
Click to collapse
replacing 'C:\backup20111230.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE 12/31: Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
NOTE 06/12: There seems to be a bug in which backup and restore operations will fail unless a desktop backup password is set under Developer Options. It will not work with a blank password.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Kevin

In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.

faizalmzain said:
In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.
Click to expand...
Click to collapse
Interesting. They must have deemed it not quite ready for primetime yet. Seems like it should show up in a future version sometime in the not-too-distant future, then. Until then, this seems to work pretty well.

I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.

RogerPodacter said:
I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.
Click to expand...
Click to collapse
While that's true, if you're already past the point of painful return, why start over when this backup method is available? It's not a question of if it works (it does work).

my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?

sahakiap said:
my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?
Click to expand...
Click to collapse
Yes, as shown in the guide, just use the 'adb restore' command after unlocking the bootloader. You may wish to backup your Internal Storage manually, just to be safe, and backup your SMS with a third party app, if you care to keep them. Obtaining root isn't covered in this guide, but yeah, you can root it once you've unlocked the bootloader.

I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?

ktulu029 said:
I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?
Click to expand...
Click to collapse
Interesting. Could you post the exact command that you used, and also what OS you're running?

copkay said:
Interesting. Could you post the exact command that you used, and also what OS you're running?
Click to expand...
Click to collapse
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64, and my phone is running 4.0.2 if that is useful information.
It runs everything on the phone like prompted, just doesn't save any data.

ktulu029 said:
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64
Click to expand...
Click to collapse
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?

Wow, this should be a freakin STICKY!!!

copkay said:
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?
Click to expand...
Click to collapse
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.

ktulu029 said:
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.
Click to expand...
Click to collapse
After allowing the backup, did you get a Toast saying "Backup Started"?

I do. And shortly after, maybe 5 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.

ktulu029 said:
I do. And shortly after, maybe 10 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.
Click to expand...
Click to collapse
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.

copkay said:
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.
Click to expand...
Click to collapse
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.

ktulu029 said:
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.
Click to expand...
Click to collapse
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.

copkay said:
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.
Click to expand...
Click to collapse
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.

ktulu029 said:
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.
Click to expand...
Click to collapse
The versions might matter, but you're on the same revisions I'm on. Now, I will say that I am running from C:/Program Files(x86)/Android/android-sdk/platform-tools/ rather than just the straight C:/ prompt, just because I've been too lazy to add ADB to my system variables. I'm also using MTP, which shouldn't affect it.
Yeah, things have changed quite a bit; going from the Droid line to the Fascinate was my last jump.
The only thing I can think of to try is to make sure that you are running your Command Prompt as Administrator. The fact that it's creating a file at all seems to disprove that this would have an effect, but it's worth a try.

[GUIDE] How to restore photochrom (by downgrading)

Preface:
OnePlus has pushed an incremental rollout to OxygenOS for the OnePlus 8 Pro, 10.5.11 (India / Global) and 10.5.10 (Europe). You can find the changelog issued here.
https://forums.oneplus.com/threads/and-10-5-10-eu-for-the-oneplus-8-pro.1253402/
Many have found that the photochrom filter doesn't work as expected or doesn't work at all after this update, this seems to depend on the region. If you want this feature back, I encourage you to write feedback to OnePlus. There are many great changes in this update and I would love to see them in another update with the photochrom filter restored.
This guide is meant to show you how to restore this filter by downgrading the firmware on your phone, this means you will lose out on the other changes present in the new incremental update, including an Android security update. This is meant to be a temporary solution for those that really love this quirky feature and I don't recommend this guide for most people. Also, if you have root on your phone then this should remove it. Currently, this guide doesn't work for India since there's no downgrade image which brings them to 10.5.8. The infrared camera was disabled for India in version 10.5.9 which is the lowest we can downgrade to at the moment.
WARNING:
Do not proceed with this guide if you lack experience flashing ROMs or have the slightest apprehension about bricking your phone. Be sure to read the guide fully before attempting so that you understand how the procedure works. If you're uncomfortable after reading this, stop and forget about it. Leave feedback to OnePlus and wait for an update. I've only tested this with the global version, but this should work with the other regions as well. That being said, I'm not liable for any damage you cause to your device. STOP if you have a network-branded phone. Proceed at your own RISK!
Phone Backup:
Do not skip this step unless you want to start anew with a wiped device. You can use whatever backup method you wish, but the one I did on my own phone was a OnePlus Switch backup and a Google backup which worked decently well.
I also used Google's Autofill services so that it was easy to sign back into my accounts. You could use any password manager like LastPass just the same, but I think this service works better. You can check if your passwords are saved under Settings > Privacy > Advanced > Autofill services from Google > Passwords.
If you use Two Factor Authentication such as through Authy or Google Authenticator, ensure that you're able to authorize a new device with another such as via another device or SMS.
If you want to use my backup method, follow these basic steps. First, you'll backup with OnePlus Switch.
Open the OnePlus Switch app.
Tap "Backup and Restore".
Select "New Backup".
Check everything that you want backed up, then select "Backup Now".
Once finished, plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy /opbackup/MobileBackup to somewhere safe on your computer. It will be wiped from your phone in the next procedures, so this is extremely important.
Next, you'll backup using Google.
Open Settings, then go to System > Backup > Toggle "Backup to Google Drive" on if it hasn't been turned on already.
Tap "Back up now" and wait for it to finish.
Downgrade Flash:
This is scariest part of the procedure since your device will first be wiped with this type of flashing before installing the initial firmware. If the flashing procedure is interrupted, you may not be able to recover. Therefore, please do the following before proceeding to ensure that doesn't happen.
Ensure your device is charged at least 30%, I recommend higher though.
Make sure your device is plugged in while flashing.
Have a charged battery backup on hand in case the power grid goes out.
Check that the firmware image isn't corrupted before flashing (instructions ahead, step 3)
Alright, so now for the procedure:
Check your phone region. Open Settings > About phone, then look at the Build number. It should be something like 10.5.11.IN11XX. The IN11XX will denote your region.
IN11AA for Global
IN11DA for India
IN11BA for Europe
You can also check the Model:
IN2025 for Global
IN2021 for India
IN2023 for Europe
If you have an Indian model, discontinue this guide unless you have some other reason to downgrade. You won't be able to restore photochrom.
Download the appropriate downgrade firmware. There's a OnePlus post that included these firmware image files used for rolling back a developer preview. Here, we're using it to rollback the official stock image to an older version.
Look for "Download links for OnePlus 8 Pro" here: https://forums.oneplus.com/threads/android-11-beta-developer-preview-for-oneplus-8-series.1233995/
You'll have 3 versions:
NA for Global
IN for India
EU for Europe
You should know what your region is from step 1. It's vital that you choose the correct region, so if you're unsure then GO BACK to step 1!
Compute the SHA1 checksum of the downloaded firmware image. This is to check that it hasn't been corrupted, which can happen when you download files or have a faulty drive. Windows has a built-in utility called CertUtil and Macs have one called shasum.
Windows: Open command prompt (find it by searching "cmd" in the search bar), then enter "CertUtil -hashfile" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
Mac: Open Terminal from Applications > Utilities. Enter "shasum -a 1" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
You'll see a long string of characters, this is the SHA1 checksum. Compare it with the following value according to your region, ensure it matches EXACTLY. If it doesn't then you have a corrupted image or downloaded the wrong region, please go back and download it again.
Global: 96f8ee55a1b8914317c7e24306bb512733530052
Europe: 74a94d4d0b1676a03ddfd40f85635b0036c5b038
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 4. This will wipe your phone and downgrade. DO NOT unplug or turn off the phone, let it finish the entire process because if you don't then it could brick your phone.
Once the phone boots up, skip through as many prompts as possible since you can set it up later. It will say installing updates during these prompts, don't worry about this, it's normal.
Update to 10.5.10 (Global), 10.5.9 (Europe):
This next step is to get you to the most recent update before photochrom was removed or changed. So hold off on restoring your backup and setting up the device.
Download the previous update that had Photochrom.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Click the reveal content button under "Signed flashable zips" and then the next reveal content button under the appropriate region. Click the download link for 10.5.10 if your region is Global or India, click the download link for 10.5.9 if your region is Europe.
Check the SHA1 checksum using the instructions in step 3 of the previous section. However, you'll instead be comparing to the following values.
Global: 4a08ebb45aed300e8707aa1dc2cbd07ea69344df
Europe: 1f5b792964312a06eb122f813a33787ccf7d3850
As before, make sure these match exactly with you calculated. If not, you downloaded the wrong file or your download is corrupted. Go back to the post and try to download again. The XDA forum post lists MD5 values which are different than SHA1 so please ignore those.
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 3. This will update your phone just like the typical OTA update.
Restoring from backup:
If you've come this far then it means you've already restored Photochrom. If you wanted a newly wiped phone then you're done. Otherwise, continue on to restore your backup. This goes over restoring using the backup method I used at the beginning of this guide.
Plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy the /opbackup/MobileBackup folder you saved before back onto the phone. Make sure it has the same path. If you need to then you can create a new opbackup folder.
Back on the phone, open up the OnePlus Switch app.
Select "Backup and Restore" at the bottom.
Select "Restore Backup".
Select and the restore you moved back onto the phone. If you don't see it, it means you didn't move it onto the correct path. It should be in /opbackup/MobileBackup.
Once the OnePlus Switch app has restored your backup, sign into your Google account from Settings > Accounts > + Add account. You should soon see a finish setting up notification from Google, tap this and continue so that it installed all your apps and restores a bunch of settings.
Once finished, double check through your settings to see if it missed anything. For me it got most settings but some weren't set.
Sign back in to all your apps and authorize your 2FA manager if you have one.
Thank you
I hope this has been helpful to some people out there. I put a lot of effort into this and triple-checked everything, but let me know if anything is confusing. I'd be happy to change anything in this guide to help clarify. Ultimately, I'd like to see either OnePlus push out an official update that restores this or see someone create a Stock + Photochrom ROM that only changes code related to that camera to keep the original functionality.

GiveMeAnthony said:
Preface:
OnePlus has pushed an incremental rollout to OxygenOS for the OnePlus 8 Pro, 10.5.11 (India / Global) and 10.5.10 (Europe). You can find the changelog issued here.
https://forums.oneplus.com/threads/...and-10-5-10-eu-for-the-oneplus-8-pro.1253402/
Many have found that the photochrom filter doesn't work as expected or doesn't work at all after this update, this seems to depend on the region. If you want this feature back, I encourage you to write feedback to OnePlus. There are many great changes in this update and I would love to see them in another update with the photochrom filter restored.
This guide is meant to show you how to restore this filter by downgrading the firmware on your phone, this means you will lose out on the other changes present in the new incremental update, including an Android security update. This is meant to be a temporary solution for those that really love this quirky feature and I don't recommend this guide for most people. Also, if you have root on your phone then this should remove it.
WARNING:
Do not proceed with this guide if you lack experience flashing ROMs or have the slightest apprehension about bricking your phone. Be sure to read the guide fully before attempting so that you understand how the procedure works. If you're uncomfortable after reading this, stop and forget about it. Leave feedback to OnePlus and wait for an update. I've only tested this with the global version, but this should work with the other regions as well. That being said, I'm not liable for any damage you cause to your device. STOP if you have a network-branded phone. Proceed at your own RISK!
Phone Backup:
Do not skip this step unless you want to start anew with a wiped device. You can use whatever backup method you wish, but the one I did on my own phone was a OnePlus Switch backup and a Google backup which worked decently well.
I also used Google's Autofill services so that it was easy to sign back into my accounts. You could use any password manager like LastPass just the same, but I think this service works better. You can check if your passwords are saved under Settings > Privacy > Advanced > Autofill services from Google > Passwords.
If you use Two Factor Authentication such as through Authy or Google Authenticator, ensure that you're able to authorize a new device with another such as via another device or SMS.
If you want to use my backup method, follow these basic steps. First, you'll backup with OnePlus Switch.
Open the OnePlus Switch app.
Tap "Backup and Restore".
Select "New Backup".
Check everything that you want backed up, then select "Backup Now".
Once finished, plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy /opbackup/MobileBackup to somewhere safe on your computer. It will be wiped from your phone in the next procedures, so this is extremely important.
Next, you'll backup using Google.
Open Settings, then go to System > Backup > Toggle "Backup to Google Drive" on if it hasn't been turned on already.
Tap "Back up now" and wait for it to finish.
Downgrade Flash:
This is scariest part of the procedure since your device will first be wiped with this type of flashing before installing the initial firmware. If the flashing procedure is interrupted, you may not be able to recover. Therefore, please do the following before proceeding to ensure that doesn't happen.
Ensure your device is charged at least 30%, I recommend higher though.
Make sure your device is plugged in while flashing.
Have a charged battery backup on hand in case the power grid goes out.
Check that the firmware image isn't corrupted before flashing (instructions ahead, step 3)
Alright, so now for the procedure:
Check your phone region. Open Settings > About phone, then look at the Build number. It should be something like 10.5.11.IN11XX. The IN11XX will denote your region.
IN11AA for Global
IN11DA for India
IN11BA for Europe
You can also check the Model:
IN2025 for Global
IN2021 for India
IN2023 for Europe
Download the appropriate downgrade firmware. There's a OnePlus post that included these firmware image files used for rolling back a developer preview. Here, we're using it to rollback the official stock image to an older version.
Look for "Download links for OnePlus 8 Pro" here: https://forums.oneplus.com/threads/android-11-beta-developer-preview-for-oneplus-8-series.1233995/
You'll have 3 versions:
NA for Global
IN for India
EU for Europe
You should know what your region is from step 1. It's vital that you choose the correct region, so if you're unsure then GO BACK to step 1!
Compute the SHA1 checksum of the downloaded firmware image. This is to check that it hasn't been corrupted, which can happen when you download files or have a faulty drive. Windows has a built-in utility called CertUtil and Macs have one called shasum.
Windows: Open command prompt (find it by searching "cmd" in the search bar), then enter "CertUtil -hashfile" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
Mac: Open Terminal from Applications > Utilities. Enter "shasum -a 1" without quotes followed by a space. Drag the downloaded firmware image onto the prompt, then press enter.
You'll see a long string of characters, this is the SHA1 checksum. Compare it with the following value according to your region, ensure it matches EXACTLY. If it doesn't then you have a corrupted image or downloaded the wrong region, please go back and download it again.
Global: 96f8ee55a1b8914317c7e24306bb512733530052
India: 84f1e472d7e5da0e50d0a4e8f135820352e6dd17
Europe: 74a94d4d0b1676a03ddfd40f85635b0036c5b038
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 4. This will wipe your phone and downgrade. DO NOT unplug or turn off the phone, let it finish the entire process because if you don't then it could brick your phone.
Once the phone boots up, skip through as many prompts as possible since you can set it up later. It will say installing updates during these prompts, don't worry about this, it's normal.
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
This next step is to get you to the most recent update before photochrom was removed or changed. So hold off on restoring your backup and setting up the device.
Download the previous update that had Photochrom.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Click the reveal content button under "Signed flashable zips" and then the next reveal content button under the appropriate region. Click the download link for 10.5.10 if your region is Global or India, click the download link for 10.5.9 if your region is Europe.
Check the SHA1 checksum using the instructions in step 3 of the previous section. However, you'll instead be comparing to the following values.
Global: 4a08ebb45aed300e8707aa1dc2cbd07ea69344df
India: 07b698e8d071ad794f3bcca38ad728ba646a4a5e
Europe: 1f5b792964312a06eb122f813a33787ccf7d3850
As before, make sure these match exactly with you calculated. If not, you downloaded the wrong file or your download is corrupted. Go back to the post and try to download again. The XDA forum post lists MD5 values which are different than SHA1 so please ignore those.
Move the downloaded firmware image onto your device. You can do this by plugging in your phone to the computer then set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Make sure your phone is charged at least 30% and plugged in as I warned above.
Open Settings > System > System updates.
Tap the gear cog icon in the top right.
Tap "Local upgrade" and select the package you moved onto the phone in step 3. This will update your phone just like the typical OTA update.
Restoring from backup:
If you've come this far then it means you've already restored Photochrom. If you wanted a newly wiped phone then you're done. Otherwise, continue on to restore your backup. This goes over restoring using the backup method I used at the beginning of this guide.
Plug your phone into a computer and set the USB mode to "File transfer" under the notification bar. On Windows, you'll see the new device in Explorer. For a Mac, you'll need the Android File Transfer program. https://www.android.com/filetransfer/
Copy the /opbackup/MobileBackup folder you saved before back onto the phone. Make sure it has the same path. If you need to then you can create a new opbackup folder.
Back on the phone, open up the OnePlus Switch app.
Select "Backup and Restore" at the bottom.
Select "Restore Backup".
Select and the restore you moved back onto the phone. If you don't see it, it means you didn't move it onto the correct path. It should be in /opbackup/MobileBackup.
Once the OnePlus Switch app has restored your backup, sign into your Google account from Settings > Accounts > + Add account. You should soon see a finish setting up notification from Google, tap this and continue so that it installed all your apps and restores a bunch of settings.
Once finished, double check through your settings to see if it missed anything. For me it got most settings but some weren't set.
Sign back in to all your apps and authorize your 2FA manager if you have one.
Thank you
I hope this has been helpful to some people out there. I put a lot of effort into this and triple-checked everything, but let me know if anything is confusing. I'd be happy to change anything in this guide to help clarify. Ultimately, I'd like to see either OnePlus push out an official update that restores this or see someone create a Stock + Photochrom ROM that only changes code related to that camera to keep the original functionality.
Click to expand...
Click to collapse
can you please tell me after rolling and installing first step
then at this point
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
can we install 10.5.8 also Indian version for me in which it was enabled.
becasue company disabled it on 10.5.10 for me.

MintuBilii said:
can you please tell me after rolling and installing first step
then at this point
Update to 10.5.10 (Global and India), 10.5.9 (Europe):
can we install 10.5.8 also Indian version for me in which it was enabled.
becasue company disabled it on 10.5.10 for me.
Click to expand...
Click to collapse
Yeah, you can use any of the images listed on that XDA page.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Though I haven't calculated the SHA1 hash for all of those versions. Since I didn't author these files, in order to verify the hashes, I download to multiple devices and then run the checksum on each to compare. So what about 10.5.9 for India? Do you know if the old photochrom works on that?
Here's the SHA1 for 10.5.8 (India): db88d05729c8b235d7d4067ed0b949348f671e61

GiveMeAnthony said:
Yeah, you can use any of the images listed on that XDA page.
https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315
Though I haven't calculated the SHA1 hash for all of those versions. Since I didn't author these files, in order to verify the hashes, I download to multiple devices and then run the checksum on each to compare. So what about 10.5.9 for India? Do you know if the old photochrom works on that?
Here's the SHA1 for 10.5.8 (India): db88d05729c8b235d7d4067ed0b949348f671e61
Click to expand...
Click to collapse
no it was working well on 10.5.8 only.
buti think we will get error message that downgrade is not possible .
Update
Just i downgraded with first post to 10.5.9 now when installing 10.5.8: OnePlus8ProOxygen_15.I.17_GLO_017_2005100301
it gives error that you can't downgrade now what ?
I don't have knowledge of root.
do you know any link of downgrade for 10.5.8 India version

MintuBilii said:
no it was working well on 10.5.8 only.
buti think we will get error message that downgrade is not possible .
Update
Just i downgraded with first post to 10.5.9 now when installing 10.5.8: OnePlus8ProOxygen_15.I.17_GLO_017_2005100301
it gives error that you can't downgrade now what ?
I don't have knowledge of root.
do you know any link of downgrade for 10.5.8 India version
Click to expand...
Click to collapse
That won't work and you shouldn't even attempt to circumvent it. If you were able to flash it then you would end up bricking your phone. The whole point of the downgrade firmware image is to bring you to a lower version than the one before the feature was removed. You cannot update to a lower version, you specifically need a downgrade image. I didn't realize the downgrade image for India didn't go below 10.5.9. For global users, the downgrade image provided by OnePlus goes to 10.5.7. I'll update the guide to reflect that this currently doesn't work for India users. In order to get it to work, you would need a downgrade firmware image which brings you down to at least 10.5.8. It may be possible to create such an image because from what I can tell, the image consists of instructions to wipe the phone and then flash the update. Basically, we would need to modify the image to keep those instructions but change the update.

GiveMeAnthony said:
That won't work and you shouldn't even attempt to circumvent it. If you were able to flash it then you would end up bricking your phone. The whole point of the downgrade firmware image is to bring you to a lower version than the one before the feature was removed. You cannot update to a lower version, you specifically need a downgrade image. I didn't realize the downgrade image for India didn't go below 10.5.9. For global users, the downgrade image provided by OnePlus goes to 10.5.7. I'll update the guide to reflect that this currently doesn't work for India users. In order to get it to work, you would need a downgrade firmware image which brings you down to at least 10.5.8. It may be possible to create such an image because from what I can tell, the image consists of instructions to wipe the phone and then flash the update. Basically, we would need to modify the image to keep those instructions but change the update.
Click to expand...
Click to collapse
yes please, I am waiting for it. because for India it was working and enabled the feature on 10.5.8 let me know if you found downgrade image tested which has enabled photochrom because i am getting an error that I cannot downgrade and i do not wish to root my phone due to I use security apps.
Right now i am on 10.5.9 which has no photochrom but i think its better does not sucks my battery like .11 and more stable.
I will keep it testing if any issues will update to latest version.

MintuBilii said:
yes please, I am waiting for it. because for India it was working and enabled the feature on 10.5.8 let me know if you found downgrade image tested which has enabled photochrom because i am getting an error that I cannot downgrade and i do not wish to root my phone due to I use security apps.
Right now i am on 10.5.9 which has no photochrom but i think its better does not sucks my battery like .11 and more stable.
I will keep it testing if any issues will update to latest version.
Click to expand...
Click to collapse
The error is because those aren't downgrade images and you're trying to "update" to an older version. Don't even attempt flashing update images of older versions, even though the System Update app blocks you, because it would brick the phone if it did allow you. The point of updating in this guide was because the downgrade image goes all the way back to 10.5.7. If there were one for 10.5.10 then global users wouldn't need the updating step. Rooting won't help you in this case either (at least not yet). There's another thread attempting to bring back this functionality with the camera, photo processing, and various services / APIs so that you can have the updates with photochrom.
https://forum.xda-developers.com/on...cussion-how-to-enable-photochrom-int-t4132807
In fact, could you try something for me?
Download and extract Android platform tools on your computer https://developer.android.com/studio/releases/platform-tools
Add the platform-tools directory to your PATH system variable. Here's how to do it on Windows. https://www.computerhope.com/issues/ch000549.htm Let me know if you don't have Windows.
Enable USB debugging on your device. Settings > About Phone > Tap the build number until it says you're a developer. Next, go to Settings > System > Developer Options then toggle USB debugging.
Run the following command in command prompt / terminal
Code:
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Press the switch camera button on the app which should've loaded until you get to Fourth Camera. Let me know the results.
I'll let you know if a 10.5.8 downgrade image is made for India. When I get a chance, I'll run some diffs on the downgrade vs update images and see if I can generate a new image myself. I have no way of testing the image though since I don't have an Indian device.

GiveMeAnthony said:
The error is because those aren't downgrade images and you're trying to "update" to an older version. Don't even attempt flashing update images of older versions, even though the System Update app blocks you, because it would brick the phone if it did allow you. The point of updating in this guide was because the downgrade image goes all the way back to 10.5.7. If there were one for 10.5.10 then global users wouldn't need the updating step. Rooting won't help you in this case either (at least not yet). There's another thread attempting to bring back this functionality with the camera, photo processing, and various services / APIs so that you can have the updates with photochrom.
https://forum.xda-developers.com/on...cussion-how-to-enable-photochrom-int-t4132807
In fact, could you try something for me?
Download and extract Android platform tools on your computer https://developer.android.com/studio/releases/platform-tools
Add the platform-tools directory to your PATH system variable. Here's how to do it on Windows. https://www.computerhope.com/issues/ch000549.htm Let me know if you don't have Windows.
Enable USB debugging on your device. Settings > About Phone > Tap the build number until it says you're a developer. Next, go to Settings > System > Developer Options then toggle USB debugging.
Run the following command in command prompt / terminal
Code:
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Press the switch camera button on the app which should've loaded until you get to Fourth Camera. Let me know the results.
I'll let you know if a 10.5.8 downgrade image is made for India. When I get a chance, I'll run some diffs on the downgrade vs update images and see if I can generate a new image myself. I have no way of testing the image though since I don't have an Indian device.
Click to expand...
Click to collapse
bro no long process needed !
I can still use the camera using factory trick
For wireless adb(require wireless adb debugging to be enabled):
https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md
this works 100% and no root needed.
i am on 10.5.9 right now in which no photochrom but can use with factory mode.
what i do not like is we have to use that factory mode and id not like it however i am feeling battery is more stable right now in my current version that is why not looking to upgrade.
https://forums.oneplus.com/threads/...tochrom-filter-to-work-like-original.1257039/
{
"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"
}

I have the Indian version of Oneplus 8 Pro. And I downgraded my phone from 10.5.12 to 10.5.4 using the MSM Tool. (EDL Mode). And the Photochrom works well on that.

rippedd_ggenes said:
I have the Indian version of Oneplus 8 Pro. And I downgraded my phone from 10.5.12 to 10.5.4 using the MSM Tool. (EDL Mode). And the Photochrom works well on that.
Click to expand...
Click to collapse
can you please share the detailed steps to do it will be very thankful to you.

Can we follow this guide even on 11.0.3.3?