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

J700P Boot-Loop

Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.

I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk

Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.

No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk

I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well

where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.

Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious

uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem

chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img

DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.

uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...

uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p

messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect

Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!

messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..

Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it

V10.0.4.0 OTA dump

Downoad: https://android.googleapis.com/pack.../ba01b724176da9aaaf8c58c30f502a2c665a530e.zip
How to extract payload.bin :https://github.com/cyxx/extract_android_ota_payload
patched boot.img : https://mega.nz/#!5tgHCKrY!-rMlD4X2ShS1QTM4TK0g9SW2uJ6QTvwqeJrgC7EscZI

Please can you give me a personal message once the patched boot image upload is complete?
My email address is [email protected]
Thank you

Nanayaw1 said:
Please can you give me a personal message once the patched boot image upload is complete?
My email address is [email protected]
Thank you
Click to expand...
Click to collapse
i found this, and its work
ps: im not in beta tester
https://forum.xda-developers.com/showpost.php?p=78900186&postcount=8

Delta updates aren't extractable.

thorin0815 said:
Delta updates aren't extractable.
Click to expand...
Click to collapse
Don't know exactly what you mean but i managed to extract all images from this payload.bin
My phone is already updated with magisk installed.
So i tried to boot with fastboot command the boot.img extracted and it failed.

-edit

thorin0815 said:
Delta updates aren't extractable.
Click to expand...
Click to collapse
Yes, sad but true... payload dumper says "can´t open image file"
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
k4sh44 said:
Don't know exactly what you mean but i managed to extract all images from this payload.bin
My phone is already updated with magisk installed.
So i tried to boot with fastboot command the boot.img extracted and it failed.
Click to expand...
Click to collapse
Can you share your extracted images?

Here is the zip file with all images.
All images 1.0.4.0 update
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.

k4sh44 said:
Here is the zip file with all images.
All images 1.0.4.0 update
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
These system/boot images are completely useless, because they are taken from a Delta update and therefore they contain only the code that has changed, not the whole image.
No wonder you couldn't boot up your extracted boot.img, it's only 50% of the file.
Some infos about Delta updates: https://en.wikipedia.org/wiki/Delta_update

So, the patched boot.img of the first post is not valid?

thorin0815 said:
These system/boot images are completely useless, because they are taken from a Delta update and therefore they contain only the code that has changed, not the whole image.
No wonder you couldn't boot up your extracted boot.img, it's only 50% of the file.
Some infos about Delta updates: https://en.wikipedia.org/wiki/Delta_update
Click to expand...
Click to collapse
Ok, good to know.
Thnx
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
jespaper said:
So, the patched boot.img of the first post is not valid?
Click to expand...
Click to collapse
It may be good.
The one i extracted is only 14MB while the one provided in OP is 26

patched boot
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg

foo9001 said:
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg
Click to expand...
Click to collapse
Thanks very much for posting the link to OTA dump. The ONLY way of updating my phone is by flashing these files, everything else fails, so good to get them so soon after the ota came out.

the version 10.0.4.0 has drain of battery?

patched boot 10.0.4.0
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
---------- Post added at 04:42 AM ---------- Previous post was at 04:31 AM ----------
professor.gold said:
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Click to expand...
Click to collapse
/file/d/1VtrcbUC7yl2kX3KgM0Fmeuxsa4Drw5gW/view
Add a title drive at the start of the download because I am a new member

Vitor00 said:
the version 10.0.4.0 has drain of battery?
Click to expand...
Click to collapse
Not on my side, same battery performance like on 10.0.3.0.

the v10.0.3.0 patched boot img still works on the latest update v10.0.4.0. i tried to reflash it and it worked ! i guess the latest security patched didn't change the boot.img

viking777 said:
Thanks very much for posting the link to OTA dump. The ONLY way of updating my phone is by flashing these files, everything else fails, so good to get them so soon after the ota came out.
Click to expand...
Click to collapse
If it's rooted it might be one of the apps is altering the system partition, I kept getting failed OTA installs as well. What you can try is flashing the current version again and then try to do the update.
My case I'm suspecting it was AdAway because I didn't have the Magisk systemless hosts module installed.

did anyone have original system.img from 10.0.4? i have problem with update i think i forgot have changed something on my system.
Update:
work with this system, Thanks
foo9001 said:
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg
Click to expand...
Click to collapse

Patched boot v10.0.7.0
Can I have the March patched boot v10.0.7.0 ?? I was unable to find it anywhere. A reply with a link to the patched boot will be appreciated.
Thanks

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.... ;-(