hard brick? no download mode - T-Mobile Samsung Galaxy S7 Questions & Answers

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

Related

Not able to upgrade from 4.4.2 to 4.4.4

Hi guys, I just received the OTA update's notification, tried to install but "/system/framework/core.odex has unexpected contents" error appeared. I tried to wipe cache but it still appear.. what can I do?
I have uninstalled xposed and modules, and other apps that modifies system's files
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
here is the zip file? if i delete the zip file, the bootloop disappear?
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
It has been said already countless times now.
You need to be completely stock to be able to update via the official OTA.
Flash stock recovery, stock /system and then you'll be able to update.
I get an error while updating, it just says ''error''. I have stock kernel, stock recovery, unrooted... Nothing seems to work. I think the problem might be that I have a custom boot animation. Is there any way to flash the 4.4.2 stock UK rom?

Droid MAXX unlocked BL Custom Recovery?

I am sure that people have ran into this question with the Chinese Man coming back and the consumer editions becoming unlocked (if you are lucky enough to be a 2014 model) My question is, i currently have an unlocked bootloader Consumer Edition Droid MAXX running 4.4 from verizon. i am looking for the correct version of TWRP or another custom recovery (not safestrap) for this phone. i apologize if somebody else has posted a thread about this, but from my quick skimming of thread titles this does not seem to be clearly addressed. Also any insight on ROMs, etc would be appreciated after the custom recovery question is addressed. Thanks guys.
C4Charizard said:
I am sure that people have ran into this question with the Chinese Man coming back and the consumer editions becoming unlocked (if you are lucky enough to be a 2014 model) My question is, i currently have an unlocked bootloader Consumer Edition Droid MAXX running 4.4 from verizon. i am looking for the correct version of TWRP or another custom recovery (not safestrap) for this phone. i apologize if somebody else has posted a thread about this, but from my quick skimming of thread titles this does not seem to be clearly addressed. Also any insight on ROMs, etc would be appreciated after the custom recovery question is addressed. Thanks guys.
Click to expand...
Click to collapse
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120
aviwdoowks said:
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120
Click to expand...
Click to collapse
None of these worked. i effectively have no recovery currently. it says invalid size or something and boots directly to bootlloader
C4Charizard said:
None of these worked. i effectively have no recovery currently. it says invalid size or something and boots directly to bootlloader
Click to expand...
Click to collapse
Tell us exactly what you did, please?
aviwdoowks said:
Tell us exactly what you did, please?
Click to expand...
Click to collapse
I specifically attempted TWRP and used flashify to flash recovery image for 2.7.whatever . is it relevant I am running KK 4.4? I then attempted philz and it worked. But I feel more comfortable with twrp as its all I have ever used.
Are you rooted? How so if you have no recovery?
If rooted you must flash the .img with Rashr recovery tools.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
If Philz worked then redownload twrp.
Philz is great use my INI file to get started.
aviwdoowks said:
Are you rooted? How so if you have no recovery?
If rooted you must flash the .img with Rashr recovery tools.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
If Philz worked then redownload twrp.
Philz is great use my INI file to get started.
Click to expand...
Click to collapse
yes i am rooted untethered with write protection off. and if i can use philz to root then i will just stick with it. no need to fix what isnt broken
C4Charizard said:
yes i am rooted untethered with write protection off. and if i can use philz to root then i will just stick with it. no need to fix what isnt broken
Click to expand...
Click to collapse
Flash from recovery
http://download.chainfire.eu/supersu
aviwdoowks said:
Here is a better way to make a nandroid backup along with twrp links.
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
---------- Post added at 12:07 PM ---------- Previous post was at 11:55 AM ----------
Here is latest
http://forum.xda-developers.com/showpost.php?p=54953458&postcount=120
Click to expand...
Click to collapse
Read notes here as to a condition where twrp may not stick, or rather the phone acts as though it is not there & gives the Bootloader instead.
http://forum.xda-developers.com/showpost.php?p=54631556&postcount=1342
Got philz to work, all good! Thanks guys
I also have a consumer addition that's unlocked and couldn't get twrp 2.7 to load. Same error message too. I ended up going with twrp 2.6.31 - ghost-4.4 and it works fine.

[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

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

Categories

Resources