Single step for Custom-Recovery and root!
Based off single step root made by @ketut.kumajaya and @Luigi2012SM64DS for P31XX - Thanks for the permissions to use yours as base
This Method should work on Android 4.0.x Android 4.1.x and Android 4.2.2.
Disclaimer:
Code:
[COLOR="Red"][B]I don´t have a P51XX - i couldn´t test - but this worked great on P3110 :)
Using this root increases your flash counter.
Use on your own risk! I am not responsible for bricked devices or dead SD cards!
Thanks [user=487416]@MJRL[/user] for confirm working on P5110XXDMI1[/B][/COLOR]
Please give some feedback if it worked
Single step for Custom-Recovery and root!
Philz Touch Recovery or CWM
SuperSU v1.94 from Chainfire, SuperSU: "su" in "adb shell" without any prompt!
BusyBox v1.21.1-stericson
Remove all existing root and busybox before installing the new one
Fix busybox symlink, prevent it conflict to Android toolbox
sysrw and sysro script for remounting /system read write or read only
Backup /etc/install-recovery.sh script to /etc/install-recovery.sh.backup and /system/recovery-from-boot.p patch to /system/recovery-from-boot.p.backup if exists, so we can restore it if necessary
Flashing using Odin3 v1.87:
Download "GT-P51XX_XXXX-SuperSU-1.94-BusyBox-1.21.1_universal.tar.zip" and extract it once (you need the *.tar.md5 inside)
Flash the *.tar.md5 file as PDA
Make sure "Re-Partition" and "F. Reset Time" UNCHECKED,
"Auto Reboot" checked!
Credits:
ketut.kumajaya,
Phil3759,
Google,
Samsung,
koush,
Chainfire,
codeworkx,
dsixda,
weltwon,
stericson,
TWRP
Luigi2012SM64DS
reserved
> 100 Downloads at the moment (since only 5 days!).
Thanks for Feedback:
@MJRL for confirm working on P5110XXDMI1 (using GT-P5110_CWM-6.0.4.5-SuperSU-1.65-BusyBox-1.21.1_universal)
Can someone else confirm if it is working?
Android-Andi said:
Can someone confirm if it is working?
58 Downloads at the moment... no feedback?
Click to expand...
Click to collapse
Thanks, OK with P5110XXDMI1, latest stock
Thanks for your feedback Wich file/recovery did you choose?
Edit: 101 Downloads ... only 1 feedback :/
Android-Andi said:
Thanks for your feedback Wich file/recovery did you choose?
Edit: 101 Downloads ... only 1 feedback :/
Click to expand...
Click to collapse
This:
GT-P5110_CWM-6.0.4.5-SuperSU-1.65-BusyBox-1.21.1_universal.
And then Triangle Away cause I need to reset counter.
:good:
Updating?
i update the one with PhilZ in the evening after work
Updated Root with PhilZ Touch:
Philz Touch Recovery 6.00.8
i have a p5113 its the same as wifi but with ir capabilities will this work and which one should i try?
you can use P5110 files.... with CWM and PhilZ Touch tested a lot of times for P31XX without problems, not tryed with TWRP but i am sure it works (there are a lot of downloads, but jo feedback).
thnx and i know i prob shouldnt be asking this here but can i put on p5100 p5110 roms because of availability?
edit: nvm i figured it out i can use a play store app for ir
P5100 = P5100 (will work on P511X too, but Phone Stuff included, maybe mic not working)
P5110 can be used on P5110 and P511X - if you use on P5100 3G and other Phone Stuff missing (maybe mic not working on P5100)
Android-Andi said:
you can use P5110 files.... with CWM and PhilZ Touch tested a lot of times for P31XX without problems, not tryed with TWRP but i am sure it works (there are a lot of downloads, but jo feedback).
Click to expand...
Click to collapse
worked great installed cm 11 and so far so good. my device says not charging even though it charged slow but it did that on stock tw rom too is it because of the charger im using?
@androidandi....GT-P5110 Twrp. Flashed. Confirmed. VERY NICE!!!
Works with new android 4.2.2 ?
LE:
"This Method should work on Android 4.0.x Android 4.1.x and Android 4.2.2."
Nice, tks a lot!
Confirmed: Works with new android 4.2.2
Hi
Updated my 5110 from 4.0.4 to 4.2.2 trough KIES without any wipe. Everything went great and my tablet worked with all apps still installed.
But I was unable to boot into download mode to install the .tar.md5 file. Every time I tried I got a android figure laying on his back. He has a red box with an exclamation point in it
The solution proved to be to adb into download and then connect to Odin.
Then there was no problem to root and install custom recovery with Android-Andi’s file :good:
ODIN FAIL with TWRP file on p5100?
Hello all-
I am pretty sure I have a p5100 (Galaxy Tab 2 10.1 ESPRESSO10, Wifi & LTE data). I was in Download mode and tried flashing the TWRP all in one file. It recognized device without issue but once it started to do it's thing, it failed. I attached a screenshot of ODIN.
Also, on the device download screen, it displayed the message "Unsupport dev_type" ??
Please advise!!
Read my next post!
@DroidJay123
LTE?
IT IS NOT A P5100! You´ll brick your device if you try to flash P51XX files!
Boot your device and take a look what device you own!
P5100 = Galaxy Tab 2 10.1 3G+Wifi
P5110 = Galaxy Tab 2 10.1 Wifi Only
P5113 = Galaxy Tab 2 10.1 Wifi + IR
What device do you own
- SGH-i497 (ATT)
- SGH-T779 (T-Mobile)
???
Android-Andi said:
@DroidJay123
LTE?
IT IS NOT A P5100! You´ll brick your device if you try to flash P51XX files!
Boot your device and take a look what device you own!
P5100 = Galaxy Tab 2 10.1 3G+Wifi
P5110 = Galaxy Tab 2 10.1 Wifi Only
P5113 = Galaxy Tab 2 10.1 Wifi + IR
What device do you own
- SGH-i497 (ATT)
- SGH-T779 (T-Mobile)
???
Click to expand...
Click to collapse
SGH-i497. From AT&T Wifi AND 3G. It also has the "Smart Remote" application and what looks like an IR spot next to SD card slot. So it has the 3G, Wifi and IR?
Related
Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Artyom.Kazak said:
Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Click to expand...
Click to collapse
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Steve_max said:
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Click to expand...
Click to collapse
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Artyom.Kazak said:
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Click to expand...
Click to collapse
No worries, **** happens. Take care of the device (we are vulnerable to a pretty nasty bug, if you use the older or touch CWM). And as usual, #BlameSamsung for the confusing nomenclature...
Hallo Forumianers and XDA-Freaks!
I've got a Samsung Galaxy Note 10.1 (GT-N8010 Wi-Fi only) and I got it two years ago with retail mode software on it. To get this retail s**t off, I flashed it with CWM and installed a custom rom with same functionality as the stock rom. I was happy with it until now. For some reasons I need to get original stock rom on it now (e.g. update capability by Samsung) and here my problem starts:
I downloaded N8010XXUCMA5 - Open Germany - JB 4.1.2 file, extracted the zip and flashed my N8010 with Odin 1.85 and the xxx.tar.md5 file. It worked perfectly until trying to write the boot.img data. At the very last second (actually 1 or 2 seconds before it should have been finished) the procedure failed with a red field in Odin and the word Failed in it.
Then I just tried to restart the device normal and I got the "DEAD-SCREEN" (An issue occurred while updating device... a.s.o.).
Frustrated from hours of work - I tried the same procedure three times with same result - and sleepy I decided to go back to a custom rom for now. So !! I flashed CWM on the N8010 by Odin and made a system restart.... !!!!! I couldn't believe: N8010XXUCMA5 rom started perfectly and works without any problems...
But my main problem stays: I can't use update functionality to update to newest Samsung version...
Does anybody have an idea on how to resolve this problem and just install original stock rom by Samsung? (e.g. resetting binary counter - not yet tried, etc....).
Do I have to do special procedure before installing N8010XXUCMA5 version???
Thank you all in advance for any help and/or ideas!!!
Best regards, Ingmar
AceLine100 said:
Hallo Forumianers and XDA-Freaks!
I've got a Samsung Galaxy Note 10.1 (GT-N8010 Wi-Fi only) and I got it two years ago with retail mode software on it. To get this retail s**t off, I flashed it with CWM and installed a custom rom with same functionality as the stock rom. I was happy with it until now. For some reasons I need to get original stock rom on it now (e.g. update capability by Samsung) and here my problem starts:
I downloaded N8010XXUCMA5 - Open Germany - JB 4.1.2 file, extracted the zip and flashed my N8010 with Odin 1.85 and the xxx.tar.md5 file. It worked perfectly until trying to write the boot.img data. At the very last second (actually 1 or 2 seconds before it should have been finished) the procedure failed with a red field in Odin and the word Failed in it.
Then I just tried to restart the device normal and I got the "DEAD-SCREEN" (An issue occurred while updating device... a.s.o.).
Frustrated from hours of work - I tried the same procedure three times with same result - and sleepy I decided to go back to a custom rom for now. So !! I flashed CWM on the N8010 by Odin and made a system restart.... !!!!! I couldn't believe: N8010XXUCMA5 rom started perfectly and works without any problems...
But my main problem stays: I can't use update functionality to update to newest Samsung version...
Does anybody have an idea on how to resolve this problem and just install original stock rom by Samsung? (e.g. resetting binary counter - not yet tried, etc....).
Do I have to do special procedure before installing N8010XXUCMA5 version???
Thank you all in advance for any help and/or ideas!!!
Best regards, Ingmar
Click to expand...
Click to collapse
Not really know what do you mean about boot.img, but I flashed my note using stock rom dozens of time without any problem, just Odin and the stock 4.1.2 rom.
I was thinking, probably the rom you downloaded was corrupted or something. I would do a factory reset from recovery mode and try flashing other version (older 4.0.2). Then do the upgrade from the settings menu instead. Probably you'll need to upgrade to 4.1.2 first then to 4.4
Resetting binary count works PERFECTLY, using triangle away (props to the dev; chainfire, purchased it immediately). You need to root your device to use it tho. And yest, GT-N80XX is supported (mine is GT N8000, Wifi-GSM).
hope that helps.
cheers
Thank you for your answer.
I tried now four different firmware versions (cma5 to cmk2) also with triangle away before (triangle away -> reset counts and status -> boot to download mode -> flash versions).
Neither of the versions work. The flashing by Odin 1.85 always fails between 20% and 99%.
Why this could hapen??? Does anybody have an idea or suggestion on how to get an official version of JB and recovery on N-8010???
Best regards,
Ingmar
http://samsung-updates.com/device/?id=GT-N8010
They even still keep ICS 4.0.4
Stock recovery :
http://forum.xda-developers.com/showthread.php?t=2102677
cheers
Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.
i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.
after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.
Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:
When in doubt, flash to stock ROM and proceed from there.
you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.
Hi folks.
Tried a bunch of links to FX 2.3.3.0 and all the same. At best is put as a user application, but just trying to make the system get FC. I have a Samsung Galaxy Tab 4 10.1 Wi-Fi , cpu Snapdragon 400, stock 4.4.2. Root and buzybox certainly is. I do not even touch build.prop, did flashable zip for recovery .
Nuclear tandem viperFX & HI-FI. Tested on my Tab, but I am sure that other Samsung Tab 4 8"&10" fit.
HOW TO INSTALL :
Go recovery , necessarily backup .
Flash , wipe cache&dalvik , reboot .
To install the driver ,reboot , and enjoy.
Good luck .
P.S. You may be need Rotation Manager from Play Market
What is viper4android? I never did figure that out.
wire55 said:
What is viper4android? I never did figure that out.
Click to expand...
Click to collapse
Hm , strange . Read here http://forum.xda-developers.com/showthread.php?t=2191223
Thank you for the link.
I have a Galaxy Tab 4 T337A. Will Viper work? Anyone have suggestions on flashing since the bootloader is locked (I have to unbrick and reroot every reboot). Will Mobile ODIN Lite or Flashify Work?
Hi,
The first is to apologize for the language used, and the length of the text. I am from Spain and my level of English is low, so as it was a fairly long post I used Google Translator and I know that makes it very literal translation ...
I write this post to see if anyone can help me or give some idea ... I explain the problem.
I own for some time ago the Tablet, Samsung Galaxy Note 10.1 (2012) . He has always liked to try new ROMs, so far without much trouble, but .... I tempted fate a lot.
At some point, after changing the Recovery and ROM, to test Marshmallow, the WiFi stopped working, which is a problem in a device of this type, you lose a lot of functionality.
I have tried many ROMS, about 10, and none of them work properly. It is true that some seems, makes the attempt, working. But it does not work.
I have also tried different Recoveries (CWRM, TWRP, Stock, HigOnAndroid, ....), and I have not gotten the Tablet WiFi work.
With all these tests, entering DOWNLOAD mode, it indicates that the device model is the Note 10.1 GT-N8000, the model without WiFi. And when you install a ROM, and go to Settings/Info, the system said that the Tablet is the GT-N8000 model.
This has led me to perform multiple tests:
A- Flash several ROMS by Recovey, usually used the TWRP.
B- Change Recovey installed by Odin 3.10
C- The last thing I have tried, is back to the original ROM and Recovery by Odin 3.10
All these attempts, multiple, have thrown me the same result. The WiFi does not work, and continues to indicate that is the model GT-N8000
The questions are:
1 - Is it normal, even the GT-N8013 model DOWNLOAD mode appears as the GT-8000?
2- Is there any way to get back to its original state, GT-N8013, with WiFi?
3- What Recovery would be most appropriate? (I once used the TWRP)
4- What ROM for this Tablet is the most appropriate? (This question is very personal, I've always liked Omega Rom)
What model do you have .
Samsung Galaxy Note (2012) Gt-N8013
peirof said:
Samsung Galaxy Note (2012) Gt-N8013
Click to expand...
Click to collapse
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
gosha98_ said:
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
Click to expand...
Click to collapse
Hi,
Thanks, sorry for delay, I can solve the isue with another Rom