Related
ok hello guys i have an international version not the at and t anyways yesterday i used mobile odin pro and flashed to the new ics germany update it was very nice but then i went to a site called rootgalaxynote and installed a cm9 for the Chinese leaked ICS before installing it i backed it with CMW and then i went to recovery mode and installed the CM9 rom but when it was finished it started booting then booted again and again i tried to restore the CMW backup but at the end it said SYSTEM RESTORE FAILED ! tried flashing it withh pc odin but it gets stuck at nand write pleeeeease help pleeeease help i will do anything to fix my phone
Deademon said:
ok hello guys i have an international version not the at and t anyways yesterday i used mobile odin pro and flashed to the new ics germany update it was very nice but then i went to a site called rootgalaxynote and installed a cm9 for the Chinese leaked ICS before installing it i backed it with CMW and then i went to recovery mode and installed the CM9 rom but when it was finished it started booting then booted again and again i tried to restore the CMW backup but at the end it said SYSTEM RESTORE FAILED ! tried flashing it withh pc odin but it gets stuck at nand write pleeeeease help pleeeease help i will do anything to fix my phone
Click to expand...
Click to collapse
Can you access recovery? I am kind of in a similar situation but I have no access to recovery only download mode.
jwais said:
Can you access recovery? I am kind of in a similar situation but I have no access to recovery only download mode.
Click to expand...
Click to collapse
Op flashed Chinese leak...which has kernel known to brick phones
Note_E said:
Op flashed Chinese leak...which has kernel known to brick phones
Click to expand...
Click to collapse
i used to be able to enter recovery mode but now i went to a store to fix it and they tried to return it to the original samsung software in says AN ERROR OCCURRED WHLIE UPGRADING FIRMWARE what should i do ?
Deademon said:
i used to be able to enter recovery mode but now i went to a store to fix it and they tried to return it to the original samsung software in says AN ERROR OCCURRED WHLIE UPGRADING FIRMWARE what should i do ?
Click to expand...
Click to collapse
They borked your phone by doing that. Samsung repair. You can try pit file followed by stock gb buts its hit or miss
heimdel should help you. i dont have much time to explain. check how heimdell works. factory.rs and zimage file is enough to flash from heimdell rest leave them blank. take the good working base. you can also take the new PLY ics base. it should work
I have used Triangle Away on XXBMA2 and the sboot it came with and while the flash counter is successfully reset, my system status flag is not, it keeps saying "custom" whatever I do with Triangle Away. Has anyone successfully stockified their I9305, and if so, which ROM and sboot? Does it even depend on sboot?
You need to do a complete wipe too.
CalInTheZone said:
You need to do a complete wipe too.
Click to expand...
Click to collapse
Yes I have done that. I started on XXBMA2, rooted and stuff, used Triangle Away and before booting I went into download mode and flashed completely stock. After that didn't work I rooted again, used Triangle Away again, and again, before booting I flashed stock. The only thing being reset is the flash counter.
I think you doing something wrong. Take it easy, root first or use pre-rooted rom. Use TA and let it finish job, boot normally. Once you've done it, reboot to DL mode, use Odin to flash Stock ROM. Restart your phone, go to Back up & Reset section in menu, select Factory Reset and voila. Should be clean as New
Sent from my GT-I9305 using xda app-developers app
Here is what I did on my Note 10.1:
Flashed ROM with correct CSC
Autorooted (Chainfire you know)
Ran TA
Before the device could boot entered recovery (on the phone you can pull the battery)
Did a full wipe
And all was virgin.
Just use this and all your problems will be solved...
http://forum.xda-developers.com/showthread.php?t=1942150
Why use this Root Method? Well the main reasons are:
- You have a complete Odin Flashable ROM Package.
- No Insecure Kernels are used or required.
- You can flash these packages on Non-Rooted devices
- The Binary Flash Counter will NOT increase when flashing these ROM Packages.
- The Red Exclamation Mark will NOT appear at boot up.
- And finally, you only have to flash one file in Odin and you have a complete firmware including Root Permissions.
Raistlin1158 said:
Just use this and all your problems will be solved...
http://forum.xda-developers.com/showthread.php?t=1942150
Why use this Root Method? Well the main reasons are:
- You have a complete Odin Flashable ROM Package.
- No Insecure Kernels are used or required.
- You can flash these packages on Non-Rooted devices
- The Binary Flash Counter will NOT increase when flashing these ROM Packages.
- The Red Exclamation Mark will NOT appear at boot up.
- And finally, you only have to flash one file in Odin and you have a complete firmware including Root Permissions.
Click to expand...
Click to collapse
Yeah but he need to send his phone to Service Centre for repair so Pre-Rooted Rom is out of game I guess...
Sent from my GT-I9305 using xda app-developers app
Its shows as original with a zero count so all he has to do is remove any apps that need root and he will be fine.
Raistlin1158 said:
Its shows as original with a zero count so all he has to do is remove any apps that need root and he will be fine.
Click to expand...
Click to collapse
I know all about it and you right but.... His phone is fully working (except Modem) and it's risky sending it rooted even if counter shows 0, imho....
Sent from my GT-I9305 using xda app-developers app
djembey said:
I know all about it and you right but.... His phone is fully working (except Modem) and it's risky sending it rooted even if counter shows 0, imho....
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
As long as I can get the system status to appear original I don't care how I do it hehe.
Rekoil said:
As long as I can get the system status to appear original I don't care how I do it hehe.
Click to expand...
Click to collapse
Did you try my "recipe"? Because I've done that three times with three different devices. All successful.
CalInTheZone said:
Did you try my "recipe"? Because I've done that three times with three different devices. All successful.
Click to expand...
Click to collapse
I will give it a go this evening.
Good luck... If you don't succeed and you are in the area of Höör this weekend then contact me and I'll give it a try
Hi, i got a GT-I9305N too , you get system status flag as custom because your phone is still rooted, any modified changes in /system will make your system status as custom like su or busybox. In order to get system status flag to official, you need to reflash your phone with a stock rom with odin3 (Unroot the phone). Send me a private message and i'll link the right stock rom to you if you want, Comviq/tele2 rom if you bought the phone from them or nordic countries.
Use this to find the correct rom : http://samsung-updates.com/device/?id=GT-I9305#sthash.YrJ0gDPY.dpuf
Good luck :good:
Sv: [Q] Stockifying a GT-I9305(N)
Raistlin1158 said:
Use this:
Galaxy S 3 LTE GT-I9305 TLA I9305XXBMA4 Android 4.1.2 - Released 10.01.2013, Change log 746327
See more at: http://samsung-updates.com/device/?id=GT-I9305#sthash.YrJ0gDPY.dpuf
Good luck :good:
Click to expand...
Click to collapse
With this release he needs luck... wrong baseband.
Swyped on my Galaxy S III LTE
CalInTheZone said:
With this release he needs luck... wrong baseband.
Swyped on my Galaxy S III LTE
Click to expand...
Click to collapse
Baseband wouldn't work anyway, I need Perseus kernel for that to work, which is the whole reason why I am returning to stock (for service). The way I see it: as long as I can get the system status flag to say 'official' it doesn't matter how I do that because after I can flash any other official rom and the flag wont get touched, so I can return to my stock carrier rom anyway (which by the way is Tele2/Comviq as tico96 suggested).
Thanks for all the tips, I will give it another go tonight.
This is what I did just now:
While running XXBMA2 rooted and with Perseus kernel I applied Triangle Away
Rebooted straight into download mode (by holding home, vol down and power, should I be powering off normally first?)
Installed stock XXALIA
Cleared data
And the result?
Custom binary download: no
Current binary: Samsung official
System status: custom
Operating system status shows "modified"
Can someone honestly tell me they have been able to reset the system status flag on this hardware and also let me know exactly which ROM package they did it from and how they rooted etc. I don't care whether it is for I9305, I9305N or I9305T, radio working doesn't matter to me at all (because if radio has to work for it to revert to stock then I am ****ed either way).
I just want to return to system status: official or normal or whatever it is supposed to say.
Your non stock kernel is your problem. Just as soon as you boot with that you are "modified". Everything has to be stock kernel/recovery/CSC just with SU and you have to run TA and do a complete wipe before the system notice it's rooted. Then you are modified again.
CalInTheZone said:
Your non stock kernel is your problem. Just as soon as you boot with that you are "modified". Everything has to be stock kernel/recovery/CSC just with SU and you have to run TA and do a complete wipe before the system notice it's rooted. Then you are modified again.
Click to expand...
Click to collapse
Ok, so before running TA I have to have a stock kernel? But don't I need to reboot into a special mode if I have a secure kernel... meaning I end up booting a secure kernel to do the TA from anyway?
Come to think of it, I don't think I've ever run TA on a system with stock kernel and recovery... I always assumed that I could replace those directly after, perhaps the check is done when I go into download mode? Will try that tonight!
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Why not to flash stock Sammy rom through Odin? This time - not modified?
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Hbohd said:
Why not to flash stock Sammy rom through Odin? This time - not modified?
Click to expand...
Click to collapse
This is what I tried... but it still get stuck at glowing samsung logo...
toeterbaas said:
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the answer.
What do you mean "wipe ****"?
Could you detail the steps?
1. Flash official sammy ROM through odin
2... enter recovery? (please confirm)
3... wipe what?
Thanks!
Have you tried flashing another kernel?Boeffla Etc then use KIES or Odin to flash back to stock
Sent from my GT-I9305 using xda app-developers app
Yes enter recovery after flashing with Odin.
When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305 then wipe cach and wipe the other one. There are 2 wipe options.
Your phone should boot now it takes some time the first time around a minute.
Let me know if it worked
- flash stock Samsung ROM for your country with Odin
- go to recovery wipe the 2 options When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305
-phone should boot takes a minute before he goes trough the flashing Samsung screen.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
All you have to do is follow my steps.
It should work now
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Click to expand...
Click to collapse
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
narcarsiss said:
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
Click to expand...
Click to collapse
Thanks for your answer!
I fear sending S3 to Samsung for repair is the only way, unfortunately... This is what I will do tomorrow (in 10hrs from now) unless a white knight arrives on this thread and gives me the golden solution!
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Well... didn't work either... since I already had knox bootloader...
It shows "unsupported version".
Oh well...
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't flash the old version. Odin will revert it back while installing.
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Click to expand...
Click to collapse
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Looki75 said:
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Click to expand...
Click to collapse
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
shucrut said:
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
Click to expand...
Click to collapse
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Looki75 said:
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Click to expand...
Click to collapse
I'd used this tutotial (just the part of commands, added everything that the original ".md5" has, removing just the "sboot.img", i'm not 100% sure if this is the only file to be off the new package, as i said, didnt work for me ), the only difference is that i'm using cygwin instead of linux itself, it worked like a charm
Basically all u need to do is unpack a original .md5 firmware (use winrar or so) and move the files (except sboot.img) to your home directory of linux or, in my case, cygwin (originally C:\cygwin\home\user-name), start the console and type the command bellow, switching the ".imgs" to match yours, of course:
Code:
cd $HOME
tar -H ustar -c image_1 image_2 > your_odin_package.tar
After this you must have a 1Gb+ .tar file (considering you will make a stock samsung flashable), now you will add md5 checksum to that, just to avoid troubles:
Code:
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
and voilà, you have your flashable odin package. Of course you can try making one with just the system.img, boot.img and modem.img. If the phone boots up, do a factory reset. I have no idea if this will work in any occasion having knox bootloader trying to flash official 4.1.x, but you can also try with a samsung 4.3 rom.
In the last scenario, try to CF auto-root your phone, then flash an official CWM recovery via odin using this method i told u, boot into recovery and flash a custom rom, do a factory reset and wiping cache and dalvik cache. I hope one of the options work for you.
I'd recommend trying to flash a custom recovery and then a custom rom. If phone boots up and is functional, try to flash samsung official 4.3 again (if your desire is having the stock of course), not forgeting to factory reset via cwm first to avoid troubles.
Been in maybe like pratically the same situation
1st flash philz touch recovery ( install latest version)
2nd backup ur efs in external sd and copy it to a pc just in case (important if u mess up imei )
3rd Copy and rom in the external sd
4th Wipe data,cache,dilvik
5th In mount and storage Format everything except external sd ( u can backup ur internal sd card with 3rd step)
6th Flash Rom and reboot
7th If no imei then try a newer modem
http://forum.xda-developers.com/showthread.php?t=2572432
http://forum.xda-developers.com/showthread.php?t=2607279
Notice I only could get to run 4.3 to run after formating everything through philz touch recovery
i have rooted samsung galaxy tab s2 T815y , but now using stock recovery i m getting (dm verity verification failed) and update from external storage is disabled error and my tab is not working working normally on existing rom(officail mm rom)
dude.rlc said:
i have rooted samsung galaxy tab s2 T815y , but now using stock recovery i m getting (dm verity verification failed) and update from external storage is disabled error and my tab is not working working normally on existing rom(officail mm rom)
Click to expand...
Click to collapse
I think you need a custom recovery installed such as TWRP to disable dm-verity, but don't quote me on it.
wirelesskebab said:
I think you need a custom recovery installed such as TWRP to disable dm-verity, but don't quote me on it.
Click to expand...
Click to collapse
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
dude.rlc said:
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
Click to expand...
Click to collapse
I think your problem is that you're not on the stock rom and you're trying to use the stock recovery... dm_verity goes hand in hand with the official rom, you can see this if you go into download mode, you would see binary would say something like "samsung official" system status would say something like "original" or "official". You can find this in smart switch > more > emergency software recovery and initialization > device initialization.
Why is using TWRP not possible? Please elaborate, what rom are you running? I think 3rd party recovery is necessary to bypass this issue in all cases when using unofficial rom.
I would suggest initializing your device via smart switch, make sure to back up everything if you can as it will be lost, however, I think that it should resolve the issue entirely. Initialization if you can't boot into stock rom, you will need to enter download mode and in smart switch type the model number and then the serial number, it should initiate then.
You could try waiting for someone who knows their stuff, but initialization via smart switch (not just the image pulled from sammobile which leaves some files out) is probably the way to go, IMO. I'm just a novice, but I'm the only one that's replied, so hopefully some others can chime in and say if I'm giving you bad advice.
dude.rlc said:
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
Click to expand...
Click to collapse
You will always fail dm-verity in stock recovery on a modified device.
It's pointless trying to OTA on a modified device. It will fail.
To update you need to flash the stock firmware with odin in DOWNLOAD mode not RECOVERY.
wirelesskebab said:
I think your problem is that you're not on the stock rom and you're trying to use the stock recovery... dm_verity goes hand in hand with the official rom, you can see this if you go into download mode, you would see binary would say something like "samsung official" system status would say something like "original" or "official". You can find this in smart switch > more > emergency software recovery and initialization > device initialization.
Why is using TWRP not possible? Please elaborate, what rom are you running? I think 3rd party recovery is necessary to bypass this issue in all cases when using unofficial rom.
I would suggest initializing your device via smart switch, make sure to back up everything if you can as it will be lost, however, I think that it should resolve the issue entirely. Initialization if you can't boot into stock rom, you will need to enter download mode and in smart switch type the model number and then the serial number, it should initiate then.
You could try waiting for someone who knows their stuff, but initialization via smart switch (not just the image pulled from sammobile which leaves some files out) is probably the way to go, IMO. I'm just a novice, but I'm the only one that's replied, so hopefully some others can chime in and say if I'm giving you bad advice.
Click to expand...
Click to collapse
thanks for ur reply but my main problem is my device is no longer sync with pc using usb(because i think its usb dock pcb is damaged) so i cant use odin thts why i m searching for a solution to install official rom without pc.
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
dude.rlc said:
thanks for ur reply but my main problem is my device is no longer sync with pc using usb(because i think its usb dock pcb is damaged) so i cant use odin thts why i m searching for a solution to install official rom without pc.
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
Click to expand...
Click to collapse
Then use flashfire to install the stock rom. It will install everything except the bootloader.
ashyx said:
Then use flashfire to install the stock rom. It will install everything except the bootloader.
Click to expand...
Click to collapse
but my tab is not rooted ,is there any way to root it without pc it is running on marshmallow(t815y)
dude.rlc said:
but my tab is not rooted ,is there any way to root it without pc it is running on marshmallow(t815y)
Click to expand...
Click to collapse
You don't need a PC. Just install supersu with twrp.
ashyx said:
You don't need a PC. Just install supersu with twrp.
Click to expand...
Click to collapse
i dont have twrp installed in my tab.
and i cant connect my tab to pc to install twrp
dude.rlc said:
i dont have twrp installed in my tab.
and i cant connect my tab to pc to install twrp
Click to expand...
Click to collapse
You said you had it installed below?
dude.rlc said:
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
Click to expand...
Click to collapse
ashyx said:
You said you had it installed below?
Click to expand...
Click to collapse
yes but i was trying to install official firmware using stock recovery thats why i have changed it because my tab is not working properky
dude.rlc said:
yes but i was trying to install official firmware using stock recovery thats why i have changed it because my tab is not working properky
Click to expand...
Click to collapse
Then there's nothing you can do. You either need root, twrp or odin.
I have a similar problem, dm+verity verification failed in stock recovery but I have not rooted or installed any other firmware.
So my questions are
1. Has someone else installed it without my knowledge?
2. Has someone installed something through adb sideload without my knowledge?
3. Have i deleted something I shouldnt have?
4. When i go into stock recovery and before i choose what to such as "recovery logs" if i hold down the home/finger print button for about 2 secs the highlighted colour changes from blue to green, is this normal?
Thanks in advance
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
y0ur5h4d0w said:
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
Click to expand...
Click to collapse
Flashed multiple part stock ?
Fully working with stock or still bootlooping?
bmwdroid said:
Flashed multiple part stock ?
Fully working with stock or still bootlooping?
Click to expand...
Click to collapse
i flashed a single file stock rom in "AP" on odin, how can i get multiple files rom? the one i've flashed right now was downloaded from sammobile with the latest updated, android 7.0 included (see a screenshot of the file name attached)
y0ur5h4d0w said:
i flashed a single file stock rom in "AP" on odin, how can i get multiple files rom? the one i've flashed right now was downloaded from sammobile with the latest updated, android 7.0 included (see a screenshot of the file name attached)
Click to expand...
Click to collapse
with the application samfirm ,you check "Binary Nature" and you have multiple files rom .Do'nt forget to specify the Region .
aboulafia1901 said:
with the application samfirm ,you check "Binary Nature" and you have multiple files rom .Do'nt forget to specify the Region .
Click to expand...
Click to collapse
i've flashed the 4 files i downloaded with samfirm, though it still bootloops i guess it's RIP
y0ur5h4d0w said:
i've flashed the 4 files i downloaded with samfirm, though it still bootloops i guess it's RIP
Click to expand...
Click to collapse
Might be worth a try to flash several times one after another.
Sometimes I read it helps.
bmwdroid said:
Might be worth a try to flash several times one after another.
Sometimes I read it helps.
Click to expand...
Click to collapse
flashed back to back 4 times, nothing changed sadly
Try perhaps with Frija in place of samfirm and perhaps with heimdall (under Linux but also windows I think) in place of Odin.
y0ur5h4d0w said:
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
Click to expand...
Click to collapse
did you fix yours?
I have the same model and finally fixed(its been > 3hrs so far) mine by formatting ALL partitions in TWRP, then installing 5.0.2.
Ri9000 said:
did you fix yours?
I have the same model and finally fixed(its been > 3hrs so far) mine by formatting ALL partitions in TWRP, then installing 5.0.2.
Click to expand...
Click to collapse
i still haven't but i might try when i have some free time! thanks for the advice would be awsome to actually fix it honestly
y0ur5h4d0w said:
i still haven't but i might try when i have some free time! thanks for the advice would be awsome to actually fix it honestly
Click to expand...
Click to collapse
mine is still up >30 hrs so looking promising. I've been working on it for 8 months or more. Thinking back, looking at the flash in "edl mode" guide . . .
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
. . maybe this is how I should have done it, but mine was stable in download mode.
In the end this is what I did ymmv.
flash back to 5.0.2stock with heimdall,
flashing twrp3.1.0-1, format internal partitions,
reflash 5.0.2stock, & twrp3.1.0-1.
edit: after 1 day it is rebooting again. groan.