First, I am not an expert. I cannot code, I do not produce ROMS in a kitchen. I can use google and I am determined and have learned bits. I offer what worked for me in the hope of helping others.
So, here’s the thing. Like others I went for the release version of KitKat for n8000 and by missing out the modem bit flashed it via Odin. Now the proper KitKat for n8010 comes out but it won’t update via odin, KIES is not happy either. I blame no one but me for this.
I figure it is the sboot that is the problem so I look for a way to flash without it. When I say “I figure” I mean I have put two and two together from many hours of google reading. I may be wrong but in the end I managed it.
Long story a little shorter I find Heimdall and I extracted the components from the n8010 kitkat update (I used winrar on the BTU version) and flashed them leaving out the sboot.img and tz.img bits as either would lead to failed flash. I now have a working n8010 with KitKat which under device, under settings, gives the n8010 build number and is recognised as an n8010 by kies.
It still says n8000 under download mode (due to locked sboot) but if I may get future updates via kies, as it recognises it as an n8010 and says it is up to date for now, then that works well enough for me.
Detailed instructions:
1. Download and unzip your update file of choice and extract the tar.md5 file to separate files. I used winrar but suspect 7-zip would work equally.
2. Download Heimdall (just Google it!).
3. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe.
4. Run zadig.exe from the Drivers folder of the Heimdall Suite.
5. If you get an error as follows:
The program can't start because MSVCP100.dll is missing from your computer.
This means that you haven't installed the Microsoft Visual C++ 2010 runtimes. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Use the x86 even if you are running 64 bit Windows.
6. Put you tab into Download mode (while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC.
7. Once you’ve started Zadig.exe and connected to PC choose Options » List All Devices from the menu.
8. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies).
9. Click Replace Driver (having selected "Install Driver" from the drop down list built into the button).
10. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on.
11. You will need to re-install the Samsung drivers later if you want to run kies.
12. Run Heimdall-Frontend.exe.
13. Hit the utilities tab then detect button.
14. If it doesn’t say detected in the output box it will not work. Try to repeat the above steps. Use a different usb port or a different pc.
15. Now you need to create a pit file. Hit save as and give it a name. Then hit download and it will create a pit file for you.
16. Go to Flash tab and hit browse and find the pit file you created earlier.
17. Then hit the add button. You will notice a drop down menu has appeared next to partition name. Then if you look below under Partition ID in brackets it says what sort of file it needs. So for example MD5HDR in the drop down requires md5.img. Use browse to find the relevant file from the files you extracted in step 1 and select then hit add again. Then repeat this until you have selected all the extracted files EXCEPT sboot.img and tz.img.
18. Hit start.
19. Bask in your new updated n8010 without needing kies or odin.
If you want to repeat this on another tab you can create a heimdall install package using the partitions and pit file you’ve created using the create package tab.
Now comes the question...
I've found places that offer an app for testing whether the sboot is locked (not sure how useful that is?) but several also offer a method for replacing a locked sboot. Such as this batch file:
@ECHO Restore OLD BOOTLOADER N7100!
@pause
@ECHO --- STARTING ----
@ECHO --- WAITING FOR DEVICE
@files1\adb wait-for-device
@ECHO --- Restore BOOTLOADER ---
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
@pause
There are others for different Samsung devices but all have the same block/mmcblk0p1 as the block to replace the sboot. And I also found a common block for the tz.img; mmcblk0p2. My question is whether this would work for the n8010, could we edit this batch slightly, grab the relevant files from a n8010 kitkat update and then have a n8010 sboot again?
Just hoping someone is either expert enough to know or brave enough to try?
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
That may also work.
What do you think of my suggested method to replace the sboot?
jika23 said:
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
Click to expand...
Click to collapse
azureus139 said:
That may also work.
What do you think of my suggested method to replace the sboot?
Click to expand...
Click to collapse
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
I am downloading the gtn7100 kitkat and will extract to check whether they are the same size. That should get us one step closer. I am still not brave enough to use adb to replace the sboot until someone more expert can comment on whether it is likley to be same address on the n8010.
YOSEFE said:
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
Click to expand...
Click to collapse
In a tar file isn't something like the updater script like in a flashable zip. Cause if there is we should know with that where the sboot is flashed.
that batch file won't do it
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
azureus139 said:
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
Click to expand...
Click to collapse
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Sadly that will not help. I have discovered it is because the leaked n8000 kitkat rom has a knox bootloader which cannot, as far as I can discover, be replaced. Thank you for the suggestion.
ivica81 said:
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Click to expand...
Click to collapse
secure boot key is what your looking for
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Well I was already out of warranty so that isn't an issue and I have it working with the proper kitkat for my device so tbh I don't know what difference it really makes. It shows n8000 in download mode and I will have to do something tricky via heimdall for any future updates, is that the only difference? Does it mean no access to custom roms as so far I've been happy to use stock and remove all bloat so that won't be too bad for me personally although it would be a real pain for some.
erica_renee said:
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Click to expand...
Click to collapse
As i said i never flashed that on my device. I am thinking all the issues/ benefits quarks of having the n 8000 boot loader on a non n 8000 device.. There may be NO Disadvantage unless Samsung Chooses to change how they sign there roms and so on.I just think Samsung Should Give us a way to avoid this .
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
I did no wipes and just flashed over the top. All apps and data as before but no phone icon.
JamesEsh said:
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
Click to expand...
Click to collapse
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
raducux said:
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
Click to expand...
Click to collapse
Nothing from me. Everything I found says no way to unlock or replace the kitkat sboot. The n7100 apparently has a way but none for the 8xxx that I have found. Don't know what a jtag is?
fail to finish
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
If you can't get heimdall to detect your tablet then it isn't going to flash to it either so a pit file wouldn't help you. It looks like a driver problem. I'd try uninstalling any samsung drivers and / or kies then reinstalling the heimdall ones.
keevo2481 said:
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This driver is too tired
Thought that could be the issue as it changes every time I reinstall the usb driver. Currently too tired. Going to do a fresh windows or Linux install on my spare computer so it's fresh to go and hopefully doesn't have driver issues. Will confirm how it goes either way. Computer needed an upgrade from 7->8.1 anyway.
wifi problem
hy guys i just did that the guide said everything is working very well i m on 4.4.2 stock samsung. But the WIFI is not working. :crying: can you help me how to fix?
Related
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk
I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
What I've done so far is to run a strings check on the preloader and uboot binaries - fastboot seems watered down somehow as it lacked references to "oem unlock" and so on, but none of that Amazon Fire-style failsafe seems present from what I can tell.
Preloader: http://pastebin.com/H9QbzqC0
lk: http://pastebin.com/kSxRKYna
Boot files from the latest firmware revision are attached here, so if anyone is interested, please please please let me know so we can fix bricked units and finally port TWRP to this underrated kids' tablet.
blakegriplingph said:
I dunno, but I thought maybe I could make a separate thread about a possible way to poke into the LeapFrog Epic's preloader so it could accept unsigned images. LeapFrog won't spill the beans for us, as their staff (falsely) claims to know next to nothing about it, so unless we somehow managed to social-engineer them into giving us a signed ROM or an unlocked bootloader, our only chance is to patch it so it would ignore the lack of digital signatures.
Click to expand...
Click to collapse
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?
Gibz97 said:
Bumping the thread.
Would also like to know is this is possible
If I may ask, how did you extract the strings from preloader and lk? Did you use a hexeditor or there is another app?
Click to expand...
Click to collapse
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.
blakegriplingph said:
I used this utility to do a strings dump off an Epic ROM:
http://split-code.com/strings2.html
It did turn up some interesting stuff but I was wondering if a binwalk or perhaps an IDA disassembly analysis would do wonders so we can finally poke into this tablet.
Click to expand...
Click to collapse
Thanks for the tool but I cannot seem find a way to use it.
@gursewak.10 or @smartmanvartan please chime in to help us because they were able to hack the preloader of k4 note and lk of RCA Viking Pro respectively
I also know a friend who is willing to donate a spare Epic, if that helps.
As for using Strings2, the following batch script should work:
Code:
@echo off
strings2 %1 > test.txt
pause
Just drag a binary to be analysed into the batch file, and a resulting text file with strings and stuff should be generated.
Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor
gursewak.10 said:
Hello friend
You need to tweak lk to unlock bootloader . i am giving you my phone's both files(.you can easily compare them.
on unlocked bootloader u can flash unsigned images via write memory option of SP flash tool .
Try HxD hex editor
Click to expand...
Click to collapse
Hmm, I can flash the preloader to my leapfrog via SPFT, but not anything else. Write memory works, and I can flash stuff one at a time to it, but I couldn't get the tablet to force itself out of flash/download mode and into normal mode. There's no reset button, and not even taking the battery off does the trick.
However, on my working Epic, I can alter the demo system image, flash it back using Write Memory and still end up with a working device, just as long as the preloader isn't messed with in any way. Right now I am at a loss as to how to revive my other Epic, short of taking it apart and shorting KCOLO and GND. It also didn't help that the testpoints aren't labeled at all. :/
Also, I did a quick logcat while running the FOTA utility, and I managed to get a few URLs off the said logs. Problem is that while the ZIPs may be of some use, they're incremental and there doesn't seem to be a full scatter/zip image to restore a faulty unit. There definitely needs to be a way to patch the bootloader so we can do whatever we want to it, but is there any one of you guys who are experts when it comes to MTK modding?
Any more ideas?
Anyone, please?
Bumping in case there's anyone interested in poking into this.
Now this is interesting let us see what we can do.
Warrior1988 said:
Now this is interesting let us see what we can do.
Click to expand...
Click to collapse
You happen to have an Epic with you? Please let me know if you need more than just the firmware images. I've tried contacting LeapFrog regarding this issue to no avail. They did give my friend and I the kernel sources, but it's no use as the bootloader has to be unlocked for custom boot or recovery images to be used.
Is anyone willing to test if SP Flash Tool 5.1532.00 works on the Epic? I managed to flash a complete system image to a bricked Epic but I was unable to revive it as it has been bricked prior due to a botched preloader flash. The ROM's on my main Epic discussion thread, but one should take note to flash just the boot, recovery and system images and see if the device still works.
im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed
SP6RK said:
im also poking around in this since my volume up button doesnt work in bootloader mode
i have a figo gravity x55l
i can also upload the stock rom files that can be checked if needed
Click to expand...
Click to collapse
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.
blakegriplingph said:
Are you able to muck around with LK or sbchk using IDA Pro or some other tool? Makes me wonder if merely deleting /system/bin/sbchk would disable boot-time checks or if there's more to it than just that.
Click to expand...
Click to collapse
well i tried hex editors but lk.bin isnt decoded for my rom so half of my lk file is not showing me anything exept weird characters but i can see some of the other half.
if you delete the file...will it brick?...will it even boot?
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
What device are you referring to? Is this for an MT8127 tablet?
blakegriplingph said:
What device are you referring to? Is this for an MT8127 tablet?
Click to expand...
Click to collapse
i have a figo gravity x55l ? and it is not a tablet
it is a mt6753 great phone btw!
im a starting developer and got this phone so i can learn from my mistakes of course?
but this should work on any device that you can get a hold of its boot.img from its firmware
hey everyone, im new here, just got a Samsung s8+ last week. had it rooted and all working well until today, had problems so i went to reflash twrp and when was unticking auto reboot in odin i accidentally ticked "nand erase"..... and i didnt notice until it was too late.
Now i cant get into recovery mode, i can get to the download mode but it wont flash the twrp at all it keeps failing. all i get is a black screen with samsung logo when i try to start it up. i am downloading factory firmware as i write this and going to see if that'll flash. any help will be appreciated.
thanks in advance, hope this is the right place to post it.
Hey
If you can get to download mode,you just install the original firmware from smartswitch,I think you have that option to recover from that program,and install the original firmware.
Or just do it in Odin and find the firmware on SamM.
Lots of work for you,but thats the only thing I can come up with.
Then you have to root it again and everything with it.
PapaD78 said:
Hey
If you can get to download mode,you just install the original firmware from smartswitch,I think you have that option to recover from that program,and install the original firmware.
Or just do it in Odin and find the firmware on SamM.
Lots of work for you,but thats the only thing I can come up with.
Then you have to root it again and everything with it.
Click to expand...
Click to collapse
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
How is it failing? Are you getting an error? Is Odin detecting your device?
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
No worry
You just have to install Microsoft visual c++ 2008 x86,after you have done that,no more errors in smartswitch.
Try that,and let us know
Long time since I used Odin now,but try the first thing first
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
Morning Mate,
Smart Switch (and KIES on Win 10) requires some old stuff to work. Install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) from https://www.microsoft.com/en-us/download/details.aspx?id=5582 My advice however would be to try and flash your carriers stock firmware with ODIN or if you want an easier way you can use KIES by doing the following -
- Install C++ 2008 SP1 from link above to get it to work on Windows 10
- Install KIES www.samsung.com/au/support/usefulsoftware/KIES/ - I'm in Australia so that's my closest but you can still get it from there no worries.
- Also select install 'unified driver' during install if you have not already installed Samsung USB drivers to your PC
- Fire up KIES and from the top menu select 'Tools' and from the drop down menu select 'Firmware Upgrade and Initialisation'
- Enter in your model number - for me it's SM-G955F (make sure model is all in CAPS or it will not work). Now it will present you with a S/N dialog box. This is the tricky part if your phone is bricked. Chances are you have not written down your serial number. You can get your serial number from the back of your phone towards the bottom in really small print, or you can get it from the box it came in from purchase if you happened to have kept that.
- Enter in the serial number and follow the instructions, it's easy as. This will install your stock firmware and you can start again. Provided there is no damage to the phone this method will always get you out of the proverbial as a last resort and it's faster than downloading firmware from updato.com or other places.
The fastest way is by using the SamFirm tool to download but it takes some knowledge and I have lost the link to where I got it (the link at XDA is dead now and refers you to updato.com). The method with KIES above will always work, is fairly fast and pretty easy for the newbies or experienced alike.
Hope this helps, let me know if you need any more assistance :good:
Thanks heaps mate, im also in australia too. have installed all the software and is updating and installing as i write this, all seems to be going well so far, thank you so much your a life saver i was starting to worry as wtf i could do with this brick haha i will keep you posted and let you know if i have nay problems. Thanks to everyone else for their help and contribution this forum is awesome. What would you recommend in regards to rooting the phone again use the twrp recovery and magisk-v14.0 root?
thanks again
I was just about to write a post about how it wouldnt work.... twice in a row it kept failing when it went to install and initialize... 3rd time lucky it ****ing worked! i have a stock phone now all working sweet. Thanks so much to everyone you guys are literally lifesavers!
LEGENDS! Happiest man alive right now.
Here is the stock firmware including the firehose needed to flash it
B10 Firmware
Here
B12 Firmware
Here
ZPI file for ZTE SalesMultiDL tool
Here
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8917.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
Here is the Stock wallpapers in case anyone wants them
https://www.androidfilehost.com/?fid=1395089523397903558
I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?
pegb856 said:
I just got this device a couple days ago and was hoping I could use PDANet/Foxfi to connect more than one device at a time to wifi hotspot but they've evidently blocked the apps.. Do you have any insight to that?
Click to expand...
Click to collapse
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
Ok thank you for the reply.
deadman96385 said:
I don't own this device sadly just grabbed the firmware for a friend of mine and posted it here in case anyone in the future wants it.
Click to expand...
Click to collapse
If you WANT to own this device it's currently $19 out the door on visible.com. No Trade required.
https://slickdeals.net/f/13221781-visible-r2-is-now-19-without-service-or-trade-in-requred
I'm gonna see if I can flash Chinese firmware to unlock the bands
Bowsa2511 said:
I'm gonna see if I can flash Chinese firmware to unlock the bands
Click to expand...
Click to collapse
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
https://imgur.com/yOe0vIx
Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.
famewolf said:
Your elite google-fu obviously exceeded my own. Please make that sharable if you can....megaupload.nz would hold it and is free.
Click to expand...
Click to collapse
https://mega.nz/#!aRo0CaBA!nm37c3V11tr2260V23wIxb4yZufD5-_f6gID8i3HjSY
Let me know if it's helpful
DISREGARD. Looks like out of date info.
Any of you able to get fastboot working on it? ADB works, but my fastboot doesn't detect the phone.
Nice looking out, just ordered one.
Using one of the hidden activities app from the play store. There is an option to change from LTE to 2G/3G/4G under one of the phone settings. But calling still did not work with either AT&T or T-Mobile.
famewolf said:
Good Luck finding the A0722 firmware (that's the model androidpolice thinks this is a renamed version of).
Click to expand...
Click to collapse
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.
FEGuy said:
Just a heads-up: even if you found the files for the A0722, you'd brick your R2 if you managed to flash them. The chassis and screen seem to be the same, but they're completely different specs-wise. Given that the A0722 has a different SoC and an eMMC chip 2-4x larger, I doubt you'd get real far in the flashing process in the first place.
Click to expand...
Click to collapse
In my case my main goal was to use it and the factory software to learn about mbn files. I've dealt with LG's TOT and KDZ files but not the mbn's. Thanks for giving folks the warning though.
Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.
FEGuy said:
Would it be possible for someone to grab the download URL for whatever OTA update is available for the device? I don't think it's anything major but I'd like to poke around at it; the firmware uploaded here seems to be from launch.
Click to expand...
Click to collapse
I've got a logcat recorder queued up to be installed and will try to grab an url by starting the download. If that fails there are a couple of alternatives....someone who has DONE the upgrade could rip the rom and make it available if @deadman96385 can point to some instructions on how to rip the rom.
Also you can always let your own upgrade occur because he's already provided the original software and QFIL which would let you restore to original factory and get the update again.
As a last resort I can grab the log from my ROUTER that the phone is connected to and try to get the url that way which I've had to do with SOME devices.
I'll probably end up taking the OTA again anyways as I've been messing around with the firmware from the first post. Honestly, I'd really recommend staying away from flashing it without a good reason. Even when the flasher works, either the logging and/or the flasher hangs and it's close to impossible to tell which without unplugging your phone. If a partial flash leaves you in a state where you can't get to ADB to boot to EDL mode, you'll have to boot into diagnostics mode, use a piece of Chinese software to boot from there back to EDL, and within five seconds or so, close that software and start the flashing process from QFIL before the com port stops responding to requests, leaving you to reboot the phone and start again.
I've been trying to get non-LTE networks and calling working, but it's entirely impossible to tell whether my tweaks are having unintended side effects or if the flashing just crapped out partway through, even when I'm just flashing single partitions.
So, I'm fairyl tech-savvy and also pretty new to flashing firmware and all that, so any help is much appreciated!
I've done the following:
-Using Odin v3.14.14 currently
-Connected SM-T377V Samsung Tablet, sees device.
-Tablet is sitting on teal screen sitting on "Downloading..."
-Attempted to download MANY different .md5, none of which provided me the BL + AP + CP +HOME_CSC files that Odin says I need.
My question is, where is a good place I can find this as multiple files that I need, rather than just the same .md5 file that seems to be in all of these?
Sorry for the noob-ness, appreciate the guidance!
TheZeak said:
So, I'm fairyl tech-savvy and also pretty new to flashing firmware and all that, so any help is much appreciated!
I've done the following:
-Using Odin v3.14.14 currently
-Connected SM-T377V Samsung Tablet, sees device.
-Tablet is sitting on teal screen sitting on "Downloading..."
-Attempted to download MANY different .md5, none of which provided me the BL + AP + CP +HOME_CSC files that Odin says I need.
My question is, where is a good place I can find this as multiple files that I need, rather than just the same .md5 file that seems to be in all of these?
Sorry for the noob-ness, appreciate the guidance!
Click to expand...
Click to collapse
I don't have your device but when you download your firmware and unzip it, it will either have 5 files or 1 file. If it has only 1 file you will need to flash it in the AP section of odin.
spawnlives said:
I don't have your device but when you download your firmware and unzip it, it will either have 5 files or 1 file. If it has only 1 file you will need to flash it in the AP section of odin.
Click to expand...
Click to collapse
Thanks for the response!
Ok got it. So when I do that, my tablet has a message that says "MDM Mode. Can't Download." and it fails in Odin.
Thoughts?
TheZeak said:
Thanks for the response!
Ok got it. So when I do that, my tablet has a message that says "MDM Mode. Can't Download." and it fails in Odin.
Thoughts?
Click to expand...
Click to collapse
From the point of MDM i can't help much.
You can take it back to where you got it from and see if they can unlocked it for you. There many guides on how to get round MDM mode from using nand erase in odin to using pit files in odin to installing twrp plus various other methods to get around MDM.
All i can suggest is to do some google research. All i did was type something like - how to flash through MDM mode which will bring up a few methods.
eg:
Solution to "MDM does not allow factoryReset..." on android devices
Okay so here is a little back story. I work in an IT department and my company loves anything VMWare produces so they use Airwatch for work emails on mobile devices. Airwatch has it's on MDM and provides security for the device in case it ever...
forum.xda-developers.com
Please be aware if you do try some of these methods your doing so at your own risk.