Database Info

[Tut][I9001] How To Repartition Brocken Partitioned I9001 devices

Hi every one !
Our Odin version doesn't support repartition , so we can't do any thing while we have a Brocken partition ! Brocken partition are software related or hardware related , If you used the method bellow with no success your problem is hardware related and you need to at least replace your EMMC ic . OK I will describe more on method , the alternative method is flashing whole of empty partitions on +8 partitions except some partitions such as efs and ...
1- you need to check out which partitions are Brocken ! Choose format/wipe option in recovery mod to find out which are brocken , mostly data or cache partitions are Brocken , or in harder situation may system !
2- you need to create empty partitions for Brocken ones , you need terminal emulator to run this ( for data and cache )
Code:
su
dd if=/dev/zero of=/data.img.ext4 count=1413120
dd if=/dev/zero of=/cache.img.ext4
count=102400
# ... do Like this for other brocken partitions
continue for every Brocken partitions
3- tar every empty partitions you have created in step 2
4- flash tar file by Odin in one package
5- When your device boots up check out Brocken partitions are fixed or not if yes wipe them in recovery if not your problem is hardware related and you need to change EMMC ! I hope all Brocken partitions fix by this method and you won't need to hardware fixing .
# Do At Your Own Risk ! # I'm not responsible any more ! #
Just do this when you have Brocken partitions ! This can cause some problems to non damaged devices !(thanks to Broodplank for reminding )
Credit:
BroodPlank1337 - Helping me
Cheers
AliReza

Ok some additional info:
You can get the block size by looking at the /proc/partitions table
Code:
major minor #blocks name
7 0 2111 loop0
179 0 7757824 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5230592 mmcblk0p28
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
254 0 2110 dm-0
Also our odin has no default repartition box idd, but I made a package a while ago which resets "all" partitions:
Code:
adsp.mbn (mmcblk0p5)
amss.mbn (mmcblk0p6)
boot.img (mmcblk0p8)
cache.img.ext4 (mmcblk0p19)
data.img.ext4 (mmcblk0p17)
dbl.mbn (mmcblk0p1)
EMMCBOOT.MBN (mmcblk0p4)
emmcparam.bin (mmcblk0p14)
osbl.mbn (mmcblk0p2)
partition.bin (mmcblk0p0)
persist.img.ext4 (mmcblk0p12)
preload.img.ext4 (mmcblk0p18)
recovery.img (mmcblk0p13)
system.img.ext4 (mmcblk0p15)
oh and a global message to all, if you don't have to use dd, don't use it. when you have non corrupted partition that you want to wipe use "cd /partition && rm -Rf *" its always the safest option. (unless executed in root hehe)

AW: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
Thats very usefull! Thanks to you both!
Sent from my GT-I9000 using xda app-developers app

XeLLaR* said:
Thats very usefull! Thanks to you both!
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thanks for supporting ... but I wish you won't ever need to use this

alireza7991 said:
Thanks for supporting ... but I wish you won't ever need to use this
Click to expand...
Click to collapse
Idd hehe, I've had some crazy moments that I accidentally removed a partition (when having over 50 windows open, and 10 of them are a commandline), but when flashing broodROM RC5 it was restored anyways ;p

broodplank1337 said:
Idd hehe, I've had some crazy moments that I accidentally removed a partition (when having over 50 windows open, and 10 of them are a commandline), but when flashing broodROM RC5 it was restored anyways ;p
Click to expand...
Click to collapse
Hehe
You were in the software damaged case , so you could restore but if you had hardware damaged emmc you had to change it ! Some thing like Buffo had done to its device was hardware Brocken emmc

UP !

Hi! Is this useful if my SGS+ always freezes when I wanna make a factory reset? And it freezes at the Samsung galaxy screen.... I tried to format with a few recoveries but always the same problem. It started after I failed to flash the newest CM 10b4.
I tried already to flash a few stock-roms over odin and other custom roms over CWM / FeaMod / TeamWin recovery.... Nothing helped. How can I find out if that emmc is brocken?

Imanidiot said:
Hi! Is this useful if my SGS+ always freezes when I wanna make a factory reset? And it freezes at the Samsung galaxy screen.... I tried to format with a few recoveries but always the same problem. It started after I failed to flash the newest CM 10b4.
I tried already to flash a few stock-roms over odin and other custom roms over CWM / FeaMod / TeamWin recovery.... Nothing helped. How can I find out if that emmc is brocken?
Click to expand...
Click to collapse
Did you flash the CM10 with a to old version of CWM? (it needs to be 5.4.0.4 atleast). this could have caused it, if not, did you do excessive rom flashing? (sometimes when im hours and hours of trying to flash things on my phone it seems to get "tired" and the formatting/installing goes so slow that you almost manually pull the batter)
Have you tried to flash broodROM RC5? don't want to advertise for it but it's generally known that it "unbricks" devices because of the large number of partitions
Have you tried the CWM bootloop solution btw? http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330

I tried the bootloop solution but it didn't work... And I don't think that my phone went "tired" cuz cache formating is still working...but the phone turns automatically off after a few seconds.
No i never tried the other rom solution cuz someone other with the same problem tried it already but it didn't work... Well I'll try it anyway.
And thanks for the fast answer! I would give you a "thanks" but i gave already 8 sorry..
Edit:
I can't remember which CWM I used before... but after I saw the "Symlinks failed" "Status 7" error I flashed the latest CWM but there it was just the same :/

How can i know about broken partitions ?
Because i have ~7 months left to change my phone, and i don't want to brick my phone which i love much <3

AW: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
DiKei said:
How can i know about broken partitions ?
Because i have ~7 months left to change my phone, and i don't want to brick my phone which i love much <3
Click to expand...
Click to collapse
If your device is booting and running fine, you dont have to worry about these things at all.
Sent from my GT-I9001 using xda app-developers app

Okay, i flashed the broodROM RC5 over Odin, but i can't still boot the phone.
And i can't make a factory reset / deleting data. The phone just freezes while the process ... Any ideas? Please :/

R: [Tut][I9001] How To Repartition Brocken Partitioned I9001 devices
Imanidiot said:
Okay, i flashed the broodROM RC5 over Odin, but i can't still boot the phone.
And i can't make a factory reset / deleting data. The phone just freezes while the process ... Any ideas? Please :/
Click to expand...
Click to collapse
Flash stock ROM via odin. Then flash broodROM again. Make sure you followed the instructions in the thread.
Grammar™ is freeware; this means you can use it without paying anything. Though, Grammar™ is not open-source; this means you can't edit source code.

edisile said:
Flash stock ROM via odin. Then flash broodROM again. Make sure you followed the instructions in the thread.
Grammar™ is freeware; this means you can use it without paying anything. Though, Grammar™ is not open-source; this means you can't edit source code.
Click to expand...
Click to collapse
I know about my grammar, sorry. And yes okay, I'll try this one
Edit:
Factory reset is still not working...so how can I follow the instructions? :/

Imanidiot said:
I know about my grammar, sorry. And yes okay, I'll try this one
Edit:
Factory reset is still not working...so how can I follow the instructions? :/
Click to expand...
Click to collapse
Can you stil mount /data & /cache ??
Can you go in /data partition via twrp file manager or aroma file manager ?

Yes I can mount data and cache over the FeaMod recovery.
Well...should I flash twrp again?

Imanidiot said:
Yes I can mount data and cache over the FeaMod recovery.
Well...should I flash twrp again?
Click to expand...
Click to collapse
You can use aroma file managed too !
just check out that you can enter in /data and remove or.copy files there !

Phone is finally dead now...I got a reset.md5 to reset all partitions, but now it won't even start...I think I can trow it now out of the window

Okay a short summary please.
What are the thing you have done to try to get your phone back to life?

[RECOVERY][DREAMTAB] TWRP 3.0.0.0 for Nabi Dreamtab HD8

TWRP recovery 3.0.0 for the Nabi Dreamtab HD8. (t8400n)
​
{
"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"
}
​
At this point this recovery is still considered in testing. The normal disclaimers apply.
IMPORTANT!!!! If you have an IN08A version do not use this recovery, this will only work on NV08A
For IN08A see a tethered recovery and rooting method here: http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25
This is for Nabi Dreamtab
Nabi2 is HERE
Nabi JR 4GB is HERE
Nabi JR 16GB is HERE
NabiXD is HERE
Updates
READ THIS FIRST!!
03/22/2016 Latest TWRP 3.0.0 files http://forum.xda-developers.com/showpost.php?p=65989774&postcount=66
10/5/2015 older TWRP 2.8.7 files http://forum.xda-developers.com/showpost.php?p=63151136&postcount=46
Initial TWRP 2.7.1 Direct Link
Stock recovery for Nabi version 1.3.7
http://forum.xda-developers.com/showpost.php?p=59290754&postcount=41
For more information on TWRP and change log see the TeamWin Website
Information
You do not need root to install this, in fact you can use the recovery to root your Dreamtab HD8. Upon exiting TWRP it will ask to root the device if it is not already, I ran in to an issue where I had to download SuperSU from play store afterwards to get it properly rooted.
Installation
Video tutorial https://www.youtube.com/watch?v=V_JML4wN3QM&feature=youtu.be
Having trouble? http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Start with Nabi booted to android, ADB debugging enabled, windows adb and fastboot drivers installed. (PDAnet drivers are popular)
-Method 1 (Recommended install , guided installer)
-Download Dreamtab Auto Installer from above
-Extract DTTWRPinstaller.zip
-Run install.bat
Code:
Select option 1 for installing recovery and immediate backup of tablet
Select option 2 to just install TWRP
Select option 3 to install the original stock recovery
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 3.0.0.0 for Nabi Dreamtab"
-Extract recovery.img from zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 3.0.0.0 for Nabi Dreamtab"
-Extract recovery.img from .zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_t8400
TWRP source https://github.com/omnirom/android_bootable_recovery
Credits
Geohot for towelroot (version 1 specifically)
TeamWin and OmniROM teams for TWRP.
Dees_Troy for build tutorials.

are you playing with new goodies again ? lol
Cant wait for you to " port " this to another nabi :victory:

aicjofs said:
.
Click to expand...
Click to collapse
You are awesome! :highfive:
Now for the $10^6 question....did Fuhu pull a Nabi2 and screw up the filesystem on the Dreamtab?
Thanks
Sno

Snoshrk said:
You are awesome! :highfive:
Now for the $10^6 question....did Fuhu pull a Nabi2 and screw up the filesystem on the Dreamtab?
Thanks
Sno
Click to expand...
Click to collapse
Better. /cache is ridiculously large, and while system is big, their ROM takes most of it and this time they left a little wiggle room. Dumbest by far is recovery being only 8MB. I may not be right on my markup below because I don't have my notes handy, but it's close
C:\Users\JON\Downloads\V50020_aboot_twrp_v2>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 959256.0K 128.0K 959128.0K 4096
/sys/fs/cgroup 959256.0K 12.0K 959244.0K 4096
/mnt/asec 959256.0K 0.0K 959256.0K 4096
/mnt/asec/com.mojang.minecraftpe-1 29688.0K 28108.0K 1580.0K 4096
/mnt/obb 959256.0K 0.0K 959256.0K 4096
/system 1548144.0K 1427960.0K 120184.0K 4096 Some free space for grow or user add system apps
/cache 1548144.0K 703612.0K 844532.0K 4096 I don't see using all this space in normal system operation
/data 10234424.0K 5400448.0K 4833976.0K 4096 I think I have a whole bunch of stuff on here so ignore this
/forever 64496.0K 4172.0K 60324.0K 4096
/forever/addon 1548144.0K 1010428.0K 537716.0K 4096
/mnt/shell/emulated 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated 959256.0K 0.0K 959256.0K 4096
/mnt/media_rw/sdcard1 31154688.0K 27072640.0K 4082048.0K 32768
/storage/sdcard1 31154688.0K 27072640.0K 4082048.0K 32768
/storage/emulated/0 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/0/Android/obb 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/legacy 10234424.0K 5400448.0K 4833976.0K 4096
/storage/emulated/legacy/Android/obb 10234424.0K 5400448.0K 4833976.0K 4096
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 30177 loop0
179 0 15267840 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 1572864 mmcblk0p4 system
179 5 1572864 mmcblk0p5 cache
179 6 2048 mmcblk0p6
179 7 65536 mmcblk0p7
179 8 1572864 mmcblk0p8 addon
179 9 2048 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 10397696 mmcblk0p12 data
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
254 0 30177 dm-0
[email protected]00n:/ # ^C
These thing at $200 at Walmart a week ago, very good deal, considering they had the Nabi2 at $179 right next to it.

Hi, just got this tablet today and I'm puzzled as why the Nabi website says this is supposed to have a Tegra 4 CPU but in CPU-Z it says is an Intel Atom Z3745. Many thanks for any info.
Sent from my DMTAB-IN08A using Tapatalk

Omegadrive said:
Hi, just got this tablet today and I'm puzzled as why the Nabi website says this is supposed to have a Tegra 4 CPU but in CPU-Z it says is an Intel Atom Z3745. Many thanks for any info.
Sent from my DMTAB-IN08A using Tapatalk
Click to expand...
Click to collapse
Interesting. Initially this was to be an Intel CPU tablet(see CES articles from Feb), then it came out as Tegra4. Look at you model number. The "IN08A" versus the "NV08A". This is a first for Fuhu. So this recovery certainly won't work. Do you have fastboot?

aicjofs said:
Interesting. Initially this was to be an Intel CPU tablet(see CES articles from Feb), then it came out as Tegra4. Look at you model number. The "IN08A" versus the "NV08A". This is a first for Fuhu. So this recovery certainly won't work. Do you have fastboot?
Click to expand...
Click to collapse
Haven't attempted to root or install recovery, but it could be that they have both tablets at Costco, first one she tried to scan didn't matched the sku and she went and got another one, I will take it back today and make sure the model number starts with NV, I was actually expecting a Tegra CPU which is way better than a crappy Atom.
Sent from my DMTAB-IN08A using Tapatalk

Omegadrive said:
Haven't attempted to root or install recovery, but it could be that they have both tablets at Costco, first one she tried to scan didn't matched the sku and she went and got another one, I will take it back today and make sure the model number starts with NV, I was actually expecting a Tegra CPU which is way better than a crappy Atom.
Sent from my DMTAB-IN08A using Tapatalk
Click to expand...
Click to collapse
This recovery definitely won't work on the Intel one. I think I typo'd above, it NV08B not A

aicjofs said:
This recovery definitely won't work on the Intel one. I think I typo'd above, it NV08B not A
Click to expand...
Click to collapse
Just came back from Costco, ended up returning it, there is no info on the boxes that says the model number anywhere, so didn't risk it. Thanks anyway.
Sent from my XT910 using Tapatalk

So is there any viable method to root the Intel version? At this point I'd be happy with just knocking out the bloat so my kid can actually install apps.

pm1066 said:
So is there any viable method to root the Intel version? At this point I'd be happy with just knocking out the bloat so my kid can actually install apps.
Click to expand...
Click to collapse
You can try towelroot. Only version 1 worked on the nvidia. Likely depends on software version and if futex exploit was patched in kernel.

I'll check it out. Don't want to brick my kid's toy!

Warning !! Locked Bootloader after OTA 1.3.7 Update
Seems they might have locked the bootloader in the OTA 1.3.7
adb reboot-bootloader
fastboot boot recovery.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.003s
The OTA 1.2.9 didn't do this, and I as able to still fire over the TWRP custom recovery just fine
fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 71.105s]
finished. total time: 71.105s
Bootloader is now unlocked again but at the expense of basically a factory reset (losing all outside data and apps)
And the question I'm left with now is how do I apply any future OTA without having to dump the data again *Grin* ?
Thanks again aicjofs

Since this is the only thread I've found that even mentions the DreamTab, I'm going to hope someone can help me. Basically my DreamTab was bricked with the latest OTA. Upon restarting after the update, I get the DreamTab logo "powered by android" and then after, it goes to the generic "android" boot animation, rather than the DreamTab animation. (The word android in the old font in a greenish color that has a "shine" moving across it) I've let it sit on this screen for a while, but it never moves beyond it. I've done a factory reset through the recovery kernel, but that doesn't seem to have helped anything. I am RMAing the device, but if I can avoid the 2+ of transit and such, I would like to. Any chance I can flash the OTA through the recovery kernel and possibly fix this? If so, any chance someone actually has the OTA zip? Thanks in advance.

chikimonke said:
Since this is the only thread I've found that even mentions the DreamTab, I'm going to hope someone can help me. Basically my DreamTab was bricked with the latest OTA. Upon restarting after the update, I get the DreamTab logo "powered by android" and then after, it goes to the generic "android" boot animation, rather than the DreamTab animation. (The word android in the old font in a greenish color that has a "shine" moving across it) I've let it sit on this screen for a while, but it never moves beyond it. I've done a factory reset through the recovery kernel, but that doesn't seem to have helped anything. I am RMAing the device, but if I can avoid the 2+ of transit and such, I would like to. Any chance I can flash the OTA through the recovery kernel and possibly fix this? If so, any chance someone actually has the OTA zip? Thanks in advance.
Click to expand...
Click to collapse
Do you know if it's the Intel or Nvidia version?
I am sure I have stock backup of nvidia in my archives somewhere, but haven't uploaded it.

aicjofs said:
Do you know if it's the Intel or Nvidia version?
I am sure I have stock backup of nvidia in my archives somewhere, but haven't uploaded it.
Click to expand...
Click to collapse
How would one tell?

chikimonke said:
How would one tell?
Click to expand...
Click to collapse
I'm at work, but I think on the back in says something like NV8B, or IN8A. nv for nvidia, in for intel.

aicjofs said:
I'm at work, but I think on the back in says something like NV8B, or IN8A. nv for nvidia, in for intel.
Click to expand...
Click to collapse
nvidia it is. Is this something that can flashed through the stock recovery? Because if this doesn't work, I still want to be able to use the RMA that I have setup.

chikimonke said:
nvidia it is. Is this something that can flashed through the stock recovery? Because if this doesn't work, I still want to be able to use the RMA that I have setup.
Click to expand...
Click to collapse
No you would have to temp load TWRP to RAM(no flashing to nand), then restore. I could upload the OTA that's flashable with stock recovery, it might work if it happens to update the right files but if you have something corrupt it will fail the SHA1 checks. You were going from 1.2.9 to 1.3.7?
Let me know how you want to proceed.

aicjofs said:
No you would have to temp load TWRP to RAM(no flashing to nand), then restore. I could upload the OTA that's flashable with stock recovery, it might work if it happens to update the right files but if you have something corrupt it will fail the SHA1 checks. You were going from 1.2.9 to 1.3.7?
Let me know how you want to proceed.
Click to expand...
Click to collapse
Alright, if I understand correctly, I could try the OTA first, then if that doesn't work try with TWRP. The temporary TWRP method, does it require unlocking the bootloader? I'm not familiar with loading a recovery only in RAM. And yes, going from 1.2.9 to 1.3.7. Thanks for your help.

[GUIDE][TW4.4.2][LOCKED BL] Max performance setup

Disclaimer: don't do any of this unless you are familiar with flashing ROMs and debricking. Your device will boot to a "custom" splash screen, can be removed when flashing stock firmware
Model name: GALAXY S III
Country: USA (Verizon)
Version: Android 4.4.2
Product Code: VZW
AP / PDA: I535VRUDNE1
CSC: I535VZWDNE1
MODEM: I535OYUDNE1
Performance/Bare-bones setup
From stock 4.4.2 install
1) TowelRoot
2) BusyBox
3) Unofficial Safestrap Recovery v3.75 (BUG: connecting device to PC via USB cable causes system crash if stock ROM is not selected)
4) Download SUPERLITEROM! v1.0 to internal memory or ext. sdcard.
Reboot into safestrap recovery, Wipe partitions: Data, Cache, Dalvik Cache
5) install SUPERLITEROM! v1.0 to Stock ROM-slot
Reboot into Safestrap recovery, run script: fix permissions (Optional)
Do not install: BusyBox installers, Safestrap, gapps, towelroot (custom ROM already provides these)
When installing apps, be sure to move from SD card to internal memory for faster load speeds.
Optional
Upgrade to SuperSU 2.02 (get Pro)
Default Access: Grant
Show notifications: disabled
Logging: None
Enable su during boot: enabled
trust system user: enabled
Settings -> About Phone
Click several times on Build number to enable Developer Options
Play Store -> Settings
Auto-update apps: Do not auto-update apps
- Root App Delete (testing)
System Apps ->
Disable "Emergency Alerts"
Disable "MDMApp"
Disable "BandService"
Disable "New registration"
Disable "com.samsung.tutorial"
- Google Keyboard
Can Root App Delete "Samsung Keyboard"
**Also can hide icon from app list from advanced settings
- Xposed installer
- Wanam Xposed
- Lucky Patcher | block advertisements
- SD Maid (get Pro) | optimize databases
- Clean Master Phone Boost
**Disable: scan memory, low space notification, junk reminder, scan big files, real-time protection and everything below
Flashlight - comes as widget in SUPERLITEROM
Thanks to:
- Chainfire For SuperSU
- Stericson For BusyBox
- mohammad.afaneh For Safestrap and SUPERLITEROM!
Mirror links for important files: http://echostorms.net/android/

About your device
Downgrading to 4.3 or earlier is not possible without a JTAG
When device is powered off
- Hold Volume Up, Home then hold Power to enter recovery mode (Volume UP + Home + Power)
- Hold Volume Down, Home, then hold Power to enter download mode (Volume DOWN + Home + Power)
Device may be stubborn and can take multiple tries to enter recovery or download mode.
To exit download mode without flashing firmware can be done by removing the battery. In download mode, the device should be recognizable by the computer and be accessed using Odin or Kies.
Odin Flashing
PIT - Partition Information Table
BL / BOOTLOADER - boot loader
AP / PDA - refers to the build version of the firmware
CP / PHONE - refers to the baseband/modem version
CSC - is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
Nand erase all: full eMMC wipe including partitions, use .PIT file when doing this.
Firmware versions
I535VRUDNE1 - KitKat 4.4.2
I535VRUCML1 - Jelly Bean 4.3
I535VRBMF1 - Jelly Bean 4.1.2 (the security policies on the device are improved)
I535VRBMB1 - Jelly Bean 4.1.2
I535VRALF2 - Ice Cream Sandwich 4.0.4
Firmware flash order
HTML:
aboot.mbn
sbl2.mbn (secure bootloader)
sbl3.mbn (secure bootloader)
rpm.mbn (resource/power management)
tz.mbn (trustzone)
boot.img
recovery.img
system.img.ext4
cache.img.ext4
NON-HLOS.bin (modem/baseband)
internal eMMC partitions
HTML:
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB ext4 userdata
16 14.8GB 14.8GB 8389kB ext4 persist
17 14.8GB 15.7GB 881MB ext4 cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
SysScope and "Nand Erase All"
The "Nand Erase All" option doesn't seem to do a full emmc wipe, as the custom splash screen remained after a repartition.
some links about SysScope
- http://forum.xda-developers.com/showthread.php?t=2324619
- http://forum.xda-developers.com/showthread.php?t=2285894

Charging device using wall charger
1) Plug the wall charger (use brand name SAMSUNG charger) the correct way.
2) Use short cable and avoid USB extension cables.
3) Close all applications and clear RAM.
4) Keep device in a cool area or under a fan.
- Cheap or low budget extension cables or multi socket outlets can cause device to become hot or charge slowly.
- This info also applies if you are plugging in your device to the PC with a USB cable.
- Power saving mode and turning off WiFi and mobile data may help.
- Reducing brightness to lowest will help conserve battery power.
- Lower volume or external speakers with a power source may also help.
Things to avoid
- Updating to stock 4.3 or higher
- BusyBox Pro features will break MMS
- EZ-unlock will hard brick device
- Adblock can infinitely download and use all bandwidth
Device out of memory bug
- Run all scans provided by sd maid pro
- Reboot into safestrap recovery, then clear Dalvik cache and possibly cache.

Couple things.
This guide should be in the general section.
Also you shouldn't link lucky patcher, if you're looking for ad blocking then adaway or adblock are better options. The purpose of lucky patcher isn't to block advertisements and shouldn't really be linked here.

BadUsername said:
Couple things.
This guide should be in the general section.
Also you shouldn't link lucky patcher, if you're looking for ad blocking then adaway or adblock are better options. The purpose of lucky patcher isn't to block advertisements and shouldn't really be linked here.
Click to expand...
Click to collapse
Lol adblock..why not suggest ez unlock too
edit: adblock has bugged out and used up over 3GB in bandwidth in just minutes over 4G, I would suggest to avoid it.
I was just kidding about ez unlock, dont actually try it.

I've pretty much completed my research and updated the thread with more information.
thanks to mohammad.afaneh (SUPERLITEROM!) again for making this possible.

LG Escape 2 (H443) 5.1.1 OTA failure after unroot/reset

Hello everyone,
I figured I'd give a forum thread a shot, this phone needs some XDA love!
I have an LG Escape 2 (H443) on AT&T, its currently running 5.0.2 H44310k and is offering an OTA to 5.1.1 H44311W but when I reboot to flash the update it gives error 0x112500.
Next it will reboot and display "This device is suspected in rooting. Software update is not available for rooted device."
That message appears to be very common with LG phones, but none of the solutions mentioned for other phones have worked.
I've tried the following:
LGMobile Support Tool and LG PC Suite, neither say there is an update.
Full unroot from SuperSU and factory reset.
I didn't remove any stock APKs, most of the bloat was disabled in the Apps tab but not removed. Due to how obscure this phone is there was no chance of a custom recovery or rom to flash to it, hell, I can't even find the stock rom to use with any of the various flashing tools.
Is there any potential locations for a log file? Does anyone know what exactly LG looks for to determine if the device was rooted?

wingzeroismine said:
Hello everyone,
I figured I'd give a forum thread a shot, this phone needs some XDA love!
I have an LG Escape 2 (H443) on AT&T, its currently running 5.0.2 H44310k and is offering an OTA to 5.1.1 H44311W but when I reboot to flash the update it gives error 0x112500.
Next it will reboot and display "This device is suspected in rooting. Software update is not available for rooted device."
That message appears to be very common with LG phones, but none of the solutions mentioned for other phones have worked.
I've tried the following:
LGMobile Support Tool and LG PC Suite, neither say there is an update.
Full unroot from SuperSU and factory reset.
I didn't remove any stock APKs, most of the bloat was disabled in the Apps tab but not removed. Due to how obscure this phone is there was no chance of a custom recovery or rom to flash to it, hell, I can't even find the stock rom to use with any of the various flashing tools.
Is there any potential locations for a log file? Does anyone know what exactly LG looks for to determine if the device was rooted?
Click to expand...
Click to collapse
Your best bet, would be to flash the stock firmware if it's available. Using the unroot features of SuperSU doesn't fully remove all traces of root.

Evolution_Tech said:
Your best bet, would be to flash the stock firmware if it's available. Using the unroot features of SuperSU doesn't fully remove all traces of root.
Click to expand...
Click to collapse
Yeah thats the unfortunate thing, I haven't found it anywhere, since its such a low end obscure phone it seems like its just ignored.
With the new Moto G finally out I'll probably switch to the 2GB version of that, 1GB on this phone did NOT perform well, things like Music and Maps open would close Music within 10-15 minutes of using Maps, had to root and use RAM Manager to force better multitasking, which also made switching between apps or launching new ones slow to a crawl after a couple days.
Kinda wish I didn't burn $180 on this, and then another $220 on the Moto G but that's the price to pay for not wanting a giant phone.

wingzeroismine said:
Yeah thats the unfortunate thing, I haven't found it anywhere, since its such a low end obscure phone it seems like its just ignored.
With the new Moto G finally out I'll probably switch to the 2GB version of that, 1GB on this phone did NOT perform well, things like Music and Maps open would close Music within 10-15 minutes of using Maps, had to root and use RAM Manager to force better multitasking, which also made switching between apps or launching new ones slow to a crawl after a couple days.
Kinda wish I didn't burn $180 on this, and then another $220 on the Moto G but that's the price to pay for not wanting a giant phone.
Click to expand...
Click to collapse
did you ever find it? I also need it for a friends phone, he tried rooting it and now its stuck on the lg boot logo, if you have the firmware let me know!

No I never found it. But, when its stuck on the logo like that... keep retrying the root in fastboot mode, I've rerooted mine several times now and it getting stuck isn't a big deal, just keep retrying the shell script until it boots. You *may* have slightly better luck if you remove any SD cards.

unsoft brick h334
Does anybody have a way to undo the soft brick for the LG H443? Mine will load to the at&t screen, but it gets stuck there and won't pass it. These are the steps I followed to try and root it were called "ONE CLICK SCRIPT TO ROOT LG ESCAPE2 H443" It will still load into download mode. Is there a compatible clockwork mod? What shell script did you use to reboot it? Is there any other rom I can flash to make it work again? Thanks in advance.

When it gets stuck on the boot logo after attempting to root it, keep retrying the root until it finally boots. I've had it take anywhere from 2-3 tries, to over an hour, but it will eventually work.
While we are getting root access, we aren't unlocking the bootloader, so there won't be any TWRP or CWM support.
I'm not using any scripts to reboot it, if its stuck just pull the battery and unplug the USB cable.

soft bricked
wingzeroismine said:
When it gets stuck on the boot logo after attempting to root it, keep retrying the root until it finally boots. I've had it take anywhere from 2-3 tries, to over an hour, but it will eventually work.
While we are getting root access, we aren't unlocking the bootloader, so there won't be any TWRP or CWM support.
I'm not using any scripts to reboot it, if its stuck just pull the battery and unplug the USB cable.
Click to expand...
Click to collapse
Thank you! I shall keep trying to root it. I have tried several times so far, but it still gets stuck at the at&t logo. I saw a comment on the tutorial I used to attempt rooting my phone that says "ATT just pushed a software update as of July 9, 2015. Both of these tools will softbrick your phone now." I can still get it to load into firmware update/download mode. That's it though. Is there any way I can just restore it to the way it was before? I can't find it's original firmware for it anywheres. Any advice you have to give is appreciated. Is there a way I can up your thanks meter? Because I'd totally do that. If I could.

ChrimsonReign said:
Is there any way I can just restore it to the way it was before? I can't find it's original firmware for it anywheres. Any advice you have to give is appreciated. Is there a way I can up your thanks meter? Because I'd totally do that. If I could.
Click to expand...
Click to collapse
Well you can try to boot into factory reset mode, which I just found working directions for.
With the phone off press and hold power + volume down
When you see the LG logo release BOTH buttons for 1 second and then press and hold both of them again
It should ask if you want to factory reset.

h443
wingzeroismine said:
Well you can try to boot into factory reset mode, which I just found working directions for.
With the phone off press and hold power + volume down
When you see the LG logo release BOTH buttons for 1 second and then press and hold both of them again
It should ask if you want to factory reset.
Click to expand...
Click to collapse
I tried it, and it let me factory reset, but now instead of freezing at the AT&T symbol, it freezes at the LG logo. It will still let me factory reset and go into download mode. Never loads passed the LG logo (Splash screen maybe?) I guess that's progress of sorts? Thanks for the help!

ChrimsonReign said:
I tried it, and it let me factory reset, but now instead of freezing at the AT&T symbol, it freezes at the LG logo. It will still let me factory reset and go into download mode. Never loads passed the LG logo (Splash screen maybe?) I guess that's progress of sorts? Thanks for the help!
Click to expand...
Click to collapse
Maybe, you could try flashing the firmware for LG H440n, which is available. But now that I think again, it may not let you proceed with the installation, because it may consider the two devices different.
Anyway, this could be a temporary solution until the h443 firmware is released..

polfrank said:
Maybe, you could try flashing the firmware for LG H440n, which is available. But now that I think again, it may not let you proceed with the installation, because it may consider the two devices different.
Anyway, this could be a temporary solution until the h443 firmware is released..
Click to expand...
Click to collapse
Thanks! I'll try it out. If I were to buy another H443, would it be possible to copy the firmware off of it, or somehow mirror it exactly onto the broken one?

ChrimsonReign said:
Thanks! I'll try it out. If I were to buy another H443, would it be possible to copy the firmware off of it, or somehow mirror it exactly onto the broken one?
Click to expand...
Click to collapse
I would like to know this as well. I would like to do so before I attempt any root method.

H443
UPDATE: I tried flashing the H440n firmware, it didn't work, quite the opposite in fact. My phone is now hard bricked, and doesn't respond to the attempt to power it on, or to being plugged in to charge. When I plug it in to my computer, instead of the normal noise it makes to indicate that a device is connected, it makes three lower beeps I've never heard it make before. So don't try that, it doesn't work. If anyone does know a way to fix it (although I find that highly unlikely) feel free to let me know. If anyone knows a way to copy firmware from a working phone to use on a different phone, I'd also like to know about that, too.

Since you can't get it to boot into any mode I can't think of any way to recover it....
I also don't know of any way to capture / restore the rom as there is no TWRP or CWM or bootloader unlock that I'm aware of for this phone. And to make matters worse, none of the LG restore tools seem to be usable on this phone either....

ChrimsonReign said:
UPDATE: I tried flashing the H440n firmware, it didn't work, quite the opposite in fact. My phone is now hard bricked, and doesn't respond to the attempt to power it on, or to being plugged in to charge. When I plug it in to my computer, instead of the normal noise it makes to indicate that a device is connected, it makes three lower beeps I've never heard it make before. So don't try that, it doesn't work. If anyone does know a way to fix it (although I find that highly unlikely) feel free to let me know. If anyone knows a way to copy firmware from a working phone to use on a different phone, I'd also like to know about that, too.
Click to expand...
Click to collapse
Whaaat? If it was to behave like this, did LG Flash tool let you install it with no problems at all?
Damn, why won't they just release the h443 software....
All I know is you can backup and restore boot.img and recovery.img from within the rom with flashify. but only within the rom :/

The_Merovingian said:
Your best bet, would be to flash the stock firmware if it's available. Using the unroot features of SuperSU doesn't fully remove all traces of root.
Click to expand...
Click to collapse
thank

Hello again. Could somebody use this guide to make a dump of a H443 working system partition and upload it? This would be lifesaving for those stuck on bootloop after trying to root.
http://forum.xda-developers.com/showthread.php?t=2450045

Interesting, I'll have to read through that guide. My phone isn't completely clean though so I'll need some time to clean it up, reset it, reroot it, then try the capturing. I'll try to give this a shot over the next couple of days and see what happens.
Updates:
I don't know if this partition information will be of any use to anyone at all.. but since the guide had me gather it might as well share it:
cat /proc/partitions
Code:
major minor #blocks name
253 0 452080 zram0
179 0 7634944 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 512 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 24576 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 8192 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 8192 mmcblk0p31
259 0 24576 mmcblk0p32
259 1 65536 mmcblk0p33
259 2 4096 mmcblk0p34
259 3 2967552 mmcblk0p35
259 4 1253376 mmcblk0p36
259 5 3098624 mmcblk0p37
259 6 13807 mmcblk0p38
179 32 512 mmcblk0rpmb
parted /dev/block/mmcblk0
Code:
Model: MMC QN1SMB (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 524kB 1049kB 524kB sbl1
2 1049kB 1573kB 524kB tz
3 1573kB 2097kB 524kB hyp
4 2097kB 2621kB 524kB rpm
5 2621kB 4719kB 2097kB aboot
6 4719kB 6291kB 1573kB pad
7 6291kB 6816kB 524kB sbl1bak
8 6816kB 7340kB 524kB tzbak
9 7340kB 7864kB 524kB hypbak
10 7864kB 8389kB 524kB rpmbak
11 8389kB 10.5MB 2097kB abootbak
12 10.5MB 27.3MB 16.8MB misc
13 27.3MB 44.0MB 16.8MB ext4 persist
14 44.0MB 44.6MB 524kB metadata
15 44.6MB 46.1MB 1573kB modemst1
16 46.1MB 47.7MB 1573kB modemst2
17 47.7MB 72.9MB 25.2MB laf
18 72.9MB 98.0MB 25.2MB boot
19 98.0MB 123MB 25.2MB recovery
20 123MB 125MB 1573kB fsg
21 125MB 125MB 524kB fsc
22 125MB 126MB 524kB ssd
23 126MB 126MB 524kB DDR
24 126MB 127MB 524kB sec
25 127MB 127MB 524kB encrypt
26 127MB 128MB 524kB eksst
27 128MB 128MB 524kB rct
28 128MB 137MB 8389kB ext4 sns
29 137MB 170MB 33.6MB factory
30 170MB 204MB 33.6MB fota
31 204MB 212MB 8389kB ext4 drm
32 212MB 238MB 25.2MB ext4 mpt
33 238MB 305MB 67.1MB fat16 modem
34 305MB 309MB 4194kB persistent
35 309MB 3348MB 3039MB ext4 system
36 3348MB 4631MB 1283MB ext4 cache
37 4631MB 7804MB 3173MB ext4 userdata
38 7804MB 7818MB 14.1MB grow
According to those, block 35 is the system partition, 18 is boot, and 19 is recovery, so I'm dumping those (dunno if they will all be of value to anyone, they are only 24MB). Are there any other partitions that I should grab?
The goods:
System.img, boot.bin, recovery.bin

Do those images work? Has anyone tried them in their own devices yet? I downloaded them, but I'm shy about flashing them sight-unseen. I may or may not have softbricked an Escape2 already trying to root it. I had to mail it off and wait for a replacement...
My new phone is actually the old software version. It's an H44310K. My old one came as an H44311W, I think. That was the one that died tragically. As far as I can tell, I lucked out and got the previous version that was rootable.
For anyone who has successfully rooted their LG Escape2, what did you use to do it? I've seen the "One Click Script to Root LG Escape2 H443" tutorial, and I've also seen the Kingo rooter something-or-other.
EDIT: I've got the AT&T version of the phone, if that matters. (Are they the only carrier for it?)
EDIT2: Also, wingzeroismine, even if those don't work, thank you. You are awesome for starting a thread asking for help, and then ending up being the one sharing the most valuable info and software. Thank you.

Request: Source (and possibly Recovery) for HTC Desire 709d (cp5dwg ChinaTelecom variant)?

My goal in this post is simple: I would like to ask anyone if they have a copy of the source code for the China Telecom variant for HTC Desire 709d (cp5dwg), or if they could contact HTC effectively, directly for this source. The only source available for this device on HTCdev is for a variant in India and would never boot on my device(tested over and over and over again). If anyone could possibly offer a copy of a custom recovery I'd be also appreciated. Note that this model uses a Spreadtrum SoC instead of a Qualcomm one.
If someone is to contact HTC for this here is some possibly relevant information for accurate search:
KERNEL VERSION: 3.4.5-gec07fd6
OTHER KERNEL INFO: SMP PREEMPT
ROM VERSION: 1.80.1401.11
Thanks.

can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?

notnoelchannel said:
can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?
Click to expand...
Click to collapse
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.

MightyPandora8 said:
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.
Click to expand...
Click to collapse
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments

you ported twrp for my device in 20 minutes???

you ported twrp for my device in 20 minutes???
oh my goodness

notnoelchannel said:
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments
Click to expand...
Click to collapse
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
i had to pull the battery to stop it from continuing to reboot

MightyPandora8 said:
you ported twrp for my device in 20 minutes???
Click to expand...
Click to collapse
yeah but it has a chance that it will not boot:
MightyPandora8 said:
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
Click to expand...
Click to collapse
i can try to port CWM recovery from an other device, maybe it'll boot

I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>

notnoelchannel said:
I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>
Click to expand...
Click to collapse
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?

MightyPandora8 said:
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?
Click to expand...
Click to collapse
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.

notnoelchannel said:
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.
Click to expand...
Click to collapse
the big problem here is the email address. I can't find anywhere with a proper email address that you send an email to it youre sending directly to the HQ and would be taken directly to relevant departments like [email protected]. all i find is some indirect tech support forms thats not going to help at all. no htc global contact/site at all either.
i doubt that the source is gone forever - for i have a samsung, which is also a CT variant from 8-9 years ago and samsung is still able to put it up on their site. htc, as the number one in android back in those good old days, shouldn't be unable to do so like samsung did. but if it's htc's policy in obsoletion then... well.