Please help needed!!
I'm stuck here for 3 days
Ok I'm going to tell everything I did,,
My Gionee E7 is indian version.
First I rooted my phone with kingo Root.
Than I flashed CWM chinese version.
I upgraded my system to kitkat and changed the recovery to stock.
I used it for a week than some how my music player and gallery were corrupted.
I don't have any rom so I download one but it was in chinese, flashed it to my gionee. than after rooting,,
I flashed the CWM, same I flashed weeks ago
Here my problem started :crying:
The CWM is not starting. I used recoery tool to boot into recovery after boot up it shows black screen. I used every method holding Vol+ and power button but the same result.
than I tired to get back to my stock recovery but it does the same.
flashed many times both recoveries but didn't worked.
I searched a lot and find a TWRP. I flashed it and wow it worked Finally I can boot into recoery mode.
Now I find the Nandroid backup of indian version. I made it a zip and flashed it through twrp.
My phone is back to indian version but its slow, not too much but its slow; camera, gallery and other apps take some time to open. I can't make or rcv phone calls. Now what i did is download the update form System update.
Now i got kitkat rom.zip but twrp failed to install it.
Some one on the internet was saying that its the problem with my Kernel. I have the latest kernel so CWM won't work cuz it uses old kernel and display drivers.
My
android version is 4.2.2
Kernel version is 3.4.0-svn2155
I also got TWRP for lolipop,
and I patched binary_update in my kitkat rom too but TWRP can't flash it
Thats my whooooolllleeeee story. "
I got stuck with this for almost 3 days now I'm damn tired can't do it anymore plz help :crying::crying::crying:
I figured it out by myself
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
AkashX4686 said:
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
Click to expand...
Click to collapse
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
No its not, it is working on 64bit windows very well.
In TWRP factory reset and format system and data, than install
Chinese 4.2 ROM. After that boot it and try it again.
It should work!
bllkarv said:
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
Click to expand...
Click to collapse
For me...problem!
there´s a cwm recovery that flashes over the kernel...
i flashed it and than i was unable to go to recovery, every time i tried the phone power off
Solution: Flash the stock boot.img
Use the file according to the Android version...
Help
I just rooted my gionee elife e7. Flashed the chinese recovery which seemed to be the only one which would be compatible. But, while changing a few setting using pimp my rom, the software just stopped working. Errors keep showing up on the screen - "system.ui is not working", "android app is not working", I cannot even go the settings because "settings is not working". Third party apps still seem to work, so, whatsap and stuff continue to function. Doing a factory reset or flashing firmware again seem to be the only viable option.
But, when I try to load up the bootloader using the power and volume keys, it gets stuck on the screen showing the gionee logo and it reads 'fastboot mode' in the bottom left hand side corner. So,
a. can you offer any advice which may be useful ?
b. can you share the link from where you got a TWRP recovery which will work on the Elife ?
c. do you have any idea what exactly went wrong here ?
Any help you can provide will be appreciated because, it's my mausi's phone and I will have a very tough time explaining what really went down here.
Regards,
Hi all
Thanks for taking the time to read this.
I have access to a 2nd Jiayu s3 3GB on android 4.4.4
I've never been able to connect my Jiayu s3 3GB using SP Flash Tools (some driver issues?)
My Jiayu s3 was running android 4.4.4 and when ever it felt like it, it would freeze and then reboot.
So, like a bull in a china shop.....i factory reseted (included format storage option) which now doesn't allow the phone to boot..
The phone won't boot - it starts and just sticks on the Jiayu (white logo)
Thankfully...
if i start the phone with volume up i see
Recovery Mode
Fastboot Mode
Normal boot
I've just tried Recovery mode... and i remember i set my Recovery mode to be TWRP (4pda version)
..and thankfully i can now access the recovery module!
I can also access the phone via fast boot.
i can now access the phone via ADB also - via the recovery mode - i can launch the shell and query the phone
what i would like to do :
change all the partition tables to accept android 5.1.x
flash via adb all the sections needed to install 5.1
After you're all done laughing at me .. can i please have some help?
Cheers
AndyC76 said:
Hi all
Thanks for taking the time to read this.
I have access to a 2nd Jiayu s3 3GB on android 4.4.4
I've never been able to connect my Jiayu s3 3GB using SP Flash Tools (some driver issues?)
My Jiayu s3 was running android 4.4.4 and when ever it felt like it, it would freeze and then reboot.
So, like a bull in a china shop.....i factory reseted (included format storage option) which now doesn't allow the phone to boot..
The phone won't boot - it starts and just sticks on the Jiayu (white logo)
Thankfully...
if i start the phone with volume up i see
Recovery Mode
Fastboot Mode
Normal boot
I've just tried Recovery mode... and i remember i set my Recovery mode to be TWRP (4pda version)
..and thankfully i can now access the recovery module!
I can also access the phone via fast boot.
i can now access the phone via ADB also - via the recovery mode - i can launch the shell and query the phone
what i would like to do :
change all the partition tables to accept android 5.1.x
flash via adb all the sections needed to install 5.1
After you're all done laughing at me .. can i please have some help?
Cheers
Click to expand...
Click to collapse
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
adilrenzu said:
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
Click to expand...
Click to collapse
Hi
Some jiayu revisions need both Volume buttons to be pressed when connecting to PC
Install spflashtools
Install drivers
Download sptf Rom
Open flashtools
Press download ( choose upgrade mode if you are on KitKat and want to go to lollipop / future MM )
Turn off phone
Press and keep pressed both volume buttons
Connect cable pc-phone
Cheers
adilrenzu said:
Nothing to laugh here, hapens to all of us. Did you try to falsh a custom 4.4 rom through recovery. You can find them on needrom. Flash that and see what happens.
Regarding flashing 5.1.x you need to atleast once flash 5.1 rom through sp tools, without that its really hard to get 5.1 running on this phone due to changed partition layout from 4.4 to 5.1
Regarding the driver problem, every problem has a solution, try to google how to properly install mtk drivers on your pc, and its fairly very easy to install them. Cheers
Click to expand...
Click to collapse
Thank you so very much!
I've downloaded and installed the :
JIAYU S3 ADVANCED (3GB version)
XPOSED version
JY-S3_Basic_20150813-Xposed.zip
JY-S3_Advanced_PatchXposed_ For_20150813_Basic_Mod_By_Gab.zip
from needrom, so good to have the phone functional again!
Hello, i decided to open new thread because I nowhere find solution. My problem is that after flashing my moto g2 with omni 6.0.1 it get stuck on warning message (about unlocked bootloader). Now I can only get into bootloader menu, connect phone to PC (it's showing dewice as motorola dadb interface),I can only flash twrp using fastboot (fastboot boot twrp.img) and that's it. I can not flash anything permanently to the phone: any custom recovery, any rom,can't fix it with logofix.It just look like phone doesn't accept any flash. I tried also to change boot and other img but with no succes, always after any operation when I reboot phone it's get to warning message.
My phone is motorola 2G xt1068, 8gb, bootloader ver 48.87. Once I tried to flash it with retail rom from sd card via twrp 3.8.0.1 it shows that previous system was omni-titan 6.0.1 and retaildsdsall can not be flash,always shows error 7.
I wonder if I can flash it with upper version of omni: 7.0.1 to fix the problem with booting the phone.
If You could give me any advise how to solve the problem, I would be very appreciate.
Waitng for your reply Guys.
After a lot of tryes I found that anythig I do on the phone after restart it's getting to the same state, even if I manually deleted folder "Firmware", after reboot it's going back. When I prepared Moto for installing new rom using Philz recovery, all the data stay on it's place ( I mean private data like thumbnails in DCIM folder etc), nothing dissapeared. It's look like it have some copy of the system in internal storage and always after rebooting it's recovering it back, even if the system is flashed by new rom.
Have U any idea what's wrong with this phone?
Additinally I found that a lot of internal memory is busy: over 4500MB and free is only 780MB. Even after wiping everything, also formatting system.Should it be like this?
Edit: 2018-02-15
Ok, if noone could help me let's treat it as a blog.
Digging in google I found spanish site with a lot of custom roms for motorola. Now I'm trying one by one till I found the right one.
It's a pitty that Father's of the omni rom leaving me lonely in that situation, I think that they are the best of source of informations about that rom.
2018.02.19
I tried to install OmniRom 6.0.1 Homemade but on the beginning I had the infothat installation failed with error 7. So I found the solution to change the information in meta-info folder.I did it but when instalation started after "symlinkig" it stopped with error: some symlinks failed, error 7. And again I stucked.I feellike I'm very close of the solution but I need help. I'm using twrp 3.2.1.0 running via fastboot (boot twrp.img).
Hello all
I installed the latest T585XXU4CRJ8 Oreo 8.1 update over Nougat 7 on the SM-T585. (BTU / UK)
Everything went well using Odin and the Oreo stock rom from the Updato website.
Cleared the cache and factory reset from recovery mode as normal practice. Booted up ok.
The problem is the device doesn't recognise the network sim card anymore (worked perfectly on Marshmallow & Nougat).
I've tried factory reset a few times, no difference.
Removed and reinserted the sim, even tried another sim.
Having checked 'about tablet > software details' , carrier is unknown and the IMEI has dissapeared !
I've tried to reinstall Nougat 7 and Marshmallow 6 back on the SM-T585 and Odin fails every time.
Tried 2 computers and 3 different usb cables.
Even trying to reinstall Oreo 8.1 again Odin fails!
Theres no frp lock activated, and the oem unlock tab is checked, usb debugging enabled too.
I've read somewhere Samsung have done something to Oreos BootLoader file to stop people downgrading back to earlier software.
I know its early days, but if anyone can offer any solutions, it'd be appreciated.:good:
How to change the BL file version, so i can reinstall earlier stock roms back?
The Oreo update seems more hassle than its worth and I didnt expect the sim card to be unrecognised once updated, let alone being faced with the puzzle of how to downgrade the software.
Thanks for reading. :good:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
tsam19 said:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
Click to expand...
Click to collapse
I had the same problem, went from Lineage 14.1 to Oreo stock rom (the flashable one you can find on this site, i flashed also the Bootloader/modem file in the thread). No imei, no baseband. Returned back to lineage and got back imei and baseband, but after my screen was going to sleep (after the regular 1 min) I had only black screen and vertical red lines. I flashed then Resurrection Remix 6.2, Lineage 15, Lineage 16, always the same problem. Then I used Odin and the original firmware of Nougat from SamMobile, at the first attempt i flashed only the AP file. I turned to have the same problem, but this time the lines were white. I flashed all the 4 files again with Odin, problem solved and back to Lineage 14.1 (the only custom rom were everything works)
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
tsam19 said:
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
Click to expand...
Click to collapse
just flash the nougat firmware from SamMobile. You have to flash all the 4 files in the zip you are going to download. AP, CSC, etc. Once you have your tablet completely stock you can install again TWRP and flash whatever CUSTOM rom you want.
I easily rooted the phone with odin flashing only the TWRP in AP box (twrp taken from this post https://forum.xda-developers.com/showpost.php?p=78145080&postcount=160) avoid the auto-reboot. You have to put the tab in DL mode, connect it to pc, start odin flash the twrp in AP file e unselect Auto-reboot. As soon as the process is done you have to log in recovery mode at the first boot with home + power + vol up and flash dm-verity. I rooted with Magisk without any problem just flashing the v17.3. Now i' m back to nougat (from Oreo) and i can install whatever custom rom i want. But honestly the only one fully working is Lineage 14.1. Resurrection remix 6.2 has problem with camera and gps don't lock. Same for Oreo version. Tried Pie, same problem.
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
tsam19 said:
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
Click to expand...
Click to collapse
Honestly i think this run for Oreo it's not really worth. I said you what I did and now i have no problems. I'm not in hurry to use Oreo (as stock rom). I think Lineage 14.1 is the most stable and fastest rom i tried till now, and most of all everything is working. I think i'll give a try via Odin to the official stock rom when it will be available for download (i live in Germany) but sadly I don't use most of the Samsung bloatware installed by default.
WRP Oreo 8.1 on Galaxy Tab 10.1 (T585)
Then I've tried
twrp_3.2.3-1_sm-t585_29918 which gives only stripes when booting into recovery
Do I have to flash the stock boot/recovery before flashing this one,
or this is broken, as well.
Many thanks for a hint,
Helmut
Hope this helps.
So, as I was trying to search for my Galaxy Tab A6 (SM-T585) for Deodexed Stock ROM, I stumbled upon this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 just follow the instructions to fully flash Oreo. By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all(Thread here, read the comment:https: //forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) . The TWRP, I think we should leave it be, don't flash an update for the TWRP.
Thanks. Hope this helps.
MiaMOTo SU # said:
By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all
Click to expand...
Click to collapse
Neither does a custom recovery, so not sure what your point is?
I mean if your having problems using MAGISK use the beta version
Hi everyone, I'm having issues with my P7500 (p4) tab. I bricked it by trying to flash a PIT file to modify the system partition size, then unbricked it by installing the stock ROM I found online for the P7500. I planned to install Android 7.1.2 eOS again so I flashed TWRP but the BigSys variant for a 1GB system partition size. Now all of this worked, but now when I try to install the custom ROM it gives me error 7, saying it's for p4 while I have a p4wifi. Before I bricked it I installed this ROM fine since it is actually a p4 not a p4wifi, I tried to force it by changing the build.prop in the ROM and renaming all the model identifiers to p4wifi but still no luck. Could this have anything to do with the stock ROM I flashed to unbrick it? If so could someone point me to a stock ROM for the P7500 'p4', or was the the TWRP BigSys variant I installed (which shouldn't have modified the model code or anything)
Help is much appreciated!
Hello, I had a similar problem with my P4 that also gave me error 7 after installing the 311 TWRP big sys version because it then is set to p4wifi instead of p4.
My solution was to use the correct TWRP version for the p4. You can find one here:
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
devdb.xda-developers.com
Transfer it to you Tab 10.1 and boot into the TWRP, recovery then just install the .zip file of TWRP for p4.
After you reboot into that one, you are able to install p4 rom again (e.g.
Ae-OS-P7500-PuckRomRemix2020.zip)
I hope this helps.
TWRP 3.11 bigsys is only for the Wifi Version and not for the 3G.