Related
Hey guys,
i just started with falshing and those things. So i'm not so familiar with building and unlocking.
I bought a M2 with QUWERTY. I had and still has bootloop problems according to: http://forum.xda-developers.com/showthread.php?t=1457373
While analysing my bootproblem, i just realized, that i have a Fastboot Bootloader installed on this phone, what seems a little special.
Next step may be, to use the fastboot get this phone work, step after, use fastboot for improve this forum . But as i said, i'm new in this deep hardware near software-things, so need all your help for that .
greetz
how strange this in your bootloader, is similar as in the Atrix? So you installed it? I would like to know more about this topic
Looks like you have a dev phone. There are a couple of forum users with dev phones
Does rsdlite recognize it? I think you should try to have a look in Motorola Defy Android Development: there is a thread named ''experimental: trying to unlock the bootloader " (look at pages 60-75) .
I think someone wrote about some particular roms to be flashed in case of unlocked phones....
Does anyone know a way to extract this bootloader??
If so, I believe that lowering the fastboot and giving the command would be possible to unlock the MS2
Fastboot => http://www.mediafire.com/?2zdhukq3ha1qlrd
1) "fastboot oem unlock" to see the Station ID
2) "fastboot oem unlock ID" to unlock the bootloader
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
http://forum.xda-developers.com/showpost.php?p=21885753&postcount=735
Click to expand...
Click to collapse
djlooka said:
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
Click to expand...
Click to collapse
i think you can send PM to MKSilver.
Lutis said:
i think you can send PM to MKSilver.
Click to expand...
Click to collapse
I already did
Anyway I think the more dumps are posted, the better it is!
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
MKSilver said:
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
Click to expand...
Click to collapse
Did you tried simply wipe via moto recovery?
Or flash different sbf.
Have you tried the "fastboot oem unlock" command?
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
MKSilver said:
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
Click to expand...
Click to collapse
Well, I have bootloader 70.12. To get into BL I have 2 options:
1) arrow up
2) Camera + Volume down
Both ways leads to standard BL. Fastboot devices doesn't list my phone, just as before. I never tried to update my BL but I don't think it will do any difference.
I've tried it with bootloader 70.13.
Only option A works to get into Bootloader mode (not Fastboot).
Next "funny" fact.
While Flashing SBF with "normal" bootlaoder modus, everythings works with RSD lite.
While Flashing SBF with "fastboot" bootloader modus, I get an error after creating image files:
"Failed flashing process. Failed flashing process. Phone [0000]: Error getting subscriber unit information. Device API Error: 0xE0000042 Command: RQHW (0x0805041); phone connected"
Then is Result:"FAIL" and the phone stays in bootloader modus (fastboot).
May be I have wrong RSD lite calibration. Will investigate this, how it behaves in linux.
Ok, so googling "unsigned motorola milestone 2 SBF" turned up this as the first
Perhaps if that link is dead you could ask endless7 if he would be so kind as to re-upload it, or perhaps it is available elsewhere.
I say this because I remember reading somewhere that once it's unlocked you can only use unsigned SBF's.. pretty sure it was the bootloader unlock progress thread in the defy forums.. but I'm sure it's been said in our forums too
Just wrote a pm to Endless7. If thats true, it could help me get this device work (even in chinese) and than i can take a look forward, while using adb for example.
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
DreadPirateDan said:
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
Click to expand...
Click to collapse
Dan,
I'm not sure, but I don't think he is limited to flashing only unsigned stuff. The difference from developer phone to production phone, besides fastboot, is that the first one doesn't check signatures during boot chain. Theoretically speaking he is able to flash and boot any Milestone2 ROM he likes. I also suspect that he is able to downgrade from gingerbread to froyo, unlike us. There should be something else preventing him to boot the phone. That's just my opinion and it maybe wrong
Hey guys,
well enough is enough, bought today a second phone for the time the m2 is still dead.
I'm about to finish the defy thread today. Already learned a lot.
Well it is correct that i can flash signed SBFs. While booting into "normal" BL Mode.
But i can also boot into Fastboot and the RSD Lite Name starting with NS seems to show me something special.
So i risk something today and flash a froyo: It worked but still bootloops. The flash was successful and the M Logo turned gray.
At GB it is Red at my M2.
But now it would be great for an unsigned SBF, some more Ideas how to get it boot, or how to manipulate it over fastboot to get it work. Cause without get it into Android we can't go on analyse the bootloader.
PLZ help me. Will also ask a guy from the defy thread, who seems to know a lot about the milestone 1 and bootloaders/OMAP cpus. May he has a great idea what he wrote there was very clever and full of knowledge.
Greetz
This post is targeted at folks who have bricked their tf300t and not yet have signed this petition. As there are a lot of you guys out there and even becoming more day by day, this will hopefully gain some attention from ASUS/NVIDIA.
link to the petition: (replace (DOT) with . new users are not allowed to post links)
change (DOT) org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
To me it is ridiculous that a simple thing like replacing the recovery can brick the tablet (only twrp-2.4.4.0-tf300t-4.2.blob is compatible at the moment). What ever ASUS has done/changed in the last update has caused a lot of trouble for the unlocked community. When releasing new updates, backwards compatibility is an important factor and has to be concerned. If you agree, take your time and sign the petition as it hopefully would help.
Sincerely
A guy with a bricked tablet
vahid_shirvani said:
This post is targeted at folks who have bricked their tf300t and not yet have signed this petition. As there are a lot of you guys out there and even becoming more day by day, this will hopefully gain some attention from ASUS/NVIDIA.
link to the petition: (replace (DOT) with . new users are not allowed to post links)
change (DOT) org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
To me it is ridiculous that a simple thing like replacing the recovery can brick the tablet (only twrp-2.4.4.0-tf300t-4.2.blob is compatible at the moment). What ever ASUS has done/changed in the last update has caused a lot of trouble for the unlocked community. When releasing new updates, backwards compatibility is an important factor and has to be concerned. If you agree, take your time and sign the petition as it hopefully would help.
Sincerely
A guy with a bricked tablet
Click to expand...
Click to collapse
Link is in my sig
Am I bricked if I can still use adb reset bootloader command from the barely working twrp?
From there I can cold boot Linux and get to my operating system. Is there a fix yet? It still boots directly to non functioning twrp if I ever have to reboot the os
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
Am I bricked if I can still use adb reset bootloader command from the barely working twrp?
From there I can cold boot Linux and get to my operating system. Is there a fix yet? It still boots directly to non functioning twrp if I ever have to reboot the os
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
If it's bricked in a the true sense of the word, you would be able to do as much with it as with a... Brick
Come on guys
200 signatures and we are there.
Something new...
We all know that in the above case is bricked tablet that starts directly in TWRP ... even if we start trying to po fastboot (volume down + power) it will start directly in TWRP
Now to answer adb shell like this:
c: \ Adb> adb devices
List of devices attached
0123456789ABCDEF recovery
But if I try to send something to it (like a touchscreen driver) see the answer and receives information
c: \ Adb> adb push 02-3011-4820.ekt / data / local / tmp /
* Daemon not running. starting it now on port 5037 *
* Successfully started daemon *
1027 KB / s (32868 bytes in 0.031s)
In other words we can send information in tablets briked .. I think now matter what name send.
I have here 2 tablets bricked (tf300tg and TF300T) and 3 functional TF300T tablet (but with broken touchscreen). The point is that I do not know what commands to send, and how to pull information from functional and tablets to the tablets who have problem
Now comes my question logic ... We can not copy anything from a 100% functional tablet and send this information to a tablet briked?? Can only boot, or recovery?
Br
Mihnea
Almost there
Come on people we only need 75 more signatures.
Hello
I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.
Now bootloader is unlocked and starts straight into TWRP.
At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.
I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way
Does anyone else have a procedure that can be repaired?
And that since the corect connection mode that allows me to write on tablet via fastboot ?
I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.
BR
Mihnea
I wait with many interes your sugestions.
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
mihnea_gsm said:
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
Click to expand...
Click to collapse
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
mihnea_gsm said:
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
Click to expand...
Click to collapse
Man, if you would have read , you would have known not to use the wipe tab. As I said before, there are threads all over the place in here stating NOT TO USE THAT WIPE OPTION. You may have done SOME research but you didn't do enough on THIS tablet. The research on all the other devices you know about doesn't count. LOL It's TF300 series we're talking about.
Oh, and you said for me not to take offense because I think you're wrong. Bro, I don't take offense because you disagree with me. I'm just trying to get you to man up and admit that you made the mistake and didn't do enough reading. LOL
quidrick said:
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
Click to expand...
Click to collapse
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Moe5508 said:
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
Click to expand...
Click to collapse
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Click to expand...
Click to collapse
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
Man you are right 100% wipe buton from asus MUST BE - wipe data from recovery (twrp) but I thing that twrp team is not agree with us...
Most important for me in this moment like other people I want to make table tablet alive....
BR
Mihnea
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
You guys aren't getting my point at all. I'm not saying that the wipe data option screwing people's tablets up is right. All I'm saying is that the info is here in this forum saying not to do it. Lol If the time is taken to read the info in these threads we wouldn't even have this thread. :thumbup:
If myself and all the other people have been able to find this information and avoid tapping the wrong wipe data option then so should other people. THAT IS MY POINT.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
At this point it really does not matter who is and who is not, right ... matter to be able to start and run ok tablets ...
So I expect all of which can give you an idea
BR
Mihnea
This is a question for developers more familiar with our partition layout. My working knowledge of android is limited, but I do have background in linux. If he can see his device under ADB, shouldnt it be possible for someone to do an adb pull of their system, data, bootloader, and recovery partitions for him to push to his?
The only reason I could think of that not working is if the wipe option deletes the entire partition table and they need to be repartitioned from scratch. Its either that or the Bootloader partition is getting wiped instead of the Data partition. Just bouncing ideas in my head here. It was on a kyocera zio and on gingerbread, but this was one way I was able to help restore a device.
NVflash seems capable of repartitioning the drive........ Does adb have commands to set up partitions as well?
One would also think odin should be able to help with repartitioning. There has to be a way.
-Edit-
Ok so if you DO have fastboot, you might be able to recover. Read this post !
http://forum.xda-developers.com/showthread.php?t=2236885
Something new...
We all know that in the above case is bricked tablet that starts directly in TWRP ... even if we start trying to po fastboot (volume down + power) it will start directly in TWRP
Now to answer adb shell like this:
c: \ Adb> adb devices
List of devices attached
0123456789ABCDEF recovery
But if I try to send something to it (like a touchscreen driver) see the answer and receives information
c: \ Adb> adb push 02-3011-4820.ekt / data / local / tmp /
* Daemon not running. starting it now on port 5037 *
* Successfully started daemon *
1027 KB / s (32868 bytes in 0.031s)
In other words we can send information in tablets briked .. I think now matter what name send.
I have here 2 tablets bricked (tf300tg and TF300T) and 3 functional TF300T tablet (but with broken touchscreen). The point is that I do not know what commands to send, and how to pull information from functional and tablets to the tablets who have problem
Now comes my question logic ... We can not copy anything from a 100% functional tablet and send this information to a tablet briked?? Can only boot, or recovery?
mihnea_gsm said:
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Click to expand...
Click to collapse
Have the same problem...
fastboot stock at < waiting for device >
my device boot/reboot or power on without any touch....always boot into recovery twrp ( but can´t mount and do nothing)
Any help?
Boot your tablets up into the selection screen where you can select to wipe data, fastboot, recovery or load OS. If you have updated your bootloader and firmware to 4.2 then the fastboot option disappears and now you are already in fastboot mode when when you load the selection screen. All you will need to do is plug the USB cable into your tablet and your computer will recognize this and load the ADB interface. Btw if your having problems with TWRP 2.5, simply flash back to 2.4.4.0.. which is exactly what I did.
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
anaschillin said:
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
Click to expand...
Click to collapse
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
bwiberg said:
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
Click to expand...
Click to collapse
OK .. to start over ... I had Asus tf 300TG firmware version 4.1.1 and I did the OTA update to 4.2.1. After that I put some revovery TWRP 2.5.0.0 (most probably was not what I had) and broke the tablet.
Now my tablet is in this variant:
C: \ adb> adb devices
adb server is out of date. killing ...
* Successfully started daemon *
List of devices attached
0123456789ABCDEF recovery
But after I want to flash blob
C: \ adb> fastboot flash system's 0x0B05 blob
<Waiting for device>
You say that I should write: openrecovery-TWRP-2.5.0.0-TF300T tablet-4.2.blob as did the OTA update to 4.2.1 right?
* But in this moment I realize WHY I broke the tablet ... because I wrote this file: openrecovery-TWRP-2.5.0.0-tf300tg-JB.blob ...
Why I wrote this? because if you look here: http://techerrata.com/browse/twrp2/tf300t he write: If you have the 4.2 official update, choose one of the files that ends with -4.2. If you choose the wrong file you may brick your tablet.
* THIS FILE NOT EXSIT: openrecovery no-TWRP-2.5.0.0-tf300tg-4.2.blob .....exist only for tf300t not for tf 300tg
I write a post at twrp blog : http://www.teamw.in/project/twrp2/97
* Now see another file: openrecovery-TWRP-2.5.0.0-TF300T-JB.img .... what to do with this file?
OK and now...
What should I do? which file should I write?
And how (mode - fastboot, apx ???) should be the tablet to write the file?
And who would command if the tablet would be in that mode (fastboot, apx)
BR
MIHNEA
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
I have nothing to do with twrp and certainly am no dev.
What I do know is the partition for recovery is a limited space and there is not enough room to emulate stock recovery and still have enough space to provide for the way we use twrp.
The "factory reset" recommended by Asus is located in settings. This is "wipe data" located in the bootloader. I have not heard or read of Asus suggesting use of wipe data but I have seen factory reset.
Now I don't believe in flaming anyone!
Explaining a mistake is positive, it helps the user know what not to do in the future but only if presented properly.
I'm sure the reply came from frustration of wanting to help but understanding that recoveries from wipe data are few.
No one wants to see a brick!
Sorry for taking space without providing any help for the OP!
If anyone has any suggestions for the OP please present them.
I was so slow posting I see help has arrived.
ok i know i didn't follow instructions i've been deep into this for about a week now and just got mad and wanted a fresh start. So this is where I am. Katkiss 7.1 twrp 3.2 i have a recovery. and I don't have a screenshot of the bootloader number but at this point im sure it doesn't matter since the tablet will only tell me the device is unlocked and its stuck there. I can use power and vol up to make my pc see an apx but beyond that im lost. i have been searching for hours and I just don't see the answer on my own i have minimal adb fastboot installed and all i can make it do is
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
please let me know what to do. this all started because linux deploy said my kernel was too old and i for the life of me could not update it and became more and more frustrated till i made a really stupid mistake thanks in advance
bud2002 said:
ok i know i didn't follow instructions i've been deep into this for about a week now and just got mad and wanted a fresh start. So this is where I am. Katkiss 7.1 twrp 3.2 i have a recovery. and I don't have a screenshot of the bootloader number but at this point im sure it doesn't matter since the tablet will only tell me the device is unlocked and its stuck there. I can use power and vol up to make my pc see an apx but beyond that im lost. i have been searching for hours and I just don't see the answer on my own i have minimal adb fastboot installed and all i can make it do is
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
please let me know what to do. this all started because linux deploy said my kernel was too old and i for the life of me could not update it and became more and more frustrated till i made a really stupid mistake thanks in advance
Click to expand...
Click to collapse
well i have continued to research and all i have found says that unless i have an nv flash back up im screwed... Is this true and now i essentially have a paperweight?
maybe
bud2002 said:
ok i know i didn't follow instructions i've been deep into this for about a week now and just got mad and wanted a fresh start. So this is where I am. Katkiss 7.1 twrp 3.2 i have a recovery. and I don't have a screenshot of the bootloader number but at this point im sure it doesn't matter since the tablet will only tell me the device is unlocked and its stuck there. I can use power and vol up to make my pc see an apx but beyond that im lost. i have been searching for hours and I just don't see the answer on my own i have minimal adb fastboot installed and all i can make it do is
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
please let me know what to do. this all started because linux deploy said my kernel was too old and i for the life of me could not update it and became more and more frustrated till i made a really stupid mistake thanks in advance
Click to expand...
Click to collapse
wow i feel like i am talking to myself... so I now see that its done but as a last ditch effort if anyone has a backup nvflash with tf700t katkiss 7.1 boot10.4.2 (im 90% on that) twrp 3.2.1 i would love a chance to download it and try it out, and if no one has that I'll take the next best thing then I'll probably get a new MB from amazon and return the broken one haha unless someone has a suggestion for another 10" tablet i can dual boot linux and drroid. Linux is actually way more important. The ultimate goal is to make it a remote for my above average intelligence home. bluetooth and microphone are a must work so i can put alexa on it. i guess while I ask for possible suggestions I cou;d use a 7" too well thanks hopefully this will work out.
bud2002 said:
wow i feel like i am talking to myself... so I now see that its done but as a last ditch effort if anyone has a backup nvflash with tf700t katkiss 7.1 boot10.4.2 (im 90% on that) twrp 3.2.1 i would love a chance to download it and try it out, and if no one has that I'll take the next best thing then I'll probably get a new MB from amazon and return the broken one haha unless someone has a suggestion for another 10" tablet i can dual boot linux and drroid. Linux is actually way more important. The ultimate goal is to make it a remote for my above average intelligence home. bluetooth and microphone are a must work so i can put alexa on it. i guess while I ask for possible suggestions I cou;d use a 7" too well thanks hopefully this will work out.
Click to expand...
Click to collapse
If you cannot get into the bootloader or recovery you are indeed hard bricked. Somebody else's nvflash files won't help you either because they are device specific (and have nothing to do with rom or recovery btw). Your best option is to get a new mobo and pray that you will be able to unlock the bootloader... Mismatched serial number and hardware ID prevented many from unlocking in the past.
Another idea: look for a used 700 that is already unlocked and canabalize the tablet in worse condition
berndblb said:
If you cannot get into the bootloader or recovery you are indeed hard bricked. Somebody else's nvflash files won't help you either because they are device specific (and have nothing to do with rom or recovery btw). Your best option is to get a new mobo and pray that you will be able to unlock the bootloader... Mismatched serial number and hardware ID prevented many from unlocking in the past.
Another idea: look for a used 700 that is already unlocked and canabalize the tablet in worse condition
Click to expand...
Click to collapse
I could have sworn I read over in transformer forums that a guy used your 300 nvflash with success and then messed up somehow I was half asleep at that point
bud2002 said:
I could have sworn I read over in transformer forums that a guy used your 300 nvflash with success and then messed up somehow I was half asleep at that point
Click to expand...
Click to collapse
I never owned a 300, so I doubt that, but you're welcome to my nvflash blobs if you want them. I can upload them for you later tonight
if its not too much trouble it will give me something to play/fight with till i find a replacement next week thanks
berndblb said:
I never owned a 300, so I doubt that, but you're welcome to my nvflash blobs if you want them. I can upload them for you later tonight
Click to expand...
Click to collapse
bud2002 said:
if its not too much trouble it will give me something to play/fight with till i find a replacement next week thanks
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=746010030569954796
Good luck and let us know how it goes
Thank Craigslist
Just found atf700t for $60 with keyboard and charger intact. only a few blocks from me that I’ll puck up in the am
When booting into the bootloader, hold the volume minus button down, then continue to hold it down when pressing the power button. Do not release pressure on the volume minus button until it boots into the bootloader screen.
NP
flashed from graphene os and back to stock during stock flashing something failed and gives me a black screen and goesinto the screenshot provided
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
JohnC said:
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
Click to expand...
Click to collapse
it wont work , that is what caused the issue, there is no adb or fasboot commands as the phone has nothing to load or read, it was flashing the official latest stock firmware using the flash-all.bat, then after the first rebbot and waiting for devices it goes to a black screen and shows what i put in the screen shot,(i believe the battery died during flashing) there is two modes it goes into the qusb which is the qualcomm download mode and some other mode i cant tell neither can the pc device find drivers to read the phone, techinically this phone is not fixable using normal methods , but i believe there is a way to flash to firmware back on,i have looked into using edl and qspt flashing but it still doesnt read the phone, any help would be greatful i have device protection but they are sending me a refurbished phone i would rather try to fix this before i do get the replacement, as it was a new and working device
i have been able to find a working qualcomm driver is there anyway to edl or msm file for the pixel 4a to fix this, now that the phone is being read properly it should be able to take commands as it is reconized as a modem driver or port
Any Ideas Why Its Failing , says sahari protocal failed
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
miko12312 said:
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
Click to expand...
Click to collapse
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
vabeachboy0 said:
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
Click to expand...
Click to collapse
I believe Qualcomm is the ones that obtain these files not Google , only other way is to dump the files from download mode on a working device
I'd like to help by dumping the required files, I didn't know anything about EDL before doing research for this thread, but as I understand using EDL mode require a device-specific non-free "loader".
I'm trying to use B. Kerler's EDL tool (https://github.com/bkerler/edl) but fail because it doesn't have the proper loader file in its database.
If anyone come across the loader for the Pixel 4a (000e60e10066000a_3ef72a02fb931be1_fhprg.bin), I'd be happy to share boot and memory dump from my phone.
I encountered the same situation as you, did you solve it?
Older thread I know, but I've used EDL mode (on LG phones) to save partitions and write partitions.
But you have to have a 'programmer file' for the specific device for it to work. Aka a 'firehose' file for the specific device / chip.
Some mfg's make this available, some don't. Google does not. So, even having the file(s) you want to flash won't help, not if you don't have the firehose file.
sorry, cheers
Has anyone figured this out? Could really use some help. Thank you
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
mizzunet said:
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
Click to expand...
Click to collapse
Only suggestions are the go to software of choice,, pixel flasher or android flash tool, both need bootloader unlocked
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
mizzunet said:
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
Click to expand...
Click to collapse
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
hammered58 said:
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
Click to expand...
Click to collapse
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
mizzunet said:
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
Click to expand...
Click to collapse
I will second that, unfortunately I don't think it's possible, at least not that IAM aware of