Database Info

absurdly stupid move by me.3113wTWRPv2.6.3.0 only left

I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...

try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload

canezila said:
I was doing fine with my PAC-4.3.1. I backed everything up. Then I erased all ... yep... no OS. And trying to install something like the MicroDelta-P3110-4.2.2xxx... says its unable to open the zip file. So I probably messed up my root also.
I have very limited access to XP. I run Linux. Ubuntu, Debian ... but I can not find a working way to salvage my tab2.7 this way. odin for XP was how I got to 4.1.2.
I believe I need help in knowing what is the actual correct next step. I read the forum and have failed so far. So would someone be able to point me to the correct link knowing my situation?
I think I was on 4.2.2. Then PAC 4.3.1
I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term...
Click to expand...
Click to collapse
Now what do you mean by you erased everything? Even wiping system, user data and both caches won't break root. Was there something else you wiped that you probably shouldn't have? What you could do is set up a virtual machine for XP, or even dual boot. It's a little time consuming, but in the end I do believe it would be worth it If you can't even flash a zip I don't really know what else you could do. Hopefully someone else will chime in with a less exhausting solution. But dual booting or using a virtual machine is certainly option. That way you can easily odin back to stock.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
Android-Andi said:
try flashing PhilZ Touch using adb sideload, reboot into philz touch and try the rom again.... maybe flash the rom using sideload
---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------
Read this: http://teamw.in/ADBSideload
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
You can also try flashing any other Rom using adb sideload
Click to expand...
Click to collapse
I thought about that, but he said he broke root and can't flash a zip? Would sideloading work around that?

Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)

Android-Andi said:
Sure Sideload should work, i think root is not broken (can access to storage be broken in recovery? i don´t think so ) - maybe bad download of the rom or he can only flash signed zip´s ? maybe he can try disable zip-verification (?)
Click to expand...
Click to collapse
I've never had to use side load lol... You know more than I on the issue

How to setup ADB on Ubuntu? ---> http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
or http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
@canezila can you please check in TWRP -> Settings -> "Zip file signarure verification?" Checked or unchecked? If it´s checked: uncheck it!

Recovery couldn't open the zip. A failed signature verification would return a "signature verification failed" error, no?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

i don´t know what he did (i don´t think he knows it too ) let´s wait for his feedback...
trying to flash a recovery or another rom using sideload might work...
or he can try another file (only flashing a recovery.zip) flashing from a microSD card?
could be a bad download of the file too...
i´m going to sleep now hope my tipps work for him - i am sure he´ll give any feedback
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
"(...)I used to have Philz installed. Recently went to TWRP because I was getting very unreliable bootloops and switching helped in the short term..(...)"
a recovery wouldn´t make a rom bootlooping i think he forgot to wipe something.
i never had a bootloop or other strange problems on a working rom! NEVER!
What i am doing:
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset (on PhilZ Touch "Clean to install a new Rom")
flash rom
reboot
if it´s working i reboot into recovery again
flash gapps
flash NEXT Kernel
flash Proprietary files for NEXT Kernel
reboot again
(sometimes flashing NEXT Kernel + Proprietary files directly after the rom before 1st boot - only if i am on Dual-Boot)
---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------
If you like MicroDelta 4.1.2
Download
MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip and MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip
Try this (yes do it again):
wipe cache partition
wipe dalvic cache
format /system
wipe data factory reset
First flash MicroDelta-P3110-JB-4.1.2-P3110XXDME3-signed.zip
directly after that flash MicroDelta-P3113-JB-4.1.2-P3113XXDME3-signed.zip

$ sudo apt-get install android-tools-adb
$ adb version
Android Debug Bridge version 1.0.31
$ adb sideload philz_touch_5.15.0-p3110-blackhawk.zip
$ adb sideload blackhawk-next-kernel-2.1.5-p31xx-miui.zip
**probably usless step but I wanted to see if it worked and it installed wo errors***
$ adb sideload miui_3.10.25_p3110_beta2.zip
$ adb sideload proprietary-vendor-samsung.zip
** yes, I have no idea what I am doing because this probably is part of another thread.... but it is ok**
But now that I can easily push ROMs over... I am going to go crazy installing a bunch of similar 4.3.1 roms.
THANKS FOR THE HELP!

I ended up on PAC MAN 4.3.1. at least for now

[ROM] SU4TL-44 100% Stock

SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.

Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk

Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install

schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct

Can I install viper and su along with this?

MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.

TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol

MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?

Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.

The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.

firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?

TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.

MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.

firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!

Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?

MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945

TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.

bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this

hard brick? no download mode

So the phone failed to boot up out of no where, I could boot into download mode fine but recovery would just show blue letters and reboot without giving me the recovery menu. So from the download mode I used Odin to upload the latest bootloader downloaded from sammobile. It was a green light but now the phone won't boot up and won't even get to download mode and I still get the same recovery mode behavior. Help? What did I do and how can I fix it ? I don't know what firmware or bootloader were installed before but I assume the latest because by mistake I tried the third latest one and it would fail to upload via Odin.

cubajean10 said:
So the phone failed to boot up out of no where, I could boot into download mode fine but recovery would just show blue letters and reboot without giving me the recovery menu. So from the download mode I used Odin to upload the latest bootloader downloaded from sammobile. It was a green light but now the phone won't boot up and won't even get to download mode and I still get the same recovery mode behavior. Help? What did I do and how can I fix it ? I don't know what firmware or bootloader were installed before but I assume the latest because by mistake I tried the third latest one and it would fail to upload via Odin.
Click to expand...
Click to collapse
Give some background info on how the phone failed to boot up in the first place... And why do you not know what firmware it had previously?

thanks for the reply but i already gave up, i got lucky enough that it got in download mode and i odin back everything bl ad etc and still nothing . for info: the phone froze while in use candy crush i think and then failed to reboot, and I don't know the original firmware because I never checked

cubajean10 said:
thanks for the reply but i already gave up, i got lucky enough that it got in download mode and i odin back everything bl ad etc and still nothing . for info: the phone froze while in use candy crush i think and then failed to reboot, and I don't know the original firmware because I never checked
Click to expand...
Click to collapse
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
Click to expand...
Click to collapse
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
Click to expand...
Click to collapse
And then from the successful boot you should be able to flash the T-Mobile PK1 firmware (the latest firmware at this time).
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
KillerClaw321 said:
There's your issue, if you had a different firmware running on it the bootloader was probably a different version. I'd say your best bet would be to flash the latest firmware(not nougat) of all S7 variants(ex: At&t,Verizon,Sprint, Metro PCS...)
on the phone with odin and you'd know which firmware it was originally running if it boots without an issue.
---------- Post added at 07:20 PM ---------- Previous post was at 07:20 PM ----------
I'm pretty sure instead of doing this trial and error if you boot into the recovery it should show you the specific firmware version with the device model #
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
And then from the successful boot you should be able to flash the T-Mobile PK1 firmware (the latest firmware at this time).
Click to expand...
Click to collapse
And good luck! :good:

thanks, the phone was a tmobile variant and i flashed pk1 but still got the same issue. i was never able to get into recovery because it would just say recovery booting and get stuck there or reboot to the same

cubajean10 said:
thanks, the phone was a tmobile variant and i flashed pk1 but still got the same issue. i was never able to get into recovery because it would just say recovery booting and get stuck there or reboot to the same
Click to expand...
Click to collapse
But try flashing the latest firmware from other variants... It could have been running at&t firmware or Sprint firmware... Which is why I'm suggesting you flash them regardless...

I stupidly tried to install the new OTA while rooted

I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?

clankfu said:
I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?
Click to expand...
Click to collapse
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.

acejavelin said:
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.
Click to expand...
Click to collapse
thank you

so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.

bradmoss said:
so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.
Click to expand...
Click to collapse
It won't install, it will get stuck in recovery... Wiping cache deleted the update file and allows the phone to boot to its previous state.

where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...

bradmoss said:
where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...
Click to expand...
Click to collapse
All you did was try to update and wiping cache didn't fix it? Then there is more wrong. Backup in TWRP and do a factory reset (wipe data and caches)

In twrp go to file manager and find cache folder inside there is file update ( -----.zip) deleted then reboot

Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1

Agiofws said:
Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1
Click to expand...
Click to collapse
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.

---------- Post added at 07:03 AM ---------- Previous post was at 06:57 AM ----------
[/COLOR]
acejavelin said:
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.
Click to expand...
Click to collapse
My phone is rooted and unlocked and has TWRP. The update zip file file was automatically downloaded by Motorolas-androids OEM. System updates which I accepted. But as I can see from custom recovery it has a message about something like a pure signature to install even when I try manually. Thank you

HTC U12+ Bootloop after uninstalling Magisk Module

Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do

Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder

Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan

hello
no problem I would like to explain in detail but my english is very bad

Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again

En joy
You're welcome

I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me

Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think

I thinked that's because of slots

Hi
buddy what exactly is the problem

completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.

lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...

Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.

hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it

Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device

can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting

so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578

isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3

re-install the same rum without deleting or update it with adb sideload

tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(