Can I unlock my Charmer to have more memory (EXT_ROM) i unlocked ext_rom but it is only 7MB capacity, can i have more space in extended rom?
Charmer (black face) and big storage are not related. First of all, identify your phone, be sure that it is not a Magician (silver face).
7MB for the Ext Rom is about right, you can't do much about it.
my phone is: (PL ERA) MDA COMPACT II.
My second problem : I can't backup ROM to a SD card:
Code:
Cmd>r2sd all
***** user area size = 0x77E0000 Bytes
R2SDBackup() - Download type = 6
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
Cmd>
I unlocked SIMLOCK (other card works) but bootloader looks locked, is there any solution for this?
cid unlock?
i tried unlock with awizard and nothing help.
Code:
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occurred
result=80072746
[11:47:10,82] Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
cid may be locked... :/
how i can unlock cid, and solve this error?
----
And 7MB is everything?? no more can unlock?
hi....
my treo 750 hang in start up, when powring on, just the keypad blink for 1
second and turn off, nothing appears on the screen, it appear that it is a
software problem.
to more explain, the phone connect with pc (active sync), but no light in led
when it connected or when i put charger
i try hard reset even zero reset but nothing happened, the problem persist
please some some help me to solve this problem by flash or any solution
plz i need your help
beleive me that i have 5 or 6 days from forum to an other, and the best is xda-developpers, but still now i can't solve my problem.
i have a black screen, with keypad blinking for one second, i try all reset types, i try with mtty ( here the log)
USB>set 14 0
Write Nand Success
HTCST ÚÈÒHTCEUSB>task 28 55aa
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 396
Storage Total block: 548
Total Bad Block in CE: 0
NeedToEraseBlockStart: 409
Storage format success
USB>
USB>checksum
USB>checkimage
IPL CRC checksum = 0xB6279C39
SPL CRC checksum = 0xA8949466
CE CRC checksum = 0xBB96F079
ExtROM CRC checksum = 0x733B2EDA
Radio Image CRC checksum = 0xA43F6FA4
USB>task 0
USB>
------------------------------------------------------
after mtty my phone is always dead, i don't make any flash because i don't know how, and i can't try sd install because the screen is black.
i don't understand task 2a and how to do, if possible give me the procedure
and a tuto for all operations
regards
Hi,
I bought a new Galaxy S6 (SM-G920F) few days ago. It starts to freeze and reboot randomly during the day (about 1 time for hour) without a reason.
I tried to factory reset but in vain.
The seller told me yesterday that he can not replace it because there are no evident defects and I have to address my problem to samsung assistance (what the f..k... less than 1 week and I have to contact the manufacturer service).
Meanwhile, my new smartphone keeps rebooting and today is saturday, so I have time to try to understand the problem.
Any ideas?
Is it possible that through a system log I can get information about the problem?
Thanks in advance for the help.
mystreetspirit said:
Hi,
I bought a new Galaxy S6 (SM-G920F) few days ago. It starts to freeze and reboot randomly during the day (about 1 time for hour) without a reason.
I tried to factory reset but in vain.
The seller told me yesterday that he can not replace it because there are no evident defects and I have to address my problem to samsung assistance (what the f..k... less than 1 week and I have to contact the manufacturer service).
Meanwhile, my new smartphone keeps rebooting and today is saturday, so I have time to try to understand the problem.
Any ideas?
Is it possible that through a system log I can get information about the problem?
Thanks in advance for the help.
Click to expand...
Click to collapse
A log cat definitely could help in diagnosing a problem. Also, boot into safe mode. If the problem does not show up in safe mode you know it is caused by a third party app. Those are the first two things you should do
Snowby123 said:
A log cat definitely could help in diagnosing a problem. Also, boot into safe mode. If the problem does not show up in safe mode you know it is caused by a third party app. Those are the first two things you should do
Click to expand...
Click to collapse
Ok, log cat is a new thing for me.
I'm trying to use aLogcat app directly from the device.
But it seems that when the freeze+reboot occurs all the log restarts after the reboot... probably I'm doing something wrong, how should I do?
mystreetspirit said:
Ok, log cat is a new thing for me.
I'm trying to use aLogcat app directly from the device.
But it seems that when the freeze+reboot occurs all the log restarts after the reboot... probably I'm doing something wrong, how should I do?
Click to expand...
Click to collapse
Use adb. An adb log cat can be performed during a boot loop. The applications that preform log cats are usually far easier to use, however they will not preform during a boot loop. If you preform it correctly and post it here, the community can point you in the right direction. There is a thread somewhere in the xda forums that explains how to perform a log cat. Don't remember where though
EDIT: I found the threaad I was referring to. I will post it below!
http://forum.xda-developers.com/showthread.php?t=2274119
Been having the exact same issue... with my new gs6, it hangs and then poooff it reboot after a while( maybe after 1min ) . My personal diagnosis, this is due to poor ram management, all the ram is consumed which cause this crappy thing to reboot... btw my gs6 is dual sim one (SM-G920FD)...
Snowby123 said:
Use adb. An adb log cat can be performed during a boot loop. The applications that preform log cats are usually far easier to use, however they will not preform during a boot loop. If you preform it correctly and post it here, the community can point you in the right direction. There is a thread somewhere in the xda forums that explains how to perform a log cat. Don't remember where though
EDIT: I found the threaad I was referring to. I will post it below!
http://forum.xda-developers.com/showthread.php?t=2274119
Click to expand...
Click to collapse
Ok! Thank you!
Now I have a txt logcat until the reboot and disconnection, these are the last lines:
Code:
10-19 12:33:28.371: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.381: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.381: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.381: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.391: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.391: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
10-19 12:33:28.391: D/ActivityManager(3522): retrieveServiceLocked(): component = null; callingUser = 0; userId(target) = 0
: E/(): Device disconnected
what exactly should I look for in the log file?
Second freeze and reboot:
Code:
10-19 12:57:58.522: D/SSRM:n(3528): SIOP:: AP = 310, PST = 301 (W:28), CP = 258, CUR = 237, LCD = 47
10-19 12:57:59.792: V/AlarmManager(3528): waitForAlarm result :4
10-19 12:57:59.992: V/AlarmManager(3528): waitForAlarm result :8
10-19 12:58:00.002: D/KeyguardUpdateMonitor(3726): received broadcast android.intent.action.TIME_TICK
10-19 12:58:00.002: I/PERF(3726): received broadcast android.intent.action.TIME_TICK
10-19 12:58:00.002: D/KeyguardUpdateMonitor(3726): handleTimeUpdate
10-19 12:58:00.022: D/SecKeyguardClockView(3726): onTimeChanged() : mShouldShowDualClock - false, isDualClockSet() -false
10-19 12:58:00.042: D/SecKeyguardClockView(3726): mTimeZone:null, hour:0, isShortMaxWidth:true
10-19 12:58:00.052: D/[zero daemon](3838): {[C6B53529A4E9A61B6E9DFAC2EC352F35413B8423020D39F21C4F88CE3B9B87CFDCC0B81B0A5ED41F6DFA9549B8ADE1F4BACF4D40B7B8E99052DE9FA88E767D1DEF99F3B50EBB0BE2EA7D97147503802808B0F46342E4D32B53ACCA63815BEAA3E6A19B15B6D34AFADF3249A820F62444]}
10-19 12:58:00.052: I/[zero daemon](3838): {[A32E1AC369E42B6168CFC8ECFBFA9951C42133C77ADF9B218D854990F6269E392BB582333EA1FB9A3DD83C292BF89A20]}
10-19 12:58:00.072: D/SecKeyguardStatusUtils(3726): regionalDateFormat = 22/11/3333 isRTLlanguage = false returnDateFormat = E d MMMM
10-19 12:58:00.092: D/DateView(3726): regionalDateFormat = 22/11/3333 isRTLlanguage = false returnDateFormat = E d MMMM
10-19 12:58:00.102: D/DateView(3726): regionalDateFormat = 22/11/3333 isRTLlanguage = false returnDateFormat = E d MMMM
10-19 12:58:00.102: D/DateView(3726): regionalDateFormat = 22/11/3333 isRTLlanguage = false returnDateFormat = E d MMMM
: E/(): Device disconnected
Here the logs, some seconds before the reboot:
http://pastebin.com/E0VqnyU7
http://pastebin.com/KR7mjMBn
Any ideas?
mystreetspirit said:
Here the logs, some seconds before the reboot:
http://pastebin.com/E0VqnyU7
http://pastebin.com/KR7mjMBn
Any ideas?
Click to expand...
Click to collapse
I personally don't understand what most of it says. Your logcats seem to show very few errors.
Most of what is written in the logcat appears to be normal processes.
I know that someone with greater knowledge than me could give more insight
I have the same problem.
Any fixes anbody?
Louizzz said:
I have the same problem.
Click to expand...
Click to collapse
jakovs said:
Any fixes anbody?
Click to expand...
Click to collapse
Update it via Smart Switch.
Did any of you had a theme instalIed while issue occured. I noticed it didnt happen since i switched back to original theme. It's too early to tell but maybe that was the problem.
@jakovs: I tried to switch to original theme and for about 6 hours it was good, but then this issue again happened - freezing and restarting.
Maybe someone else have other solutions how to fix that? I went to shop(official samsung dealer) where I bought phone and they said that lot of people were complaining about that and they sent their phones to warranty, but they have been returned with explanation that it is because of software (update), so I don't want to wait 15 days to get answer that I need wait for update.
Also tried factory reset + wipe cache partition - my phone also freezed right after factory reset on setting my phone up ;
It also freezed a couple times on Android boot menu - it can be related to android version also or then it is hardware issue?
My phone was also freezing and rebooting in safe mode and in every other situation. I also thought it was a hardware problem. Maybe a water damage, but since I switched to orginial theme it didnt happen. I hope you'll sort it out.
Sent my phone to warranty. If it will continue to happen, will reflash stock rom and if it would not help, then will ask for money back and will take Nexus 5X.
Same problem Here!!! Any Fix guys?
I asked to change my phone and it solved the issue. New one works perfectly with same setup.
I have the same problem, i think that's some problem related with the apps installed, the problem started after the Spotify updated, after removed the app stopped to totally freeze the phone, but I have some restarts, I've read a lot and find a lot of problems like, I will wait one more day without Spotify, if the problem happens again, i will send to the warranty. I've already tried a factory reset, cache and data reset. The problems seems to be started on 02/12~03/12
I have other problems with the phone, like lines one the screen when the bright is at maximum, but since I've read it's a trade off of amoled display.
Testers wanted: Anyone who uses this method, let me know if you can access stock recovery after this method.
Summery
Thanks to the amazing work by our active member @bibikalka, a method was found to unbrick these devices Thread link here. The method he found was slightly tedious for some people, so I've decided to put together a Linux iso that you can boot into on your computer with everything you need to get your device running again. It uses the same methods proposed but makes things easier. This comes with all the necessary drivers, scripts to do everything you need, all the img files needed to flash, a hex editor for advanced users, and more. Before the scripts included in this OS, determining the option (A, B, or C) to take in order to unbrick the device required .part files to be evaluated manually. Now with the custom script, it can quickly evaluate what option to take.
Video Instructions
Brief Instructions
1. Download the Linux iso:
Linux ISO
2. Burn the iso to a USB drive or cd
3. Boot into the operating system
4. Type "root" at the login prompt
5. Right click on the desktop and choose file manager. Go to "aftv2-tools" folder
6. Right click on file manager and press "open in terminal"
7. From device turned off, enter command "./handshake.py", then plug in device. You may need to do this a couple times to get a connection. Try pressing volume keys & power etc to get it connected. See video if you have problems
8. After handshake is complete, run "./reader.sh"
9. After all addresses are read in, run "./determineOption.sh". You should get back a result of A, B, or C
10. Depending on the option returned (A,B,or C), run "./readerSpecialOptionA.sh", "./readerSpecialOptionB.sh", or "./readerSpecialOptionC.sh". This is an optional step but may be useful if you want to back up part files or their were no options available. Back up part files to a usb drive if you want to be safe.
11. Now the actual unbricking. Run "./unbrickOptionA.sh", "./unbrickOptionB.sh", or "./unbrickOptionA.sh" depending on your option. This can take about 40 minutes
12. hold volume up and run "./complete.sh" at the same time to get into TWRP
13. boot into your default operating system on your computer
BE VERY CAREFUL FROM NOW ON
13. We will be installing Fire OS 5.3.1. If you are not installing this ROM, make sure you know what you are doing. Download the ROM:
update-kindle-20.5.5.2_user_552153420.bin
14. Download 5.4.1_1133_stock_recovery_uboot.zip: 5.4.1_1133_stock_recovery_uboot.zip. Without this you could turn your device into a paperweight. This installs stock recovery and a uboot version that MUST be installed. This file was taken from the thread here: how-to-upgrade-to-lollipop-root-gapps
15. Rename the ROM extension from .bin to .zip
16. Transfer the two files to the Fire
17. Do a factory reset. Flash the ROM and uboot&recovery file
18. Reboot! Your device should now be working. It will take about 15 mins to boot up.
Big thanks to @bibikalka for helping work everything out and for the initial unbrick method.
Edit 10/13/21: Fixed Google Drive Link
Linux ISO Changelog
Updated 10/5/16:
*Optomized scripts
*Added "complete.sh" This reboots the device
Updated 9/27/16:
*Added script to auto-detect which unbrick option to use (determineOption.sh)
*Added scripts to write img files to correct addresses ( unbrickOptionA.sh, unbrickOptionB.sh, and unbrickOptionC.sh)
*Added scripts to read in and label part files (readerSpecialOptionA.sh, readerSpecialOptionB.sh, and readerSpecialOptionC.sh)
*Nemo open in terminal fixed
*.part files set to open with ghex by default
Updated 9/24/16:
*Nemo as default file manager
*Updated html page with instructions from forum
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
gascomm said:
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
Click to expand...
Click to collapse
great to hear! I hope everything works for you! After you get everything done, can you check if you can get into recovery.
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
gascomm said:
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i be tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
Click to expand...
Click to collapse
Good to hear everything is working. Ya TWRP does not work with 5.x bootloader. Good to hear you can get into stock recovery because I had some incidents where I could not get into it. Thanks for responding. The only custom ROM ATM is CM13.
powerpoint45 said:
The only custom ROM ATM is CM13.
Click to expand...
Click to collapse
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
gascomm said:
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
Click to expand...
Click to collapse
I meant to say CM11. This guide is probably one of the best http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page1
This is a bit older one: http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351/page1
In order to have TWRP, you must have a 4.x bootloader so CM11 would work with it.
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
gascomm said:
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
Click to expand...
Click to collapse
sweet!!!
PRInCEI7 said:
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
Click to expand...
Click to collapse
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
nai1ed said:
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
Click to expand...
Click to collapse
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Confused
First you say it should be OK to downgrade:
powerpoint45 said:
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Click to expand...
Click to collapse
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
Code:
[[email protected] aftv2-tools]# ./handshake.py
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
[[email protected] aftv2-tools]# ./reader.sh
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^Z
[1]+ Stopped ./reader.sh
[[email protected] aftv2-tools]# kill %1
[[email protected] aftv2-tools]#
[1]+ Terminated ./reader.sh
[[email protected] aftv2-tools]#
The above is for a 4th gen HD7 with this device showing in 'lsusb':
Code:
Bus 001 Device 006: ID 0e8d:3000 MediaTek Inc.
powerpoint45 said:
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Click to expand...
Click to collapse
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
draxie said:
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader?
Click to expand...
Click to collapse
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
draxie said:
First you say it should be OK to downgrade:
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
The above is for a 4th gen HD7 with this device showing in 'lsusb':
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
Click to expand...
Click to collapse
My understanding is that you only need to worry about bricking if You are downgrading to another lollypop ROM. We found out that the device has a fuse that is set in later lollypop ROMs where it will check against the current version. But this check only seems to be on lollipop ROM's. As for the aftv2 protocol, you might be right but I don't know enough about that yet to know. Currently we have no unbrick method for latest bootloader. If you can get into recovery then you could sideload but most can't get into recovery during brick.
I've followed the steps but not into twrp, only screen amazon and reset. I'm not good at English
error trying to unbrick hd6
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
kingwill101 said:
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
Click to expand...
Click to collapse
You are on any version.
You can access to recovery now