Related
Need some help here. Basically im on the tweaked bootstrap( the one where it says bootstrap recovery and reboot recovery when the apk is clicked on) and im currently running the monster rom. Ive been recently interested in installing safestrap but i have no idea how to switch over. Ive been reading alot of different forums and people have been struggling trying to switch and i heard theres data confliction and it can be difficult. Soo im gonna throw some questions at you guys and it might be alot but its good info that i would like to know so... thanks in advance!!
1) Do i have to start from scratch. Meaning wipe data as my first step?
2) is it as simple as deleting the bootstrap and installing safestrap?
3) Can i flash a new rom with safestrap (lets say cm7 for example) over the monster rom even tho monster was installed using the tweaked bootstrap?
4) using safestrap, how does it actually work? Meaning do i still install a new rom the same or similliar way as the tweaked bootstap? ( ex: cwm recovery.. install from sd.. etc.)
5) and the 5th question is. Im sure im missing some important info so.. What am i missing that would be helpful to me?
THANK YOU GUYS
Sent from my droid 3 using Tapatalk
you can just install safestrap but when you flash a rom now it will be flashed to your pre install partition leaving your original system (in this case with monster rom intact, though hash meant for you to keep the blur original system) intact. if you are leaving monster rom though i recommend just backing up with titanium backup and sbf ing back to stock then doing everything from safetsrap from now on
jellydroid13's answer is right on point.
However, I can answer your questions in more detail:
1. Installing Safestrap won't affect your primary system, as jellydroid13 says. It's meant to add a "2nd- system" where you're protected against bad flashes, etc. So there's no worry about /data for the 1st step.
2. Yes. Remove Koush's Bootstrap and Install Safestrap. Then open the app and use the "Install Recovery" button. The next time you reboot, you'll should see a splashscreen right after the Red "M" Logo. While that's being displayed you can enter Safestrap recovery by hitting the [ menu ] button.
3. No. Currently, there is no way for you to affect your MonsterROM /system from Safestrap. Be it flashing or otherwise. Now you can do a bunch of stuff with the data for your MonsterROM installation, via backup / restore, etc. But that's a bit more advanced.
4. Safestrap is basically a modified version of Clockwork Recovery. It has mostly the same menus for making backups, flashing ROMs, etc. If you're familiar with Koush's Clockwork Recovery, then you'll immediately know where everything is in Safestrap. For reference, Safestrap recovery is currently using CWRecovery 5.0.2.7 sources as it's base.
The biggest difference is that anywhere you see "/system" it's talking about a 2nd-system on your phone. SO, when you flash a ROM, you're flashing it to this 2nd area which you can now choose to boot from.
Added to the normal Clockwork Recovery menus is a Safestrap Menu, where you can set which system you want to boot from. When you "toggle" between the systems, Safestrap will stash your current data/cache files and save them and try to load any previously stashed data/cache for the system you're going to.
If you want your data from a previous ROM (or the Non-safe system) you'll need to advanced restore it from a backup file (data partition only). In many cases, data can cause a hung boot. If it does, then battery pull, go back into Safestrap recovery and wipe data/cache. You'll have to use a titanium backup instead once the OS is loaded.
5. Know that the /system backups you make in Safestrap are NOT compatible with Koush's Bootstrap(or the tweaked version of it). Safestrap expects to be loaded from the /preinstall partition. When you try and restore a Safe System to the main /system.. you will get a hung boot at the Red "M" Logo.
Don't do it... Bad.
Just so I understand.....
Hashcode, can you tell me if the following is true?
The actual phone has only one "real" /data partition.
Each time you toggle between systems (which is done via toggleing safe mode on and off), safestrap tars up the contents of /data and copies the tar file to sd/emmc, then DELETES the contents to free up the only real /data partition. Then optionally restores the /data from the previously deactivated system from a previously created tar file.
Right now my phone is running CM4D3 from an activated safesystem. Can I assume the contents of my original /system partition still contains the stock blur rom, and my original stock /data has been DELETED (after having been tarred up and moved to SD/EMMC by the toggle process)?
Questions:
Is the /restore partition a real actual disk partition or is it a subdirectory somewhere?
If something goes terribly wrong, is there a working SBF method that works no matter what has happened?
Following your directions, I do a "wipe data/factory reset". During this process, safestrap says it's formatting sdcard-ext. This obviously scared the **** out of me. Turns out my external sdcard was NOT formatted. What actually happened?
Now that I have a orig system and cm4d3 system in my tars, do I need to wipe data/cache and format system each time I toggle? (Does the unzipping of the saved system info do a format or wipe first)?
Since I did a backup BEFORE activating safe system, this backup does contain my stock /system and stock /data correct? I was using safestrap 1.04.
When you release a new version of cm4d3, do I need to wipe data before installing if I'm running a previous version of cm4d3?
When I installed safestrap, did you resize any of my physical partitions?
So far, I love SafeStrap and CM4D3. What was bugging me about stock (openvpn and tether) is working great! Thanks for all your hard work. For me, the only thing I see so far are the known audio-volume and camera issues. Also, it seems youtube and cam360 both try to scale and position video into a small box rather than go fullscreen (or be where they should be). MoboPlayer in hardware decode mode gets it wrong too, but in software decode mode, works fine.
Hello ryanmcdonald,
These are very insightful questions. I'm probably going to put them up on my FAQ.
Answers:
- Yes, the phone (and Safestrap) currently manage the 1 /data partition. (It's 2Gig in size, I couldn't find a 2nd area to store Safestrap's data in)
- Yes, it's doing a /data swap between toggles from the original system to 2nd-system.
- Your original system still contains the stock blur ROM. And your original /data has been moved to the .tar in {internal storage}/safestra/orig (and deleted from the /data partition)
- The restore files are stored in a subdirectory on your internal storage: safestrap/orig and safestrap/safe
- YES, we have a full fastboot for 5.6.890 (It's somewhere around here in the forums)
- The message is "formatting sd-ext" but yeah it looks scary when you first see it. The sd-ext area is where apps go when you place them on the SD card.
- You do not need to wipe data/cache between toggles now, as long as you want the same ROM and apps when you go back to that system.
- YES, you did exactly what you should have done: make a full backup prior to entering Safe Mode which means you have a fall back of your entire stock system for Safestrap to restore from should anything unforseen happen.
- You will not need to wipe data for new versions of CM4D3 (unless I say so in the release notes, but I can't think of a reason offhand.)
- No, I didn't resize any partitions. SIDE NOTE: I was considering in the future placing the 2nd-system and a new 2nd-data partition on the external storage area -- which would require resizing the vfat partition to be smaller by about 2GIG. But, I'll talk about that if I move towards that direction. I need to confirm that running from the SD card is a stable option through testing.
And thanks!
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
DoubleYouPee said:
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
Click to expand...
Click to collapse
I remember he said he had 3 people who had issues like you are describing. i believe uninstalling his bootstrap and then installing safestrap should do it. i thought part of the safestrap install was to remove the other hijacks. when in doubt, SBF, root with 1 click, safestrap and go go go
edit: i recently moved from tweaked bootstrap to safestrap and it worked find for me and its in his instructions per the thread in dev. DoubleYouPee I see where you actually quoted Hashcode saying that but i cant find where he said he knew of a couple people who had problems but i know he said he was looking into it. that couldve been a prior release too, not sure.
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
Which version of the Droid3Bootstrap were you running? I had made an original one back in Sept. (before Koush picked up support). And that hijack was slightly different than Koush's. It may be that there's an issue with Safestrap cleaning up the hijack files for that original version.. but I'd like to see what you were running.
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
RandomTaskMan said:
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
Click to expand...
Click to collapse
I'm not sure but that ROM might still have the /system/etc/rootfs files in it which causes Safestrap to bomb out during boots.
You can try deleting that folder from the ROM. Then format your /system and re-flashing. Let me know if that fixes it.
---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------
DoubleYouPee said:
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Click to expand...
Click to collapse
There may be some case I'm missing for the cleanup of the old bootstrap code, and I'm nearly certain you ended up with 2 bootstraps installed. I'll have to take a look and see if I did anything different in my tweaked version vs. his which is available in the Market. Sorry about that.
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Hashcode said:
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Click to expand...
Click to collapse
Ah I see, well no problem then I also think it didn't properly remove the older boostrap. But I'm sure I followed the right steps. Anyway the debrick was very easy with the 5min debrick and it works great now. Used it with maverom.
Goodluck with safestrap and CM7 etc!
Worked like a charm! Thank you sir!
WORKS like a charm. Thank you for your hard work. Your dedication to the development of these products is greatly appreciated.
Bootloop in safe system of Droid 3 XT862
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
jimcarter said:
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
Click to expand...
Click to collapse
Looks like you never got the OTA for 5.6.890 install that first then try again.
I second the OTA install. In almost all cases, the ROMs are built from the 5.6.890 files (including kernel modules).
With 5.6.890 CM4D3 boots
Thanks, Hashcode and eww245! I de-installed Safestrap Recovery, uninstalled Safestrap entirely, (didn't remove Superuser, Busybox or setUID "su"), updated to system 5.6.890 and reinstalled everything. Now CyanogenMod CM4D3-nightly-20111116-1445.zip installs and boots successfully.
I have an initial report on items that I tested. Almost everything is working, except I have an unusual carrier issue which I haven't dealt with yet, and the cellular connection isn't going to happen until that's resolved one way or the other. Here's the URL: (sorry, I'm new on this site so am not allowed to put links in posts, mail to [email protected] and I'll send it). The only real failure is well known to you: the camera app in the distro doesn't show camera content. But surprisingly, the Barcode Scanner app can use the rear camera to read barcodes. This suggests that the underlying driver or interface library is not whacked; the camera app may be doing something that the others avoid.
Anyway, thank you Hashcode for putting together this system image.
safestrap 3.71
I rooted my AT&T I337 4.2.2 mf3 s4 and installed safestrap It said installed and when I press install recovery it comes up with installation complete but when I reboot the phone it just reboots the phone it does not go into a safe strap menu. I am using 3.71 ver.
One quick note I have been reading and learning a lot from this site and would like to thank all the Devs for thier work. Thanks for any help you can give.
:good:
This thread will list and link to all core device essential stuff.
PM me if there is new stuff or something doesn't work please
STOCK ASUS FIRMWARE
WW_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
US_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
kernel_11_4_1_17.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
CWM Recovery V6.0.4.8. for 4.3*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery recovery.img [where recovery.img is the name of the file image you downloaded]
CUSTOM ROM'S
By Sbdags based on stock with quite some enhancements: HERE
CyanogenMod 11 Preview Proxy thread: HERE
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!
Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/show....php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/show....php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/show....php?t=2621028
Delete
Root and firmware.
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
tf701mega said:
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
Click to expand...
Click to collapse
If you want to root then use my guide as it is for 10.26.1.18. Downgrading to .47 and back up again is really painful.
download problem
Hi OP,
Download links are down...
please fix theme?
henengel said:
Hi OP,
Download links are down...
please fix theme?
Click to expand...
Click to collapse
anyone know where I can get the files? links are broken
kuthedude said:
anyone know where I can get the files? links are broken
Click to expand...
Click to collapse
Which files are you looking for?
Most of the files are available from ASUS's website and the ROM and recovery links are old and newer ones are available in the Development section of this form.
Sorry for the inconvenience.
Asked in the OP to PM me if there is new stuff or if somethings doesn't work but received nothing.
Files will be back end of the day with latest firmware and kernel source.
Hi, I am getting my tablet soon, and I am assuming the tablet will be on 4.3 or earlier by the time I get it.
What firmware/kernal/boot loader is the best setup to get me onto the latest 4.3 OS. I only am wanting this because I want to avoid the 4.4.2 battery drain issues (since I am most likely going to flash an AOSP ROM after I get this tablet).
Also, how would I be able to properly update the tablet with the firmware/kernal/boot loader? Thanks for the help!
Sent from my SCH-I545 using Tapatalk 2
Hi, I tried pushing my firmware file to root, but it wouldn't work. I would use root explorer and it would just freeze and restart. anyone know why this would happen? Im trying to update to 4.3 without getting into 4.4.2. please help if you can
You have to unpack the file, inside this is another zip file. Put it then in sd root this should work as far as i know
Gesendet von meinem LG-D855 mit Tapatalk
Hi
There is a new firmware version 11.4.1.27.
Is it posible to add this version to the post?
This warning also serves to other variants.
I see that many users of this variant are using other variant binaries and images trying to unlock the bootloader and install TWRP recovery.
My advise is to not do this or you can end with a brick.
Even worse, when trying to unbrick the phone, people are using other variant nand backup images, this will lead you to the infamous lost IMEI problem, and from this point if you don't have your modemst partitions backups, you are lost.
Flashing KDZ won't recover these partitions, they are unique to your phone and are not flashed in a normal KDZ flash, the only way to flash them is in TWRP or ADB.
I already supplied the proper D410HN Kitkat v10c and Lollipop v20a/b/c (they are the same) unlocked aboots and bootstacks but people insist flashing files from other variants.
My advise is, after rooting your phone, before doing anything else, the first thing you must do is to backup your modemst1 and modemst2 partitions to make sure you IMEI data is safe. You can make this backup in ADB or Android Terminal app with:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img
This will save modemst1.img and modemst2.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard.
Also, make a nand backup image in case of you need to make a testpoint or direct flash in nand to attempt to unbrick the phone.
Code:
dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=512 count=323583
This will save an unbrick.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard. Do not share this file with anyone else, this image have your IMEI data.
Why make your own unbrick.img file?
If you look at the partition table, you will have this:
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
unit s
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16384s 147455s 131072s fat16 modem
2 147456s 149503s 2048s sbl1
3 149504s 150527s 1024s rpm
4 150528s 151551s 1024s tz
5 151552s 152575s 1024s sdi
6 152576s 156671s 4096s aboot
7 156672s 157695s 1024s rpmb
8 157696s 158719s 1024s tzb
9 158720s 162815s 4096s abootb
10 162816s 166911s 4096s pad
11 166912s 173055s 6144s modemst1
12 173056s 179199s 6144s modemst2
13 179200s 211967s 32768s misc
14 212992s 278527s 65536s ext4 persist
15 278528s 323583s 45056s laf
16 327680s 372735s 45056s boot
17 372736s 417791s 45056s recovery
18 417792s 423935s 6144s fsg
19 425984s 427007s 1024s fsc
20 427008s 428031s 1024s ssd
21 442368s 443391s 1024s DDR
22 458752s 459775s 1024s encrypt
23 459776s 460799s 1024s rct
24 475136s 491519s 16384s ext4 drm
25 491520s 507903s 16384s ext4 sns
26 507904s 548863s 40960s factory
27 548864s 614399s 65536s fota
28 622592s 624639s 2048s sbl1b
29 624640s 690175s 65536s ext4 mpt
30 704512s 909311s 204800s ext4 cust
31 917504s 918527s 1024s eksst
32 933888s 5128191s 4194304s ext4 system
33 5128192s 6971391s 1843200s ext4 cache
34 6971392s 15223807s 8252416s ext4 userdata
35 15237120s 15269854s 32735s grow
(parted)
This ubrick image have your partition table and the partitions until sector 323583 (partition 15 - laf), which is enough to enter in download mode and flash KDZ with LG Flash Tool and make a complete and perfect recover. This also explains why when you flash an unbrick image from a unknown source and variant you lose your IMEI, modemst1 (11) and modemst2 (12) partitions are flashed along, overwriting your unique data.
Keep your backups in a safe place and now you can go ahead and unlock the bootloader, install TWRP, change partitions size and etc knowing that if anything goes wrong, if you manage to unbrick your phone, you won't loose your IMEI.
Good luck :good:
Files:
Unlocked bootloaders (aboot):
D410HN KitKat v10c: http://www.mediafire.com/download/lg0ewb6vnl184mq/aboot_d410hn_v10c_unlocked_.zip
D410HN Lollipop v20abc: http://www.mediafire.com/download/dzp38dk9jivw31j/aboot_d410hn_v20abc_unlocked.zip
TWRP Custom Recovery: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
Bootstacks:
D410HN KitKat v10c: http://www.mediafire.com/download/qx3cv5fzdzjsod2/Bootstack_D410hn_KitKat_v10c.zip
D410HN Lollipop v20c: http://www.mediafire.com/download/wxa5m1ch80hth54/Bootstack_D410hn_Lollipop_v20c.zip
Stock Flashable ZIP (for stock partition tables only):
D410HN KitKat v10c: http://www.mediafire.com/download/8u4zsj8tnyz4r6n/Flashable_D410hn_Stock_KitKat_v10c.zip
D410HN Lollipop v20c: http://www.mediafire.com/download/oqp0ubsq2jmzjph/Flashable_D410hn_Stock_Lollipop_v20c.zip
Thanks for posting these files for D410hn and warning owners of this LG L90 variant.
Recently, I decided to switch from stock to cyanogenmod and I got to find out your files in the middle of other posts.
Now this post made things crystal clear.
Thanks !
Gacrux, i must first of all thank you for your effort on gather all that info e put it on one post, this for us newbies was a great hand. But, for those like me that already have did things wrong, and already are on a mud puddle, and not expert like you guys here on XDA learning and teaching all concernments about root, flash, custom rom, stock, our beloved android, i must ask you some more of your patience, and write some more detailed tutorial, link us to posts that can help recover lost IMEI because used that russian files and process that you quote on another post. I managed after long time research to find a process that a could insert one of my IMEI to the slot one, but slot 2 stills IMEI "0", checked with *#06#. Interesting is that here on my home, phone are getting signal on both sims, i have tested and both can do and receive calls, data flow, etc, but when i got to drive to another near city, like go to my job, i loose signal on both. So, i dont have (i didnt know that i have to) that backups modemst1 and modemst2 partitions, what can i do ? I still can remove my battery and put on a paper that 2 IMEi numbers that i need, in case to do some process. I'm using D410HN lollipop 5.0.2, base band M8626A-AAAANAZM-1.0.6063 kernel 3.4.0+ ,next info LRX22G.A1440649755 and V20c-OP1-HQ What would be the steps i need to follow to at least try to put IMEI on place, unlock, install a more light rom, that consumes least internal storage space, but all functions like cameras, nfc, bluetooth, etc are working. I'm sure 100% that you will be helping a lot of people. Thanks another time, and awatin directions !
I'll try to look into this IMEI issue soon and try to find out if there is a chance to rebuild both modemst partitions with both SIM cards on D410hn, but from what I could find until now, I wouldn't get hopes up... In the past, when IMEI were stored in EFS partitions, they were stored in plain text and could be hex edited, but they don't do this anymore, I downloaded modemst partitions from two L90 and compared them and found out that this data is now fully encrypted.
You loose signal probably because you are using other variant modem and modemst data.
Regarding the storage issue, I have a self made slim version of stock v20c and modified the partition tool in this topic (http://forum.xda-developers.com/lg-...ck-partition-table-tool-lg-l90really-t2946323) to fit to my needs, and more importantly, to change the units he used to respect the partitions beginnings and ends (partition by sectors I find to be more precise and safe), I removed everything that I judged useless from the stock LG rom and remade the partition table to shrink system partition to give more room for userdata.
I removed this stuff from the original ROM:
/system/usbautorun.iso
/system/app/Books
/system/app/ChromeWithBrowser
/system/app/Drive
/system/app/Gmail2
/system/app/GoogleTTS
/system/app/Hangouts
/system/app/LGPCSuiteUI
/system/app/LGSearchWidgetProvider
/system/app/LGWeather
/system/app/LGWeatherService
/system/app/LGWeatherTheme
/system/app/Maps
/system/app/Music2
/system/app/Newsstand
/system/app/PlayGames
/system/app/PlusOne
/system/app/Street
/system/app/talkback
/system/app/Videos
/system/app/YouTube
/system/apps/bootup/LGBoxnet
/system/apps/bootup/LGFlashlightWidget
/system/apps/bootup/LGSmartWorld
/system/apps/bootup/LGTaskManager
/system/priv-app/LGApplicationManager
/system/priv-app/LGBackup
/system/priv-app/LGBrowser
/system/priv-app/LGDictionary
/system/priv-app/LGDMSClient
/system/priv-app/LGEasyHome
/system/priv-app/LGEmail
/system/priv-app/LGFileManager
/system/priv-app/LGMemo
/system/priv-app/LGPCSuite
/system/priv-app/LGQTranslator
/system/priv-app/LGUpdateCenter
/system/priv-app/Velvet
/system/vendor/carrier/system/LGRemoteCall
/system/vendor/carrier/system/rspermlge
/system/vendor/overlay/com.android.browser
/system/vendor/overlay/com.lge.appbox.client
/system/vendor/overlay/com.lge.bnr
/system/vendor/overlay/com.lge.easyhome
/system/vendor/overlay/com.lge.email
/system/vendor/overlay/com.lge.filemanager
/system/vendor/overlay/com.lge.lgworld
/system/vendor/overlay/com.lge.task
/system/vendor/overlay/com.lge.updatecenter
/system/vendor/overlay/com.lge.sizechangable.weather
/system/vendor/overlay/com.lge.sizechangable.weather.theme.optimus
My post on the repartition tool thread about my personal changes: http://forum.xda-developers.com/showpost.php?p=63218497&postcount=151
So, about that modem partitions, i read somewhere, that some "box" called octopus/octoplus can repair that **** i did on my phone e by that restore that 2 IMEI to his place, i looked into some tecnicians here im my city, but anyone have that, nor knows nothing that can repair, help me, i will try a day off my job next week to search on a bigger city for a technical assistance that have this box to try it out, this is what i could found, about this problem losing imei by overrun that partition where they are writed. I must say that I have encountered too much resistence from the people that knows how to do the process, because they think i stole the phone, even seeing me gather to his front door inside my police uniform. I must thank you Gacrux another time to be willing to help me and other people, even without know me, thank you man ! About your rom, all hardware is functional ? Did you managed to reduce the size of that system data about to 4.21 GB that are untouchable, chequing from configuration=>general=>storage just below cache data, "many" where when i click i can see that "system data" in about 4.21 GB. I already did a full wipe, but i dont have a custom recovery, because i tried to install twrp from "rom installer" from JRummy and it says that no one is compatible with my phone. This is one thing that i wanted to with a custom recovery, install a custom rom that have this system data a little smaller.
My phone is fully functional, mainly because from the start I never flashed other variant files in my phone and after rooting I knew it was a wise move to backup my modemst partitions before doing anything else after root the phone.
When I decided to mod my L90 I saw that nobody had unlocked the D410hn variant or made proper bootstack for us, with a little search I realized how to unlock our kitkat and lollipop aboots with IDA disassembler and built the proper bootstack from the partitions extracted of our kdz file.
As far as I tested, from bootloader downgrade and softbricks, the modemst and own unbrick images were enough to make a perfect recover of the phone (I had to simulate some scenarios in my own phone to test if my files and my advises would actually work).
Unfortunately, for the ones that didn't know that they MUST do some obligatory backups files, the lack of these backups lead them to problems like the one you are facing.
Custom recovery can be flashed with adb, no need for app, I'll post later when I arrive home.
System partition is actually 2GB. With stock LG ROM, there are around 60MB free. The debloating I did freed around 610MB, this allowed me to reduce system partition to 1.39GB. Also, I reduced cache partition from 900MB to 64MB. The difference was given to userdata partition, allowing me to grow from the stock 3.34GB to 5.38GB.
thank you your attention ! From your knowledge im making my own, thank you for advices too, that i will follow for sure !
To flash custom recovery with adb only (needs root and unlocked bootloader, if you already have, there is no need to repeat):
1. Root.
2. Copy aboot.bin and recovery.img (rename TWRP_2.8.7.0_270615_L90.img) to the root of your external microSD card.
3. Open adb shell or android terminal, take superuser permission with su and allow it in your phone screen.
4. Flash the hacked unlocked bootloader for D410HN Lollipop with dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. Flash custom recovery (TWRP) with dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
To boot the custom recovery, from android you can send reboot recovery in adb or terminal (needs su). To boot recovery from the phone off, hold VOL - and PWR, when LG logo appears, release and hold PWR button. A blank screen asking to reset the phone to factory settings will appear, select YES twice and wait custom recovery to boot. Don't worry, your phone won't be reset since stock recovery was replaced with a custom one.
Well, i think i can take that line of commands with ADB, but the problem here is that files, can you please link that needed files that are "for sure" functioning in D410HN lollipop 5.0.2, because i dont want a new brick ! You can link to some post, that you are certain about, and i will go there e download, thanks again !
edit: I dont have unlocked bootloader, because, as i said i was feared that i could download wrong files and did **** again, if you can help in this one too, i will pay a beer !
edit: About root, i tried purpledrake, towelroot, and others, last one, and only that works was kingroot, fully functional, checked with root checker.
I think I found a way to recover the second SIM IMEI.
Requires Qualcomm Product Support Tools (QPST), HxD (or any other decent hex editor), LG Mobile Support Tool and an IMEI to HEX converter.
Though I didn't tested it myself in my own phone, I believe it's going to works, also in any Dual-SIM variant.
I'll first try to find a way to convert the SIM to those HEX values (they are not a straight text to HEX conversion), if OK, I'll write something about this matter and will post soon.
---
It's done, read: http://forum.xda-developers.com/lg-l90/general/imei-fix-2nd-sim-slot-t3229097
Hi there. I also have a D410hn. I was on 20b rooted and using TWRP, then the 20c upgrade came. So I've used your 20c flashable zip to go to 20c.
It worked just fine, then I've used the flashable superuser as you've suggested and it worked just fine too. The problem is that when I go to phone settings -> about this phone -> software info it displays "V20B-SCA-XXXX". I've checked build.prop and it shows 20c, so what's wrong?
If I flash your 20c bootstack it will fix it? Will I lose something like have to root or install custom recovery again?
Thanks
Sent from my LG-D410 using XDA Free mobile app
Flash v20c bootstack. Lollipop bootstack v20c is different from v20ab, as noted here: http://forum.xda-developers.com/showpost.php?p=63292272&postcount=57
The user who edits the topic didn't updated to include the newer bootstack for D410hn.
You are not going to loose anything since it won't flash boot and system partitions.
It worked, settings display 20c now. Thanks
Sent from my LG-D410 using XDA Free mobile app
Hello. I have D405n and when I try to unlock bootloader i bricked phone. Then I was searching for solution and somehow did that with success but in setting phone was D405 (without N). It was few months ago but these days I was testing custom roms and noticed that on rom 5.1.1 i dont have imei and dont have signal, but on stock lollipop I have signal but imei is zero. Any ideas how to fix this?
Would help flashing loader?
Fangio92 said:
Hello. I have D405n and when I try to unlock bootloader i bricked phone. Then I was searching for solution and somehow did that with success but in setting phone was D405 (without N). It was few months ago but these days I was testing custom roms and noticed that on rom 5.1.1 i dont have imei and dont have signal, but on stock lollipop I have signal but imei is zero. Any ideas how to fix this?
Would help flashing loader?
Click to expand...
Click to collapse
Try QPST: http://forum.xda-developers.com/showthread.php?t=2701861
This can also be a 5.1.1 issue or you are in a different bootloader. CM development for L90 is a little messy, don't know if it's using kitkat or lollipop bootloader now.
How to flash stock bootloader? I try flashing 4.4 kdz and 5.0 kdz and its the same.
Fangio92 said:
How to flash stock bootloader? I try flashing 4.4 kdz and 5.0 kdz and its the same.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Done that few times and its the same... QPST not working but with EFS I manage to read data but not to write.
If I get a backup of another L90 and restore it to mine, and then change the IMEI 1 through the QPST, does it works?
ps .: my IMEI 2 is zero
LG-D410HN "deadboot"
Hello, have a LG D410hn with deadboot, someone would have Loader.img file D410hn (Brazil), as did only with the D410 and the front camera has stopped working and zeroed IMEI. If anyone can help I am grateful!
As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!
Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.
True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is
Just leaving here partitions structure:
Model: MMC 8GND3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED
Lets go recovery!
idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;
my /proc/idme/board_id reads 0025001040000015
Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk
I did yesterday didn't work
Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk
No I'll try today
Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.
Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.
How would we flash it?
Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...
Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader
- P A R T Y -
Android Partition Treblerizer
A tool able to seamlessly create / remove the vendor partition from within TWRP
INTRODUCTION
This was my weekend project. The creation of a tool able to create and remove the vendor partition from TWRP, so a computer was not required. The idea came to me las weekend when I was travelling and I couldn't test some roms since I didn't had the right partition configuration and no computer on hand. So I created this TWRP flashable ZIP that can create and remove the Vendor partition from the system or userdata partitions without a computer and without wiping the files in the mother partition in the recommended configuration.
The tool will try to resize the mother partition without wiping it, both when creating and removing the vendor partition. Nonetheless it can be done only when the mother partition is ext4, only when the vendor partition is at the end of the mother partition, and when the mother partition is not encrypted. The recommended configuration is what you get when selecting the first choice in every option: splitting 512 MB from the end of the system partition. A reboot is required after patching the partition table since the kernel has to reload it before doing any other thing.
REQUIREMENTS
Due to the use of a key detection binary, it is compatible only with ARM and ARM64 devices running TWRP. So far I have tested it in the Axon 7 but It should work in any compatible device. I made it this way so other legacy devices could transition to Treble ROMs + GSI, and Android Pie. Please let me know about other devices using this tool!!!!!
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
Either for creating or removing a vendor partition,, follow these steps:
1. Download the TWRP ZIP tool to your External SD card.
2. Boot to TWRP recovery, under Install, flash the ZIP file as any other ROM or MOD file to execute the tool.
3. Reboot to recovery again to ensure the changes are applied properly.
4. In some cases you will need to format the mother partition after adding or removing the vendor partition next to it.
CREATE A VENDOR PARTITION:
So far these are the available options:
Mother partition selection: system / userdata
Split position: Splitting from the end / start of the mother partition.
Vendor partition size: 512 / 800 MB
REMOVE THE VENDOR PARTITION:
Should a Vendor module already exists, Party offers to remove it, returning to a Non-Treble partition table. It will return the space to the mother partition, system or userdata. So, older non Treble ROMs could be flashed after the mandatory reboot.
DOWNLOAD
Party_v0.5_ARM_20180831.zip
SOURCES
C'mon, it is a script!!! the sources are inside the zip. Use them in your projects but don't forget to give credit to the source !!!
CREDITS
@someone755 for the keycheck binary
@Zackptg5 for the V4A install script that inspired my version.
Just in case you want to use this tool for preparing the partition table for flashing some common sets of ROMs:
The The first Treble ROMs made by NFound splits 800MB of Vendor partition from the beginning of the data partition. You can do it using a Computer and flashing the EDL package or you can use this tool from TWRP.
The Unofficial LOS 15.1 20180810 splits 512MB of vendor partition from the end of the system partition. The new Unofficial LOS 16.0 ROMs requires a vendor partition using this scheme. The benefit of this configuration is that the user data is not formatted or modified and system partition is resized without losing any data.
In case you want to return to a previous non-treble rom, you just need to run this tool from TWRP and seamlessly remove the vendor partition.
Thanks yet again oki, for all the great tools you bring us for our phones.
Question: If you were to choose, which vendor part version would you recommend people create to prepare for upcoming Treble releases, the 800 MB or the 512 version?
Also , since I & others already have the NFound method installed, is there a need/benefit to convert over to the other one?
Thanks, this is great!
Not mentioned in your Procedure: are there any prerequistes, such as having a specific ROM, TWRP, bootloader, or ??? already installed?
Can this be run from B35 Stock to then be 'Treble Ready'?
christoophat said:
Thanks yet again oki, for all the great tools you bring us for our phones.
Question: If you were to choose, which vendor part version would you recommend people create to prepare for upcoming Treble releases, the 800 MB or the 512 version?
Also , since I & others already have the NFound method installed, is there a need/benefit to convert over to the other one?
Click to expand...
Click to collapse
The best configuration is splitting 512MB (more than enough) from the end of the system partition. That leaves 5.5GB for system, when usually it doesn't even reach 2GB. a 3GB system partition is considered large nowadays. 5.5GB is still overkill. I have even thought in creating a Treble A/B partitioning for seamless update. But let's first stabilize Treble A before thinking in more advanced configurations.
amphi66 said:
Thanks, this is great!
Not mentioned in your Procedure: are there any prerequistes, such as having a specific ROM, TWRP, bootloader, or ??? already installed?
Can this be run from B35 Stock to then be 'Treble Ready'?
Click to expand...
Click to collapse
The only prerequisite for this tool is having TWRP. It actually can be used in any legacy ARM device, not only the Axon 7, to create the vendor partition from system or data.
You can run it with any bootstack, even the old Nougat or MM bootstacks. The tool is bootstack agnostic. However, there is no point on having a vendor partition with a ROM requiring an old Nougat or MM bootstack, since they don't use it. Treble ROMs are all compiled using the Oreo B12 bootstack, and they won't boot with any other bootstack. This tool only prepares the partition table, the bootstack is another thing you must prepare before flashing any ROM.
Hi @Oki
Thanks for your handful tool!
It states that it has found vendor partition before data partition (I had it installed with NFounds method)...
My question: Will deleting this vendor partition using your tool leave data as is or will it wipe the whole internal storage also?
Gachmuret said:
Hi @Oki
Thanks for your handful tool!
It states that it has found vendor partition before data partition (I had it installed with NFounds method)...
My question: Will deleting this vendor partition using your tool leave data as is or will it wipe the whole internal storage also?
Click to expand...
Click to collapse
It will wipe data and internal storage since the split was done at the beginning of the userdata partition so it was easier to flash using the EDL method both in the 64 and 128GB Axon 7. Now with this tool there is no reason at all for splitting from the data partition. Those with the initial 800MB split will have to backup data and storage to recover those 800MB and transition to the 512MB vendor partition at the end of the system partition. I already did it so now I can go back and forth seamlessly without losing the internal storage.
Hello Oki, I'm planning on following the steps below to install the treblerized August build of los 15.1 and was wondering if your tool would make the process any easier or would it even be necessary? I'm currently on the non treble 7/23 build of 15.1. Also thanks for all your contributions to the Axon 7 community!
blu3wh0 said:
Coming from the July LOS builds, install of the 8/10 build was simple and no impact to my data:
1. Install TWRP 3.2.1-8-TREBLE (for decrypting data) or 3.2.3-0-axon7. Reboot.
2. Wipe system/cache/dalvik cache (and data if not using LOS).
3. Install 8/10 LOS build. This will partition Treble if it does not exist, otherwise I think it'll update it.
4. Install GApps.
5. (optional) Install Magisk 16.7 (SafetyNet fails, but I don't seem to have any issues otherwise).
6. Boot into ROM.
My most frustrating issue is the one I mentioned above, but I have yet to try anything other these LOS builds so far.
Click to expand...
Click to collapse
First, thanks Oki! This is a great addition to our tool set, and will make life much easier going back to stock.
I've been following the LOS threads and have been trying to keep up, so if these questions have been answered already please just point me in the right direction. There's a lot of information all over the place, and it's difficult to search for without already having a working understanding of it.
Now that we have a simple method of adding a vendor partition (acknowledging LOS having an already integrated treblerizer, but no return), are we now able to reliably flash standard GSIs? If not, what exactly is needed to make our phone compatible with standard GSIs?
The kernel still goes into the /boot, which would still be device-specific, so the way I understand it is that we still need the other device-specific stuff like DAC configs, which would then go into the /vendor? I take it this means the HALs (if that's what I'm talking about) are at a level above bootstack but below kernel?
If we were to go flashing GSIs now, would a lot of crap just be broken, or would it pretty much work save for the DAC? If broken, could we get it to just default to the SD820 integrated DAC? Are we (the xda community, developers, users, etc) able to make HALs that would accomplish getting audio to work properly in either case, or is this something that must be included in the ROM or kernel rather than /vendor?
If there is any interest, an FAQ on this might be a good idea, if one doesn't currently exist. We'd just need someone to maintain it. I'd be happy to do so, but obviously I'm currently terribly confused LOL, and definitely need to do a lot of required reading on this.
roisuke said:
Hello Oki, I'm planning on following the steps below to install the treblerized August build of los 15.1 and was wondering if your tool would make the process any easier or would it even be necessary? I'm currently on the non treble 7/23 build of 15.1. Also thanks for all your contributions to the Axon 7 community!
Click to expand...
Click to collapse
LOS15.1 20180810 already creates the vendor partition, so no need for my tool for creating it. It is already an easy process when coming from a non-treble LOS15.1. In case you prefer to go back to the previous non-treble rom, then you will need PARTY. PARTY is also required to transition from the old 800MB vendor to the new location at the end of the system partition.
Masterjuggler said:
Now that we have a simple method of adding a vendor partition (acknowledging LOS having an already integrated treblerizer, but no return), are we now able to reliably flash standard GSIs? If not, what exactly is needed to make our phone compatible with standard GSIs?
The kernel still goes into the /boot, which would still be device-specific, so the way I understand it is that we still need the other device-specific stuff like DAC configs, which would then go into the /vendor? I take it this means the HALs (if that's what I'm talking about) are at a level above bootstack but below kernel?
Click to expand...
Click to collapse
All the hardware specific drivers are in the Kernel, but the configuration files and libraries are in the vendor partition in a treble rom. GSI use the available libraries, but they must ask for those entry points. So if a Vendor partition doesn't provide the GSI with the standard entry points along with the configs, then the specific hardware won't work. In our case the DAC is critical since most of us purchased the Axon 7 instead of the OP3 just because of the amazing sound of this device. The Vendor partition is the key, but it all depends on the device tree and ported vendor blobs.
Masterjuggler said:
If we were to go flashing GSIs now, would a lot of crap just be broken, or would it pretty much work save for the DAC? If broken, could we get it to just default to the SD820 integrated DAC? Are we (the xda community, developers, users, etc) able to make HALs that would accomplish getting audio to work properly in either case, or is this something that must be included in the ROM or kernel rather than /vendor?
Click to expand...
Click to collapse
Probably the future will be a Treble ROM for the Axon supporting the standard Qualcomm devices and some kind of patches for the GSI so we could enjoy the excellent DAC. The best would be if ZTE release an Android Pie update for us the same way it is going to happen for the OP3.
Masterjuggler said:
If there is any interest, an FAQ on this might be a good idea, if one doesn't currently exist. We'd just need someone to maintain it. I'd be happy to do so, but obviously I'm currently terribly confused LOL, and definitely need to do a lot of required reading on this.
Click to expand...
Click to collapse
You are very welcome to create answers or gather the answers in a central FAQ.
I have created this tool so the Treblerization of legacy devices could be easier and the Axon 7 could benefit of it too. This device has an amazing hardware configuration, the only problem is the software. It all depends on ZTE and the user base.
So other than the DAC config, is there anything else broken or preventing us from flashing GSIs? Put another way, what else would we need to port/create for /vendor in order to properly run a GSI? I'm sure if we create a vendor partition and just flash a GSI, /vendor will still be empty and useless until we do something with it.
Also, for anyone who cares about semantics, I am saying "we" because I would at some point like to learn more and also contribute to these projects. I don't have much time for the foreseeable future due to college starting again, but we have to remember it's not like developers are a certain breed that do nothing but unpaid work for us. It's everyone's responsibility to keep development alive.
So i flash this in twrp and can delete vendor partition?
---------- Post added at 06:44 AM ---------- Previous post was at 06:38 AM ----------
Well,after i flashed this... vendor is still here and twrp is unable to mount vendor...what to do now?
Hi!
Of course you deserve the THANKS word, so I would start with that ...
My question is; I am running the treblerized version of AEX 5.8, provided by NFound, so my vendor partition is 800 mb one. Is it recommended to flash the PARTY to make it smaller (512 mb) or is this one just good enough?
Thanks.
Dear @Oki, can i use this on any device? say i have an old xperia z ultra (togari) and i wanna trebelize it..
Is there ANY way this could be used to reduce the system partition to 2GB or 2.5GB like stated in another comment? And kill other ones?
- BT_Firmware : 1GB wasted
- Cache : 750mb wasted
- dev : 2GB wasted
- system : 4GB wasted
> 8GB that I can barely use, or that I should paste into, using root programs...
Thanks!
Predatorhaze said:
So i flash this in twrp and can delete vendor partition?
---------- Post added at 06:44 AM ---------- Previous post was at 06:38 AM ----------
Well,after i flashed this... vendor is still here and twrp is unable to mount vendor...what to do now?
Click to expand...
Click to collapse
I should have been removed. Could you please run PARTY and at the end do not reboot, open the terminal and type:
Code:
cp /tmp/Party.log /sdcard/
Then boot to system and share or send to me the Party.log file that should be in the internal storage so I could see what happened.
Thanks
samo_lego said:
Hi!
Of course you deserve the THANKS word, so I would start with that ...
My question is; I am running the treblerized version of AEX 5.8, provided by NFound, so my vendor partition is 800 mb one. Is it recommended to flash the PARTY to make it smaller (512 mb) or is this one just good enough?
Thanks.
Click to expand...
Click to collapse
800 is good to go, there is no need to recover that space unless you need those 800MB returned to your internal storage.
taufikthexfader said:
Dear @Oki, can i use this on any device? say i have an old xperia z ultra (togari) and i wanna trebelize it..
Click to expand...
Click to collapse
It should work. But creating the vendor partition is just one step. Be aware that the developers should do the hard work of splitting the ROM files and configuration from a single system image to a vendor and a system image, along with the changes in the kernel of the rom.
RedWave31 said:
Is there ANY way this could be used to reduce the system partition to 2GB or 2.5GB like stated in another comment? And kill other ones?
- BT_Firmware : 1GB wasted
- Cache : 750mb wasted
- dev : 2GB wasted
- system : 4GB wasted
> 8GB that I can barely use, or that I should paste into, using root programs...
Thanks!
Click to expand...
Click to collapse
BT_firmware is only 1MB, not 1GB
Cache is in the same disk than data so it can be added to the main storage with some backup and repartitioning. We can recreate another cache partition from the system partition.
Not sure what partition are you referring to as "dev". Devinfo is only 4KB and Devcfg is 128KB.
So far the only partitions we can use to increase the storage userdata partition are in the /dev/block/sda disk. This is the stock partition table:
Code:
Number Start (sector) End (sector) Size Code Name
1 6 7 8.0 KiB FFFF ssd
2 8 204807 800.0 MiB FFFF cache
3 204808 205063 1024.0 KiB FFFF misc
4 205064 205191 512.0 KiB FFFF keystore
5 205192 205223 128.0 KiB FFFF devcfg
6 205224 205255 128.0 KiB FFFF fbop
7 205256 205383 512.0 KiB FFFF frp
8 205384 205511 512.0 KiB FFFF cryptkey
9 205512 13944826 52.4 GiB 8300 userdata
As you can see only cache is there with enough space to consider it. The System disk is another interesting partition since the Treble A/B could be possible with some work:
Code:
Number Start (sector) End (sector) Size Code Name
1 6 133 512.0 KiB FFFF rpm
2 134 645 2.0 MiB FFFF tz
3 646 773 512.0 KiB FFFF hyp
4 774 1285 2.0 MiB FFFF fsg
5 1286 1289 16.0 KiB FFFF sec
6 1290 1417 512.0 KiB FFFF pmic
7 1418 25737 95.0 MiB 0700 modem
8 25738 29833 16.0 MiB FFFF dsp
9 29834 30089 1024.0 KiB FFFF dip
10 30090 38281 32.0 MiB FFFF mdtp
11 38282 38537 1024.0 KiB FFFF aboot
12 38538 54921 64.0 MiB FFFF boot
13 54922 1627785 6.0 GiB 8300 system
14 1627786 1644169 64.0 MiB FFFF recovery
15 1644170 1644170 4.0 KiB FFFF devinfo
16 1644171 1644426 1024.0 KiB FFFF bluetooth
17 1644427 1644458 128.0 KiB FFFF lksecapp
18 1644459 1644522 256.0 KiB FFFF keymaster
19 1644523 1644586 256.0 KiB FFFF cmnlib
20 1644587 1644650 256.0 KiB FFFF cmnlib64
21 1644651 1644714 256.0 KiB FFFF apdp
22 1644715 1644778 256.0 KiB FFFF msadp
23 1644779 1644779 4.0 KiB FFFF dpo
24 1644780 1653135 32.6 MiB FFFF splash
25 1653136 1663375 40.0 MiB FFFF echarge
26 1663376 1663887 2.0 MiB FFFF sti
27 1663888 1663994 428.0 KiB FFFF last_parti
We have a total of 6.5GB in the /dev/block/sde disk that could be repartitioned to handle the Treble A/B configuration for seamless update in our Axon 7.
Oki said:
BT_firmware is only 1MB, not 1GB
Cache is in the same disk than data so it can be added to the main storage with some backup and repartitioning. We can recreate another cache partition from the system partition.
Not sure what partition are you referring to. Devinfo is only 4KB and Devcfg is 128KB.
Click to expand...
Click to collapse
This might be coming from an A2017 or A2017U. This is what appears on a A2017G:
Here is what I see using a root file explorer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It doesnt seems to be SYMLINKS, since I only have a 52GB DATA partition, which would account for those 8GB missing + 2-4GB of system and a bit more.
Is there any way I could use the tool to modify partitions, or is that in ROMs as well?
- I know that If I go this route, I'll probably have to modify ZIP files for the rest of the device lifetime, but I'm ok with this...
- At the time of the Galaxy S2 (i9100) and HP Touchpad, we ended up removing the partition size files in ROMs and getting much, much more space.
i did a stock restore trough EDL miflash.But i used party zip when i had gsi firmware installed on system,and i did use remove vendor option,i think that was a problem..i had to full clean phone first i think
RedWave31 said:
This might be coming from an A2017 or A2017U. This is what appears on a A2017G:
It doesnt seems to be SYMLINKS, since I only have a 52GB DATA partition, which would account for those 8GB missing + 2-4GB of system and a bit more.
Is there any way I could use the tool to modify partitions, or is that in ROMs as well?
- I know that If I go this route, I'll probably have to modify ZIP files for the rest of the device lifetime, but I'm ok with this...
- At the time of the Galaxy S2 (i9100) and HP Touchpad, we ended up removing the partition size files in ROMs and getting much, much more space.
Click to expand...
Click to collapse
The system reports logical sizes. A partition can appear to the system with a virtual size, the same way a VHD drive can have virtually 200TB when the image file is only 100MB in size, or compressed drivers storing virtually more space than the physical available space. The physical 1MB BT partition holds a vfat filesystem that wraps a 72MB firmware image (3 files) in a virtual 1GB partition. But the filesystem image is only 1MB.
dev is the device mount, it is a region in memory for communicating with the kernel through the fsnodes.
The other entries are mount points, some of them virtual or not corresponding to a physical partition.
Bottom line, that app provides you not with the physical partitioning of the device, but with a list of logical mount points and logical/virtual sizes.
Predatorhaze said:
i did a stock restore trough EDL miflash.But i used party zip when i had gsi firmware installed on system,and i did use remove vendor option,i think that was a problem..i had to full clean phone first i think
Click to expand...
Click to collapse
No, it should work in any case. Please provide me with the log file so I could figure out what you have and why it didn't worked for you. It will also helps others. I am suspecting you could have 2 vendor partitions in two different disks, so when you remove one, the software will still detect the other one in the next run. This is just an hypothesis I would like to clarify. Since you already flashed an EDL package on top, then there is no way to see it now.
Please, if you or someone else encounter this situation, please let me know.