From the 3.1.0 version of TWRP I have accidentally deleted everything, including my phone's OS. Thus when I reboot from twrp, it says no OS installed. I have downloaded several stock roms for my phone (Samsung Galaxy Grand Max SMG-720N0) When I install them with twrp, I always get invalid zip file. I do not have a backup on my sd card, so if anyone has a backup, or has the same phone, I am sincerely and desperately asking your aid to upload a restore version of a freshly formatted rom. I am stumped as to what else I can do.
Try looking up rom for your device at SamMobile & use odin to reload your OS
Jjkraust101 said:
From the 3.1.0 version of TWRP I have accidentally deleted everything, including my phone's OS. Thus when I reboot from twrp, it says no OS installed. I have downloaded several stock roms for my phone (Samsung Galaxy Grand Max SMG-720N0) When I install them with twrp, I always get invalid zip file. I do not have a backup on my sd card, so if anyone has a backup, or has the same phone, I am sincerely and desperately asking your aid to upload a restore version of a freshly formatted rom. I am stumped as to what else I can do.
Click to expand...
Click to collapse
Maybe try flash with ODIN stock FW and etc...
Related
Hi Guys, and thank you in advance for reading this post, I have looked in several places and cannot find a solution. When I boot into recovery, there is no option to backup and restore, I am rooted on Stock Android 4.2.2. Baseband: VRUAMDK. I tried switching out SD cards from my extFAT 64GB card to a FAT32 GB card, no go, I am also running into the same exact issue on my galaxy note 8.0. If anyone could help me out I would highly appreciate it! Thank you in advance! I really want to try a different ROM but want to perform a nandroid backup just in case. Thanks!
DroidForPresident said:
Hi Guys, and thank you in advance for reading this post, I have looked in several places and cannot find a solution. When I boot into recovery, there is no option to backup and restore, I am rooted on Stock Android 4.2.2. Baseband: VRUAMDK. I tried switching out SD cards from my extFAT 64GB card to a FAT32 GB card, no go, I am also running into the same exact issue on my galaxy note 8.0. If anyone could help me out I would highly appreciate it! Thank you in advance! I really want to try a different ROM but want to perform a nandroid backup just in case. Thanks!
Click to expand...
Click to collapse
Which custom recovery are you running?
Sent from my SCH-I545 using Tapatalk
I downloaded ROM manager because I was under the assumption that I was running CWM. I'm still a newbie so please excuse my ignorance. I did root using Odin.
DroidForPresident said:
Hi Guys, and thank you in advance for reading this post, I have looked in several places and cannot find a solution. When I boot into recovery, there is no option to backup and restore, I am rooted on Stock Android 4.2.2. Baseband: VRUAMDK. I tried switching out SD cards from my extFAT 64GB card to a FAT32 GB card, no go, I am also running into the same exact issue on my galaxy note 8.0. If anyone could help me out I would highly appreciate it! Thank you in advance! I really want to try a different ROM but want to perform a nandroid backup just in case. Thanks!
Click to expand...
Click to collapse
Did you install a custom recovery? Stock recovery doesn't allow you to make nandroid backups or flash roms via recovery. If rooted you could try latest installing recovery via Rom manager. Or flash a custom recovery via odin.
sulla65 said:
Did you install a custom recovery? Stock recovery doesn't allow you to make nandroid backups or flash roms via recovery. If rooted you could try latest installing recovery via Rom manager. Or flash a custom recovery via odin.
Click to expand...
Click to collapse
Thanks for the response, I tried installing CWM via rom manager but it doesn't seem to be working at all, tried several times and nothing, how can I install via Odin? I cannot find instructions on doing this for the Verizon Galaxy S4 (SCH-I545) I still have not accepted the OTA update from Verizon so I am still fully rooted and running stock android version 4.2.2
TWRP seems to be the go to recovery for the S4 on Verizon
I think I finally have it, and contrary of what I read it seems to be working on my 64GB exFAT SD card. I will let you know shortly if it backed everything up
The problem was CWM wouldn't install so I went here teamw.in/project/twrp2/181 and just downloaded GooManager and read their instructions: Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
I then booted into recovery and BAM! there was the backup option, I have 10GB to backup so I needed it to backup on my SD card, thought it would be a problem since I read that it wasn't possible to perform a nandroid backup on a 64GB SD formatted as exFAT but it seems to be working, will update once complete, it might take a while to backup all that data
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive:
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!