Hi,
In recovering from a brick, I had to install new firmware on my tablet. The firmware was for a different device, but still runs on my tablet. Since I installed this firmware, the system cannot connect to either camera when I try to use the camera app. I assume this is because the firmware is configured for a different camera setup.
My tablet is a no name Chinese made tablet. It is Allwinner A33 based (I opened it up to check). The current firmware is running KitKat. I have root access.
Any suggestions will be appreciated.
Thanks
Hey,
is there no possibility to reflash the old firmware again? Or to recover it?
If not, I would suggest you to try other firmwares with other camera setup till you find a working one...
Related
Hi all
A week ago a rooted my Samsung Galaxy S6 device following this post: http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
All was OK. At that point my device is using the Android Version: 5.0.2
The question I have is that now the version 5.1.1 (Lillipop) has been released, I would like to know if my rooted device can still be upgrading when the new version is released in my region (Mexico) by the phone provider. (Telcel). In case it cannot be updated automatically, I guess I will need to do it manually or unroot my device. In that scenario, Does someone know a good tutorial how to do that?
Regards!
@LesthadMK, sure you can update rooted devices. But it may not be possible via OTA update. You will have to download the full firmware and install it manually.
Because root makes changes to system partition, OTA fails when you have rooted. If you unroot and flash stock recovery and kernel back, then OTA may work. Otherwise, simply flash the full firmware, in .tar format using Odin software, and you're good.
It's good to have full firmware saved on PC anyway, as if in case you brick your device, you can fix it by installing your device's firmware manually.
If you need help with 5.1.1 firmware installation on your s6, let me know the build no. of your device.. I will guide you to page you need to look at.
Thanks for the help. I have download Odin in case I need to do it manually.
Also, mentioned that yesterday I read an article saying that using the Samsung software "Smart Switch" in an rooted device will upgrade the device to the newest version (which I don't know if it it's true or not) Any way this is the link I found:.... Well seems since I'm newby I cannot post some external links. So just google it as: How to Use Smart Switch to Update Your Galaxy S6—Even It's Rooted.
By other hand, this is the build number for my device: G920IDVU1AOE3, so if you can help me to know how to upgrade that version that would be very helpful
Regards!
Not sure if this is the right place to ask this, if not just move it. TY
I have an Xperia Z3 SO-01G from Japan.
I updated it with the latest firmware from xperifirm, however, the lollipop version is only 5.02 and they don't have 5.1.1 from Docomo
When I use the generic firmware NFC doesn't work.
My question is, is it possible to use the generic firmware and just extract the NFC drivers from the docomo firmware?
I want to use the generic firmware with the latest version of lollipop with no issues regarding the drivers.
I will highly appreciate if someone could help.
Thanks a lot
Id also love to hear if this is possible. Same phone and same issue
First, to clarify, there is no 100% working method to port NFC firmware from Japanese variants to Global firmware. Sony Japan uses different method to encrypt the drivers of all Japanese model, and it can be only used by using the required firmware.
Secondly, if you want to use NFC badly, STAY WITH STOCK. There is NO USE updating the software to 5.1.1 since the stock software from those network providers is fully compatible with the devices.
If you just want to use NFC for devices to devices connection, you can port the whole NFC packages and firmware from the stock rom and flash it to the Global one (I don't have SO-01G but the SOL26 from KDDI AU, and the package is call NFC Osafu/Keitai).
And if you are not using NFC really much, you can just disable the package from root.
Note: I used to obsessed with new OSes and try to do as much as I can to port every apks from Japanese firmware to Global, but after then I realized: Tons of bugs shown in catlogs, unstable system, apps crashed a lot, overheating even when not using (with NFC-Wifi-Bluetooth disabled too, no background apps), etc...
Now I'm sticking with the stock from providers and happy with it.
Thanks N0K0m3
I'm not so much obsessed with having the latest latest software as I am about root. I'd go back to 5.0.2 (or whatever the current global) firmware if NFC still worked. I don't suppose I could flash the previous kernel on top of this ROM and everything would be honky dory.
Any more advice you have is welcomed. I'm sure I'm not the only person curious.
Thanks again
this is my work long time ago for firmware (23.1.A.62), can not guarantee 100% working with NFC driver, because I don't have condition to test.
If you like, you can flash it as flashing prerooted zip.
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8
if wifi get problem, after flashing rom, flash this fix
https://drive.google.com/open?id=0B0EOZK8Eg5HBYjdGVVlsclNadm8
i was trying to remove kingroot and replace it with supersu after rooting; changed some superuser files and rebooted, now android won't load and i don't have a stock ROM or backup.
ironically i was trying to switch to supersu to get flashfire to work since i can't find a custom recovery (or any files or official english documentation) for it and don't trust flashing a possibly compatible custom recovery; it is a chinese, unbranded 8 inch tablet with built in projector, the ROM installed on it is likely customized from a network projector build of kitkat 4.4.4. the only scant documentation it came with is entirely in chinese, since it has no real "brand" i have no company site to visit for help and official downloads.
i tried a factory reset with no luck, and the stock recovery requires signed packages which would be excellent if i knew where to procure them.
the only thing i am certain of is the model rk3188, which is rockchip. i tried scouring through their entire list of firmware downloads but could not find anything close to BULUSE, H69, T80, YS, or any of the other generic names i've found it listed under.
this is the tablet:
https://www.geekbuying.com/item/BUL...Dual-Cameras-Bluetooth-4-0---Gold-367696.html
https://www.banggood.com/BULUSE-T80...-Inch-Android-Projector-Tablet-p-1024125.html
thanks!!
Dear Android Brothers and sisters,
I am wanting to update the firmware on my S6 (downloaded from SAMmobile) but am in an odd position...
My S6 main board failed (unable to see mobile networks), and after trying everything in the known universe to fix this, concluded it was hardware and purchased a second hand main board off eBay, that I've now fitted. It was working OK, but is from France (I am in England).
It worked OK but had an ancient stock ROM. The first thing I wanted to do was install Lineage, however there didn't seem any option to allow for the bootloader to be unlocked to allow me to flash the TWRP recovery. After much 'jiggary pokery', I downloaded the English firmware from SAMmobile, extracted all of the binaries and tried to flash them individually using Heimdall (I run Linux not Windows). Whilst this worked for some, there appeared to be a mismach in the partitions that were expected - I guess this is something to do with the France firmware being structured differently? So after a bit of soft-bricking, I managed to get Lineage on the phone, which is mostly working, but behaving somewhat strangely. At the end of the day, I want the latest firmware (radio etc.) and to have Lineage working OK.
Is it possible for me to somehow flash the English firmware on this French board (including the PIT which I assume relates to the partition structure which will allow it all to work)? Any ideas how I'd do this? If I'd have to use Odin, so be it, I'll do it work on my windows box, but ultimately I would like someone to confirm I can do this without bricking my phone. I've read around and people seem to suggest it would be OK but I don't know the best way to do this. I assume the best way to get to my stable end, would be to flash the latest English firmware from SAMmobile, unlock the bootloader, flash TWRP then install Lineage in the 'normal' way?
Any thoughts or suggestions (including pointers to other posts I may have missed) really gratefully received !
Cheers,
Neon
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.