Related
As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.
If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480
Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?
pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.
terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin
Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app
Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks
Works fine on i317m
anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593
qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.
Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.
Work only on Oreo 8
You must be Stat Normal
Oem Unlocked
Enable USB Debugging Mode and OEM Unlock in your mobile. To do this; go to settings >>> about >>> Tap on the “Build Number” 7-10 times consistently to enable “Developer Options,” then go to the “Developer Options” and enable USB Debugging Mode and OEM Unlock. There is no complicated process in the Samsung Galaxy J7 Duo.
Download and install the Samsung USB driver to your computer system.
Also, download the ODIN software. Select above Oreo version in the ODIN list. Install ODIN in your PC.
Download Magisk.Zip (Download Latest version) and forced encryption disabler, Copy it to Your Phone Memory. We Need to flash encryption disabler to avoid Boot Warnings in the future after the Root process.
Download and save the TWRP File. Select Correct TWRP file from Below. This TWRPs can support Up to Oreo.
SM-J720F
SM-J720M
Flash TWRP using ODIN
Samsung Galaxy J7 Duo Download Mode
Connect your USB Cable with PC. Switch off your device. Then, enter into Download mode. To do this; press and hold down the Volume Down + Home + Power buttons and connect your micro USB Cable.
Samsung Galaxy J7 Duo Download Mode Warning Screen
Press the Volume Up button to continue when you see the warning message.
Now, connect the Samsung Galaxy J7 Duo mobile to the computer via USB cable.
Launch the Odin app on your computer. If the device is detected by this app (Odin), it will show you a message that reads – added!!!
ODIN Added Message
However, if the device is not correctly connected to the PC, you won’t see this message. So, you have to check the USB cable if it is reasonable and reconnect the device.
After connecting the Samsung device, click on the PDA/PA button to browse/search and get the TWRP from where you saved it on your PC. Also, navigate to “options” and tick the Auto Reboot.
Odin Auto Reboot
Click on “Start”
Once the file is loaded into the device, reboot your device.
Kudos, you have just Installed the TWRP on your Samsung Galaxy J7 Duo. If you installed TWRP, Don’t turn on your mobile. Immediately, move to Magisk Installation steps.
You should not Boot into Normal OS Booting, after TWRP. After TWRP Flash, Immediately Boot into Recovery or twrp will gone
Boot it Into recovery mode->Volume Up + Power Button.+Home
Now it Will Boot into TWRP Recovery Mode.
Install Magisk, forced encryption disabler in your Samsung Galaxy J7 Duo using TWRP
Select Wipe->Advance Wipe->Select Cache Data.
Return to Home of TWRP select Install.
Select Magisk.Zip.
After Installation again Navigate to Home select Install. Select forced encryption disabler.
After the Installation Reboot Your Mobile.
You can also install Magisk.apk in your Mobile Applications. Forced encryption disabler is used to avoid the boot loop issue after rooting.
enjoy
SM-J720F
SM-J720M
encryption disabler
Samy6699 said:
Work only on Oreo 8
SM-J720F
SM-J720M
enjoy
SM-J720F
SM-J720M
encryption disabler
Click to expand...
Click to collapse
Can it be used on the Dual-Sim version SM-J720F/DS released in 04/2018 ?
Can i install it on Galaxy J7 Duo running Android pie
Nitin devarasetty said:
Can i install it on Galaxy J7 Duo running Android pie
Click to expand...
Click to collapse
i also need that man.
Please make one thing clear
Do we have to turn off "Auto reboot"
Or keep the "Auto reboot" option checked on?
Android 9.0
Hello, when it will be possible ? If never, why ?
I followed the exact process but everytime i tried to boot into TWRP recovery immediately after the flashing, the device still boots into stock recovery instead of TWRP
Please help me with this
Thank you
I figured out a way to root the Galaxy J7 duo
Actually i have tried lot of ways to root using TWRP flash and all.. but one day i accidentally bricked my device
So i downloaded the stock ROM to flash my device
And i downloaded the 8.0 android ROM
So this root method basically tested on android 8.0
So now i have android 8.0 stock ROM downloaded
Step 1 -
So make sure you also downloaded the ROM
And extract the ROM file (you must have got the "AP" "CP" "BL" "CSC" and "HOME CSC" file)
Then copy the "AP" file in your phone
Then install magisk manager in your phone
Open magisk, select install, select and patch a file from magisk
Then select "AP" file
And wait while magisk is patching the "AP" file
When flashing is done the patched file will be saved on storage, emulated, 0, download (file will be saved as "magisk_patched.tar")
Then simply copy the patched file in your computer
Step 2 -
Open odin in your Computer
In odin, select "magisk_patched.tar" in "AP" section
Select "BL" from the stock ROM folder in the odin's "BL" section
Select "CP" from the stock ROM folder in the odin's "CP" section
Select "HOME CSC" from the stock ROM folder in the odin's "HOME CSC" section
make sure you select all the official files from the stock ROM folder... just instead of the "AP" file, select the "magisk_patched.tar"
Then connect your phone via USB cable
Odin will detect and show "added" message
Start the flashing process
It will take few minutes
When its done your phone will boot up
But it will show something like "erasing" and "verification unsuccessful"
Just agree with that and erase the phone
(It will cause a data loss because everything will be deleted and your phone will reset, so i suggest to make a backup using samsung smart switch)
Then when your phone will reboot, just follow the steps to setup
Amd install magisk latest apk
Open magisk and boom!
You can already realize that magisk root is activated
Amd magisk will ask you to "setup environment"
Just agree and your phone will reboot withing 5 seconds
And done!
Your phone is now rooted
Install root checker and verify your root status
how to un-brick
Same thing here,
Tell me how you un-bricked your phone
I bricked my phone by installing wrong twrp file to sm-j720f android pie with odin
and now it shows only bootloader screen and I can't even go to recovery mode or home screen just showing " SAMSUNG GALAXY J7 DUO secured by Knox powerd by android" noting else
That is exactly what was happened in my phone
So what i did just downloaded the Stock ROM for J7 duo from the sam mobile website.
Then extract the ROM and you will get few files ("AP", "BL", "CP", "CSC", "HOME CSC")
Then boot your phone into download mode using this method
(Connect the phone to your PC using USB cable, then press and hold Power + volume down + home, then when the "powered by android" logo appears release only the power button... so your phone will boot into download mode, press volume up to continue)
Now, in odin you can see "added" message that means device is connected
Now select the ROM files respectively, BL, AP, CP, CSC
Then click start, and the process will start, will take few minutes
When done, your phone will boot normally
Yeah everything is right until...
[grand_theft;83142325]That is exactly what was happened in my phone
***********
So what i did just downloaded the Stock ROM for J7 duo from the sam mobile website.
Then extract the ROM and you will get few files ("AP", "BL", "CP", "CSC", "HOME CSC") *********
Then boot your phone into download mode using this method
Fact that I cant even go to download mode I tried out many times
Just follow this step
(Connect your computer with your phone using USB cable, then press and hold Power + volume down + home, then when the phone vibrates and appears the samsung logo again just release only the power key, while holding the volume down and home key)
(Just release only the power key when the "powered by android" logo appears)
Thats how you can go to the download mode
No virtual change
Done it as u say,
But my mobile shows noting but just logo screen
*****SAMSUNG GALAXY J7 DUO secured by Knox powered by android*****
again and again
These is not first time, last I did the same mistake before and I went to Samsung service store they recovered it, I don't know how they did but it worked.
These time I want to (tring to) do it on my own bcoz I love playing with ROM's, root, etc.
Thanks for replys
I also did the same mistake by flashing wrong TWRP
But however i managed to enter into downlod mode following those steps
And flashed official ROM to unbrick the phone
You must go into download mode to flash the official ROM using odin
Thanks alot
Thanks man,
I'm able to enter download mode and I installed official ROM. Now in using it as normal but (1)Secure folder and Pay mini are not working.
(2)Do you have any idea on other ROMs that works on SM-J720F other than Samsung's one UI.
(3)can I install android 8 on it in ordered to root as you said it in previous post.
(4)from previous your post on oreo twrp explanation, is twrp works fine. What happens to twrp if I update phone to Q (from system updater)
I'm glad you made it!
Now,
1) Secure folder and pay mini won't work because the phone thinks you rooted your phone and maybe your binary is cracked (so forget using those)
2) I'm not sure about any ROMs which is stable with this model. But you can search the internet (I think pixel ROM is pretty popular)
3) I'm not sure if my process of rooting supports android 9.0 or not, because i personally tetsted it on 8.0, So you can download the oreo ROM from the internet and then follow all the steps i mentioned before
4) If you want to install TWRP, you can still install TWRP after rooting via the method i provided
(You can install TWRP using flashify on a rooted phone)
But if you want root access then you can simply root your phone first..
And whatever custom ROMs you want to install, install it using flashify
Because if you update software via official OTA, the root access and TWRP both will be gone
And if you root your phone, then however you won't be able to perform a official OTA update.
(First root your phone, then simply download your TWRP file and flash it with root permission within your phone)
Instated of Oreo AP file,
grand_theft said:
I figured out a way to root the Galaxy J7 duo
Actually i have tried lot of ways to root using TWRP flash and all.. but one day i accidentally bricked my device
So i downloaded the stock ROM to flash my device
And i downloaded the 8.0 android ROM
So this root method basically tested on android 8.0
So now i have android 8.0 stock ROM downloaded
Step 1 -
So make sure you also downloaded the ROM
And extract the ROM file (you must have got the "AP" "CP" "BL" "CSC" and "HOME CSC" file)
Then copy the "AP" file in your phone
Then install magisk manager in your phone
Open magisk, select install, select and patch a file from magisk
Then select "AP" file
And wait while magisk is patching the "AP" file
When flashing is done the patched file will be saved on storage, emulated, 0, download (file will be saved as "magisk_patched.tar")
Then simply copy the patched file in your computer
Step 2 -
Open odin in your Computer
In odin, select "magisk_patched.tar" in "AP" section
Select "BL" from the stock ROM folder in the odin's "BL" section
Select "CP" from the stock ROM folder in the odin's "CP" section
Select "HOME CSC" from the stock ROM folder in the odin's "HOME CSC" section
make sure you select all the official files from the stock ROM folder... just instead of the "AP" file, select the "magisk_patched.tar"
Then connect your phone via USB cable
Odin will detect and show "added" message
Start the flashing process
It will take few minutes
When its done your phone will boot up
But it will show something like "erasing" and "verification unsuccessful"
Just agree with that and erase the phone
(It will cause a data loss because everything will be deleted and your phone will reset, so i suggest to make a backup using samsung smart switch)
Then when your phone will reboot, just follow the steps to setup
Amd install magisk latest apk
Open magisk and boom!
You can already realize that magisk root is activated
Amd magisk will ask you to "setup environment"
Just agree and your phone will reboot withing 5 seconds
And done!
Your phone is now rooted
Install root checker and verify your root status
Click to expand...
Click to collapse
************************************************************************************************************************************************************************************************************************************************************************************************************
Ok I agree with you,
But what if I replace Oreo's AP file with android 10's AP file(which I installed recently on my phone), will it boot with root or not.
************************************************************************************************************************************************************************************************************************************************************************************************************
I have not tested this method on any other android version, you can still try it on your own, there is nothing to lose, just make a backup before flashing. If you succeed then that's great
But i have personally tested this method only on android 8.0
(Before doing anything, just make a proper backup using samsung smart switch. So you can restore your important data)
Success
Replaced with android 10's AP file and flashed with Odin. Now my phone has rooted with Magisk manager.
Any suggestions to tweak android
Claudio4780 said:
Can it be used on the Dual-Sim version SM-J720F/DS released in 04/2018 ?
Click to expand...
Click to collapse
Have you ever got the answer or figured it out? I've got the same model and I cannot find anything on the net to help me with rooting this phone.
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"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"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy
ExileTM said:
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse
ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least
There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.
Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)
I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..
I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:
To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news
Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.
Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.