Related
hello friends, my nexus 4 usb debugging was disabled when the device blew rom, however I can turn it back on bootloader
I tried to install another rom when just ruining what was already installed, then it is no system running.
I'm not consiguindo to flash any other rom via ADB and TOOLKIT, also tried to install the ROM from sideload and I got nothing.
Also tried to transfer files to install an internal memory via rom put the "push" command does not succeed, all options call for activation of usb debugging.
How do I fix this? Please if anyone knows help me!
What recovery do you have? And what version also could I ask what ROMs you flashed that made this happen?
Sent from my Nexus 4 using Tapatalk
You can fix all issues like this by flashing a stock rom. Download it straight from google https://developers.google.com/android/nexus/images.
Flash using "flash-all.bat" for it to work properly you must have the fastboot.exe in the same directory (or have added it to your path).
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Brilliant! Thank you so much! Do you know any custom ROM what is better than the factory ROM?
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Adreno306™ said:
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Click to expand...
Click to collapse
Do you think it's easier/possible to adapt a ROM from a similar device like say, the Alcatel
Pop 2 (5) Premium ? I don't know if there's any ROM for that phone tho, but since it's branded as Alcatel you might get more support from the community here than by using Vodafone's name.
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Adreno306™ said:
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Click to expand...
Click to collapse
Hey, Andreno306
I don't know much about Rom's in that level of expertise I'm afraid :/ but I did some digging and came across this simple tutorial on XDA:
http://forum.xda-developers.com/showthread.php?t=2387941
I imagine it does not work for every single device out there, at least not with modifying stuff after, but it might be a good starting point I think, in fact I would try to actually make one myself had I a working PC currently at home. But even if I did I had no way of testing it because this is currently my daily driver phone.
Just wanted to say that I'm also very interested in getting a slim ROM for this device. I can't offer any expertise I'm afraid! Just wanted to show that there are people interested in your project.
:highfive:
Stock Kernel
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
vojta_horanek said:
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
Click to expand...
Click to collapse
I have one
https://mega.nz/#!tMJD3B4T!f6m2ELYCVupqGCcN2aGbkrNzEqijLu7au-7usEfeVL0
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Demonlord6 said:
I have one
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Click to expand...
Click to collapse
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
vojta_horanek said:
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
Click to expand...
Click to collapse
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Demonlord6 said:
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Click to expand...
Click to collapse
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
vojta_horanek said:
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
Click to expand...
Click to collapse
Yeap, that's not the same version as my ROM, mine is not 130FNN etc. Maybe that's why it didn't work
Enviado do meu GT-S5280 através de Tapatalk
Sorry for the stupid question but... does it works on Smart Prime 7 too?
Has anyone installed that linked ROM? It seems to be what we are looking for... a slim debloated rom.
I presume we need to be rooted, install this TWRP, then flash that ROM?
It mentions unlocking the bootloader, I dont think I've seen any info anywhere about unlocking the bootloader.
Can anyone give a quick lowdown on all the steps required to install that ROM please?
Hi everyone, I discovered that Elephone Trunk and Smart Prime 6 have (almost) identical specs: https://www.devicespecifications.com...ison/c584481c6
So it would be great to "port" (or build ?) the official Nougat-OmniROM for Trunk to VF-895N: http://dl.omnirom.org/trunk/
Last but not least, here's official Vodafone Smart Prime 6 sources: Vodafone_Smart_prime_6_20150413.tar.xz
TWRP for vodafone smart max 4 990N (coolpad 8890u).
I tried this recovery image for vodafone smart max 4 990N (coolpad 8890u).
The phone is in a bootloop state. I think i have usb debugging enabled already.
So, in fastboot mode i can see the device in my pc in adb fastboot cmd.
Im trying to ''fastboot boot recovery.img" but it stops in ''booting..''.
Dont know whats the problem but for sure i can not find a specific twrp image for this device.
If i enter fastboot oem device-info it says ''(bootloader) Device unlocked: true''.
Any ideas ?
hi i was wondering if you could share how you did this or if you can make one for the Vodafone smart n9 (VFD720) it would help a lot of people out looking for this
Needed to root a Vodafone Smart Prime 6 (VF 895N) (got it from a friend because it became unresponsive from all the updated google play stuff ) to get linux-deploy running. Just wanted to leave a big thank you here for Adreno306 for his TRWP 3.0.0-0. it did the job very well!
Only the procedure to get it installed differed quite a bit for me, since Flashify is no longer available.
I wanted to preserve boot and just flash trwp to recover, what worked quite well.
The first thing I did was to boot the phone manually in recovery mode (Power+Vol up) and reset it to factory settings from there. It takes a little while. Then follow the setup, go to phone settings, enable developer mode and set usb debugging. If "unlock oem" is not available there, reboot into recovery again, set unlock there and reboot into bootloader.
The prerequisites are adb and fastboot, both must work. Means adb devices and fastboot devices must show the phone. What can make problems under win10 as it sometimes does not detect the phone in bootloader mode. An actual google usb driver is needed, as provided by google.
For me adb worked well, but when rebooted into bootloader with adb reboot bootloader, fastboot didnt detect the phone. With the phone still connected, the windows device manager showed an unknown device with and exclamation mark (!). Right click, install driver, select driver manually, select driver from device list, mark all devices (first entry) and click "disk", then point to the usb driver director and select "ADB fastboot driver". ( A more comprehensive description is available here )
Once adb and fastboot detect the device, it is time to prepare it. Boot to system (normal operation) first. Make sure that the TRWP 3.0.0-0.img is renamed to trwp.img and then
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot boot trwp.img
Now the phone should show the trwp menu, set it up to root the phone and install SuperSU. Reboot into bootloader and
fastboot flash recovery trwp.img
fastboot reboot
Verify with adb reboot recovery, you should see trwp now. Reboot to system.
Now finally go into the app selector, start SuperSU, and root the phone. SuperSu uses trwp recovery mode to install its image and root is done.
Again, big thanks for providing the TRWP image!
Adreno306™ said:
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Click to expand...
Click to collapse
Hi, I would like to try your tutorial but I can't root this phone (which is an important step in the tutorial), is there any way someone could help me??
Thanks
Hey guys,
I hope someone can come to the rescue with this matter. I did an OTA update on my LG G2 (D803) and it booted to twrp option menu. I downloaded the stock firmware (which is a ".kdz" file) for the phone but can't find a way to install it on the phone since the PC is not connecting to it neither does it have external memory. I played around the options like restore, advanced but it seems empty. I can't even turn off the device with the power button. What can I do? Please help
rosh88 said:
Hey guys,
I hope someone can come to the rescue with this matter. I did an OTA update on my LG G2 (D803) and it booted to twrp option menu. I downloaded the stock firmware (which is a ".kdz" file) for the phone but can't find a way to install it on the phone since the PC is not connecting to it neither does it have external memory. I played around the options like restore, advanced but it seems empty. I can't even turn off the device with the power button. What can I do? Please help
Click to expand...
Click to collapse
OTA updates don't work when custom recoveries are installed. The device would be bricked. Sorry you found out the hard way. If you can boot into TWRP, you can download a ROM and Gapps. Buy the usb flash drive that has both USB point and Android 3.0 point. Copy the downloaded ROM unto it, slot into the charging port of the phone, boot into recovery. It should detect the usb flash, navigate to downloaded ROM and flash. This would work if you can boot into TWRP. Hope it works. Give feedback. Good luck
Sent from my Motorola Droid Turbo
abbykay said:
OTA updates don't work when custom recoveries are installed. The device would be bricked. Sorry you found out the hard way. If you can boot into TWRP, you can download a ROM and Gapps. Buy the usb flash drive that has both USB point and Android 3.0 point. Copy the downloaded ROM unto it, slot into the charging port of the phone, boot into recovery. It should detect the usb flash, navigate to downloaded ROM and flash. This would work if you can boot into TWRP. Hope it works. Give feedback. Good luck
Sent from my Motorola Droid Turbo
Click to expand...
Click to collapse
What about ADB or terminal command? I see it under the "Advanced" Menu in TWRP?
If you can do into download mode and allready have KDZ file just use flash tool 2014 to go back to stock (search here for "going back to stock:" post)
Also.. if you can send data over usb cable, try to use sideload to upload custom rom, or like stated before, use USB stick with OTG
You can also try this one: https://forum.xda-developers.com/showpost.php?p=71044359&postcount=2
or this as a last case scenario: https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
sakej said:
If you can do into download mode and allready have KDZ file just use flash tool 2014 to go back to stock (search here for "going back to stock:" post)
Also.. if you can send data over usb cable, try to use sideload to upload custom rom, or like stated before, use USB stick with OTG
You can also try this one: https://forum.xda-developers.com/showpost.php?p=71044359&postcount=2
or this as a last case scenario: https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
I have moved the kdz file to a usb stick and attached a usb stick to an OTG. But where in TWRP do I go to read the usb stick and how can I complete the process? Also I did try the SRK tool from on the links you provided. The phone is not detecting the computer while plugging in the usb while the phone is on TWRP and the computer makes a noise when the usb is connected but srk tool is not reading the phone.
You can't flash kdz with twrp or other recovery! Download custom Rom and gapps or a debloated stock rom and flash it with twrp. The custom Roms are zip files. Do you have twrp installed?
Gesendet von meinem LG-D802 mit Tapatalk
Yes you CANNOT flash KDZ with TWRP you need FLASH TOOL 2014. Download flash tool 2014 (search it on xda) than, in your G2 go into download mode, connect your phone to pc with usb cable and than run flash tool to flash kdz
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?