Hello my fella Developers.
lets do this again. i have the threat all typed up with details and closed it by an accident.
anyways
I have htc one max 8060-t6dug Chinese variant without OS. HTC-1
I had issues with this one, it came with bloatware and lots of it. some of it is pornographic. (got kids who play with my phone)
i decided to root, got the TWRP Recovery. flashed with latest SuperSU. got titanium pro (paid) to get rid of unwanted bloatware. i guess i missed out on something. as soon as i connect with wifi. it starts to download apps. and formatting doesnt help. so i thought maybe repeat the process. BUT in recovery i accidentally wiped system.
i have been through xda developers forums completely found some roms but dead links.
went though several other sites without any luck.
went though Chinese forums (Baidu i think) found some firmwares but TWRP gives me error trying to flash it.
i have tried to flash these with adb command, but mostly get remote not allowed error or space not allocated error.
came back to xda forums and found this
http://forum.xda-developers.com/htc...m-ruu-htc-one-max-809d-t6dwg-sense-5-t3006498
i know this is for t6dwg variant.
t6dwg and t6dug are both Chinese variants and dual sim. i have tried all roms listed on this thread. TWRP Flashed it fine but now when it boots up and gets to lock screen, when i unlock it it show HTC white screen and restarts after a min or so.
I went to the store and purchased another htc one max, same variant. HTC-2
i thought maybe make a nandroid back up and flash it to HTC-1
i repeated the steps and got HTC-2 rooted, latest TWRP, and made the back up. but i am unable to flash it into HTC-1
HTC-1 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111
issues, NO OS!
http://picpaste.com/pics/htc1-l8ImCwQL.1462326306.jpg
HTC-2 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111, boots perfect,
issues, bloatware
http://picpaste.com/pics/htc2-BrCDb5Tw.1462326402.jpg
lets not forget its been about a month since i am trying to figure this out without disturbing developers and wasting their time. this is my last resort
any help would be greatly appreciated.
Thanks in Advance
Anyone out there to my rescue?
@waqas9240 So you made the backup with TWRP? Why not backup to an sdcard one the working one. Place the sdcard in the non-working one and do a restore.
waqas9240 said:
Anyone out there to my rescue?
Click to expand...
Click to collapse
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
waqas9240 said:
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
Click to expand...
Click to collapse
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Flyhalf205 said:
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Click to expand...
Click to collapse
thats what i thought at first. i confirmed the path on both phones. i even got to push the back up in the non working htc to restore from the root as it was located in the working htc max. still does the samething. the second folder after TWRP is serial number folder. i even renamed the serial number to the non working htc ( i dont know if that would have made a difference or not) but still running the same issue. i dont have both phones on me right now. they are at home. let me finish work and will try it again as you explained.
meanwhile if you can figure out something else that would be great bro!
Thanks
Related
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
Hi all,
A week ago I followed this thread to unlock and root my phone. All went well and I flashed Venom 4.3.0 but now cannot receive calls (I was told I need the international firmware?). Beforehand, my phone had an OTA update to Lollipop, and I was stupid and did not make a backup before flashing. I've looked and found some different options, one of which is a stock recovery here.
The biggest problem I'm having now is that I cannot get it to connect to the PC where I can copy over files. It says that the device has stopped responding or has been disconnected. I can delete and view everything, however. In searching around, it looks like some have had this issue with some corrupt files, but I cannot even copy a .jpg or empty .txt file. I have tried uninstalling HTC Sync and HTC Sync Manager, leaving them installed, uninstalling and leaving drivers, using just the drivers here, multiple cables, ports, and even different computers. Windows tries to install Android 1.0 when I connect while in the bootloader or TWRP, and it doesn't show up in explorer (I can see it in device manager as an android device).
Any help would be greatly appreciated!
rhughes93 said:
Hi all,
A week ago I followed this thread to unlock and root my phone. All went well and I flashed Venom 4.3.0 but now cannot receive calls (I was told I need the international firmware?).
Click to expand...
Click to collapse
I don't think firmware has much to do with it. Folks have had issues with some "international ROMs" (including ViperOne) on AT&T's network; and flashing various firmwares doesn't seem to help.
Best explanation I've seen, is that it has to do with changes AT&T is making to their network in preparation for rollout of Voice over LTE (VoLTE, or "HD Voice" and AT&T calls it).
I think Team Venom was looking into the problem. But I don't know if anything ever came of that. I'd say your best bet is to try another ROM, or the stock AT&T ROM (as you've already suggested).
rhughes93 said:
The biggest problem I'm having now is that I cannot get it to connect to the PC where I can copy over files. It says that the device has stopped responding or has been disconnected. I can delete and view everything, however. In searching around, it looks like some have had this issue with some corrupt files, but I cannot even copy a .jpg or empty .txt file. I have tried uninstalling HTC Sync and HTC Sync Manager, leaving them installed, uninstalling and leaving drivers, using just the drivers here, multiple cables, ports, and even different computers.
Click to expand...
Click to collapse
Try uninstalling all HTC software (Sync and HTC drivers). Then go to Device Manager, find the device, and select the option to manually install the drivers, and pick the generic Android MTP Device drivers. See if that gets adb/fastboot working.
Another option, is use a removable SD card and card reader, put the desired ROM on the card using your PC. Then insert card into the phone and flash the ROM in TWRP.
redpoint73 said:
I don't think firmware has much to do with it. Folks have had issues with some "international ROMs" (including ViperOne) on AT&T's network; and flashing various firmwares doesn't seem to help.
Best explanation I've seen, is that it has to do with changes AT&T is making to their network in preparation for rollout of Voice over LTE (VoLTE, or "HD Voice" and AT&T calls it).
I think Team Venom was looking into the problem. But I don't know if anything ever came of that. I'd say your best bet is to try another ROM, or the stock AT&T ROM (as you've already suggested).
Try uninstalling all HTC software (Sync and HTC drivers). Then go to Device Manager, find the device, and select the option to manually install the drivers, and pick the generic Android MTP Device drivers. See if that gets adb/fastboot working.
Another option, is use a removable SD card and card reader, put the desired ROM on the card using your PC. Then insert card into the phone and flash the ROM in TWRP.
Click to expand...
Click to collapse
Thanks for your help. I wasn't able to flash from the SD card for some reason - kept getting a failure. I tried manually installing drivers, but it was no different. I did figure out that even though the PC didn't recognize the phone in fastboot, adb/fastboot still worked and I was able to push files that way. Unfortunately, I tried flashing SkyDragon and still don't receive calls (though it thinks I'm on Tmobile - maybe I missed a step in my haste), and haven't been able to get that stock ROM I linked before to flash. Though, somewhere along the way it wiped Venom so that it didn't re-apply any of my previous settings and now I can directly copy files using the PC instead of pushing. Not sure exactly how that makes sense, but it'll make things easier I think.
I definitely think I'm getting closer, or at least have some options now that I can copy files either directly or pushing. I just have to find a ROM that works and that I can actually flash.
rhughes93 said:
I wasn't able to flash from the SD card for some reason - kept getting a failure.
Click to expand...
Click to collapse
What version of TWRP? Most common reason for ROMs failing to flash is outdated TWRP version.
rhughes93 said:
Unfortunately, I tried flashing SkyDragon and still don't receive calls (though it thinks I'm on Tmobile - maybe I missed a step in my haste).
Click to expand...
Click to collapse
You probably picked T-Mob in the AROMA installer when you flashed the ROM. You can flash again, and pick either AT&T, or the "other GSM" or whatever its called works fine for me on AT&T.
rhughes93 said:
and haven't been able to get that stock ROM I linked before to flash.
Click to expand...
Click to collapse
What you linked was a stock nandroid backup, not a flashable ROM. There is a distinct and important difference.
With a nandroid, it has to be placed in the exact right location, then you pick RESTORE in TWRP instead of INSTALL. If the nandroid folder isn't copied to the exact right location, TWRP won't see it when you select RESTORE (you can't browse for the file like you can a ROM).
The easiest way to determine the "exact location" for the nandroid is to make a backup in TWRP (if you haven't already) examine the folder structure in the folder named "TWRP" and copy the downloaded files (from the thread you linked) to the corresponding location.
But basically, all the nandroid files need to be unzipped than copied to: TWRP/BACKUPS/serial number
Where "serial number" is the actual serial number for your device. The TWRP folder can be on your internal storage, or on the removable SD, depenging on what location you choose in TWRP settings (internal storage is default).
I was using TWRP 2.8.6.0, but the issue was really what you described about it being a recovery and not a flashable ROM. I had figured that out, but missed the exact location because I had not created a backup, and therefore the folder with the serial number was not there. So, I was able to sort that out and restore and all is well again. Thanks for that!
As far as SkyDragon goes, I definitely picked AT&T in AROMA, but there are a few places in the software that still reference T-Mobile, such as in the software version under "about". Perhaps that's just the way it is. I'm still annoyed that I can't get it to work, as I'd rather use a custom ROM, but I can tinker around more now that I have made a proper recovery and can always roll back. Maybe now that I have a proper recovery, I can branch out more. I'll also try re-flashing SkyDragon and choose the "other GSM" to see if it works.
Hi. Recently I stuffed my ZTE Blade A452 with MIUI ROM found on here: hxxp://forum.android.com.pl/topic/319435-a452miui-v8-miui-global-8020. I also installed TWRP . I've been using it for a while and unfortunately it didn't meet my expectations. It is barely usable, phone crashes a few times a day, apps aren't kept in background.
I decided to come back to my stock ROM. I don't have, however, any back up of it. There are some sdcard packages on ZTE's support page, however when I tried to install it with TWRP, it displays that packages (all of them) are for device id P635F33, while my device is P635E40. And I found nothing for my dev id.
Is there a way to force installing one of those packages in my phone? Editing version.txt inside update.zip did nothing.
Maybe one of you guys have a matching package?
Also my sister's got the same model, Blade A452, bought at the same service provider. Maybe there is a way to extract a ROM from her phone and put it into mine? (Her device must be left quite untouched).
damiandbcz said:
Hi. Recently I stuffed my ZTE Blade A452 with MIUI ROM found on here: hxxp://forum.android.com.pl/topic/319435-a452miui-v8-miui-global-8020. I also installed TWRP . I've been using it for a while and unfortunately it didn't meet my expectations. It is barely usable, phone crashes a few times a day, apps aren't kept in background.
I decided to come back to my stock ROM. I don't have, however, any back up of it. There are some sdcard packages on ZTE's support page, however when I tried to install it with TWRP, it displays that packages (all of them) are for device id P635F33, while my device is P635E40. And I found nothing for my dev id.
Is there a way to force installing one of those packages in my phone? Editing version.txt inside update.zip did nothing.
Maybe one of you guys have a matching package?
Also my sister's got the same model, Blade A452, bought at the same service provider. Maybe there is a way to extract a ROM from her phone and put it into mine? (Her device must be left quite untouched).
Click to expand...
Click to collapse
You Have a Same Phone Available .That is Great. You can give her Sleep Drug Sneak Into Her Room.Get the Phone From Under The pillow.And Now You can Unlock The bootloader flash TWRP Make a Backup and Then Flash Stock Recovery.Then Put The Phone Back Under The Pillow.The Process Will only Take about 30Mins.
5Min to unlock Bootloader
2.5Min to flash TWRP.
2.5Min to install stock Recovery
And 20 min to move the back Up
Or
You can Slice her Throat and Get the phone.Seriously Save 30Min of time.
Or
You can Backup Using a Desktop Application and Restore on your Phone.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
You can Unlock The bootloader flash TWRP Make a Backup and Then Flash Stock Recovery
Or
You can Backup Using a Desktop Application and Restore on your Phone.
Click to expand...
Click to collapse
Yeah, TWRP on her phone isn't an option, as the whole system is quite buggy and she's gonna probably use the restore option. I'm gonna try with some desktop apps and give an answer in 1-2 hours. Thank you.
Sorry it took so long to answer.
I couldn't make a nandroid backup any desktop app (MTK Droid Tools can't create scatter file, couldn't find any other app).
As I said, TWRP was not an option. But I managed to do the nandroid backup from phone-level anyways.
First I rooted the source device with KingRoot, installed on it BusyBox and made a custom TWRP-style backup on SDcard with Online Nandroid Backup *ROOT. Default settings are fine, even though it couldn't recognize my phone model.
Then I moved SD into target device and performed a backup with TWRP (just to create my device directory). Then I moved the source-phone backup into the new-created directory and performed Restore.
And Voila! On my phone there was a 1:1 copy of the system. It wiped out TWRP so I could perform a system Restore and get a factory-new soft.
Thank You. I didn't even realize it was possible to restore A-Backup on B-Device. Even though my sister's phone was a P635F33 (I didn't know it earlier) and mine was P635E40, it worked well.
damiandbcz said:
Sorry it took so long to answer.
I couldn't make a nandroid backup any desktop app (MTK Droid Tools can't create scatter file, couldn't find any other app).
As I said, TWRP was not an option. But I managed to do the nandroid backup from phone-level anyways.
First I rooted the source device with KingRoot, installed on it BusyBox and made a custom TWRP-style backup on SDcard with Online Nandroid Backup *ROOT. Default settings are fine, even though it couldn't recognize my phone model.
Then I moved SD into target device and performed a backup with TWRP (just to create my device directory). Then I moved the source-phone backup into the new-created directory and performed Restore.
And Voila! On my phone there was a 1:1 copy of the system. It wiped out TWRP so I could perform a system Restore and get a factory-new soft.
Thank You. I didn't even realize it was possible to restore A-Backup on B-Device. Even though my sister's phone was a P635F33 (I didn't know it earlier) and mine was P635E40, it worked well.
Click to expand...
Click to collapse
It Did Work Right.I am Happy To Be of Your Assistance.
Sent from my Nexus 6P using Tapatalk
Since there isn't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Oreo took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
https://drive.google.com/open?id=1lBsTd04Un6xJQkA0E6LpWxeDX7bhwsai
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD/EXTRACT zip file from above Google Drive's link to your PC
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage SD card)
browse to that folder and open that SD card's TWRP backup folder, using your PC
go to last folder where you should see some files, delete them then
Copy EXTRACTED files from (Google Drives) into TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card.
Where xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP
RESTORE everything showing there (all those three partitions)
REBOOT to system
IF you can't see those copied files on your tablet then you have missed something. Restart back into TWRP
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Hi, I have a T380, I thought about installing this, but before I do, will this work on the t380? Because you have T380T, and I have T380. And if I want, can I put some of the stock apps back on?
Indeed it works on a T380
CaptainChris2018 said:
Hi, I have a T380, I thought about installing this, but before I do, will this work on the t380? Because you have T380T, and I have T380. And if I want, can I put some of the stock apps back on?
Click to expand...
Click to collapse
I just installed it on my T380.. Be sure to follow the directions entirely. And remember to reboot TWRP after putting the sdcard with the backup files back in or else it may not read it (mine would not).
zanophol said:
I just installed it on my T380.. Be sure to follow the directions entirely. And remember to reboot TWRP after putting the sdcard with the backup files back in or else it may not read it (mine would not).
Click to expand...
Click to collapse
followed the directions but device wont read the backup file. would you mind posting all the steps you took to do the backup.
I had the same issue, so when the proper backup files are in place on the ext sdcard and reinserted into the device, but the device won't read it -- for me, I had to reboot the device into recovery and THEN it would read it.
Hi,a friend is running android 9 stock on the T-380.Does not have alot of apps installed,but hardly and internal memory left.I was thinking of rooting it,and uninstalling some system apps. Can you possibly tell me which system apps are safe to uninstall on this tablet?
bobbylo said:
Hi,a friend is running android 9 stock on the T-380.Does not have alot of apps installed,but hardly and internal memory left.I was thinking of rooting it,and uninstalling some system apps. Can you possibly tell me which system apps are safe to uninstall on this tablet?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...-safe-to-remove-ktu84p-m910vvru1anj5-t2976286
always change apk extension with .APKbak
so if you got into mess you can rename the APKbak into .APK
if i got android 9 can i do this it?
Is file support with t385??
I want to personally thank you for this TWRP image! I completely hosed my sm-T380 that I just got as a backup tablet while trying to root it.
This did the trick Thank you again!!!
I did this using internal memory and all ok. thanks.
I need to say THANK YOU BRO!!!! You just saved my ass!!
But can't tell how much a custom ROM is needed for this device.
Only things to do, is to remove all the bloat left whit the link you provide above and that's it.
Once again, 3 thumbs up! (don't ask me where I found the third one lolll)
it's a great work .I want download it, but I can't download google file directly(site blockked), I have to through VPN.So the speed is not quick enough for me,I can't complete the downloading within an hour when google vary the token.The download work can't continue and must restart from the beginning.
If you have time,would you please split it into several parts,each size blow 300M?Thanks a lot,this file I think useful and can give me big help and save me time.
Hi,
I need to restore some twrp images. I have these on my PC but I forget where they should go. I've tried putting there on the SD card in TWRP\Backup but restore doesn't see them so I moved them to the top of the SD card but it still doesn't see them. Where should they go?
FYII recently had my vf-895 play up. I'd previously installed twrp and magisk and it was working if rather slow. Then it started to take 20min to send or receive txts and swapping sim to another phone stopped that (so fault was with phone). I thought I'd try LineageOS since getdriodtips site says there is a 14.1 version for the smart prime 6. Didn't work for me although I'm not sure I did it right. I just pointed twrp at the zip. But also zip has 839 in the name not 895 and more googling suggests the getdriodtips for for the smart ultra 7 (or 6 I forget, not not the prime anyway). The other getdroidtips suggestion of MIUI 8 also didn't work for me but maybe I'm not doing it right.
Will twrp just install a zipped custom rom or does it have to be a special zip? Or how to I do this (other than using adb which often take a while to get working I find).
Thanks
UPDATE, after posting this I had a though, do a backup and see where it goes. Now I'm really confused as the files I have are TWRP 3.0.0-0_VF-895N.img and the like so all *.img where as the backup is a folder with *.win and *.win.md5.
I've come to the conclusion that TWRP 3.0.0-0_VF-895N.img is just the recovery img to load TWRP instead of stock recovery. Hence I don't have a backup like I thought. If anyone has a TWRP backup for a smart prime 6 (UK) I would appreciate a copy.
I've tried stock rom downloads but they all use sugar and I can't get sugar to recognise the phone and/or install the usb drivers. When I put TWRP in adb sideload then the phone with adb appears in control panel so the cable works.
I've tried other ROM and some even flash but after the phone just boot loops.