[Q] Unlocked bootloader for E617G? - Optimus L3, L5, L7 Q&A, Help & Troubleshooting

Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).

Skellums said:
Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).
Click to expand...
Click to collapse
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!

KingDaedrix said:
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!
Click to expand...
Click to collapse
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
All credit to the original devs of the unlock, fix is the same, just different source files were used.

Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.

KingDaedrix said:
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.
Click to expand...
Click to collapse
Unfortunately no. Windows Phone 7 is not open source so there is no easy/legal way to port the OS over. There are launchers that have been made so the Android interface mimics Windows Phone 7, but it's still Android running under the hood.

Help!
Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
I have followed the instruction you posted but i still cant boot into recovery. I have used adb command reboot bootloader and it gets stuck on a black and white screen tht says fastboot processing.
I am not sure if there something wrong with my device.

Thanks!
Me again, just replying to confirm that following the steps posted I successfully unlocked the bootloader of the phone. Not very much use however as there is very few ROMs for the model. Thanks a lot though OP!

I also successfully unlocked the bootloader using your binary. Thank you!
I wrote an article here on getting it all running with CM10.1 on the L5 E617G!

Related

Extracting Seperate Files from a .img?

Ok, I'm sorry if this has been asked already (or is too obvious to have been asked), but I'm having problems with my phone after rooting it and I'd like to get it fixed if possible.
Basically, I rooted my phone and flashed Cyanogen. Everything works perfectly by the accelerometer and compass, which are both completely kaput it seems.
I've tried the method in Cyanogen's FAQ (the one involving restore and deleting two files), but one of the two sets of files that he asks to delete doesn't exist.
I've already tried performing multiple wipes and reinstalls of different roms (Including Cyanogen, JF's, even the original T-mobile mytouch rom) to no avail. I even flashed back to JF's 1.5 since some people said their problems started with the 1.51 update.
Now I'm back on Cyanogen since it's my favorite so far and it seems that the problem follows me no matter what.
Now it seems that my only choice as determined by this thread is to port in some files from JF's 1.42 and delete the Cyanogen version. I have no idea if this will work since these guys are obviously on G1's and I'm using a mytouch, but I figure it shouldn't hurt too much as long as I can still get to the recovery console if something goes crazy.
This is the method given:
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
Click to expand...
Click to collapse
And I understand every single bit of it but the part where he copies the jf1.43 akmd to bin because I can't seem to get my hands on that single file.
Here's the actual question in case you want to skip all of that crap.
How do I extract the particular file that i need (akmd from JF's 1.42) from the .img file that I downloaded. Is there a particular method, or am I just downloading the incorrect package?
Furthermore, if you have any other possible solutions to my problem, I'd be glad to hear them. I'm pretty much shooting in the dark here since the first time I even looked into the system was yesterday when it was rooted.
Ok I found the perl script that I needed and ran it to extract the image. Now I'm looking for the file.
Oh my god. I'm an idiot. Opened the file in Linux and everything showed up. I think I might've had hidden files not showing.
Sorry for the stupid question, hah.
Edit: No luck. Am I really the only one who got a broken accelerometer from rooting?
Edit2: For someone who usually picks up on stuff like this quickly, I'm an idiot. For some reason every problem crossed my mind but the fact that I was using a rom that was not specifically made for the MyTouch. I flashed with the modded Cyanogen rom and the accelerometer works again.
You can delete this thread if you'd like mods.

[Q] Possible Hboot Hack ????

Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Keep up the experiments!
Thanks!
keep up doing it, you are great
thousands of people hope this work in the future...
i think unrevoked is not doing anything now
we r 4 months from 2.2....
Any more luck? How is this getting on?
dannyjmcguinness said:
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Click to expand...
Click to collapse
I tried this a week ago and it does not seems to work :S
cid version is on "ro.cid" prop. Change cid on mtd0, flash it and then try a "getprop ro.cid"
Of course, you'll get the original CID, not the supercid. You cannot change these properties (ro.secure is another one. The ONE that prevent us from writing on system, etc)
I think these properties are Read-Only and are loaded into the system from the hboot at boot time.
I managed to change the default.prop on "/" from ro.secure=1 to ro.secure=0 but every time you reboot your phone this file goes back to ro.secure=1, so I think hboot re-load every file and prop needed for their security lock at boot.
I repeat, even with root access you won't change a single property with "ro." before.
Not a single one.
Sorry guys, we'll have to wait more...
For more information abot the proccess read my post: http://forum.xda-developers.com/showthread.php?t=1042077
As you can see, no one has answered yet so I think this is useless...
Looks promising!
Sent from my HTC Wildfire using XDA App
Think I've discovered a bit more, I'm absolutly posotive that this is the way forward. Problem is not enough people seem interested in this post.
It would appear that this can be used to issue a boot message, so please share your knowledge on what you know of boot messages, coz I'm pretty sure a boot message could be used to override certain parameters.
Please people, if you read this, HELP ME OUT
I know what are you talking about,and I think that might help you
http://runtimeworld.com/2011/04/a-complete-list-of-hboot-commands/
I could work with you on this, PM me if you are interested
edit: this command has 8 letters (like cidnum):
writemid // write model ID
The best thing u've found.. I'm feeling like we'll oly root wildfire before unrevoked.,
It'll be good if we do it our self as unrevoked has tried hard but not succeeded due to heavy lock of hboot.. If there is a luck and ability to do it, we can do it..
I dont hav knowledge in linux and android much elz i would hav joined to root wildfire with u all..
Best of luck for rooting and make sure not to brick the phone..
God, I must follow this post.
Thanks for your hard work.
Sent from my HTC Wildfire using XDA App
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
ejnreon said:
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
Click to expand...
Click to collapse
cant be THAT new if you joined in 2009 :L

Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)

Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)
Hi!
When removing Bloatware with Titanium Backup a while ago, I accidentally missed a click (never used a touch screen...) and uninstalled MediaProvider, which I have not been able to recover since.
I tried putting the files back from a friend's HTC, which didn't work; after that I was told even the packages differ between manufacturers, so I tried getting them from a stock Bell Atrix .zip posted on these very forums, which didn't help either. Neither #android-root nor AndroidForums were able to help, thus I ask here: Can anyone tell me how to either make my system accept Bell's files, or where I can find a "vanilla" Motorola build?
(Problem is, the phone didn't come from a phone company, a friend of mine got it pre-release from his uncle who is with Motorola, so it may even be different from what hit the market later on...)
I guess the following information will help, it's a Titanium Backup info file for another componend I backupped shortly after:
#Titanium Backup
#Sat Feb 25 03:28:43 MEZ 2012
app_gui_icon=[...]
sys_ro.build.date.utc=1302536066
app_version_code=8
sys_ro.product.model=MB860
has_prefsdata_jpu=0
sys_ro.serialno=<xxx>
sys_ro.build.description=olympus-user 2.2.2 OLYEM_U4_0.44.0 578673 ota-rel-keys,release-keys
has_prefsdata=0
app_gui_label=com.android.providers.applications 2.2.2
sys_ro.build.version.release=2.2.2
app_apk_md5=1989ff2476ee73ad445760b9bef5f44e
has_dbdata=0
app_apk_codec=GZIP
app_is_forward_locked=0
app_is_system=1
app_label=com.android.providers.applications
app_version_name=2.2.2
generation=1
app_apk_location=internal
(Most of this is unnecessary, I guess, but I can't really be sure what you might need to judge what I would have to to...)
I would be very grateful for any help, it is extremely limiting not to be able to use any media capabilities.
So, thanks in advance,
David
maybe flash a new rom if your contacts are all backed up?
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Intelensprotient said:
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Click to expand...
Click to collapse
Yes, but you have to set the permissions same the other files in .system/app folder.
I have attached the missing files to this post. My gingerbread version is 2.3.4.
Good Luck!
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Intelensprotient said:
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Click to expand...
Click to collapse
I would hard reset too at this stage. I'm sorry it didn't work out.
Now, that's interesting. Factory reset didn't change anything.
Sorry for reply to self, but I was less than clear, so - help?
My next step would be to try to unlock the bootloader, then flash CWM and see if anything can be fixed that way; then, I would try flashing CM7 (or, more specifically, the Neutrino GT ROM) by CWM; then, I would try flashing it without. Is that a safe progression of attempts? Or have I possibly broken anything that would hard-brick it by any of these methods? And can you recommend any finer increments what I could do before / between / after those mentioned? I still have the option to apply an update in Recovery - is it possible, for instance, to put a .zip onto my SD that has 0 Byte MediaProvider files in it?
(I have thought about installing Neutrino for a while, and this seems to be a good time to flash it, as my data is cleared now anyways. To my understanding, this should not be any more dangerous than just re-flashing the Froyo that was there before, right?)
As an additional fact, ADB now doesn't detect any devices any more, even with Early USB. This could be because USB Debug is not a factory standard setting, though, as I reset it to factory defaults.
Also, the startup Moto screen behaves differently: It doesn't go to the point where the logo disappears in a flash, the background light switches off before that. As far as I can tell, the display still shows the animation, though, but it is not lit. Furthermore, the reboot seems to happen immediately after the animation has ended, and not 1-2 minutes later, like it was before the reset.
I would be grateful if anyone could explain what happened. To my understanding, a factory reset should clear /system, and the error started when I put some non-compatible .apks there, so I thought this would fix things. Is it possible something broke on the hardware side, when (for instance) 2.2.2 called a function that has had its parameters changes in 2.3.4?
[If a moderator reads this - does this qualify as a general Android question? I have no experience with different devices, so I'd be glad if you could decide if this thread has to stay here or if it can go to a sub-forum with a wider audience - General Android Q&A, for instance.]
Bump...
Success Neutrino up and running!

SUCCES! Adding content to HTC 8S stock Rom

Hey guys, I don't know if this is of any use for you, but I think it won't hurt to share it.
Based on some posts and ideas I read in different threads, I managed to write to the EFIESP and the PLATpartition of the stock rom of my HTC 8S. I changed the bootimages in the PLAT partition to a custom one,flashed the image and it worked. I'll attach a picture to prove it and if that's not enough, I will post a video.
So, the first step is to download the stock rom (obviously...) and extract the .exe file. (I use 7-ZIP) Then there is a file called "RUU_signed.nbh". If you open it with a Hex Viewer, like HxD, you can find multiple partition Headers. I found 4 that I can use, the rest is encrypted with what appears to be Bitlocker, hence the different headers. Now, what I did was mark the area of the first partition (starts approximately at offset 228BEF90 and is a FAT16 Partition) and continued the selection until the end of the file. Then I created a new one and pasted it. I ddid the same with the rest, always selecting and copying from where the partition starts until the end of the whole file and pasted it into a new one. Then I mounted the files using OSFMount and voilà, you can put stuff and files in there! If you finished, you just unmount the files. Then I opened each file again with HxD, selected EVERYTHING and pasted it
to the according area in the original RUU_signed.nbh. I started with the first one, then the second and so on, so you don't overwrite the changes you have made if you start in reverse order. After packing the file, I tried to flash it and to my surprise, IT WORKED! After rebooting I saw my custom bootimage! Downside of this is obviously that it requires you to use the stock firmware and it will be overwritten once you update your device. But I hope our skilled Devs here have some use for those 2 partitions. Theres 2 more that are usable, but I don't know their names, but you can still put files in them.
Now again, I don't know if this is of any use for you devs, but I still felt kind of obligated to share it
Stupid thing, I put my HTC 8S into Diag Mode and THEN flashed it, now it doesn't connect as MTP but as HTC Diagnostic Interface and I can't change it back because I can't deploy anything to the device. It works perfectly, boots and everything, but no USB Connection via MTP. So be very careful before flashing, since the mode is determined by a NV value which you can't edit afterwards.
This is not a tutorial to be followed by everyday users, but something ment for developers. You do everything at your own risk! And keep in mind that this has only been tested on an HTC 8S!
cheers, hutchinsane_
Yeah, I heard that it is possible, though I hadn't had a chance to test it on my 8X.
As for EFIESP: you can edit \efi\Microsoft\Boot\BCD to enable Kernel Debugger functionality and it is basically enough to hack the whole OS even with actions currently performed.
The most interesting partitions are MainOS (second to last), and Data (last one). Interop Unlock can be done in MainOS.
Thing is that newest ROMs are encrypted (not hard to crack but still)
Darn, hoped I was the first to come up with the idea. I do have acces to the file you're talking about. MainOS seems to be encrypted with Bitlocker since their headers start with -FVE-FS-. I could take a look into the 8X Rom aswell, I expect the situation to be the same. So is there a thread on the Kernel Debugger thing?
EDIT: I just did what you set, although I used a program called "Visual BCD Editor" since I don't know about editing the BCD Store just YET. Now I edited some values from "False" to "True" and for 1 second it showed me what appeared to be a windows boot selection. Now when I boot up, and once the "Windows Phone" blueish logo appears, it shows "Not for resale", meaning that we actually can edit BCD on this device!
Very nice Work
I run in Nokia Lumia 920 RM-821 APAC Malaysia Amber ROM
I find the same
Maybe we can edit Lumia 920 FFU and get first Custom ROM
that's enough to enable WinDbg operopability.
Code:
bcdedit /store F:\EFIESP\efi\Microsoft\Boot\BCD /dbgsettings usb targetname:woatarget
bcdedit /store F:\EFIESP\efi\Microsoft\Boot\BCD -set {default} debug on
bcdedit /store F:\EFIESP\efi\Microsoft\Boot\BCD -set {default} dbgtransport kdusb.dll
Sorry for my Question but how can we find that here is the end of a file in HxD .
I'm now looking for it to flash a Custom Rom on my Lumia 920 but I can't build images correctly using HxD and OSFMount.
Thanks .
@ngame Thanks If you look at your first 2 screenshots, you didn't select the "ë" You MUST select and copy it aswell, it's always the start of a partition, fot FAT aswell as for NTFS. After that, you should be able to mount. For finding the end, I didn't. I just Selected until the end of the file and pasted it back in. It should work, Afterall, my HTC has a "custom" rom aswell now, since there's a custom bootimage
@ultrashot Thanks! I used the commands and it worked succesfully. Waiting on the phone to flash now
EDIT: It doesn't boot once you set a) the target b) the type or something else. but enabling the kernel debugger itself works. Trying to figure out which value makes it unbootable.
ngame said:
Sorry for my Question but how can we find that here is the end of a file in HxD .
I'm now looking for it to flash a Custom Rom on my Lumia 920 but I can't build images correctly using HxD and OSFMount.
Thanks .
Click to expand...
Click to collapse
u must ask me dude .
zimone die
amir323b said:
u must ask me dude .
zimone die
Click to expand...
Click to collapse
PM Me please if you know
Thanks
hutchinsane_ said:
@ngame Thanks If you look at your first 2 screenshots, you didn't select the "ë" You MUST select and copy it aswell, it's always the start of a partition, fot FAT aswell as for NTFS. After that, you should be able to mount. For finding the end, I didn't. I just Selected until the end of the file and pasted it back in. It should work, Afterall, my HTC has a "custom" rom aswell now, since there's a custom bootimage
Click to expand...
Click to collapse
I will test again
Sorry in advance if this is a stupid question ...
Here is a list of partitions from my 928 .ffu but which ones are needed to edit? Just the FAT and NTFS partitions? Are any of the others of any interest?
As far as I know, you have to look for the specific headers, since some are encrypted with Bitlocker, therefor have the "-FVE-FS-" header. Easiest way is to use the search function of HxD and search for NTFS, FAT12 and FAT16 partitions Also, there are no stupid questons
hutchinsane_ said:
As far as I know, you have to look for the specific headers, since some are encrypted with Bitlocker, therefor have the "-FVE-FS-" header. Easiest way is to use the search function of HxD and search for NTFS, FAT12 and FAT16 partitions Also, there are no stupid questons
Click to expand...
Click to collapse
:highfive: Here's a better list including the device layout and read and write partitions if it helps anyone. Also when mounting FAT16 or FAT12 partitions it says it needs to be formatted or is unsupported. What am I doing wrong???
Can you ost a screenshot of the file you use as a partition? I don't know if it even works with Nokia Roms. Which one are you using exactly? I might be able to have a look at it.
feherneoh said:
Don't try it on Lumias, as your phone will stuck in Quallcomm HS-USB QDLoader mode, like my L520 did
Click to expand...
Click to collapse
You tried this way ?
now you can't flash your Phone using Care Suite ?
did you try Reffbox or ATF to repair your Boot Loader and flash your phone again ?
Hey, Lumia owners, get out of here!
By the way, Huawei W1 has same access to partitions. You can join forces and develop one hack for both phones.
-W_O_L_F- said:
Hey, Lumia owners, get out of here!
By the way, Huawei W1 has same access to partitions. You can join forces and develop one hack for both phones.
Click to expand...
Click to collapse
I think @reker can help us . he created a W1 Custom Rom
ngame said:
I think @reker can help us . he created a W1 Custom Rom
Click to expand...
Click to collapse
Not rom any more, I'm making tool can directly operate NTFS, so I can modify everything without losing any data. A hard work XD
reker said:
Not rom any more, I'm making tool can directly operate NTFS, so I can modify everything without losing any data. A hard work XD
Click to expand...
Click to collapse
Can't you publish it ? or Private send it to me ?
This tool can modify every NTFS Partition ?
@-W_O_L_F- They do? Didn't know that, thanks for the info! Yeah, might be a good idea, actually.
@reker how do you plan on doing this? adding the tool to the rom or deploying it as a xap? I actually need a way to use hidden pages without the toast launcher, or to include the toast launcher into the rom since I can't deploy it anymore
ngame said:
Can't you publish it ? or Private send it to me ?
This tool can modify every NTFS Partition ?
Click to expand...
Click to collapse
Proto-type now, NTFS is a biiiiiig thing. I will release it when finish.

[Q] Samsung Galaxy Tab 4 8.0 AT&T SM-T337A Root but NO Recovery

Hi Devs,
I've just joined and am uncertain of the proper place for this thread. Apologies if inaccurately posted.
I have the T337A, which I have rooted on ANF4, but I cannot find a recovery. I have read and read but am not finding the solution to my little project. I would like to get a safestrap on this locked bootloader so that I can install and learn to write custom ROMs. I have tried a safestrap but it was not for this specific device and did not work. I have also installed and purchased CWM Recovery and TWRP Recovery, in my learning process. The problem with the recovery is that there is no custom recovery written for this device and the bootloader is locked, as this is the AT&T WiFi/LTE version. So it looks to me like I need to figure out the partitioning image somehow in order to make a safestrap work on this device...as step 1. Is there anything else that I can do with this locked bootloader? I would love to have some help in writing a custom recovery and ROM for this device but I am a tiny tiny noob here and not a hard core programmer. If I could get some feedback on places to start for such a daunting task, it would be great. I guess one thing that I do not understand is why I cannot make my current rooted ROM the default recovery in TWRP. It asks me to choose from the list of supported devices. I understand that it goes: NAND --> aboot.img/bootloader --> recovery/or/kernel --> OS/or/ROM? If this is close to accurate then I would have to write something to the NAND?, which I'm not sure what is yet, in order to hijack the factory bootloader and then write the partitions on the sdCard for the ROM, like the safestrap folks wrote? It looks to me like they also included a version of TWRP touch which I used on the S4 yesterday and was really cool, so I guess that would be needed as well and is also why TWRP does not work for me now...it cannot hijack the locked bootloader. How do I hijack this hard headed thing? fastboot does not work to this device. In the process of this project, I have also run into a roadblock trying to update the /system/framework/framework-res.apk, in the manner that a flash needs to be done, I think. I want to change the /res/values/bools/bools.xml switch "voice_capeable" to true. AT&T or Samsung disable this on this version of the tablet, I guess to sell tethering or something else I'm not familiar with...but the way it looks to me, everything is configured on the device and I have a phone number provisioned for data at least. Why can't I turn on this switch and use the phone portion of the device? Any time I tickle the running framework-res.apk, it kills the OS. I tried compiling an update.zip aligned and signed with test keys or something like that but when I flash it, it fails with wrong footer and invalid signature...then it wipes me back to the stone ages. I warned I was a noob..! ...but not scared to brick some shtuff in order to learn this and write some custom solutions. An after thought...is there a solution for a bootable extSdCard for Android? This might lead to some options if it is possible.
Gathering phone info...
Collecting information. Be patient! Do NOT disconnect the phone!
Model: SM-T337A
Android Version: 4.4.2
Sales Code: ATT
PDA Version: T337AUCU1ANF4
Phone Version: T337AUCU1ANF4
CSC Version: T337AATT1ANF4
Product Code: SM-T337AZWAATT
HIDSw Version: T337AUCU1ANF4/T337AATT1ANF4/T337AUCU1ANF4/T337AUCU1ANF4
Board Platform: MSM8226
Serial Number: R32FA00PMRF
Imei: 3534.............
Unique Number: C1604.......
Connections: AT,MTP,MTP
Battery Status: 4.28V (94%)
Network Type: GSM
SuperSU Pro v2.40
TWRP donate latest
CWM donate v5.5.3.7
BusyBox Stericson donate v1.23.0
Titanium Backup Pro latest
xPosed v2.7.1
Wanam xPosed v3.3.1
NinjaMorph Pro v2.8.2
ROM Toolbox Pro v6.0.6.5
RootLogger Pro v1.9
Nandroid Backup v4.4.5
Next Launcher 3D Shell v3.20
Root Firewall Pro v2.1
SetCPU v3.1.2
w/respect. PitPin
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
pre4speed said:
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
Click to expand...
Click to collapse
Thanks pre4speed. I am taking a look at the two tasks again tonight and decided to take the res/bool = voice_capable issue on first since this will determine how brickable this device can be for me. If I can use it as a regular modem phone then I might be a bit more careful with the bootloader project I did some more tinkering with the framework-res.apk ...specifically the /res/values/bools/bools.xml resource and tried the following:
-------
Factory wipe
Flashed sammobile.com T337AATT1ANF4 firmware
Rooted
SuperSU
Busybox
Froze AT&T update service and others involved
Titanium backup and pulled a good backup
Online Nandroid and pulled a good backup
Installed my XDA app. of course..!
-------
Framework-res.apk:
Used total commander to copy the running apk off to the sdCard and then my PC.
Decompilled in APKStudio2.0.3b-Windows (I am also using Ubuntu 14.04 if there is a better way here..also Android Studio on both OS...just learning).
Edited my value.
Recompiled with zip align/sign option.
***Now here in lies the problem, if I haven't already created one above ***
The random article I dug up said that in order to get past the wrong footer and signature issue, and stone-age wipe, when attempting this via abd sideload with an update.zip, is to now copy the edited file back into the original APK using 7zip in order to retain the original signing keys. When I open the original APK archive, it does not show the resource folders deemed "important and I should not jack with them" in the compiled APK (mainly values/* folder). The article mentioned the resource folders such as res/values/bools are compiled and hidden and that I needed to copy over the new resources.arsc file. I see this in the newly compiled APK I made but it also put the Manifest.xml and /res folder in there. Do I need to copy all of that or just the compiled resources.arsc file? I did all and it boot looped me so I'm guessing that I either did something wrong or this was not the right answer. The last part was to chmod the new APK, use total commander to mount the folder as rw, copy over the file, and reboot. All of that worked and I had to reboot many many times...loop.
That is where I am on the modem part and am going to attempt copying just the resources.arsc in a few. I will post more on the bootloader side soon, as I've been researching what goes on from the time I push the power button until the time I swipe the first screen. Lots of reading
w/respect - PitPin
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
PitPin said:
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
Click to expand...
Click to collapse
Stalled out temporarily on the tab project as laptop hard drive bought the farm. Back in action and made some progress on the tab voice_capable issue. Everything appears to be there and in working order but the SMS modules. I think this has something to do with why the contacts app is blowing up but not sure yet. GoSMS and EXDialer seem to work together without blowing up but the dialer taps the modem and then dies. Taking a break from this to start a thread on rooting the AT&T Alpha. I'm about half way through the exploit on that project. Any input on what might be my SMS problem on the tab 4 would be appreciated. Attached are a few screens.
Does anyone know how to removed the caution sign on the left corner it keep telling me unauthorized action have been detected.
I am in the same boat, I so wish this would come through because I do love this little tab.
same boat
/baker said:
I am in the same boat, I so wish this would come through because I do love this little tab.
Click to expand...
Click to collapse
so did you finally get it going or what?I have been wanting to get my Tab going as well. I've Rooted it and paid for an unlock even, which worked fantastic by the way...Thanx XDA!!! The rooting guide I got from here was right on point,no problem at all!!But anyways, I have it on metro pcs now on the unlimited $60 plan which is awesome (.REAL unlimited internet with NO THROTTLING ) for me because now at home I run pda.net, which gives me very good, fulltime, internet for my home computers as well as the ability to stream everything onto a large screen or even via windows when we want to watch with all the bells and whistles! No lag at all usually,and I don't use my hotspot because of the usb internet connect on pda.net. When I do use the wireless connect, it doesn't take any of the allotted hotspot usage up either!!All in all it's a great deal for me. I just got a new sim for it, called in the imei to metro ,which in turn gave me a phone number and data account, and presto!Been on the net ever since! Now that I've had it for over a month ,I wanna get the voice capability to work as well, being that I am paying for 2 lines now. Although I can use the old trusty hangouts dialer with the GoogleVoice easily enough. I want to be able to use my metro number mainly because these phone companies charge and charge and charge, never caring about us,or our need to have communication at our disposal at all times.Cell phones are by far not inexpensive and the internet wasn't started for us to pay aan arm and a leg to use.Anytime I come out good while dealing with a wireless company. it's a stupendous event,I'm telling you!! Heck ,I'm writing from my home computer now, going through the Tab at this very moment! Nevertheless, I'm wanting for the devs, to come through as well. With maybe even a new rom,sans the at&t stuff, of course, since I do now have a different carrier? Heck, the Tab is even great for when we travel! 24/7 unlimited internet /streaming , and the screen size is much better than the phone screen ever was!I just really wanted to thank XDA for the work they put in to help us part - timers out,Ive been rooting and unlocking and bricking and un-bricking for quite some time now,I even repair phones now actually,but the programming and the putting it all out here for guys like me to have fun and tinker with these phones would be entirely impossible without the DEV'S and their hard work for SURE...Thanx Guys!!You ROCK!

Categories

Resources