Hello to all good guys in xda-developers forum.
This is my very first post and I really feel desperate and need your kind help.
New Acer iconia with stock firmware 3.2.1 was nicely running this morning until I tried to root the device.It was supposed to be very simple process and not to get into dirty complicated procedures but the gingerbreak.apk did not work as expected so I tried alternative methods.What I read in various forums was that the gingerbreak application is not able to root the new firmwares version so I tried to downgrade the firmware to 3.0.1.
Downloaded the Acer stock recovery firmware EUUs_SBK_Acer_A501_0.017.01_PA_ATT.exe and attempted to flash onto my tablet .I think I did all necessary pre-installation checks.The process started but it stopped on 10 percent for about 30 minutes without any progress.Only Acer logo was displayed and 'entering file downloading mode' at the top of the screen.
After long time no change I finally gave up and unplugged the device from the USB port and restarted but nothing works since then.
1. No vibration on Start
2. Black screen
3. No new USB device appear on my PC
4. No sign of any activity other then power button light
I guess the original firmware was wiped but the new firmware was not flashed...for whatever reason...perhaps the worst scenario.
I will really appreciate If anybody may give me advice how to fix it.
So it turns on but does not display anything? Have you tried to hold the power button and volume down button at the same to when you turn it on to try to get it into recovery. Also there is a little reset button on the side you can try to push.
Sent from my A500 using xda premium
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
acera500 said:
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
Click to expand...
Click to collapse
Try this thread. Look about halfway down, and you'll see almost the exact thing you did, and how this guy got it going.
http://forum.xda-developers.com/showthread.php?t=1291747
Basically you can run a search for APX in the main forum threads and find some other posts, but hopefully this will get you going.
I pulled this from the general forum (eventually), but you can also search the Q&A main forum page as well, and the dev forum.
Another link;
http://forum.xda-developers.com/showthread.php?t=1255519&highlight=apx&page=2
If its new just return it to the store for another one.
Sent from my A500 using xda premium
Acer or the store did not brick it
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Piece of cake to fix if you kept you USB serial number (from the downgrade tool)???
===== If you have your USB serial number ====================
1. Lets assume you know your USB serial number. If not, then you might be able to get it from your registry.
2. Download my flashing tool at http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
a. Open up the readme.pdf for the instructions on how to flash
3. KEEP your acer unplugged and run the program
4. The program will install the APX flash drivers and will tell you to plug in the USB. Ignore this step. It will not work. In the instructions skip steps 3, 8, 9, 10.
5. Eventually the flashing tool will timeout because you do NOT have the tablet connected. It will then display a message box telling you how to use a paperclip and the power button to get you into APX mode. THIS IS THE secret to getting the tool to flash your ACER. However, once you get it into APX mode you will need your USB serial number (without it, you are fubar).
a. Plug in the tablet to your computer with the USB and paperclip yourself to fastboot.
6. Now in step 11, enter your USB serial number
7. Now just follow the rest of the instructions.
====== NO USB Serial number ==========
If you do not have your USB serial number than you are going to be out of luck, unless you have ever connected the device to your computer. If you did, then your registry will have a history containing your serial number.
Google usbdeview tool and download it. This will show the serial number of any USB device you've connected to your computer.
===== No Serial number, never connected it, what to do ==========
If you have no serial number and cannot get it, then hopefully you can get to recovery mode (power & volume) and flash using a signed update.zip from ACER. Download one of the update.zip's and put it on your external SDCard and then boot to recovery.
=== Bricked and No serial number, never connected, and you fubar'ed the recovery image ===
If you never connected your table to the USB and your computer to get the USB serial number then you are NOT going to be able to flash it to fix it.
If you fubar'ed the recovery image then you won't be able to get into recovery to run the ACER update zip.
At this point, you can still get your tablet into APX fastboot mode using a paperclip and the power button. But I know of NO way to flash it without the USB serial number and I know noway to get the USB serial number from the APX driver. I've tried and looked at getting the serial number from just APX mode, but I cannot determine how to get it. Someone out there might know.
Hope this helps,
TD
Your CPUID can also be found in the uid.txt file in your cwm backup folder - /mnt/external_sd/clockworkmod/backup/ - just remember to drop the 0x when you need to enter it
erica_renee said:
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Click to expand...
Click to collapse
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
wade7919 said:
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
Click to expand...
Click to collapse
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Why locking a bootloader will cost ACER billions
Moscow and wade7919, you both make good arguments.
But it is what point of view you're coming form. If I bought a car and changed the RIM's on all 4 wheels and the engine blew up, would GM refuse to honor the warranty?
However, if I put jet fuel and alcohol in for gasoline and blew the engine why would they honor the warranty?
So, the question here is does rooting a device cause actual damage to the device thereby preventing rooting saves them warranty issues? Or is the device also considered to include the software and is covered under warranty?
I'm not taking sides here, but you both are making very good points but with different examples at different points of view.
So, lets look at other items and see if we can draw a parallel. If I buy a brand new Dell computer and send it in for Warranty and there is nothing wrong with the hardware they charge me (correct?). So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty.
So, why does an Android MFG take the warranty one step further and include the OS and take steps to lock it so you cannot change it? Well, this is because nobody owns the OS (it's open source) therefore they take ownership of the build. Because there's no Microsoft to blame, they lock the software and consider it to be part of the overall device (Apple claimed this in their lawsuit). So, in the MFG's mind, there is no difference from the screen, keyboard, or the firmware & software.
So the question is what do you think should be covered under warranty? Most people think it should be just the hardware like a PC. Others see the whole device which includes the OS.
My point of view:
What follows is my rant and my opinion (you are warned )
In my opinion, I had NO problem until they decided to lock the bootloader. I have no problem with them claiming warranty from A-Z and if I change anything they won't warranty it. No problem, I understand that and accept full responsibility. But by ACER locking the bootloader they went too far.
To me this would be like GM welding the hood shut on my car. Better yet, it would be like me waking up one morning and opening my garage to get in my car and discover that during the night GM welded the hood shut. This, in my opinion, is illegal. Matter of fact, in my opinion, it violates US Federal hacking laws because they enter a system and destroyed data. I eventually think OEM's will get a class action suit filed on them for this.
Secondly, Windows 8 is going to be the game changer. OEM's can now make a hardware device and sit behind only warranting the hardware. You have a problem with the OS, call MS. Also, there is a HUGE (I mean HUGE). Did I mention HUGE, demand for tablets in business. Businesses will NOT put a device that has all these consumer games and social networking loaded into the workforce. There are billions in business applications that can be made, but you cannot sell them if they only run on a tablet that cannot have games removed etc.
Example might help: Medical field <- Think of all the applications a tablet can be used to save costs in hospitals. Do your really want your doctor or nurse etc using this tablet on facebook? Insurance company's, law firms, retailers, traveling sales, etc etc (Government). The list goes on.
Developers will see this huge opportunity and will write applications because they can sell them to A-Z and the business buying them will buy them because they can remove facebook and gmail from their company owned tablets. Now, as more and more developers move to Windows they'll drop Android. Want another example, read about Netflix and the issues they have had supporting a fragmented Android OS. So, business applications will move to Windows, but you might say so what, the consumer market is still there. True, but all you need is one killer application that everyone will want and for that to only be on Windows 8. Want some examples, here's my list, NFL (or sports), Netflix, Skype (gee owned by MS now isn't it?), or something new.
Bottom-line is this, if ACER and the others want to lock their bootloaders then they have just taken themselves out of the game for any business sales. Can you imagine walking into a boardroom showing the Government how your new VA application will save the VA Hospitals millions next year alone and improve veterans healthcare. Your application runs on any HC Android tablet. Everything is smoking, going great, as you hand your tablets, ACER a500', around the room. They are loving it. You just hit 'pay-dirt', then someone says hey I see these ACER's have gmail, facebook, blah blah. We cannot have government employees using tablets with those applications loaded, your installer removes them doesn't it? Silence enters the room, all eyes are focused on you. Your mind see millions escaping which were just within your grasp, you pause, you think, and you say YES General as you grab your Motorola Xoom and say 'that's why we recommend you buy nothing but Motorola.'. ACER just kissed millions in sales goodbye (oh and this is a true story).
i do believe acer should lock the bootloader on there devices.
However thee are things I would be doing with my tab if it were not locked.
Acer should give us the ability to flash the bootloader and not use the proprietary software. Lock that software to there bootloader.for there protections.
Give us a wway to unlock it..AT OUR OWN RISK..
So it should be locked but have a way to unlock it with the end user understanding they are totally on there own ..
I would be OK with voiding my warranty.
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Moscow Desire said:
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Click to expand...
Click to collapse
Very well put.I do know of a few people who have sent there device to acer after messing it up installing rom and telling acer.acer still fixed it free.
Honesty is always best
The evils of rooting
I'm still missing something here, why locking a bootloader does anything. Go get a Mortorola Xoom (not the FE) and you run the unlock OEM. It tells you that you are unlocking it. It tells you that you unlock it at your own risk. You cannot relock it until it is 100% back to stock. It asks you three times are you sure.
Locking the bootloader and treating everyone as an idiot is the problem. Just do what Motorola does, and stop being everybody's keeper. If they want to 'Police' this then you should have to call ACER and they fax you a form. You give DNA to prove who you are and fax it back. Then you go to a mandatory rooting class, that lasts for 5 days, where ACER preaches to you the sins of rooting. Then you have to take and pass a test. Then and only then, after passing the test you get a certificate. Then you call back, give them your certificate ID. Now they give you the secret key to unlock only your tablet.
That's the ticket,
TD
Bottom-line, it's not that they locked the boatloader, it's that you cannot unlock it. Like I said, go out to your driveway some morning and find that GM welded the hood to your car shut because they think you are stupid and shouldn't be opening the hood. Mind you that YESTERDAY, and at the time your bought it, it was not welded shut. That ladies and gentlemen is what ACER did with their OTA.
Moscow Desire said:
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Click to expand...
Click to collapse
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
wade7919 said:
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
Click to expand...
Click to collapse
I still like my car comparison
I make the car comparison to illustrate a point, because when I compare tablets to a PC everyone piles on *****ing about MS.
Bottom-line it doesn't matter if it's a blender or a PC. I own it, you own yours and I can do what I want with mine as you can with yours. Now, again I have a BIG(did i mention BIG issue with them changing it on me after I bought it.
To get back on topic, is the original poster still out there?? Has any of this helped? Are you still bricked?? Give us an update so we know if anything worked or you still need help.
The device was returned and accepted for replacement by the shop.Got new one and feel very nervous to start rooting procedure over.I was really lucky that they did not charge me anything but I really want to know what I did wrong so I don't brick my new device again.
I will provide further details soon about my computer OS and firewall settings and perhaps we may figure out what I did wrong.
To all good guys who send me them suggestions and solutions I wanna say big THANK YOU !!!
Your help is really priceless and thrilled me deeply. Will update topic soon
Happy New Yer to all Android fans!!!
So...Back on the subject.
My device was purchased in Japan and its current firmware version is
Acer_A500_7.009.03_AAP_CUS6JP
Q1. Can I flash US or World Wide firmware version on that device.
Q2. Does anybody know the Acer's ftp download server address for Japan
Q3. I think its a good idea to dump my original stock firmware but it seems there is no way doing that prior rooting.So..kinda stuck .any suggestions appreciated.
P.S. I'm thinking about flashing the latest Rooted rom 3.2.1 V3 by timmiDean (thanks for your hard work) I read the instructions very carefully and I think that everything will go smoothly but just in case (considering the specific Japanese firmware version)
would appreciate any further directions by the author.
Thanks
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Code:
adb shell setprop persist.sys.usb.config mtp,adb,acm
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7. This is almost certainly going to work on the HD 10. https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Turns out I wasn't crazy or stupid after all !!!!!! All I ever asked was for you guys to just listen to me and understand I knew exactly what I was seeing
DragonFire1024 said:
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Code:
adb shell setprop persist.sys.usb.config mtp,adb,acm
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7. This is almost certainly going to work on the HD 10. https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Turns out I wasn't crazy or stupid after all !!!!!! All I ever asked was for you guys to just listen to me and understand I knew exactly what I was seeing
Click to expand...
Click to collapse
Can you explain what is the acm mode, its bootrom download mode? I do not understand what we can do with the tablet in ACM mode. If we do not get the tablet to enter the BootROM Download Mode this mode will not help us at all.
How does the computer detect the tablet when it is in ACM? I tried it on my Fire 7 and it does not install any driver ...
EDIT: I read this:
Code:
Before Download mode can be entered, the Preloader has to find out if a host is connected via USB or UART and running the MTK SP Flash Tool. It does this by configuring a virtual CDC ACM discipline on USB, so both lines are in fact serial ports and behave similarly.
The USB port will assume that the tool is connected if it receives a “set line coding” (configures baudrate etc.) CDC message. It then sends the string READY to the tool and waits for the reception of a token of eight bytes.
After successful detection, the tool can send the special Start command sequence (0xa0 0x0a 0x50 0x05) to enter a special mode that is only available via USB. It interprets the following commands (I left the ones marked with “legacy” out):
Its seem that ACM mode its Download Mode
Rortiz2 said:
Anyone owning a Fire 7 needs to stop drop and roll...literally. Please go to your tablet and with a file explorer (i don't know if you need root) in the root directory please try in whatever way possible to read the contants of all files (theres like 3 or 4) with 'fstab' in the file title. Look for ANY properties ANYWHERE that have to do with 'acm'. I am fairly certain, without root you can persist this property in ADB. Get your tablet, plug into PC and open ADB window and type:
Can you explain what is the acm mode, its bootrom download mode? I do not understand what we can do with the tablet in ACM mode. If we do not get the tablet to enter the BootROM Download Mode this mode will not help us at all.
How does the computer detect the tablet when it is in ACM? I tried it on my Fire 7 and it does not install any driver ...
EDIT: I read this:
Its seem that ACM mode its Download Mode
Click to expand...
Click to collapse
ACM allows a device to emulate ports. Example: the tech doesn't have a usb port to connect the tablet. ACM can be used so the tablet emulates a different port other than USB. In our case, ACM appears to be the God mode.
DragonFire1024 said:
ACM allows a device to emulate ports. Example: the tech doesn't have a usb port to connect the tablet. ACM can be used so the tablet emulates a different port other than USB. In our case, ACM appears to be the God mode.
Click to expand...
Click to collapse
Had this device before. Got a new phone and gave it to my brother. But can you explain a bit, just entering those acm commands wont give you root, I know but what after that?
Will check this method when I go to my brother's.
Adyatan said:
Had this device before. Got a new phone and gave it to my brother. But can you explain a bit, just entering those acm commands wont give you root, I know but what after that?
Will check this method when I go to my brother's.
Click to expand...
Click to collapse
Please see: https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
ACM is a proprietary function mediatek uses to emulate the USB port as a different port so they can access their devices using various hosts. It's also a way for them to access the device without modifying the firmware or system. It's a clean, legit way an oem should access a device. This explains a lot of my discovery that kicked off this whole process. We could see all this happening in the HD 10 binary files, but we couldn't see how this access was happening or where it was coming from. My theory was Amazon used a back door and a mode or user ID greater than super to access devices without the use of private keys. Of course that was crazy talk and impossible and I can't blame any one of you for not believing me. I however never imagined this going beyond Amazon. I'm honestly in total disbelief that any of this is happening and even more so that my crazy cat lady theory was right from day one. I'm just greatful and honored that the few of you who didn't think I was crazy, took it to the next level. If it weren't for all of you, my theory would have been buried and forgotten. In the 3 years since I started all this I never imagined it would come to this. All of you are amazing!!!
DragonFire1024 said:
Please see: https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
ACM is a proprietary function mediatek uses to emulate the USB port as a different port so they can access their devices using various hosts. It's also a way for them to access the device without modifying the firmware or system. It's a clean, legit way an oem should access a device. This explains a lot of my discovery that kicked off this whole process. We could see all this happening in the HD 10 binary files, but we couldn't see how this access was happening or where it was coming from. My theory was Amazon used a back door and a mode or user ID greater than super to access devices without the use of private keys. Of course that was crazy talk and impossible and I can't blame any one of you for not believing me. I however never imagined this going beyond Amazon. I'm honestly in total disbelief that any of this is happening and even more so that my crazy cat lady theory was right from day one. I'm just greatful and honored that the few of you who didn't think I was crazy, took it to the next level. If it weren't for all of you, my theory would have been buried and forgotten. In the 3 years since I started all this I never imagined it would come to this. All of you are amazing!!!
Click to expand...
Click to collapse
ACM isn't a proprietary function from mediatek. TtyACM is typically used for modem-devices, but in the end it's just a serial-connection.
And the ACM you are enabling using this command has nothing to do with the ACM of the BOOT-ROM.
Also this has nothing to do with amazon or backdoor-keys or any super user access.
It is an exploit of the mediatek boot-rom which is part of the SOC and cannot be changed.
They are totally different things.
DragonFire1024 said:
Your PC will light up like a christmas tree with new drivers for the tablet. If it does, then the chances are VERY high that you will be able to root and unlock your fire 7.
Click to expand...
Click to collapse
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
whattheclap said:
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
Click to expand...
Click to collapse
If device is running FireOS 5.3.1 or lower it can be rooted via software hack. Otherwise, you'll need to crack open the case and play the pin shunt game.
whattheclap said:
Does that mean the 2015 Fire 7 in (5th gen) may be able to be rooted? If so, do we have to do the thing where the back of the tablet needs to be opened and the pins have to be grounded?
Click to expand...
Click to collapse
Davey126 said:
If device is running FireOS 5.3.1 or lower it can be rooted via software hack. Otherwise, you'll need to crack open the case and play the pin shunt game.
Click to expand...
Click to collapse
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
bibikalka said:
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
Click to expand...
Click to collapse
Would this work on the Austin?
Pix12 said:
Would this work on the Austin?
Click to expand...
Click to collapse
Yes it already does. A bit limited by the current low knowledge of the hardware but it will improve with time
and some software tool to help less skilled people avoid to have to do with a soldering iron and/or disarm the tablet.
.:HWMOD:.
hwmod said:
Yes it already does. A bit limited by the current low knowledge of the hardware but it will improve with time
and some software tool to help less skilled people avoid to have to do with a soldering iron and/or disarm the tablet.
.:HWMOD:.
Click to expand...
Click to collapse
Oh nice, so this could lead to a bootloader unlock for both Fire 7s?
bibikalka said:
Don't have to open the case! Need to start by bricking with 5.0.1 sideload, then you can talk to 5.0.1 preloader as in here:
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671
It'll be bricked with 5.0.1, but preloader with get into Bootrom via a button push, and that's all you need.
Click to expand...
Click to collapse
Well that's an interesting approach and one I would not advise to the faint of heart. That said, it's probably the path I'd pursue on a personal device that I would be willing to sacrifice. Advantages of 5.0.1 bootloader outweigh other considerations in my world where simplicity, stability and minimal maintenance outweigh redirected blood flow.
Davey126 said:
Well that's an interesting approach and one I would not advise to the faint of heart. That said, it's probably the path I'd pursue on a personal device that I would be willing to sacrifice. Advantages of 5.0.1 bootloader outweigh other considerations in my world where simplicity, stability and minimal maintenance outweigh redirected blood flow.
Click to expand...
Click to collapse
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
k4y0z said:
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
Click to expand...
Click to collapse
It can need a paper clip and opening the device as well.
"With older preloader-versions you can then simply hold the left volume-button while pluging the device in.
If you have a newer version, you will have to open the device and remove the metal-shielding (it is clipped on)"
k4y0z said:
Why not advice? Definitely safer than opening it up and poking around with a paperclip
But sure, if you have a rootable OS and that's all you desire both methods aren't for you.
That said the tablet is now basically unbrickable
Click to expand...
Click to collapse
Most of my varied devices are bootloader unlocked which affords full control over hardware and flexible recovery from all but the most aggregious flubups. Not my first stroll through the turnip patch. That slobber lined path is far removed from experiences of the common user. Intentionally bricking a working device is not guidance I would give lightly during the early stages of exploit exploration. Same goes for blindly probing around the circuit board with metal objects. Die hards will eagerly take the plunge regardless of risk and share their experiences, good and bad, with the community. Tip of the hat to those bold adventures. Only after the liabilities and rewards are fully understood would I reconsider guidance for non card carring members of the geeks-r-us society. Seen plenty of noobs go down in flames naively following supposedly 'easy' instructions to nirvanaville.
Simply put .... a suggestion for the novel user poking around in the hardware is enough as a sign of being helpful.
Why should we insist trying to make them stay away from the world of electronics ?
I just suggest to start using a resistor about 1kohm when shorting test points or pads on the motherboards working from 3V to 5V.
This gives them a minimum margin of safety and potentially avoid or makes it less probable they burn some components on the PCB.
Later on they can try to lower that resistor value to a value from 100ohm to 200ohm if they didn't had the expected results and retry.
Many will burn some of their stuff, yeah ... why not, they are used to it. They paid for it and deserve to do what they want with it.
My view though, everybody has the right to express different point of view.
.:HWMOD:.
hwmod said:
Simply put .... a suggestion for the novel user poking around in the hardware is enough as a sign of being helpful.
Why should we insist trying to make them stay away from the world of electronics ?
I just suggest to start using a resistor about 1kohm when shorting test points or pads on the motherboards working from 3V to 5V.
This gives them a minimum margin of safety and potentially avoid or makes it less probable they burn some components on the PCB.
Later on they can try to lower that resistor value to a value from 100ohm to 200ohm if they didn't had the expected results and retry.
Many will burn some of their stuff, yeah ... why not, they are used to it. They paid for it and deserve to do what they want with it.
My view though, everybody has the right to express different point of view.
Click to expand...
Click to collapse
Agree with all the above including the sensible cautions. If one understands the basic function of an electrical resistor and the units involved then there is probably both interest and knowledge to proceed. Now we've addressed the 5% club I submit the rest should stay on the sideline until more is known. Same for the brink-n-revive suggestion that started this exchange. I hold no power over what individuals do with their devices. I can only provide guidance based years of experience that extends well beyond hand held gizmos.
Davey126 said:
Agree with all the above including the sensible cautions. If one understands the basic function of an electrical resistor and the units involved then there is probably both interest and knowledge to proceed. Now we've addressed the 5% club I submit the rest should stay on the sideline until more is known. Same for the brink-n-revive suggestion that started this exchange. I hold no power over what individuals do with their devices. I can only provide guidance based years of experience that extends well beyond hand held gizmos.
Click to expand...
Click to collapse
I agree with both of you, all I'm saying is for those who have made up their mind and want to do this, I think bricking intentionally and then using the exploit is the safer route, since it's a software-only solution.
With poking around on the mainboard there is more things that could go wrong, I've seen people shorting VBAT to ground.
Pix12 said:
It can need a paper clip and opening the device as well.
"With older preloader-versions you can then simply hold the left volume-button while pluging the device in.
If you have a newer version, you will have to open the device and remove the metal-shielding (it is clipped on)"
Click to expand...
Click to collapse
It's going to cost you .... You can make a hole like me with a knife but I do not recommend it ...
ITS SOLDERED ON! In Austin