Related
Hi, guys!
Here's updated version of TWRP
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup of internal storage.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd part application: will boot in TWRP. In case of local update, OTA-update, "force update" (3buttons method) or factory reset from menu: will boot into EMUI recovery.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSu from build.
Included support of crypted data.
Screen lock replaced with screen off at power button.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Known bugs:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data. Otherwise you will get error, saying that TWRP can't mount "storage". So don't bother if you'll see this error.
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_MT2-3.0.0-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Download: TWRP_MT2-3.0.0-0.img
For TWRP: TWRP_MT2-3.0.0-0.zip
Older version: TWRP_MT2-2.8.1.0.img
Kostyan_nsk said:
Hi, guys!
I've built TWRP for MT2-C00 by request, so I would like to share it with you.
It works also on L05 because it's on the same SoC.
Download: TWRP_MT2-2.8.1.0.img
Requirements:
Unlocked bootloader
Android 4.4.2
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_MT2-2.8.1.0.img
fastboot reboot
Known issues: I don't know because I'don't have a device and didn't test it by myself.
Click to expand...
Click to collapse
Thank you very much !
I have flashed this onto my MT2-L05 using flashify from the Playstore ( because i'm lazy, lol ) and can confirm that it appears to work perfectly on 4.4.2 b606 EMUI 3.0 rom.
I had no problem booting into TWRP or making a backup. I will attempt to restore my data later to make sure it's working 100% as it should. Excellent work and thanks again !
How did you root your phone ?? I have same model on EMUI 3.0
That is good that the two devices are on the same SoC however I have a relatively important question to ask. Do both the L05 and C00 models contain the same partition layouts? For example, lets say, hypothetically speaking, that the boot partition for device one was mmcblk0p20, then would device two be equal to that and following through with the other partitions as well? Most newer model phones these days will use the "by name" scheme which is in lamen terms just a mere variable that directs to the actual value stored to that variable in which always points to the correct location as it should. So my next question would be, does the device tree include these "by names" variables?
Merely asking this so as to clear the air with less in experience users as to prevent any future complications as well as a better understanding.
Modding.MyMind said:
So my next question would be, does the device tree include these "by names" variables?
Merely asking this so as to clear the air with less in experience users as to prevent any future complications as well as a better understanding.
Click to expand...
Click to collapse
Yes, partitions are mounted via "by-name".
Kostyan_nsk said:
Yes, partitions are mounted via "by-name".
Click to expand...
Click to collapse
Outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this TWRP build for both devices but presumably only for the C00 model given that it was initially built based on it's structure. Appreciate your timely response
Modding.MyMind said:
Outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this TWRP build for both devices but presumably only for the C00 model given that it was initially built based on it's structure. Appreciate your timely response
Click to expand...
Click to collapse
I can confirm that the this recovery works perfectly on MT2-L05.
I have used it to back up and restore system, boot and data partitions and it's worked flawlessly every time.
modding.mymind said:
outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this twrp build for both devices but presumably only for the c00 model given that it was initially built based on it's structure. Appreciate your timely response
Click to expand...
Click to collapse
The only place where size of partitions is defined is BoardConfig.mk, owners of L05 can compare them with their own.
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1610612736
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12790530048
Click to expand...
Click to collapse
But I didn't notice that these variables somehow related to TWRP. For example, there is not defined size of 'cust' partition, but TWRP makes backup of it or some other partition placed in twrp.fstab successfully.
TWRP has its own methods of determinig size of partitions, so do you have any proves that it could be unsafe to use for L05 if partition's sizes are not identical?
I'm just curios what your suggestions are based on?
4L0M said:
I can confirm that the this recovery works perfectly on MT2-L05.
I have used it to back up and restore system, boot and data partitions and it's worked flawlessly every time.
Click to expand...
Click to collapse
I'm sure it does and I appreciate the reply back. Glad to here it actually. I merely asked because in any given device tree used to build from source, twrp in this case, you must determine the used partitions and their sizes and allocate that information towards the boardconfig.mk file. I own a K2_CL as well and there are also three other models to that variant. All of which are on the same SoC, but not only are their partition layouts different but so are their partition sizes. Having said that, it could cause problems should the improper TWRP be used in this case. For example, if you were to use TWRP to say, wipe your data partition and reformat it, but the sizes for the data partition were different from each other then you would literally be resizing your partition where it be smaller or larger than before. Even more so, say it were to enlarge it, then by doing so, it could presumably crash the phone since any given device is given but only so much space unless it were to be intentionally manipulated which is far outside of this discussion.
Modding.MyMind said:
I'm sure it does and I appreciate the reply back. Glad to here it actually. I merely asked because in any given device tree used to build from source, twrp in this case, you must determine the used partitions and their sizes and allocate that information towards the boardconfig.mk file. I own a K2_CL as well and there are also three other models to that variant. All of which are on the same SoC, but not only are their partition layouts different but so are their partition sizes. Having said that, it could cause problems should the improper TWRP be used in this case. For example, if you were to use TWRP to say, wipe your data partition and reformat it, but the sizes for the data partition were different from each other then you would literally be resizing your partition where it be smaller or larger than before. Even more so, say it were to enlarge it, then by doing so, it could presumably crash the phone since any given device is given but only so much space unless it were to be intentionally manipulated which is far outside of this discussion.
Click to expand...
Click to collapse
Take a look at TWPartition::Wipe_EXT4() function
Kostyan_nsk said:
Take a look at TWPartition::Wipe_EXT4() function
Click to expand...
Click to collapse
Just got off of work. Decided to take a look at partitions.cpp and I am seeingng what you are pointing out. Will take a closer look at.
Meanwhile, decided to to look elsewhere and realized in some ways I should correct myself. Ultimately depends if the devices kernel supports "by-names" or not, which the K2 variants unfortunately do not. Though can easily be added.
In addition, the sizes in BoardConfig.mk are used by the compiler to ensure that the boot.img, recovery.img, etc that it produces are not too large for the partition on your device.
Been a fun learning and refreshing discussion . Enjoyed it lol.
didn't work on my phone
well, i tried this recovery on my device. Its MTL2-L05 and it didn't work. Tried to reboot into recovery but the phone just restarted after an attempt to boot into recovery.
mawais15 said:
well, i tried this recovery on my device. Its MTL2-L05 and it didn't work. Tried to reboot into recovery but the phone just restarted after an attempt to boot into recovery.
Click to expand...
Click to collapse
The reason being, you haven't unlocked your bootloader I reckon. The recovery works perfectly on MT2-L05, on firmware b606 4.4.2
4L0M said:
The reason being, you haven't unlocked your bootloader I reckon. The recovery works perfectly on MT2-L05, on firmware b608 4.4.2
Click to expand...
Click to collapse
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
mawais15 said:
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
Click to expand...
Click to collapse
What is the exact wording on your phone in Settings-About Phone-Build Number?
mawais15 said:
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
Click to expand...
Click to collapse
Read requirments carefully in the first post.
Won't work on 4.2.2
4L0M said:
What is the exact wording on your phone in Settings-About Phone-Build Number?
Click to expand...
Click to collapse
Screenshot attached plz
Kostyan_nsk said:
Read requirments carefully in the first post.
Won't work on 4.2.2
Click to expand...
Click to collapse
is there any way i can upgrade it to 4.2.2 or any other method to root my version??
mawais15 said:
is there any way i can upgrade it to 4.2.2 or any other method to root my version??
Click to expand...
Click to collapse
You mean downgrade TWRP? As to allow it to work while on 4.2.2? Assuming the partition layout isn't different from the android OS's on your device then you can literally just unpack your stock recovery image "take note of the configurations used to rebuild it" then unpack this TWRP build and swap out the kernel binary from the TWRP build with the one from your stock recovery image. Then using the build configurations you should have taken note of, simply rebuild the custom recovery image and flash it to your recovery partition. This will resolve your issues as an unethical but temporary solution.
Modding.MyMind said:
You mean downgrade TWRP? As to allow it to work while on 4.2.2? Assuming the partition layout isn't different from the android OS's on your device then you can literally just unpack your stock recovery image "take note of the configurations used to rebuild it" then unpack this TWRP build and swap out the kernel binary from the TWRP build with the one from your stock recovery image. Then using the build configurations you should have taken note of, simply rebuild the custom recovery image and flash it to your recovery partition. This will resolve your issues as an unethical but temporary solution.
Click to expand...
Click to collapse
I wish i were that good at development stuff to understand your post but sure thanks for trying to help
The problem is i don't know where to get my stock recovery image first. which is the first step in your suggestions..
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
So I was attempting to get 5.0 dev preview with root.
I flashed 4.5.3, rooted, had TWRP and SuperUser installed.
Stripped 5.0.2 dev preview of the images/ folder, and modified the updater-script to not look for those.
Flashed 5.0.2, rebooted into recovery. I installed root when TWRP asked.
I then used uboot-4.5.3 and replaced the images/ folder with the one from the 5.0.2 dev preview that I stripped out earlier.
I flashed the firmware from the dev preview and rebooted my device.
Now I only have a solid black screen that I can never get anything to happen. No Amazon logo, no recovery when holding Vol+ and Power, nothing. I issue fastboot and adb to wait for device connection and neither ever respond.
I fear that the new boot.img sees I have a non-standard recovery and just halts. I am not sure though as I have no output.
Does anyone have any suggestions? I was going to pop this thing open and connect my Arduino the UART port, to see if any log output would be helpful. Otherwise I"ll see if Amazon will honor a warranty for it.
emailer33 said:
...
I then used uboot-4.5.3 and replaced the images/ folder with the one from the 5.0.2 dev preview that I stripped out earlier.
I flashed the firmware from the dev preview and rebooted my device.
Now I only have a solid black screen that I can never get anything to happen. No Amazon logo, no recovery when holding Vol+ and Power, nothing. I issue fastboot and adb to wait for device connection and neither ever respond.
I fear that the new boot.img sees I have a non-standard recovery and just halts. I am not sure though as I have no output.
Does anyone have any suggestions? I was going to pop this thing open and connect my Arduino the UART port, to see if any log output would be helpful. Otherwise I"ll see if Amazon will honor a warranty for it.
Click to expand...
Click to collapse
So, looks you've retraced the bricking steps from here (with a small variation on the theme):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
If you don't see even white Amazon logo, my guess is that your flash for the new 5.0.2 TEE1/UBOOT did not go so well. The sequence for the boot is TEE1 -> UBOOT (white Amazon logo) -> boot.img (yellow Fire logo), alternatively, UBOOT -> recovery. There is also TEE2, but I am not sure how to boot that one. Note that 5.0.2 UBOOT will not boot TWRP recovery, at most one could do here is flash 5.0.2 Amazon recovery in the same go as TEE1/UBOOT. Then you could do factory reset, if this flash goes well.
I've tried to get MTK tools going, but no dice :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
Tell Amazon that an update made your Fire dark, and don't tell them that you actively participated in the process
At this point I think that Amazon should have provided more recovery options for people here to use, instead they now spend money on shipping bricked Fires back and forth. Sloppy programming, methinks ...
Sounds like I should've definitely flashed the stock recovery after flashing the 5.0.2 UBOOT. I will try my warranty options, thank you!
Edit: Amazon support is probably the most helpful and quickest tech support I have ever used. They're sending me a new one and I send the old one back in the shipping box.
I went through the same screw up. I'm guessing the only way to get TWRP to actually flash a stock recovery would to do an ADB sideload since it protects itself from getting overwritten.
siegesoldier said:
I went through the same screw up. I'm guessing the only way to get TWRP to actually flash a stock recovery would to do an ADB sideload since it protects itself from getting overwritten.
Click to expand...
Click to collapse
I still wonder why your upgrade did not work. On paper it should have been fine, flash 5.0.2, install su/SuperSu, {clear /data}, flash uboot/tee1, and go boot into 5.0.2. Flashing Fire recovery was not necessary, other than to do a factory reset (clear /data). But, one could have cleared /data in TWRP before. Did TWRP screw up /system partition to an unrecoverable state? Or was it SuperSu flash that did not go well? Anyway, I hope people stop trying this, since so far it's been 2 bricks for 2 attempts ...
New Fire just arrived, so I'll probably stick to rooted 4.5.4 for now (5.0.2 was sooo pretty though).
The unit that arrived was version 4.1.1, pretty old, wonder if its easier to root.
emailer33 said:
New Fire just arrived, so I'll probably stick to rooted 4.5.4 for now (5.0.2 was sooo pretty though).
The unit that arrived was version 4.1.1, pretty old, wonder if its easier to root.
Click to expand...
Click to collapse
Wow, 4.1.1 was never offered for download!!! Try to get root, and copy the UBOOT, and TEE1 partition. Just in case.
bibikalka said:
Wow, 4.1.1 was never offered for download!!! Try to get root, and copy the UBOOT, and TEE1 partition. Just in case.
Click to expand...
Click to collapse
Already have root on it, which mmcblk blocks should I copy?
emailer33 said:
Already have root on it, which mmcblk blocks should I copy?
Click to expand...
Click to collapse
The exercise is a bit academic, but what the heck ...
dd if=recovery.img of=/dev/block/mmcblk0p7 (PART 7)
For other partitions, see below.
[PART] 1: 00000100 00000040 'PRO_INFO'
[PART] 2: 00002000 00000800 'PMT'
[PART] 3: 00002800 00002800 'TEE1'
[PART] 4: 00002800 00005000 'TEE2'
[PART] 5: 00000400 00007800 'UBOOT'
[PART] 6: 00004000 00007C00 'boot'
[PART] 7: 00004000 0000BC00 'recovery'
[PART] 8: 00000800 0000FC00 'KB'
[PART] 9: 00000800 00010400 'DKB'
[PART] 10: 00000400 00010C00 'MISC'
[PART] 11: 00008000 00011000 'persisbackup'
[PART] 12: 00258000 00019000 'system'
[PART] 13: 001B8000 00271000 'cache'
[PART] 14: 018F3FDF 00429000 'userdata'
Academic or not, that should be posted to a sticky thread or a wiki. But I've backed up everything except cache and userdata, is there anywhere I can put it up? I will say zipped /system/ is 779MB.
emailer33 said:
Academic or not, that should be posted to a sticky thread or a wiki. But I've backed up everything except cache and userdata, is there anywhere I can put it up? I will say zipped /system/ is 779MB.
Click to expand...
Click to collapse
Well, the only value would be in UBOOT and TEE1. You should try to boot with "Pwr Vol+" button hold, to see if it lets you into recovery (either Amazon's or TWRP). 4.5.1 and 4.5.2 would not do so, which causes bricks ... If it does not let you into recovery via these buttons, no value then ...
Ok So I have a Nextbook NX16A10132S Ares 10A
I have TWRP custom recovery installed on it that I used from the Ares 8A.
I've tried flashing the Ares 8A rom, the Remix OS rom for it but no luck.
https://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
gives an error does not installed..FML.
So then I found a site with a option to restore this backup for TWRP after just putting it in the backup folder for TWRP.
This I was able to do, it installs the system not the boot part of this backup, but it still doesnt boot into the system.
Literally if anyone has a Ares 10A 11A any ****ing that close to this system that they have TWRP/root on and woul back it up so I can restore it..you will literally have my eternal thanks. Or really anyone else that could get a rom that would work for this intel atom based android tablet that has driven me insane.
I am also at a loss with this Nextbook tablet as well. A customer of mine brought me one that has an activation lock on it. She got ripped off and bought it 2nd hand and didn't know about the lock until it was too late and seller disappeared on her. So now i'm trying to help her figure out a way to at least bypass the activation in anyway. I tried using remix OS but that didn't work, so I am trying Pheonix OS.
have same tablet and twrp backup
i have the same tablet just been playing with it i have a twrp backup image if you need it its incomplete as my version of twrp cant backup the data partition let me know how and where to get the image file to you guys
mi useing twrp meant for ares 8 tablet it works almost perfectly i also have a image file made with nandroid overthe air app but the backup files it makes are too llarge not broken up into 1 gig partials like twrp does
can contact me directly at [email protected]
I gave a working system image made from my unencrypted rooted ares 10a If your bricked you cand hold volume down buttom while plug in usb to carde keep holding vol down button and tablet will boot into recovery from ther you can data wipe or factory restore and make a backipimage vamprila has a good root solution that supplies restore and boot images to flash as well
Decrypt ares 10a
Could you explain how I decrypt my ares 10a I can't find any steps on xda
Nextbook 10
killainferno said:
I am also at a loss with this Nextbook tablet as well. A customer of mine brought me one that has an activation lock on it. She got ripped off and bought it 2nd hand and didn't know about the lock until it was too late and seller disappeared on her. So now i'm trying to help her figure out a way to at least bypass the activation in anyway. I tried using remix OS but that didn't work, so I am trying Pheonix OS.
Click to expand...
Click to collapse
I have a similar problem. I bought this one second hand. And what a bargain it's been. I can't get past the activation lock. Please help. It's nice to know I'm not alone in this Savage world lol
trying to root nx16a10132s need twrp stock boot.img
read thru the root ares 8A with android 6.0.1 thread read it all then this rooting stuff starts to make sense does anyone have the stock boot.img and or stock sys.img you can use the twrp from this post 8A's twrp but HAVE TO HAVE a fixed boot.img before you do anything but twrp backup the boot.img and the sys.img and data.img (the data.img is complicated to get right) another member says he'll fix the 8A boot.img he may do the same thing for us if we can get hmi the 10a boot.img maybe but i think its any of ours only hope. cant really root with out it being modified. the boot file should be areound 30Mb so if you have a stook boot contact me and i'll walk you thru temp twrp extracting it nextbook has changed up thier security measures soo DONT change anything until we all get the modifies boot.img if some one is dareing there are posts on how to modify or repack the boot.img i aint that good yet its beyond me still but it can be done by someone who is a little more knowledgeable also post whick build your device is what kernal it uses blah blah all the stuff under settings>about tablet> these numbers are important if you dont use the matching versions you will end up with no wifi no bleutooth and no sound I've seen posts on how to get around the activation code on the thread i mentioned READ the WHOLE threade before you do anything by the time you finish it LOTS more stuff will make sense and you'll say F**K i so luck i aint really screwed my tablet up
Code:
billybleu97 said:
read thru the root ares 8A with android 6.0.1 thread read it all then this rooting stuff starts to make sense does anyone have the stock boot.img and or stock sys.img you can use the twrp from this post 8A's twrp but HAVE TO HAVE a fixed boot.img before you do anything but twrp backup the boot.img and the sys.img and data.img (the data.img is complicated to get right) another member says he'll fix the 8A boot.img he may do the same thing for us if we can get hmi the 10a boot.img maybe but i think its any of ours only hope. cant really root with out it being modified. the boot file should be areound 30Mb so if you have a stook boot contact me and i'll walk you thru temp twrp extracting it nextbook has changed up thier security measures soo DONT change anything until we all get the modifies boot.img if some one is dareing there are posts on how to modify or repack the boot.img i aint that good yet its beyond me still but it can be done by someone who is a little more knowledgeable also post whick build your device is what kernal it uses blah blah all the stuff under settings>about tablet> these numbers are important if you dont use the matching versions you will end up with no wifi no bleutooth and no sound I've seen posts on how to get around the activation code on the thread i mentioned READ the WHOLE threade before you do anything by the time you finish it LOTS more stuff will make sense and you'll say F**K i so luck i aint really screwed my tablet up
Click to expand...
Click to collapse
I am shocked that the custom twrp, that vampirefo made, that I provided in my ares 8a thread for the nextbook ares 8a, would even work for this tablet?
temp booting twrp is used to create a backup of the original boot.img.
I then unpack it and remove the encryption flag and dm-verity flags, then repack it.
In order for the data partition to be unencypted after this, the data partition must be deleted. you will loose all data on the data partition.
when the tablet is booted with the new, modified boot.img, a new, unencrypted, data partition is created. your old data partition is not magically unecrypted, so you need to backup any important files through, for example and mtp connection to a computer. that also means that only certain types of data can be backed up this way from the internal sd card and the external sd card. any apps you have will have to be reinstalled from scratch. any game and app data will probably be lost also unless you can back it up also some way.
deleting your existing data partition so a new, unencypted on can be created, is the only way I know how to do this.
The user who found a solution as to how to disable the activation of the tablet said he would post how he did it in my thread, but never did and I don't know how to do it. I bought mine from the only legitimate source I know that sells it: Walmart. I purchased my tablets from the store I work at. An activation code is printed on the receipt, and is unique to each tablet.
There are some bits and pieces of what he did to defeat activation, in my thread, but they are somewhat vague. Maybe you can PM him to get him to answer.
Most of the users I have helped and modified boot.images for different versions of the 8a, have taken my modified boot.imgs and ran, no longer to be seen.
When I asked them for supersu systemless, patched images, they never even had the courtesy to even respond to me.
I have become disillusioned by ungrateful xda members who feel entitled and don't give to the community in return.
However I am still, irregardless, trying to help if possible.
I tried to learn how how build twrp myself, but it is a very, very steep learning curve to do it. And it can only be done with a linux computer with lots of disk space to download the twrp source files. That is way beyond my abilities, currently. However, I do run Linux Mint Mate, most of the time now, as it boots and runs much faster than my windows 7 drive, despite being on a persistent, casper-rw, usb key, 32gb.
---------- Post added at 02:51 AM ---------- Previous post was at 02:20 AM ----------
A backed up data partition from the original, stock tablet, doesn't work on the rooted ares 8a either, because it is an encrypted backup. A modified boot.img removes the encyption flag and verified boot, but this does not decrypt an existing data backup in twrp. Hence the need to:
Code:
fastboot format userdata
, hit return
Code:
fastboot format cache
, hit return
Can you successfully flash supersu systemless with vampirefos twrp for the 8a on your 10a and gain sucessful root access? And of course the userdata must be deleted with the above commands, in fastboot mode, if supersu can be sucessfully flashed and works. I use jrummy's root test app, from the play store. I also always flash yds busybox in twrp, also, after supersu flash.
UPDATE: I think you need to delete userdata in fastboot, before you flash supersu in twrp, not after. I am tired so my memory is not as good, so I believe that is the safer way to do it, not after flashing supersu.
I have not written this in the 8a thread, but currently I recommend supersu in its default systemless mode: supersu 2.82 SR5, from the supersu beta thread.
I previously recommended the unoffical, systemmode supersu for the 1.0.8, 1.1.1 and 1.2.0 versions of the 8a.
UPDATE: upon looking at the specs of the ares 10a they are the same as the 8a with it having twice the internal storage space as the 8a: 32gbs vs. the 8a's 16gbs. I am not sure how this would affect the 8a twrp build if used on the 10a the android partitions are more than likely a different size.
a good android utility for determining the partition sizes is called diskinfo.
Here are the partitions for the ares 8a:
system
cache
data
metadata
boot
recovery
misc
bootloader
bootloader2
persistent
config
metadata
sd card
external SD
There are others, but those above are the main ones
PLEASE NOTE: THIS MAY NOT WORK FOR YOUR 10A. THIS MAY BRICK YOUR DEVICE. IT IS ALL THEORY BASED ON THE 8A, WHICH HAS ALMOST IDENTICAL HARDWARE EXCEPT FOR ONLY HALF OF THE 10A'S 32GB STORAGE SPACE.
SINCE VAMPIREFO'S TWRP WAS BUILT FOR THE 8A, THERE MAY BE UNEXPECTED CONSEQUENCES!
YOU HAVE BEEN WARNED! DANGER, WILL ROBINSON! (A LOST IN SPACE REFERENCE, FOR THE YOUNG.)
the bootloader must first be unlocked. See my ares 8a thread for very detailed info on how to do the below steps. One updated change from it though: YOU MUST USE THE OFFICIAL SUPERSU.ZIP, WHICH INSTALLS AS SYSTEMLESS. IT WILL ALSO PATCH YOUR BOOT.IMG TO DISABLE ENCRYPTION AND DISABLE DM_VERITY (ANDROID VERIFIED BOOT), SO NO NEED FOR A USER MODIFIED BOOT.IMG.
THE ORIGINAL UNOFFICIAL SYSTEMMODE SUPERSU I HAD PREVIOUSLY PROVIDED DOES NOT PATCH THE BOOT.IMG TO REMOVE ENCRYPTION AND DM_VERITY.
Code:
fastboot format userdata
hit enter, wait to complete.
Code:
fastboot format cache
hit enter, wait to complete.
this will delete all user data so a new, unencrypted data partition can be created.
Of course, any data will be deleted so a backup is needed through, for example, mtp to a computer. user apps will have to be reinstalled. System apps will still be there.
it look like on should then be able to temp boot the 8a twrp recovery in fastboot mode by issuing:
Code:
fastboot boot Ares8A_recovery_twrp.img
then once into twrp hit the install button and select the SR5-SuperSU-v2.82-SR5-20171001224502.zip systemless and flash it. it must already be on the internal sd card, or the external sd card. If all goes well you should see a message in twrp that supersu has successfully patched your boot.img and backed up the original to a new folder created in the root of the device, called .subackup. the files in that are the originals extracted from your stock boot.img.
The next step is to reboot. The first boot will take a very long time. The last time I did it on one of my 8a's, it took ~5 minutes to get past the animated nextbook animation before going to the android security, usb debugging prompt and setup screen.
See my ares 8a root thread, for better details
Question about ares 10a nextbook
i have brand new ares 10a but dont have an activation code anyway around it? Can i install rom are what? thanks god bless
there was someone who uninstalled one of the system apps and it help get rid of activation code need read thru root ares8 thread there was another person that installed a differnt rom and did the same thing but i wouldnt advise that for the ares10a..thers a link on the nextbook site that is supposed to give you the code if you put in a number from the tablets box but i dont know if thats a 100% solution either but its a starting place to look
thanks I'll check into it once i can someone on ebay is sale the code $15 and info he needs is I believe its all done online for free. LOL
I'll need some information from the tablet itself
YOU WILL NEED
1. a mini-usb cable that plugs into the tablet - this is the same type of cable that charges most android phones (not an apple cord) or a playstation 4 charging cable will work too
2. Laptop or desktop computer with internet access - preferably running windows 8 or windows 10 (you can use windows 7, but you may have to download drivers for it to recognize the tablet)
I will need you to copy a file from the tablet to your desktop and open it - the copy and paste it into this message for me along with your serial number
are you able to do this?
If so, then you can go ahead and pay and i will send the rest of the instructions
my experiance dont trust ebay
I've been looking for some solutions for my ares 10a for months now but NEVER have i seen anything like this ebay guy is offerong... sound to good to be true.....read thru the ares 8a threads 2 hrs of reading may save you a brick tablet or just keep you from getting screwed by a stranget from ebay if you dont find anythig then give em a ty if you risk it
tone4life said:
thanks I'll check into it once i can someone on ebay is sale the code $15 and info he needs is I believe its all done online for free. LOL
I'll need some information from the tablet itself
YOU WILL NEED
1. a mini-usb cable that plugs into the tablet - this is the same type of cable that charges most android phones (not an apple cord) or a playstation 4 charging cable will work too
2. Laptop or desktop computer with internet access - preferably running windows 8 or windows 10 (you can use windows 7, but you may have to download drivers for it to recognize the tablet)
I will need you to copy a file from the tablet to your desktop and open it - the copy and paste it into this message for me along with your serial number
are you able to do this?
If so, then you can go ahead and pay and i will send the rest of the instructions
Click to expand...
Click to collapse
I had the same issue with "/data" not being mountable. I used twrp to wipe that partition and make a new one. There's something wierd with it because i wasn't able to root and install twrp in the recovery partition until I did the wipe. It would default back to stock image when it had issues booting
oxendine9381 said:
I had the same issue with "/data" not being mountable. I used twrp to wipe that partition and make a new one. There's something wierd with it because i wasn't able to root and install twrp in the recovery partition until I did the wipe. It would default back to stock image when it had issues booting
Click to expand...
Click to collapse
My guess would be that your original data was not mounted because it is encrypted. With a modified boot.img to remove encryption and dm-verity, the userdata must be wiped to create a new, unencrypted, data partition, on next boot.
I do not own an Ares 10A, as was stated a few posts above, but I was wondering if any of the info I provided concerning the Ares 8A was useful in getting root on your 10A's?
Thanks
eternal2u said:
Ok So I have a Nextbook NX16A10132S Ares 10A
I have TWRP custom recovery installed on it that I used from the Ares 8A.
I've tried flashing the Ares 8A rom, the Remix OS rom for it but no luck.
https://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
gives an error does not installed..FML.
So then I found a site with a option to restore this backup for TWRP after just putting it in the backup folder for TWRP.
This I was able to do, it installs the system not the boot part of this backup, but it still doesnt boot into the system.
Literally if anyone has a Ares 10A 11A any ****ing that close to this system that they have TWRP/root on and woul back it up so I can restore it..you will literally have my eternal thanks. Or really anyone else that could get a rom that would work for this intel atom based android tablet that has driven me insane.
Click to expand...
Click to collapse
GO TO [email protected] FOR FAST HELP
Can rooting help Nextbook NX16A10132S Ares 10A...
Do we have a forum for fixing the bad implementation of Android 6 on the nx16a10132s,—PC Windows 7 sees it as an mp3 player, and its file Modification dates are fake Creation dates of every Move/Copy... 14 GB of these useless Modification dates, of 17 GB usable of 24 GB listed by the filename-abbreviating file manager 'garbage-on-top-of-garbage' of 32 GB advertised... (Rooting doesn't fix this, Or, does it,—Rooting just makes it hang faster—true, or not, true...)
I have a next book 10a and I don't have the activation code. What can I do. PLEASE HELP ME OUT
I was able to get the offending lock-screen app passcode program in the Nextbook NX16A10132S Ares 10A removed. On kernel 3.14.64-x86_64 android 6.0.1 -- This method erased all user data on the device and returned it to factory settings -- only without the lock screen program.
With the device turned off and unplugged, I hold down the power and the volume button that's farther from the power button until the system boots into the fastboot screen. I plug in the USB to the computer and use the Android Developer tool: Fastboot to unlock the boot loader:
fastboot flashing unlock
fastboot format userdata
fastboot format cache
I then tell the device to shutdown.
I Download and Extract the Ares8A_recovery_twrp.img from this thread, and put it into the computer's working directory I'm using fastboot from:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
I unplug the USB and start it back up with the power and volume button again until the fastboot screen appears again. I then plug in the USB and run :
fastboot boot Ares8A_recovery_twrp.img
Once TWRP is running, I click the Mount button on the tablet and check the box to mount System.
Then I use ADB SHELL to rename the bad application:
adb shell mv /system/app/VUDUStartWizard/VUDUStartWizard.apk /system/app/VUDUStartWizard/VUDUStartWizard.apk.bak
Then I shutdown the device, and start it back up normally. Then it works for me with no lock screen.
Ok originally I had come in here because of boot loop caused after removal of specific apps. This has been an issue even before I managed to get it rooted, I still wouldn't mind a streamlined fast alternate rom for my nxa10 but figured out the boot loop issue. Just go back into twrp and factory reset... it wont replace the apps you removed... kind of a weird roundabout way to debloat but hey if it works haha.
Me too!!! I need an Ares 10a ROM
I trashed the system partition on my Ares 10a. I just need A ROM... any working rooted ROM for a 10a. I had a ROM for an 8a that worked just fine... until I killed it.
So please, if anyone knows where to get a working 10a or 8a ROM would you let me know? Thanks.
Hello everyone.
I know many of you have worked on safe-strap TWRP recovery in light of the inability to unlock the bootloader.
I have been testing on my note 8 and as someone else pointed out if you install the Engineering Rom listed below you will have the oem unlock toggle.
This service rom.
COMBINATION_FA71_N950USQU2AQK3_CL12591988_QB15811772_REV00
As far as everyone believes this option is only for FRP reset.
To tell you anyway the FRP reset is simply ZEROing out the persistence partition.
A persistence partition that is ZERO is default OEM Unlock ON. Meaning the toggle is set to not allow oem unlocking.
Using the mentioned rom above it is possible to set oem unlocking allowed.
This does not mean the bootloader is unlocked.
But i do feel that it is very close to unlocked and leads me down a path that i can unlock the bootloader.
I have a Galaxy Tab E that is allowed to be bootloader unlocked.
By doing a dd dump of all partitions then doing hexdump of the dd dumps the hex dumps can be diffed in terminal effectively.
By doing a comparison of the unlocked and locked state partitions I can Identify the changes being made.
I am still in the process of testing and comparing the dumps.
I need a TWRP build for N950USQU2AQK3 or ver 2 bootloader.
I almost think I have the bootloader set to where it will allow TWRP to Run.
This may not be a full unlock yet but having a good TWRP build would be a good test.
I could build TWRP myself but i do not have a build system setup currently..
So one of you that has compiled twrp for safestrap or other testing please share to save me some time.
I dealt with this same scenario on a HTC Desire 526 that was bootloader locked by verizon.
I did develop a unlock method using this same process i am using now.
So no......This is not a JOKE.
I am making progress on unlocking the note 8 USA Variety. :victory:
Help me out and share your TWRP.
HI, I have a SM-N950U and I'm on Verizon,
My Baseband is:
N950USQU1AQI5
What would you like someone to do for you?
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
pbedard said:
Htc is different then samsung....samsung has checks on every partition in the device if it detects something the phone will not boot ha
Click to expand...
Click to collapse
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
JedidroidX said:
Bigcountry has been doing all the necessary research which involves how the partitions interact with each other. He is really close to officially unlocking the boot loader apparently. We all are aware of how strict Samsung is but there seems to be a small window of opportunity that WILL enable a true bootloader unlocking method.
Click to expand...
Click to collapse
ºȯº could it be?
Wow really this would be awesome. Cannot wait. Thanks for the hard work.
I really hope this works
Interesting
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I have a V3. I also am currently learning some arm assembly this semester, so I might be of some (minor) use. Note sure what my schedule will allow, but I will definitley assist how I can.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on bootloader 5. I'll be glad to help ya out with what you need.
BigCountry907 said:
I am still making progress on this. I took a step back to make sure I can unbrick my device when I screw something up.
Currently I am working on the unbrick for the V2 bootloader.
Someone got the firehose for the s-8 and s-8 + versions and some people have had luck unbricking s8 and s8+.
I have to rebuild the s8 unbrick rom for the note 8.
This involves getting the GPT tables off the device then decoding the GPT to write the partition.xml. Since we have ufs memory there are 4 primary partitions which means there are 8 GPT tables.
Once I have this all completed we can flash anything we want with the firehose. Even single partitions.
What I was asking for was TWRP that is Built for the Note 8.
So I can see if I can get it to boot.
This would save me from building TWRP myself and leave me more time to work on other stuff.
My Note 8 is currently on V2 bootloader.
We will need a unbrick rom for each bootloader version.
In order for me to make that I will need the GPT tables from each bootloader version. I can provide the commands to do it. Anyone wanting to help just let me know. I will be starting a new thread of how to do this soon.
Click to expand...
Click to collapse
I'm on v3 bootloader...if you need anything I will try my best to help you out and see if we can get this phone unlocked
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Vell123 said:
I'm interested and will get note 8 for this work. Is there any particular bl you'd prefer like rev1 and or 3 or just rev 2. Also I have a Samsung edl tool to aid the firehose process. Now that I think of it I already have firehose Rev2 from when I bricked out on SD.
---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------
Also what sort of programming knowledge can help you if you don't mind me asking
Click to expand...
Click to collapse
Currently I am working on Rev 2. bootloader.
You guys that have other Revisions Can help us all out by getting GPT backups from your devices. Then I can Compare the GPT for differences.
I currently have the UNBRICK for bootloader version 2.
Anyone with a HARD Bricked device that is on samfail V2 possibly samfail V2..5 or the factory AQK2 or the AQK2 factory repair should test this unbrick. I am sure it will work.
If other versions of the bootloader have the same gpt then we can take the bootloaders out of the stock firmware and swap them with the files in the unbrick and it should work. If the gpt is different then new GPT files will need made for the other bootloaders.
@Vell123;77796726
Which Box do you have?
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode?
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files.
@Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U
Which Box do you have? I have the z3x box however i also have a edl repair cable/tool.
You mention SD / does the sdcard method still work.
Do you put the sdcard into the device to boot download mode? I don't have a SD card version. I was told by Me21( that made Samfail ) it wouldn't work so i didn't mind working on anything. However it might work. When i said SD i was referring to Snapdragon processors.
If that is the case we can run full android off the sd card potentially.
I would love to have a copy of the card if you can dd and image that would be great.
I have been thinking about buying the medusabox pro. It supports firehose and these phone models.
I don't know what box is best but whatever it is i want to buy one.
I'm sure your may already know the boxes use AT+COMMANDS but the most support is the best!
As far as bootloader unlocking I noticed after the GPT on the beginning of dev/block/sda there is a pretty decent chunk of data that is not the GPT or the PIT and may be a place for us to look into. Its basically a hidden spot in the emmc that samsung is not normaly written to.
@kronickhigh
If you can re-base and disassemble the abl.img that could lead us down the right road. You may be able to locate where the security checks are executed. If you can locate those it could be possible to determine the memory addresses where this data is stored.
I'm going to start a new thread on GPT and I will post there the commands to pull the GPT and what were looking at.
I am also going to start a new thread for the unbrick files. @Vell123;77796726
If you can share the sdcard image you have that would be superb.
For now here is the v2 unbrick tor the N950U[/QUOTE]
Rip note 8
What Happened
pbedard said:
Rip note 8
Click to expand...
Click to collapse
What happened to your note 8.
The unbrick files are legitimate Samsung Leaked files.
If you are on bootloader rev 2 you should be able to unbrick it.
You need to load the qualcomm edl drivers.
If you are on a different bootloader version we can try to make a unbrick for you.
Also depending on what you were doing.
You may have got the device stuck in sahara mode or something.
I once thought i bricked mine.
It was deader than dead. Only showed up as unrecognized device.
I left it that way overnight until the battery fully died.
Then when i plugged it in the next day it came back to life.
Unless you physically damaged the note 8 it can be recovered. Sooner or later.
Sooner if you are on rev 2
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
I am on rev 3 i fixed my bricked device myself with a friends help
BigCountry907 said:
So as this thread first asked.
Who has a halFway decent tree for me to build TWRP.
I going to need it pretty soon.
Were about there. I gotta get me a 64gb sd card tonight and finish up a little more work on my gpt decoder.
Looking at the strings in the elf files I can see that the option to boot from sd card is in there.
Other than that I need to create sparse chunk images of partitions like /system and /data and /persist.
All the big boys gotta get sparsed out to chunks small enough for edl flashing.
I have a very special set of bootloaders and I'm thinking this set will be able to be unlocked.
What needs done is building a complete edl flash using these bootloaders and the standard U2 version /system and other images needed to complete the flash. If this all works as I anticipate it will be RIP Locked Bootloader.
Click to expand...
Click to collapse
Fingers crossed and good luck!