[a520f] Bricked after flashing boot partition with heimdall no Downloadmode/Recovery - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

[a520f] Bricked after flashing boot partition with heimdall no Downloadmode/Recovery - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
i cannot acces Download mode or recovery or boot the phone
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response

wolkengold said:
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
Click to expand...
Click to collapse
Can you boot to download mode? If you can, flash latest oreo.

iloveoreos said:
Can you boot to download mode? If you can, flash latest oreo.
Click to expand...
Click to collapse
no i cant... at least not with button combinations...

wolkengold said:
no i cant... at least not with button combinations...
Click to expand...
Click to collapse
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.

iloveoreos said:
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
Click to expand...
Click to collapse
thanks, i will try if smart switch will help me.

wolkengold said:
thanks, i will try if smart switch will help me.
Click to expand...
Click to collapse
There is a small chance.

iloveoreos said:
There is a small chance.
Click to expand...
Click to collapse
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...

wolkengold said:
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
Click to expand...
Click to collapse
Cool! Now what happens when you reboot to download mode from twrp?

SnowFuhrer said:
Cool! Now what happens when you reboot to download mode from twrp?
Click to expand...
Click to collapse
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.

SnowFuhrer said:
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
Click to expand...
Click to collapse
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Flash stock firmware using Odin?

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.

SnowFuhrer said:
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
Click to expand...
Click to collapse
sorry for the late response. You were right, i accidentally downloaded an older oreo release and thats why i could not flash it. I now downloaded the newest stock rom from updato.com and it worked perfect.
Thanks for your support

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked

jack364030 said:
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
Click to expand...
Click to collapse
You are correct but...He sorted this 4 months ago.

Related

Can't Get Into Recovery Mode

Following the steps provided by Team Win on http://teamw.in/project/twrp2/213, I flashed the pre lokid recovery img that they provided, however I can't access it, I get "Secure booting Error! Cause: boot certification verify"
My firmware is V50020d(seems to be a troublemaker)
Command used
Steps Taken:
1. Enter adb shell
2. Get root using su
3. dd if=/sdcard/openrecovery-twrp-2.8.0.1-awifi.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How I try to enter recovery mode:
Power + Down, Release Power, Press and Hold Up + Power, Release All Three, Press Power again and again

Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.

woody1 said:
Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.
Click to expand...
Click to collapse
The linked provided only works for 20a and 20b, do you have a mehtod that works for 20d?

Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.

woody1 said:
Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.
Click to expand...
Click to collapse
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.

woody1 said:
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?
Click to expand...
Click to collapse
Flash stock via the LG Support Tool, then did everything again and now running CM11 M10
Beer

muiriddin said:
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.
Click to expand...
Click to collapse
You were right adb caused an issue for some reason.
Beer

[Q] SM-P600 Bricked (no recovery)

Hi,
SM-P600 without ROM, without recovery, Kies and Odin doesn't work.
How can I reflash stock ROM or CM12 rom ?
Device : SM-P600 (with samsung rom stock 4.4!?)
I root my tablet with odin and teamwin 2.8.0.0 (PDA field + tar file)
the root flash should success.
I restart in recovery and install custom rom CM12 + Gapp
the tablet restart and stay to CM12 loading during all the night.
I come back into recevery mode
I try to wipe cache/dalvik => unable to mount cache/dalvik
I try to wipe cache => unable to mount cache
I try to wipe system => unable to mount system
I install Kies on my computer and try to restore the official rom with it.
The download of the rom is ok and Kies try to send the rom to the table a transfer is running during 15min (progress bar into computer windows, but no progress bar into tablet).
After that a second transfer progress bar into computer stay to 0% during 1 hour. I unplug my tablet.
Now I have got a table without recovery. I have access to download mode.
But I cannot transfer stock rom (PDA field) with Odin.
Thx for your help.
Staying at your disposal

I can flash recovery mod (TeamWin) with Odin.
But I cannot send Kies tar file by Odin.
I am downloading old stock rom (*tar) to transfer by Odin 3.09
How can I convert a CM12 zip file in tar file to tranfer it (I haven't SD card)

You could use a USB OTG cable (micro USB plug on one end and a socket like the USB ones on a computer on the other), one of these:
http://m.ebay.com.au/itm/301542874539?nav=SEARCH
And use it to plug a USB stick with the zip file on it into your tablet. You would have to mount it in twrp before flashing the zip.
They are a very useful cable to have, if your screen breaks and touch doesn't work you can use it to plug a mouse into the android device and use that for things like backing up your data before repair or disposal.

Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English

Hi Dribounet
Dribounet said:
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Click to expand...
Click to collapse
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers

p600 bricked
kafencetu said:
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
Click to expand...
Click to collapse
I have the same problem! There is download mode only - NO recovery, NO rom! ((
I have tried to flash original rom from sammobile via Odin. No results.
Who can help???

uno mas said:
I have the same problem! ((
Who can help???
Click to expand...
Click to collapse
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk

kafencetu said:
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
In other words - should I go to the service?

uno mas said:
In other words - should I go to the service?
Click to expand...
Click to collapse
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk

kafencetu said:
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266

uno mas said:
I have rooted also. No the warranty. But it doesn't matter if you have a bricked. ((
The Odin starts writing but no finish.
Click to expand...
Click to collapse
yep this is the case , Odin start process of writing and then suddenly - error - in the middle of the procedure.
I have tried to install only custom bootloader - pass successfully ,but then I am not able to go in bootloader mode ( I am trying with Volume down + Power , do not know is that correct - do you have an idea? )

uno mas said:
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
Click to expand...
Click to collapse
Hello uno mas
would you advice what tools you have used and also what order you have follow.
First update PIT and then installed the ROM or other
Thanks in advance for time and efforts!

[Q] Nand write fail for rom flash SM-T805

Hi, I am in need of assistance. I have a Tab S 10.5 SM-T805 with rom XXU1ANF8
I am struggling to flash firmware for my sm-t805 using odin and stock roms downloaded from sammobile. I have tried various version of the stock roms as well as different versions of odin, but they all have the same result.
The result is either "NAND Write Start! FAIL!!" or "Setup connection.. Can't open the serial(COM) port." The order in which I do things might impact which error I receive, such as attaching the tablet first or selecting the ROM file first in PDA box.
Here is why I am desperate. Since this result was pretty consistent, I flashed TWRP successfully and wiped all the partitions, including the system partition. Now, there is no OS installed. Using TWRP I have attempted the 'Install' method of flashing ROMS, but now my error is exclusively the first type.
I read some of the other threads and attempted any advice relevant posted there. This is sort of relevant to what I am trying to do, but my system partition has been wiped. (http://forum.xda-developers.com/galaxy-tab-s/help/odin-flashes-fail-t3028264), so there is no relevance to enabling USB debugging for disabling reactivation lock. This is a guy who can do what I am trying to do. (http://forum.xda-developers.com/galaxy-tab-s/help/roms-flashing-advice-t805-t3031963)
Please help!

eeekw0 said:
Hi, I am in need of assistance. I have a Tab S 10.5 SM-T805 with rom XXU1ANF8
I am struggling to flash firmware for my sm-t805 using odin and stock roms downloaded from sammobile. I have tried various version of the stock roms as well as different versions of odin, but they all have the same result.
The result is either "NAND Write Start! FAIL!!" or "Setup connection.. Can't open the serial(COM) port." The order in which I do things might impact which error I receive, such as attaching the tablet first or selecting the ROM file first in PDA box.
Here is why I am desperate. Since this result was pretty consistent, I flashed TWRP successfully and wiped all the partitions, including the system partition. Now, there is no OS installed. Using TWRP I have attempted the 'Install' method of flashing ROMS, but now my error is exclusively the first type.
I read some of the other threads and attempted any advice relevant posted there. This is sort of relevant to what I am trying to do, but my system partition has been wiped. (http://forum.xda-developers.com/galaxy-tab-s/help/odin-flashes-fail-t3028264), so there is no relevance to enabling USB debugging for disabling reactivation lock. This is a guy who can do what I am trying to do. (http://forum.xda-developers.com/galaxy-tab-s/help/roms-flashing-advice-t805-t3031963)
Please help!
Click to expand...
Click to collapse
Is activation lock off? That what causes it not to flash. The only thing I can suggest is transferring a custom zip rom and flash it with twrp. Or try another firmware from a different country.

Thanks for your response.
DUHAsianSKILLZ said:
Is activation lock off? That what causes it not to flash. The only thing I can suggest is transferring a custom zip rom and flash it with twrp.
Click to expand...
Click to collapse
It was my observation that this activation lock is off by default on the stock rom. In order to turn this on, you have to register with a Samsung account.
DUHAsianSKILLZ said:
Or try another firmware from a different country.
Click to expand...
Click to collapse
The versions I hav already tried are from different countries as well as from different update dates.
Please help!

Here's lollipop for T805, someone took out a few files which should fix NAND Write. http://forum.xda-developers.com/showthread.php?p=59828324

Have you got the Samsung USB drivers installed? If you don't get the 'added' message when connecting the tab you wont be able to flash anything.
Sent from my SM-T805 using XDA Free mobile app

I am having a very similar problem, except my device is working properly. The only thing is that I can't flash the new Lollipop firmware because of this error.
Does anyone know how to solve it?
Thanks!

vrgimael said:
I am having a very similar problem, except my device is working properly. The only thing is that I can't flash the new Lollipop firmware because of this error.
Does anyone know how to solve it?
Thanks!
Click to expand...
Click to collapse
Try flashing this? http://forum.xda-developers.com/showthread.php?p=59828324 Someone took out the hidden.img and cache imgs and tar it back together. You can take a look at the thread for more info

DUHAsianSKILLZ said:
Try flashing this? http://forum.xda-developers.com/showthread.php?p=59828324 Someone took out the hidden.img and cache imgs and tar it back together. You can take a look at the thread for more info
Click to expand...
Click to collapse
Just tried it. Odin doesn't recognize it as a firmware for some reason. Is there anyway to fix this? Also, what is knox warranty void?

Hi, i have also this problem, Original and the cleared .tar (swisscom) comes with this "fail" information in Odin ...... no plan what that for a problem. I am from Germany and i use a 805 LTE. Wich Odin version is the best for flash 5.0.2 i use 3.10.6 eventuelle is that an problem

meexx said:
Hi, i have also this problem, Original and the cleared .tar (swisscom) comes with this "fail" information in Odin ...... no plan what that for a problem. I am from Germany and i use a 805 LTE. Wich Odin version is the best for flash 5.0.2 i use 3.10.6 eventuelle is that an problem
Click to expand...
Click to collapse
Is reactivation lock off as shown here

This is my odin screen ..... no entris with reactivation. 4.4.2 runs with cf-autoroot and twrp recovery

meexx said:
This is my odin screen ..... no entris with reactivation. 4.4.2 runs with cf-autoroot and twrp recovery
Click to expand...
Click to collapse
Idk then, I guess you got to wait for another firmware that comes to your country

Just flash the Swiss Rom then after it fails, boot into download mode again then Install and boot into twrp.
Twrp will wipe the cache and auto reboot. The device should then boot normally.

Is TWRP 2.8.6.0 chagallwifi ok for this procedur ? and can i flash the original swisscom ? or the cleared .tar without the two files ..... and when i in download mode ... wich kombo can i use for reboot in download mode again

meexx said:
Is TWRP 2.8.6.0 chagallwifi ok for this procedur ? and can i flash the original swisscom ? or the cleared .tar without the two files ..... and when i in download mode ... wich kombo can i use for reboot in download mode again
Click to expand...
Click to collapse
Twrp for chagallwifi should do it. Flash swisscom odin firmware then flash twrp and wipe. Reboot into Download by holding power+volume down+ Home buttons

I have tested this procedure and it dont work for my tab .... i must wait for a no branding rom. It dont boot .... hangs on system.img in odin. Twrp is ok now i cant boot after flash twrp, it stay at samsung logo and no boot .... i have 30 minutes wait. Ok i will wait for a other lolipop rom

meexx said:
I have tested this procedure and it dont work for my tab .... i must wait for a no branding rom. It dont boot .... hangs on system.img in odin. Twrp is ok now i cant boot after flash twrp, it stay at samsung logo and no boot .... i have 30 minutes wait. Ok i will wait for a other lolipop rom
Click to expand...
Click to collapse
There is no branding in the system image. I don't see why it won't flash. Can you post a screenshot of Odin. Also what is your official firmware build number?
German Vodafone firmware is up: http://samsung-updates.com/details/43138/Galaxy_Tab_S_10.5_LTE/SM-T805/VD2/T805XXU1BOCC.html

ashyx said:
Just flash the Swiss Rom then after it fails, boot into download mode again then Install and boot into twrp.
Twrp will wipe the cache and auto reboot. The device should then boot normally.
Click to expand...
Click to collapse
I had the same issue today, when using the UK 5.0.2 ROM. These steps helped and it worked afterwards, thanks!

Issue -Wipe while boot 4.4

I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?

moby.dog said:
I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?
Click to expand...
Click to collapse
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.

levone1 said:
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.
Click to expand...
Click to collapse
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?

moby.dog said:
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?
Click to expand...
Click to collapse
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.

levone1 said:
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.
Click to expand...
Click to collapse
no i dont get into recovery because i cant boot 4.4

moby.dog said:
no i dont get into recovery because i cant boot 4.4
Click to expand...
Click to collapse
If you want to be on 4.4, use Flashtool and flash a stock 4.4 ftf, then root with Doomlord. If you want to be on LP, use Emma, it will download and flash firmware for you.
Flashtool - http://www.flashtool.net/index.php
Emma - https://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
KK ftf - https://forum.xda-developers.com/so...f-xperia-z1-compact-d5503-14-4-0-157-t3118047

how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone

moby.dog said:
how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone
Click to expand...
Click to collapse
When you flash with Flashtool, there is a box that says 'wipe'. Check the 'userdata' option.

thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img

moby.dog said:
thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img
Click to expand...
Click to collapse
Did you unlock bootloader? KK version 442 or 443? Add debugging enabled in settings? If all yes, I'm not sure why it wouldn't work. You could try different options, there are a few for KK - pimped kernel, Great devs kernel, and you could root with easy rootkit.
BTW - to restore your phone without flashing whole ROM again, check boxes under 'exclude' options for everything but kernel.

levone1 said:
KK version 442 or 443?
Click to expand...
Click to collapse
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.

moby.dog said:
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2784900

I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."

moby.dog said:
I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."
Click to expand...
Click to collapse
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?

levone1 said:
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?
Click to expand...
Click to collapse
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?

moby.dog said:
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?
Click to expand...
Click to collapse
Ok, try this - download this zip https://mega.nz/#!lh9i0AYI!iH3Vw5keSNo66CHvq3c6V9HMCWAWJ5FIYcZZ35U254g It contains 2 files, one is a kernel and one is a recovery. Also download supersu 246 zip from here https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 and put it on your phone somewhere. Then connect in fastboot mode and flash the 2 IMG files:
'fastboot flash boot [name of kernel file].img'
'fastboot flash recovery [name of recovery file].img'
Then unplug and power on. When you see colored led, press volume key and you should get into recovery. When in recovery, flash supersu zip. Then power off, and connect in flash mode. Open Flashtool and flash the stock kernel from your ftf. Reboot and you should be rooted.

Thanks that worked! And now i flash the 4.4 stockrom and after that a prerooted version?

moby.dog said:
Thanks that worked! Can i flash the latest stockrom now?
Click to expand...
Click to collapse
You can flash whatever you want now. If you want stock 5.1, you can use Flashtool / Xperifirm to download ftf and flash, or use Emma. You will lose root, but you can get it back the same way you just did. If you want to root 5.1 that way, you can extract boot img from advanced kernel and download latest twrp img, and just fastboot those, and no need to reflash stock kernel afterwards.
Advanced kernel - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060
Twrp 3 for Z1c - https://www.androidfilehost.com/?fid=529152257862711713
Alternately, you could flash a prf, or any custom ROM you want

Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..

moby.dog said:
Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..
Click to expand...
Click to collapse
What did you flash?

A70 vbmeta error after magisk update 20.0

Hello everyone,
after many hours of research I couldn't find anyone with the same problem or any solution for this.
Recently (yesterday) magisk brought out a new update 20.0 and I got a notification so I opened magisk manager and clicked on update magisk auto (recommended). After it updated successfuly, a reboot button appeared on right bottom corner and I clicked it. After it turned off and on it went directly to download mode and of top of the screen there was this error:
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Screenshots:
https://prnt.sc/pigzsh
https://prnt.sc/pih0ax
And after like 3-5 times I hardreset (VOL DOWN + POWER) then immediately press VOL UP + POWER to come into magisk root mode again, the device boot but I have no root anymore. And there is no auto update choice anymore at magisk. I tried also patching the official firmware again and flash it but didn't work, I'm still not rooted and I get always many times to download mode with this error if I reboot the device.
Did anything go wrong during magisk auto update?
If yes, why it said "update success"?
Do I have to update magisk? I used the auto update method the first time and I am deep in trouble.
What should I do to fix this and getting rooted again?
If possible without losing my files/wipe data.
My device: Galaxy A70 (SM-A705FN/DS)
Android 9
Thanks in advance
HH

Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.

Vmbeta Image
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?

xeedes said:
Hello, could you please post the original stock vmbeta image, i can't get out of that screen in the screenshots without flashing it and i am very stressed.
Please help me?
Click to expand...
Click to collapse
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^

Ial69 said:
hello xeedes, what screen you have ?
the same as "partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC" ???
try twrp maybe ?
flash with odin.
what have you done to get screw to that screen ?
ps : i think this screen mean you have try to modify partition system with stock vbmeta. stock vbmeta does not allow modifications. maybe... i dont know exactly ^^
Click to expand...
Click to collapse
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen

xeedes said:
I tried to relock the bootloader when flashing a modified vbmeta, now its stuck and will only continue if i flash the stock vbmeta i assume. yes its the exact same screen and message and this phone won't let me flash anything :/ nor exit the screen with any key commands, just flashes a70 and immediately goes back to the said screen
Click to expand...
Click to collapse
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
ps : cant post link to samfirm because the forum lock me to post external link....(because im a new user)
and you need to have unlock your bootloader to flash, bad things can happens with a lock bootloader. like brick.

Ial69 said:
I think you need custom recovery if you're stuck on this screen.
its a good news your phone boot in download mode and is detected by odin.
dont relock bootloader. (maybe... if you know what you do forget that ^^)
if you want stock vbmeta try to download all the stock rom from samfirm.
then flash all the stock rom ( if possible, verify the requirements)
hope this help.
Click to expand...
Click to collapse
hey, thank you for the reply, i've tried flashing the stock rom but nothing happens. downloading it from samfirm though. im going to sleep. thank you for the help

its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released

emadhussein said:
its really that hard guys, no one can root this device without having vbmeta and magisk problems,
it has been 6 months since this phone released
Click to expand...
Click to collapse
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...

I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?

xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
Reboot phone and pc. Then retry to flash TWRP. The phone will boot fine.
this work for me.
I root this phone with magisk at first time. no problem...
follow tuto.
for magisk :
https://forum.xda-developers.com/galaxy-a70/how-to/to-root-magisk-odin-t3930099
for TWRP :
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
i have vbmeta error too, bypass with TWRP. cant help you more than that, sorry....

BK said:
never got problems like that , as long as you follow tutorial it's fine , a blank vbmeta image have to be flashed in order to bypass boot verifications like theses , it's not that hard...
Click to expand...
Click to collapse
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix

emadhussein said:
Everything was fine till magisk got update v20
I got vbmeta error in the download mood , even tho i flashed vbmeta file , any idea how to fix
Click to expand...
Click to collapse
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?

Ial69 said:
to update magisk you have to patch a recovery.img with magisk then install it with TWRP/odin.
just like the first time you get root with magsik ?
Click to expand...
Click to collapse
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still

emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
sorry, do you have try to install twrp ? he cause the vbmeta error ?
what odin says ?
Do you have reboot phone and pc before each try ?
need to uncheck autoreboot in odin too, like even.

Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
emadhussein said:
yes i did that, but i end up with vbmeta error , i flashed vbmeta but still
Click to expand...
Click to collapse
Better try flash twrp since it works for many.
Read all answers in this thread.

HornyHugo said:
Thanks for every answer, I didn't try flashing TWRP but I will try when I go home. Seems like it fix the problem for alot of people. Thanks guys I will tell you if it worked for me or not.
Better try flash twrp since it works for many.
Read all answers in this thread.
Click to expand...
Click to collapse
this is what i say from the beginning.

Ial69 said:
Hello !
Dont worry, same here. Just install the unofficial twrp from step 4 (flashing vbmeta)
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
Now your phone will be able to boot to twrp then to system
Follow step 5 for root.
I do that and my phone boot again and magisk updated.
You will lose nothing, easy and fast
Good luck !
PS : dont know Why we have this problem. But this solution work for me.
Click to expand...
Click to collapse
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?

HornyHugo said:
But step 4 says after flashing vbmeta.tar you need to go to recovery mode and wipe data. And this will make me lose all data. Do I need to flash vbmeta if I flash twrp?
Click to expand...
Click to collapse
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
4 - Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
You begin from step 4. step 4 no need to wipe.
wipe is for step 3.
you are already unlock and rooted your phone if you have tried to update magisk and get stuck on vbmeta error.
ps : just do step 4. flashing recovery. then step 5 for root access ^^
good luck !

xeedes said:
I've attempted to flash the stock rom but when i do, i get this.
https://ibb.co/mqhCKfc
Any thoughts?
Click to expand...
Click to collapse
just connect your device to computer with cable and boot it with volume buttons

Develop Bugs

welcome