Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
DJABHipHop said:
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
Click to expand...
Click to collapse
I always disable screen timeout in the settings of TWRP so I haven't run into that issue. Im not sure why you would say its buggy as hell. I dont think a screen timeout bug qualifies it for all that. Just disable screen timeout in twrp settings and move on. Certainly not a reason to downgrade, but to each their own I guess.
some one please port it to t330nu ...
MTP
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Reshan Kariyawasam said:
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Click to expand...
Click to collapse
Let me know if the camera and mic work
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
mrdreamers said:
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
Click to expand...
Click to collapse
Thats really odd!
As of right now I've seccessfuly fixed the microphone but its still really quite witch requird more digging all soulutions are welcome at this time freas build comming today for t530&t530nu user new thread started by to posted all device fixes and rom tweaks to The Samsung Galaxy Tab 4 in general.
https://drive.google.com/drive/folders/1F3qVR2Gy-SCqFwg5El7-aeGn6UhX-_-_?usp=sharing
DJABHipHop said:
Thats really odd!
Click to expand...
Click to collapse
ya i just odin firmware and started over no root no recovery, its a x-mas gift to my sister and law anyway she don't need all that, she's not nerdy like us lol!!!!
How it look?
How's the recovery doing? Is it working fully?
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
PizzaG said:
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Click to expand...
Click to collapse
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
srialmaster said:
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
Click to expand...
Click to collapse
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
nico3dd said:
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
Click to expand...
Click to collapse
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
PizzaG said:
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
Click to expand...
Click to collapse
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
nico3dd said:
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
Click to expand...
Click to collapse
At this point I would probably start over from scratch and flash stock with Odin. How did you try installing updated TWRP?
If you want me to update the tar file with newer TWRP so it can be flashed with Odin, send me the tar file of old twrp and the newer twrp img file and i'll get that done for you.
can you please port the twrp to the t330nu?
zuhero said:
can you please port the twrp to the t330nu?
Click to expand...
Click to collapse
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
PizzaG said:
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
Click to expand...
Click to collapse
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Delete
---------- Post added at 06:12 AM ---------- Previous post was at 06:08 AM ----------
zuhero said:
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Click to expand...
Click to collapse
If you know how to get skype working on the tab 4 for matisse & milet device hit me up on tellgrem @DJABHipHop I can sure use the help with fixing all the little but anoying bugs.
Thenk in advance.
Related
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Fran Montero said:
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Click to expand...
Click to collapse
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Ruben Craveiro said:
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Click to expand...
Click to collapse
Have you installed it already?
Many thanks!
Fran Montero said:
Have you installed it already?
Many thanks!
Click to expand...
Click to collapse
Im using latest twrp with updated preloader and LOS13
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Maybe you have a sd card formatted as internal storage?
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
1. load scatter.txt in earlier post.
2. select preloader, lk and boot imgs, location of these from the stock 20160810 ROM.
3. select recovery, location of TWRP img.
4. unselect everything else.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
If your device already rooted, you can also install flashyfi and flash the .img file.
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
a bit late (did came to it to test your solution earlier) but it worked indeed. perfect, very much appreciated.
Can u upload 20171201 again?! Link is not working... Thx
opss said:
Can u upload 20171201 again?! Link is not working... Thx
Click to expand...
Click to collapse
You'll find a link here: https://forum.xda-developers.com/el...t/rom-stock-rom-android-6-0-12-01-17-t3542463
Thx dude
jotei66 said:
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
Click to expand...
Click to collapse
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
Click to expand...
Click to collapse
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
Click to expand...
Click to collapse
Have you tried pressing power and then keep finger pressed on vol up to go straight to TWRP recovery and then flashing a new ROM in TWRP ?
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
thecrazyfarang said:
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
Click to expand...
Click to collapse
No worries, just glad you got it sorted out.
Btw (although I know you dont really wanna risk trying it) my son uses my P9000 and has TWRP installed with no issues at all and root with Magisk.
But great yous sorted out
Root twrp Step by step for newbeee-
Ok,so I've installed TWRP 3.0.2-8 and when I start the phone it goes into the recovery... what to do next? Can I find a tutorial somewhere how to do this? And wich image can I use or is the best for the moment?
thx for helping...
Man every phone I get, I brick!! Im stuck in a BLU boot loop. Can't find any files out there for this model. Well did see one here
http://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio%20XL%202/
They want $$ for the download :crying:
Anyone a member there that could get me this file?
Thanks for the help
Try this
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
what version is this?
dougunder said:
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
Click to expand...
Click to collapse
is this firmware v08? it rendered my phone inoperable. no cell, no camera and several other issues. the phone came installed with v09
Anyone ever find V09??
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
crmcc said:
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
Click to expand...
Click to collapse
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
mrmazak said:
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
Click to expand...
Click to collapse
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
killer13666 said:
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
Click to expand...
Click to collapse
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
mrmazak said:
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
Click to expand...
Click to collapse
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
killer13666 said:
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
Click to expand...
Click to collapse
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
mrmazak said:
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
Click to expand...
Click to collapse
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
Click to expand...
Click to collapse
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
Click to expand...
Click to collapse
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
mrmazak said:
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
Click to expand...
Click to collapse
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
killer13666 said:
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
Click to expand...
Click to collapse
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
mrmazak said:
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
Click to expand...
Click to collapse
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
killer13666 said:
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
Click to expand...
Click to collapse
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
mrmazak said:
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
Click to expand...
Click to collapse
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
killer13666 said:
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
Click to expand...
Click to collapse
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
mrmazak said:
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
Click to expand...
Click to collapse
So in other words, it won't let you flash anything that'll modify the data partition as well?
killer13666 said:
So in other words, it won't let you flash anything that'll modify the data partition as well?
Click to expand...
Click to collapse
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
mrmazak said:
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
Click to expand...
Click to collapse
Please do let me know how that goes.
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
Moved here
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
steps
Installation Instructions.
There is never only one way to do anything. The following steps have worked for me.
Before you start, make sure you have rooted the A20
https://forum.xda-developers.com/android/development/root-samsung-galaxy-a20-rooting-guide-t3954872
This part may not be necessary if you're recovering from a crash.
To install TWRP
1. Download the U2 custom recovery from here
https://androidfilehost.com/?fid=1899786940962574261
2. On the PC rename the unpatched recovery as recovery.img
3. Use 7zip to make it into recovery.tar
(right click and choose add to archive)
4. Use 7zip to add your patched boot.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
5. Download vbmeta.tar from here (https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237) and extract vbmeta.img
6. Use 7zip to add vbmeta.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
7. Install recovery.tar to ap slot using Odin.
If you are getting messages about being unable to flash the recovery try this.
https://forum.xda-developers.com/showpost.php?p=80216465&postcount=276
8. Boot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe) - this will remove the encryption of the data partition.
10. Flash this zip View attachment Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
11. Reboot into Recovery. It may reboot into download mode. If it goes to TWRP skip step 12. If you already have a backup, you can go to step 16.
12. On the pc install recovery.tar to ap slot using Odin.
13. Reboot phone and re-enter all data.
14. Reboot into Recovery.
15. Backup only 3 parts: boot, data & system (not system image)
16. You can now restore boot, data & system from TWRP after any crash, but you may need to forget your wifi and go back in to it.
You can now move on to installing a new GSI ROM .
It you get stuck you can come back to Samsung by using your backup.
GSI ROMs are here.
https://forum.xda-developers.com/android/development/gsi-galaxy-a20-t3964546
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
How did you get a copy of the stock recovery?
@physwizz Stock recovery is in the AP image in the ROM.
jajk said:
@physwizz Stock recovery is in the AP image in the ROM.
Click to expand...
Click to collapse
I'll get grab it now.
jajk said:
Android Image Kitchen can unpack TWRP for Samsung S9 (Exynos version) which is fairly similar to our device.
I switched over the kernel and charger files, changed the recovery fstab to match our device plus a few other device specific files and repacked it and tarred it. Odin happily flashed it but the phone would not reboot out of download mode and had some negative message about a Custom Recovery.......reflashed the stock recovery and now back to square one.
I have used this technique before with success but there is a lot more protection on these newer phones that I am not familiar with getting around.
Anyway, it is still a potential way of gaining a TWRP for our device short of compiling one from scratch - just needs a few eyes and brains to have a poke around
Click to expand...
Click to collapse
After hitting dead ends with Mac and Windows, I succeeded in installing Android Kitchen on Ubuntu and unpack the s9 image.
Next step is to try to modify it to fit the A20
Hmmm...
Look at S10 Exynos TWRP versions also.
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Thanks
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
Now I just need to work out how to repack it.
@jajk
AIK now wants an update-script and I can't repack the recovery.img without one.
Edit: went back to the Mac and worked it out.
Didn't install [email protected]
-deleted-
@TBM 13 Can you help build?
physwizz said:
@TBM 13 Can you help build?
Click to expand...
Click to collapse
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.
TBM 13 said:
I don't actually have the device yet. I will probably buy it in like two weeks (but i won't make nothing to it once i get bored, my parents will kill me if i brick it lol).
I can build TWRP, but i only have LOS 14.1 source (i'm not sure if that version of the source can work for a device with Android Pie).
I'm also a little bit noob on this.
Click to expand...
Click to collapse
???
Does this device have a Telegram group?
TBM 13 said:
Does this device have a Telegram group?
Click to expand...
Click to collapse
No, not at this stage.
jajk said:
Look at S10 Exynos TWRP versions also.
Click to expand...
Click to collapse
The A30 have 2 versions of twrp.
https://forum.xda-developers.com/galaxy-a30/development/team-win-recovery-project-3-3-1-0-t3940850
@physwizz A30 TWRP appears never to have worked.
Kiss of death to have an off forum Telegram group - should be banned
Helpful Info
Download Odin Flash Tool For Android Phone, Then Extract It
Now Download >> TWRP Recovery
Then Go To Settings >> About Phone >> Tap On Build Number 5 To 7 Times You Will See Developer Option
Now Tap On Developer Option >> Then Enable USB Debugging And Also Enable OEM Unlocking
Now Boot Your Smartphone In >> TWRP Recovery Mode
To Boot Phone In Recovery Mode You Have To Turn Of Your Smartphone Then Press Volume Up + Power Botton Together To Turn On >> Recovery Mode
Then Select >> Reboot To Bootloader, After Some Time You Will See Downloading Mode
Now Cannect Your Smartphone To Computer Using USB Cable, Then Open >> Odin Flash Tool In Your PC
Now ID:COM Tab On Your Odin Will Turn Blue Which Means Your Phone Is Successfully Recognized By Odin Flash Tool, If It Doesn’t Reconnect Your Device And Check Again
Now Tap On >> AP Button On Odin Flash Tool And Select >> TWRP Recovery For Smartphone You Downloaded Earlier
Now Tap On >> Start Button
After Some Time You Will See “Pass” Button On Screen, It Means TWRP Recovery Successfully Installed On Smartphone
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.