Related
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
Sounds little bit like Chinese for me but hope you can get a break through and goodluck for all who trying to make it for us an even great phone
ok, i have had my jellybean semi running and oneX rom running, both not very functional, as most hardware did not work well.
the lgdrmserver kept crashing on me as well, but probably less important.
the solution i made was the early boot used the original libraries from /lib from and vendor/lib , so i simply mapped the 2 files in /lib with a symlink to the /system/drm folder and ran the wallpaper binary and it worked fine.
secondly changed a vold binary to be a little script, that
1: bind'd new libraries for drm in drm2 folder (mount -obind drm2 drm) so the new booting os would get related files.
2: start vold
and the workaround seemed to do just fine for the drm security check.
IF it fails during regular boot if you unintentionally copied over the files, do not worry. booting into safe mode (keep VOL UP pressed and press power) you can connect with a shell and bypass the check, and fix your failure and reboot.
Hi
Is DRM checking forced from kernel?
Can we live without it?
no, its called from init.d
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
It is allways exciting to see people like you fellow.
Curious, courageous, openminded, wise and most of all doing all without expecting anything.
Success on your way..:good:
Dexter_nlb, You're a hero :good:
When will be released some beta?
since we have root, shouldnt init.d be accessable and easily modifyable?
The Troll said:
since we have root, shouldnt init.d be accessable and easily modifyable?
Click to expand...
Click to collapse
its part of the boot.img (ramdisk), so not really, but the 2nd-init makes it possible to make a new ramdisk and start it. but its only ramdisk, not the kernel, which remains static.
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
The Troll said:
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
Click to expand...
Click to collapse
nah, we haven't nothing to lose... someone should try it
The Troll said:
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
Click to expand...
Click to collapse
i believe you reference a different hardware platform not Nvidia based. o4x is nvidia tegra3 and different from omap and other platforms security wise.
can you link to the tegra fuse , you reference here? (fuse is a connector which will break the firmware open and full access granted, but can also cause firmware to not load, since fuse is broken)
reas0n said:
nah, we haven't nothing to lose... someone should try it
Click to expand...
Click to collapse
flash image GUI..
someone rooted should try that first..
also, unlimited.io <--- website.. for details of the downgrade mode trick..
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1491107
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1627917
the basic idea of this is 2 connectors close to the camera.. short circuit them to switch the phone to downgrade mode *QHSUSB_DLOAD*.. bricking the device and mounting all partitions as read and writable.. then using linux to find the right partition to flash/dump the hboot *the bootloader*
at the end, if it uses fastboot/adb, i dun think this will be too different from the evo 3d..
try it.. but dont say i didnt warn you..
im not sure its a fuse, its more of a reset?
also, i dont exactly have the phone *yet* so i cant tell..
but for the 3d, its exposed.. 2 holes in the back under the cover, next to the camera..
http://unlimited.io/juopunutbear-public-beta-0-1/instructions/evo-3d-cdma-shooter/
or you can find a schematic of the phone itself..
if you dont mind me asking, whats the reason for the lack of devs?
this is an excellent phone..
is it the extreme security?
iphone got a jailbreak too :/
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Dexter_nlb said:
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Click to expand...
Click to collapse
how did one x get the kernels running?
**edit.. nvm.. htcdev.. forgot..
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Dexter, the One X solution is for Tegra3 devices. The QUALCOMM-Device is called HTC One XL. So if the chipset is nearly the same, there must be a solution? If I could code anything, I would. But I cannot
Hilmy said:
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Click to expand...
Click to collapse
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
aremcee said:
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
Click to expand...
Click to collapse
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Dexter_nlb said:
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Click to expand...
Click to collapse
I'd rather not forewarn them by asking for a contact for this
My personal opinion: a mailrobot would be a bad idea, they'd just filter it out. Actual users, with actual devices (serial numbers in the message and all that) would carry much more weight than just generic "gimme". From experience... petitions don't work, either, unless they hit visible news outlets;
My suggestion would be to hit a support contact, consistently (instead of dispersing the message to random contacts); most companies will escalate any issue given enough occurrences of it. On the other hand, I can't find contacts besides the country-specific ones at http://www.lg.com/global/supports/service-sites.jsp ...
1: Why would i wanna root my chromecast, have looked around no one have shown anything special, that i can do with it?
2: If i root my cc, would i be able to change the Google DNS, so i would be able to use Netflix outside US? (My router is not able to use DD-WRT)
Thx for reading a sorry for the questions Hehe new user!
bormeth said:
1: Why would i wanna root my chromecast, have looked around no one have shown anything special, that i can do with it?
2: If i root my cc, would i be able to change the Google DNS, so i would be able to use Netflix outside US? (My router is not able to use DD-WRT)
Thx for reading a sorry for the questions Hehe new user!
Click to expand...
Click to collapse
1. With a rooted image, the best thing you can do is disable automatic updates so you can keep your exploitable bootloader for later flashing if anything good comes out.
2. Yes, you can change the DNS Servers the chromecast uses by using CastFlash and modifying the proper files. (I will make a flashable zip to do this if there is enough demand)
There isn't anything super amazing to do with root yet, but you should root right out of the box anyway.
Rooting will preserve the unlocked bootloader. If you don't immediately root, and something awesome comes along later, you won't be able to make use of it because your bootloader will be locked.
Thx everyone Some light on the subject helps!
ddggttff3 said:
1. With a rooted image, the best thing you can do is disable automatic updates so you can keep your exploitable bootloader for later flashing if anything good comes out.
2. Yes, you can change the DNS Servers the chromecast uses by using CastFlash and modifying the proper files. (I will make a flashable zip to do this if there is enough demand)
Click to expand...
Click to collapse
I would LOVE a modified zip to flash on it! Maybe using https://unlocator.com/setup/ <-- so can everybody outside US use it on any router etc.
If i can help somehow feel free to contact me.
Just found out my new chromecast is using v12072 woohoo
1: But i can't seem to find a powered Micro-USB OTG cable anywhere near where i live, so is the any solution where i can do this using my computer somehow?
2: If i flash my chromecast, would i be able to return it to the factory settings again?
Thx for reading!
bormeth said:
Thx everyone Some light on the subject helps!
I would LOVE a modified zip to flash on it! Maybe using https://unlocator.com/setup/ <-- so can everybody outside US use it on any router etc.
If i can help somehow feel free to contact me.
Click to expand...
Click to collapse
I'll try to get one made, and posted in the next few days. I will make a thread for it, so keep an eye out.
bormeth said:
1: But i can't seem to find a powered Micro-USB OTG cable anywhere near where i live, so is the any solution where i can do this using my computer somehow?
2: If i flash my chromecast, would i be able to return it to the factory settings again?
Thx for reading!
Click to expand...
Click to collapse
Congrats!
1. Sadly you need a Micro-USB OTG cable that is powered, like this one:
http://www.amazon.com/Micro-Cable-P...id=1379946981&sr=8-1&keywords=powered+usb+otg
2. Yes, if you truly desire, you can always flash back to stock.
ddggttff3 said:
I'll try to get one made, and posted in the next few days. I will make a thread for it, so keep an eye out.
Congrats!
1. Sadly you need a Micro-USB OTG cable that is powered, like this one:
http://www.amazon.com/Micro-Cable-P...id=1379946981&sr=8-1&keywords=powered+usb+otg
2. Yes, if you truly desire, you can always flash back to stock.
Click to expand...
Click to collapse
Thx m8 i will take a look around for one!
Interested in testing? Flash this, it should set the DNS to use unlocator. If it works, let me know, and il make a thread.
https://mega.co.nz/#!tBcQEIzR!WZ_7hw7Z-tNLOOk7SV7n_wn-7TQGVgEdNfb2ETJ582I
ddggttff3 said:
Interested in testing? Flash this, it should set the DNS to use unlocator. If it works, let me know, and il make a thread.
https://mega.co.nz/#!tBcQEIzR!WZ_7hw7Z-tNLOOk7SV7n_wn-7TQGVgEdNfb2ETJ582I
Click to expand...
Click to collapse
Would love to test it out, but havnt found the OTG cable yet... Im waiting for a respons for serval resellers here in Denmark.
Is it possible to backup the TA Partition (DRM Keys) without root?
The Backup TA tool requires root, although I haven't tried it yet.
No, and why you asking this question if clearly is wrote HERE.
wedge905 said:
Is it possible to backup the TA Partition (DRM Keys) without root?
The Backup TA tool requires root, although I haven't tried it yet.
Click to expand...
Click to collapse
It would be rather silly if it didn't require root, wouldn't it?
Rekoil said:
It would be rather silly if it didn't require root, wouldn't it?
Click to expand...
Click to collapse
When decrypting files after official update one of the files seems to hold TA information... no root required....
I might be wrong.
zimbashka said:
When decrypting files after official update one of the files seems to hold TA information... no root required....
I might be wrong.
Click to expand...
Click to collapse
You are wrong, the only thing that file includes is a customisation ID reset, besides, writing to TA is not the same as reading from TA. I'm sorry but this just isn't going to happen.
Rekoil said:
You are wrong, the only thing that file includes is a customisation ID reset, besides, writing to TA is not the same as reading from TA. I'm sorry but this just isn't going to happen.
Click to expand...
Click to collapse
Cool
Thanks for input.
Today I learned something new.
Well i wanted to try to root manually. But that requires an unlocked bootloader. But i cant backup the ta without root. So it becomes a chicken and the egg problem.
So i was just wondering if theres any other way to back up, but i guess theres not
wedge905 said:
Well i wanted to try to root manually. But that requires an unlocked bootloader. But i cant backup the ta without root. So it becomes a chicken and the egg problem.
So i was just wondering if theres any other way to back up, but i guess theres not
Click to expand...
Click to collapse
I guess you don't search and read properly. You can root your phone with Locked Bootlader.
eclyptos said:
I guess you don't search and read properly. You can root your phone with Locked Bootlader.
Click to expand...
Click to collapse
No, I want to experiment a bit, not just use the pre-made tools or images. I'd like to try it completely manual, something like this.
wedge905 said:
No, I want to experiment a bit, not just use the pre-made tools or images. I'd like to try it completely manual, something like this.
Click to expand...
Click to collapse
There is no Link and whatever you want to do, you just wasting you time, there is just one method to Root your Z1 and it's this one http://forum.xda-developers.com/showthread.php?t=2572988.
Do you think to know what Devs don't? If it will possible do it other ways we will already know it.
eclyptos said:
There is no Link and whatever you want to do, you just wasting you time, there is just one method to Root your Z1 than this one http://forum.xda-developers.com/showthread.php?t=2572988.
Do you think to know what Devs don't? If it will possible do it other ways we will already know it.
Click to expand...
Click to collapse
link was there, just broken. now fixed.
wedge905 said:
link was there, just broken. now fixed.
Click to expand...
Click to collapse
Good luck with that, btw I will suggest to use Bin4ry on .534.
eclyptos said:
Do you think to know what Devs don't? If it will possible do it other ways we will already know it.
Click to expand...
Click to collapse
no offense:
with this kind of attitude, technical progress would just stagnate.
don't get me wrong, i really don't want to offend you, but i'd rather support people who are trying to do something "the other way" instead of turning him down.
i'd go even further and give him probs for digging in deeper rather then just relying on tools made by others.
xXFlippyXx said:
no offense:
with this kind of attitude, technical progress would just stagnate.
don't get me wrong, i really don't want to offend you, but i'd rather support people who are trying to do something "the other way" instead of turning him down.
i'd go even further and give him probs for digging in deeper rather then just relying on tools made by others.
Click to expand...
Click to collapse
No taken, just read what he asked in the first post. Then ask your self, is that easy to extract the FTF and Root it "Manually" and then flash it again or even extract just the system.sin, switch to insecure and do all steps to get root. Even an ignorant like me understand in first place if something like that will be possible we will not have all this trouble to get root. Ending this story how you can ask just for Backup TA without Root and not explain what you REALLY want to do? Which help you get? Come on!
xXFlippyXx said:
no offense:
with this kind of attitude, technical progress would just stagnate.
don't get me wrong, i really don't want to offend you, but i'd rather support people who are trying to do something "the other way" instead of turning him down.
i'd go even further and give him probs for digging in deeper rather then just relying on tools made by others.
Click to expand...
Click to collapse
I was thinking the same thing, but wasn't going to say anything. So thank you dude.
I know I didn't explain myself fully in the initial question. I was just looking for a simple yes/no answer, I didn't think the context was that important to the question.
wedge905 said:
I was thinking the same thing, but wasn't going to say anything. So thank you dude.
Click to expand...
Click to collapse
I think you don't think enough, I do not stop your development, you do starting from a point where is there no way out.
This is the ONLY solution which you have, from a guy without experience like me, Root your phone with the method by NUT for Locked Bootloader, there is no other way for your purpose, then when you are rooted easily you can Backup your TA and DRM keys. Now you are in safe place and you can Flash Back Stock Rom from PC Companion or from Flashtool some FTF from XDA and you are ready, Stock like NEW with Locked Bootloader ready to Unlock it and experiment what you have in mind.
wedge905 said:
I know I didn't explain myself fully in the initial question. I was just looking for a simple yes/no answer, I didn't think the context was that important to the question.
Click to expand...
Click to collapse
You got that answer but you was going in your way no matter what, the only way I explained already.
I'm working on a (100% legit legal and 100% ORIGINAL works) way to flash to our /system partition for kitkat.
I've put my turbo through physical abuse. And it finally croaked weeks after "the drop".
I would need someone who has flashed a /system img via mofo to run USBlyzer on the correct port during the flashing process and then save and upload the log file. I will guide as needed. Remote desktop would allow me to quickly setup and start the process.
No longer having a phone that even turns on, I've resorted to using as USBlyzer as my debugging info by comparing my output to the known correct output. However, I have only logged the beginning of an upload. I need a complete, in order log.
I can help in about 12 hours
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
5.1:
How it works: Nobody has a clue because the 4.4 loophole is patched.
4.4
How it works: (I'm just making an example don't pick apart my math or partition sizes)
system.img = 3.5gb
cache partition = 1.5gb
So with a modified fastboot, you will write to the cache partition, but send more than 1.5gb of data, since the /system partition is next in order anything you send now will actually write to /system and not the /cache partition.
There are a few quirks I've seen, fastboot sends the "download" command 2x back to back, while the first "download" command hardly sends anything. This has something I assume to be "fake writing" Not quite sure. Its like it writes a tiny amount of data to /cache, sends the second "download" command to now write to /system. I've noticed that the data sent to /cache is actually a clone of a portion of the data sent to /system. Also there is 3gb of ram on the device, so after that gets filled up, the flash command is sent, then it goes back to download commands.
At the end it erases /cache because its full of garbage.
koftheworld said:
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Click to expand...
Click to collapse
SaschaElble said:
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
Click to expand...
Click to collapse
Fair enough that is exactly why I stayed on kk.
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Does anyone have any info on the lolipop .img s
SaschaElble said:
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Click to expand...
Click to collapse
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
just use a vm...
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
Good idea. I'd be willing to do that.
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
That log data contains your device serial and UID for your turbo... Thanks for helping the turbo community!
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
That should work
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
SaschaElble said:
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
Enjoy uploading 5-8gb of log data since you don't trust me being on your computer. Oh and since we are talking trust, that log data contains your device serial and UID for your turbo... SO actually you might not even want to do that either. Thanks for helping the turbo community!
Click to expand...
Click to collapse
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
TheSt33v said:
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
Click to expand...
Click to collapse
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
SaschaElble said:
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
Click to expand...
Click to collapse
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
TheSt33v said:
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
Click to expand...
Click to collapse
lol. I will for sure! But I won't get banned again. Not if everyone plays by the same rules they expect me to.
Anyone is free to contact me at (Edit: I was such an idiot. 5 years later... wow. ) If you want an easy two click way to get onto my channel on IRC follow the link in my signature.
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Michaelmansour1997 said:
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Click to expand...
Click to collapse
I would buy the bricked one, or you can let me see if I can fix it remotely.
NEW:
My vouching thread for those who I request access to their device remotely or gain knowledge of sensitive information:
http://forum.xda-developers.com/general/off-topic/saschaelble-vouching-thread-want-help-t3150299
Do you have a hangouts
i have read this post (https://forum.xda-developers.com/showthread.php?t=2581166) and this seems to be last hope to bring s3 mini back to life before touching JTAG.
Phone cant enter download mode, don't charge, don't show any sign of boot or bootloop.
If someone have debrick img for s3 mini gt-i8200, please give me link.
Or you can make by following instruction here:
(https://forum.xda-developers.com/showthread.php?t=2625628) and
(https://forum.xda-developers.com/att-galaxy-s6/help/create-debrick-img-stock-rom-t3367325)
Still waiting to get any help from XDA developers experts and users
Helloooo! I need the same, could somebody who knows how to do it just provide it for us? I'm willing to make a donation
marianvr7 said:
Helloooo! I need the same, could somebody who knows how to do it just provide it for us? I'm willing to make a donation
Click to expand...
Click to collapse
Not found yet. This unbrick image is needed when you messed up your bootloader, are you sure of that?
sadiqeen3210 said:
Not found yet. This unbrick image is needed when you messed up your bootloader, are you sure of that?
Click to expand...
Click to collapse
If you can't get boot into download mode at all, you might be done. Hard bricks are often the death call of a phone. I'm curious, were you able to work this out?
cloudmann said:
If you can't get boot into download mode at all, you might be done. Hard bricks are often the death call of a phone. I'm curious, were you able to work this out?
Click to expand...
Click to collapse
It can be worked out. See youtube for JTAG, and unbrick.img method. And there is also freezer method.
sadiqeen3210 said:
It can be worked out. See youtube for JTAG, and unbrick.img method. And there is also freezer method.
Click to expand...
Click to collapse
What's the Freezer method?
w0lf_b said:
What's the Freezer method?
Click to expand...
Click to collapse
see this thread, people are talking about freezer method here https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114/page53
It is a shame no one found the file. I have to buy a working device now I guess.
L3P3 said:
It is a shame no one found the file. I have to buy a working device now I guess.
Click to expand...
Click to collapse
Same model?
sadiqeen3210 said:
Same model?
Click to expand...
Click to collapse
Yes yes, an 8200n, I ordered one in bad condition but it boots so I will post the data here as soon as I got it!
I have copied the first 128M of the mmcblk0 of that device. Now I have no idea what to do. Maybe one of you have a better idea.
Hey, any progress here? I also need the img.
As I wrote, I got the raw data but I have no idea what to do with that!
Here is the raw dump of the beginning of internal flash. Flashing it directly to mmc (not to some partition but to /dev/mmcblk0 or similar directly) might recover booting. Then you have to wipe /system /data etc. and install an image from twrp, because OS is not included in this img. In case anyone has a better idea what to do with that, please tell!
https://l3p3.de/shr/goldenve3g-raw.img.gz
Thank you for your fast reply.
As I understand, the debrick img file is used to be written to a SD Card and the hard bricked phone should boot from that.
After flashing your image with Win32DiskImager or Etcher and putting it in the phone, it won't start.
When I flash the last file from this post (Debrick for 4.4.2) (Yes, wrong model). The SD-Card shows something like 26 partitions. That confirms this post:
should show approximately 23 partitions (IIRC)
Click to expand...
Click to collapse
Your img does not create any partition, but when extracted with binwalk, I can see that there are multiple files inside.
So I think your img is broken, how did you create it? Did you use this post or maybe this one? Can you replicate my partition list? Can you build it again?
I have just dumped the raw internal memory, the first x megabytes of it. It should contain partitions but I don't remember much.
I can look at it again later, have not much time now. But I have that phone and it will be done.
Hey, how are you? Do you have some spare time around?
Sorry, I worked a lot on https://github.com/L3P3/minicraft the last weeks. I have forgotten this thing. Next weekend, I try to do it.
It is an old phone, you should keep it but it does not hurry too much, right?
I also recommend buying a used S4 Mini [serranoltexx] and put Android 11 on it like I did.
Minicraft looks like an interesting project, I will keep an eye on that.
No, there is no hurry, I am trying it just for fun.