Related
Don't know if this would actually work but it's better trying than doing nothing.
ReTweet this or create your own tweet asking Asus to unlock their boot loader and give us better root access to their transformer:
Edited tweet: https://twitter.com/#!/stevegaron/status/76007197145960448
We may want to speak up on their facebook page too... http://www.facebook.com/ASUS?sk=wall
It worked for HTC...
Tenny said:
It worked for HTC...
(FYI: Easier not easyier)
Click to expand...
Click to collapse
Damn! I think I made it obvious that english is not my first language... I changed the tweet...
steve.garon said:
Damn! I think I made it obvious that english is not my first language... I changed the tweet...
Click to expand...
Click to collapse
Wait so we aren't going to resort to kidnappings and firebombs....man, hate this place.
I'm confused.
I thought the bootloader was unlocked...
Or are you talking about APX mode being locked? If that's the case, then I'm with you on that one. Without a functioning APX mode, I am scared to do anything to my Eee Pad. I couldn't count how many times I've soft bricked my GTab and APX saved my bum!
and why should this thread be in the development section?
rj3005 said:
and why should this thread be in the development section?
Click to expand...
Click to collapse
Just because it would help make dev easier. So I thought it belong here.
Sent from my Transformer TF101 using Tapatalk
KnightCrusader said:
I thought the bootloader was unlocked...
Or are you talking about APX mode being locked? If that's the case, then I'm with you on that one. Without a functioning APX mode, I am scared to do anything to my Eee Pad. I couldn't count how many times I've soft bricked my GTab and APX saved my bum!
Click to expand...
Click to collapse
Unless I misunderstood what lock bootloader are, I beleive its locked. It requires root to flash another recovery/rom and requires an exploit to get root. That pretty locked for me
I would be much more fun if you could just do a fasboot flash recovery like the Nexus phones ;-)
Sent from my Transformer TF101 using Tapatalk
Did my part on facebook....
I posted on their wall too
hope they follow like HTC did
steve.garon said:
Unless I misunderstood what lock bootloader are, I beleive its locked. It requires root to flash another recovery/rom and requires an exploit to get root. That pretty locked for me
Click to expand...
Click to collapse
Go to the Acer Iconia A500 forums, and then you'll find out what a "locked bootloader" really is.
What you should really be asking for is simply official root access, without having to find an exploit. Note that HTC have only said they are ending their policy of locking the bootloaders on their phones - as far as I'm aware they've said nothing about giving official root access.
Regards,
Dave
The never ending discussion about what a locked bootloader is, is useless because it depends on your definition on "locked". If "locked" means that it checks signatures before flashing or booting, then yes, the Eee Pad bootloader is unlocked. If however "locked" means that you have no way of recovering from a system/recovery fail, then the ASUS EeePad is very well locked down. The only way around this would be fastboot and/or nvflash access which we don't have.
So as opposed to the Xoom or other Tegra devices like the G2x etc, the ASUS bootloader is locked, and the only way of flashing boot/recovery is through a (admittedly simple) reverse engineering process. That is a shame, and also could be locked down anytime by ASUS if they were sigchecking those updates in the bootloader (though I think that's unlikely to happen).
So in my opinion ASUS shouldn't announce that the bootloader is open etc, when at the same time they do not provide a documented flashing method.
Equally though, I agree that there is no practical sense in complaining or doing further work on this, because all people care about is flashing boot/recovery (unless they are bricked of course...).
stridger said:
The never ending discussion about what a locked bootloader is, is useless because it depends on your definition on "locked". If "locked" means that it checks signatures before flashing or booting, then yes, the Eee Pad bootloader is unlocked. If however "locked" means that you have no way of recovering from a system/recovery fail, then the ASUS EeePad is very well locked down. The only way around this would be fastboot and/or nvflash access which we don't have.
So as opposed to the Xoom or other Tegra devices like the G2x etc, the ASUS bootloader is locked, and the only way of flashing boot/recovery is through a (admittedly simple) reverse engineering process. That is a shame, and also could be locked down anytime by ASUS if they were sigchecking those updates in the bootloader (though I think that's unlikely to happen).
So in my opinion ASUS shouldn't announce that the bootloader is open etc, when at the same time they do not provide a documented flashing method.
Equally though, I agree that there is no practical sense in complaining or doing further work on this, because all people care about is flashing boot/recovery (unless they are bricked of course...).
Click to expand...
Click to collapse
Well put. We need either fastboot or Nvflash access.. just eliminates any sort of risk we have while messing with our TFs
r34p3rex said:
Well put. We need either fastboot or Nvflash access.. just eliminates any sort of risk we have while messing with our TFs
Click to expand...
Click to collapse
Then that's what should be asked of Asus, rather than "unlocked bootloader" which is open to interpretation!
Regards,
Dave
I don't think that downgrading is a viable option for installing a custom Rom. Just because we can downgrade now, doesn't mean we will be able to in the future. Beside, having to rely on an exploit is also to me not a viable option. I'd rather have the exploits fixed! It's safer that way.
The fact that the boot loader is not signed, NAND locked or encrypted is a big plus and I congratulate Asus for this. It's a good design decision. But the missing ingredient for the completely unlock bootloader is the tool the allows us to flash anything from the bootloader...
If in the end Asus give us fastboot/nvflash access to the bootloader well to me its a win for all Transformer's owners. This is even a win for Asus because most devs would go for hardware that they can easily modify which would increase sales. (Not that sales are a problem right now.. )
How's this then?
Please @Asus give us a fastboot/nvflash and official root access - like the Google Nexus phones - for your amazing #eeepadtransformer!
jerdog said:
How's this then?
Please @Asus give us a fastboot/nvflash and official root access - like the Google Nexus phones - for your amazing #eeepadtransformer!
Click to expand...
Click to collapse
Works for me... Tweet it!
steve.garon said:
Works for me... Tweet it!
Click to expand...
Click to collapse
http://twitter.com/#!/jerdog76/status/76296399330873346
done.
foxmeister said:
Then that's what should be asked of Asus, rather than "unlocked bootloader" which is open to interpretation!
Regards,
Dave
Click to expand...
Click to collapse
Yeah, thats what I asked them for when I posted a message on their Facebook wall.
I just posted on their FB page
Is there any word on whether or not the bootloader is encrypted? If so does anyone have any idea on what the chances of it being unlocked is, as this is the only thing stopping me from buying this phone.
Sent from my SCH-I535 using Tapatalk 4
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
I'm ready for the complete package so I can start flashing
Sent from my VS980 4G using Tapatalk 4
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
soapinmouth said:
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Is there a way to check if the bootloader is locked? I'm getting a T-mobile version and am curious if they have it locked as well.
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
joshuadjohnson22 said:
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Click to expand...
Click to collapse
You mean WAS working with the S4...
Samsung changed the method 100% and no longer works with ANY Samsung device that is up to date.
Sorry guys, not trying to be a downer... I really want this phone... Very angry with the games carriers play.
scrosler said:
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
Click to expand...
Click to collapse
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
djkinetic said:
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recomend anyone trying to do...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Ah ic
Sent from my GT-I9505G using Tapatalk 4
---------- Post added at 12:43 PM ---------- Previous post was at 12:43 PM ----------
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
djkinetic said:
Ah ic
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Trust me man, I played this game on Samsung... Then quit it and went back to HTC.
With Samsung they dropped the loki method of kernels. So now, they have yet to have an unlocked bootloader...
I can only SUSPECT this phone is using the same method the Samsungs are now using...
Otherwise we would have lokied the ***** and we would all be crack flashing :highfive: :angel:
djkinetic said:
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
DeaconBoogie said:
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
Click to expand...
Click to collapse
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
scrosler said:
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
Click to expand...
Click to collapse
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
DeaconBoogie said:
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
Click to expand...
Click to collapse
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yea hope so too, but its a shame that its locked down, the device itself is awesome, Sadly ill prolly get a nexus 5 for my crack flash addiction lol
scrosler said:
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
Click to expand...
Click to collapse
Think we'll have a definitive answer in a week as to the prospects of unlocking?
DeaconBoogie said:
Think we'll have a definitive answer in a week as to the prospects of unlocking?
Click to expand...
Click to collapse
Once again... On pure speculation...
Impossible to know!
I just know the S4 has been re-locked for a couple months and no one has made any posted progress. I am "assuming" this phone uses the same method as Samsung. LG has always tended to play "follow Samsung."
So with that said... I would be watching the S4 forums for an answer...
Hello everyone. I am a kindle fire hdx user from China. We all waited your root method and turned out that we rooted first.
The method is very simple.
1. Install the attached software in your compurter, connect your device .(be sure you installed driver)The software will connect your device.
2. Click the low right button. Your device will be rebooted in five seconds. Root completed.
joetech1989 said:
Hello everyone. I am a kindle fire hdx user from China. We all waited your root method and turned out that we rooted first.
The method is very simple.
1. Install the attached software in your compurter, connect your device .(be sure you installed driver)The software will connect your device.
2. Click the low right button. Your device will be rebooted in five seconds. Root completed.
Click to expand...
Click to collapse
Can you show the source. I really don't trust this, if it works or not. Can we see the code. I put together code from other known Devs. The package seems shady, just saying. Anybody else install this?
Faznx92 said:
Can you show the source. I really don't trust this, if it works or not. Can we see the code. I put together code from other known Devs. The package seems shady, just saying. Anybody else install this?
Click to expand...
Click to collapse
It's a pretty popular rooting tool use among people how lack knowledge of Linux. Btw I rooted mine use the same tool, and I'm chinese too. We don't really know what exploit they use but it seems to work pretty well.
Sent from my KFTHWI using Tapatalk
wz7820431lb said:
It's a pretty popular rooting tool use among people how lack knowledge of Linux. Btw I rooted mine use the same tool, and I'm chinese too. We don't really know what exploit they use but it seems to work pretty well.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I would like to know what exploit they used. Hold onto that for a future root. That is what I'm really interested in.
Faznx92 said:
Can you show the source. I really don't trust this, if it works or not. Can we see the code. I put together code from other known Devs. The package seems shady, just saying. Anybody else install this?
Click to expand...
Click to collapse
I didn't since this was the first post by someone just claiming it works without any source code or proof. I have to agree with you that this seems shady.
R1Mike said:
I didn't since this was the first post by someone just claiming it works without any source code or proof. I have to agree with you that this seems shady.
Click to expand...
Click to collapse
Either way I'm not install this to my computer. I really want to see what exploit they used. But yah, I don't know what this is. Better to be safe then sorry.:angel:
joetech1989 said:
Hello everyone. I am a kindle fire hdx user from China. We all waited your root method and turned out that we rooted first.
The method is very simple.
1. Install the attached software in your compurter, connect your device .(be sure you installed driver)The software will connect your device.
2. Click the low right button. Your device will be rebooted in five seconds. Root completed.
Click to expand...
Click to collapse
And doubt you rooted first since this suddenly appears 2 days after it was first rooted here on XDA from our great jcase.
Faznx92 said:
Can you show the source. I really don't trust this, if it works or not. Can we see the code. I put together code from other known Devs. The package seems shady, just saying. Anybody else install this?
Click to expand...
Click to collapse
I don't know how it works but it works. Show you the evidence.
Is this work for the model HDX 8.9" as well?
lanegan said:
Is this work for the model HDX 8.9" as well?
Click to expand...
Click to collapse
Just tested on HDX 7. Not suggest you to try.
joetech1989 said:
Just tested on HDX 7. Not suggest you to try.
Click to expand...
Click to collapse
If you can find who made this or what the exploit code is it may be a future rooting method.
Faznx92 said:
If you can find who made this or what the exploit code is it may be a future rooting method.
Click to expand...
Click to collapse
It's a very popular root tool in China that made by a company. I tested it OK and here to share with you. Can't get any code.
The best and quickest method to root.
joetech1989, Thank you, bro!!!
Your method really works fine.
Very easy and fast.
Equinox666 said:
joetech1989, Thank you, bro!!!
Your method really works fine.
Very easy and fast.
Click to expand...
Click to collapse
Can you please tell us your version? Are you on the latest version of hdx7? Give us more specific would be very helpful. Thanks bud!
andyt315 said:
Can you please tell us your version? Are you on the latest version of hdx7? Give us more specific would be very helpful. Thanks bud!
Click to expand...
Click to collapse
Current version: 13.3.1.0. At first it is necessary to include in settings Enable ADB, then to install adb drivers.
Seems sketchy. So seeing as you only have a few posts...it seems you just joined XDA developers. And you have a root tool but you cannot tell us more about it. I mean if it works then GREAT but most people would want to know what exactly it is that they are downloading..just saying. don't be offended.
equisbox said:
Seems sketchy. So seeing as you only have a few posts...it seems you just joined XDA developers. And you have a root tool but you cannot tell us more about it. I mean if it works then GREAT but most people would want to know what exactly it is that they are downloading..just saying. don't be offended.
Click to expand...
Click to collapse
This kind of reminds me of the whole fiasco with Kango root, which was secretly sending peoples IMEI numbers to a server in China, even though the dev claimed to be from Canada. It was a very easy to use program to root many different phones but was eventually pulled from XDA because of security concerns. It was/is sending 'sensitive' data without encrypting it and then also sent the IMEI as well. It also connected to the internet to download 'drivers' so a virus scan was not of much use for Kango Root. That is a completely separate program which was posted by a different XDA member.
Just to be clear... I am not at all inferring the original poster has malicious intent or has posted a malicious tool. I am merely explaining why some would view it with such skepticism especially in light of previous events. I don't yet own a Kindle Fire HDX, so, I don't have to make the difficult choice of choosing which way to root the device. Virus Total reports the files as being clean, but, that does not always mean it is safe, especially if something is downloaded once the file has been executed.
If you could shed some additional light on the tool it would likely help to put a lot of people's minds at ease.
joetech1989 said:
It's a very popular root tool in China that made by a company. I tested it OK and here to share with you. Can't get any code.
Click to expand...
Click to collapse
What is the company's name in China and do they have a webpage that we can see and get the root tool from?
Yes ,it works. maybe they use exploit we get it on XDA.
FYI : thus is just one of a few xda posts I've seen concerning vroot.... http://forum.xda-developers.com/showthread.php?t=2473354
Sent from my SCH-I545 using Tapatalk
Anyone know of any word on these two roms making a appearance here soon?
Sent from my SM-N900V using Tapatalk
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
akellar said:
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Jeremiah_1988 said:
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
carlz28 said:
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
Click to expand...
Click to collapse
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
willjohnson said:
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
Click to expand...
Click to collapse
Kind of what I thought, just going to try and wait patiently for more development
Sent from my Nexus 7 using Tapatalk 4
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
akellar said:
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
carlz28 said:
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
Click to expand...
Click to collapse
All i was saying, is that our device is way to new to be saying what it will or wont have development on in the future. Thats just my opinion.
i have an unlocked developer edition where is my cm/aosp then haha
oneandroidnut said:
i have an unlocked developer edition where is my cm/aosp then haha
Click to expand...
Click to collapse
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
shiftr182 said:
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
Click to expand...
Click to collapse
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
oneandroidnut said:
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
Click to expand...
Click to collapse
Unlocked does not equal aosp, at least functioning. Ril is likely an issue.
Sent from my SM-N900V using xda app-developers app
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
TechSavvy2 said:
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
Click to expand...
Click to collapse
i have a friends bricked note 3 he can get haha
If i were to change the emmc chip on my 7th gen 7" and 8" fire tablets for an emmc chip with vanilla Android am i likely to run into any issues?
J_IO_B said:
If i were to change the emmc chip on my 7th gen 7" and 8" fire tablets for an emmc chip with vanilla Android am i likely to run into any issues?
Click to expand...
Click to collapse
yes, you will run into many problems. 1st problem is desoldering it. 2nd problem if desoldering wasn't a dead end, finding a preprogrammed emmc chip that will work for it is pretty much impossible. but don't worry there is a new exploit for all MediaTek processors that will let you flash partitions in boot rom mode! it's only a matter of time for this device to get hacked.
ANDROID2468 said:
yes, you will run into many problems. 1st problem is desoldering it. 2nd problem if desoldering wasn't a dead end, finding a preprogrammed emmc chip that will work for it is pretty much impossible. but don't worry there is a new exploit for all MediaTek processors that will let you flash partitions in boot rom mode! it's only a matter of time for this device to get hacked.
Click to expand...
Click to collapse
Thanks for the reply if i did have the ability to desolder/resoldrer and program the emmc chip do you know what i should program it with? a compatible image? Or is it this that isn't available?
The exploit sounds even more promising do you know where i can find out more?
J_IO_B said:
Thanks for the reply if i did have the ability to desolder/resoldrer and program the emmc chip do you know what i should program it with? a compatible image? Or is it this that isn't available?
The exploit sounds even more promising do you know where i can find out more?
Click to expand...
Click to collapse
I pach a system.img with root now I'm just waiting for a script to flash it!( The scripts use python and I'm kinda new to programming python) I requested on a different thread for the script...
So I wouldn't go with the desolder the emmc route because then you have to warty about soldier balls, bridges, killing you emmc chip with heat, etc.
Sent from my VS986 using XDA Labs
ANDROID2468 said:
I pach a system.img with root now I'm just waiting for a script to flash it!( The scripts use python and I'm kinda new to programming python) I requested on a different thread for the script...
So I wouldn't go with the desolder the emmc route because then you have to warty about soldier balls, bridges, killing you emmc chip with heat, etc.
Sent from my VS986 using XDA Labs
Click to expand...
Click to collapse
How did you get on?
J_IO_B said:
How did you get on?
Click to expand...
Click to collapse
if you short one of the pads under the sheld to ground you will be able to boot to boot rom mode. that's when you will run the script to that will decrypt the keys so you can flash anything from there.
Bit late but its kinda impossible to change emmc chips.
If you get past soldering you could replace emmc chips with one from an old broken fire
and maybe it will work then
But who knows
we already have full root and bootloader unlock for most of the fire devices now
check the relevant sub for your model
LOS (soon)
ANDROID2468 said:
if you short one of the pads under the sheld to ground you will be able to boot to boot rom mode. that's when you will run the script to that will decrypt the keys so you can flash anything from there.
Click to expand...
Click to collapse
Sorry for the hijack here, but do this work on Fire HD 8 5th Gen model?
Thanks!
mugorj said:
Sorry for the hijack here, but do this work on Fire HD 8 5th Gen model?
Thanks!
Click to expand...
Click to collapse
Yes, technically it will but this method is harder to do.
here is a more in-depth guide on this. But I would not use this method, it's complex.
About the bootloader unlock:
The explicit to unlock the bootloader hasn't been ported to your device (if it has, I can't find it on XDA). It's because this model isn't that common. I will help Root you device using this method but I'm not skilled enough to Port the bootloader unlock.
ANDROID2468 said:
Yes, technically it will but this method is harder to do.
here is a more in-depth guide on this. But I would not use this method, it's complex.
About the bootloader unlock:
The explicit to unlock the bootloader hasn't been ported to your device (if it has, I can't find it on XDA). It's because this model isn't that common. I will help Root you device using this method but I'm not skilled enough to Port the bootloader unlock.
Click to expand...
Click to collapse
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
mugorj said:
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
Click to expand...
Click to collapse
ok, first I need to know what version of fire os you are running.
Then, I need a picture of your board. you need to open your tablet and you need to take off the shield. here is an example (you have the 5th gen so the shield should just pop off):
mugorj said:
@ANDROID2468:
Thank you very much for your help!
If I can achieve root access, I believe I'll be 97% happy. I have just managed to have another launcher working on my device with Launcher Hijack (just discovered that Amazon implemented a childish blocking by the app name), and the thing is flying! I'm much happier! The device is perfectly usable now!
If I just can uninstall some Amazon crap and have my stuff going, I'll be happy, even if it's still running FireOS underneath.
I'll read the topic you mentioned carefully. If I still need help, I'll politelly ask you for guidance.
Thanks again!
Click to expand...
Click to collapse
sorry, I didn't read your message carefully. the post that I posted previously was about porting a root method used by the fire 7 (7th gen) which was used before the bootloader unlock was released(well the 5th gen was released at the time but not 7th gen ). that method is a lot easier to do and less likely to kill your device.
Do you have a link for the root method please?
laharl_22 said:
Do you have a link for the root method please?
Click to expand...
Click to collapse
do you have a hd8 5th gen? or something else?