Related
!!Check out the Video on how it works!!!
http://www.youtube.com/watch?v=ZANt0vaiZYs
[Disclaimer]:
The method of rooting your Android device as described below is solely by your choice and your choice only!
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
I, XDA, and other forum members claim no liability for any harm that may come to your device, including, but not limited to: bricked phones, voided manufacturer warranties, bootloops, loss of data, etc
While generally this software is safe, and does have fail safe and error checking, it does not mean that something can/shell/or will not go wrong. Please be prepared if it does.
[/Disclaimer]
[Information]:
Device Supported:
MZ600 VZW 3G/4G
Software Supported:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
Method Used:
Fastboot oem unlock
Unsecured boot.img for device software.
Features:
Fast and easy 1 click root method for supported sw.
Error checking to prevent mistakes as much as possible.
Takes 5-8 Mins to Unlock/Root device.
Install's SU and Superuser.apk
Detects Software version to version selected, helps install correct files needed.
Other Information:
This will WIPE ALL USER DATA.
Tested with:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
I have personally restored to all three version's of the software and tested root and unlock on all software version's. This should/will work as long as you follow instructions. Its really not hard, and its hard to mess up.
[/Information:]
I know there is just a WIFI Version and I will add support later. It will auto detect you're phone mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[DOWNLOAD LINK HERE]
Download Here DO NOT POST ON OTHER FORUMS IF ITS POSTED ON OTHER FORUMS I WILL REMOVE LINK AND STOP SUPPORT THIS IS FOR XDA ONLY!
Download Unroot_tools, please extract into the unroot_tools folder.
If you use this software please leave feedback.
Supported Devices:
US VZW 3G/4G on either 3.0/3.0.1/3.1
Support for other devices planed:
US VZW WIFI on either 3.0/3.0.1/3.1
EU Xoom's
Support to flash Clockwork Recovery is planned.
Support to install new framework for SMS/MMS/UAString on either 3.0/3.0.1/3.1
*I will not enable phone features untill a phone app can be used, i use another carrier other then VZW and I myself would like to be able to use the phone feature as well but can't untill a new phone.apk is compiled for honeycomb or one comes out that works with it*
Looking pretty smooth. Just took the plunge to root via adb though.
The unroot method will let you lock without getting any LNX errors,?
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
I am assuming the device cannot be locked and boot because the img files are not signed files from Motorola? I ran into this problem recently while trying to revert back to stock and locked to give the video app a try. I had a terrible experience with LNX 0x0004. Pretty severe brickage. Kinda scurry thought I had a high dollar paper weight.
amoamare said:
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
Click to expand...
Click to collapse
Yes, sorry still at work so short answers.
From what it seems is that you have to return completely to stock images, even then it might now work. From what it seems the application the removes the lock might also implement security in order to prevent from being locked again.
While the lock method works for some I think its all dependent on when people got their xoom. Mine is new and came loaded with latest software.
I think you hit it right on the nail. I think that even returning back to stock because the images and boot partitions have been modify the device will fail to boot. I have tried RSDLite to restore the SBF all the way from version 4.8 to 5.3.1 and it will not restore it fails each time. Only way to recover it was to re unlock the device and the device booted fine.
Tried to relock again and it failed to boot.
W00t just what we need...
It should be much more difficult for them to brick there device with this tool. As the user isnt using a 1 click method made for 1 version of the system.
The problem with the 1 click's out is currently they flash 1 boot.img for only 1 system either 3.0 or 3.01 this cause the device to hang at boot then people thinking something went wrong.
The program is designed with error checking in mind.
As seen in the video I show you this by purposely selecting the wrong software version, it notify's me that i'm trying to install the wrong boot.img for the a mismatched version of the os.
Also i was receiving the LNX errors before when trying to relock the device i figured out a good method and it will be implemented.
This is amazing if this works flawless, and I'm Super new to android, and I just bought a Xoom, I'm curious what does Rooting do for the device?, also why do people try to Un-Root for?
This is 3G only?
Yes 3G only, once the 3G is completly done ill focus on the WIFI version. I do not have a WIFI version myself so it will be based of whats posted.
Bad ass! Can't wait for wifi version! Great work
Azrael X 4.0
Can you tell me where the download link is?
Its comming as soon as i fix the MD5 Checks for the files and images.
Download Link Added.
Thanks op, I used this to unroot my xoom and it worked perfectly.
Thank you for the reply glad you liked it.
I'm eagerly awaiting the WIFI version! Woot!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I dont have a WiFi version so I need someone with adb experience so that I can implement a wifi version.
I take it just need the right boot images as well for the wifi version as there seems to be some hardware differences. But i need someone who can adb the device and get me some getprop information so that i can implement the wifi version of the device. I have rooted and unrooted my device over 20 times with this tool. Its fast and easy to use. I actually just updated it again with a new help box when it gets to fastboot oem unlock. I will have to also add one for the fastboot oem lock feature as I think I forgot to add that one.
Anyway.
If you have used this software Please Please leave feedback so that other users can see the success to fail rate. *THERE SHOULDNT BE ANY FAIL RATE* but if it fails i need to know so i can fix what ever it didnt do.
Will u not being doing this for EU xooms?
Mod Edit: Content removed and thread closed.
Looks like I am not done yet... For some reason flashing to a WW firmware will cause loss of IMEI + BT/WIFI MAC's and also the sound. Something to do with the RIL? Instead of flashing to a WW Firmware I flashed a few custom ROM's and while my IMEI / Baseband remained intact I still lost my BT/WIFI Mac Addresses along with all sound.
Looking for a way to repair all now. Hopefully I can modify some files and not need to reflash everything all over again. Anyone else ran into this with this handset?
Great Simeón started the task.
I do still have this phone as a paperweight.
But mine is really hardbricked. I tried flashing other raw firmwares. And it has no fastboot mode anymore.
Boot stuff and bootloaders has to be fixed and I haven't found the compatible files to write
Enviado desde mi SM-G930F mediante Tapatalk
Ok I recovered the MAC's/Sound etc and edited the steps. However now after a few reboots I seem to lose my MAC's again and the serial (unknown) is replaced by Medfield1534DD97. Both WiFi and BlueTooth still work though. You just have the random default generated MAC's. I can live with that as long as it works. Though if anyone can shed some light on this issue or anything else I would be extremely grateful.
yurais said:
Great Simeón started the task.
I do still have this phone as a paperweight.
But mine is really hardbricked. I tried flashing other raw firmwares. And it has no fastboot mode anymore.
Boot stuff and bootloaders has to be fixed and I haven't found the compatible files to write
Enviado desde mi SM-G930F mediante Tapatalk
Click to expand...
Click to collapse
What modes are you able to get into? I once lost fastboot mode but recovered it somehow. If you need any help / files let me know. I have backups, various versions of raw/update firmware, recoveries stock and custom and much more. All for this handset. Only thing I am lacking is the AT&T firmware or someones AT&T backup that actually works. I have a backup of AT&T system from someone here but I could never get it to work after flashing the WW firmware.
Hello
No modes
Only one mode I dont know how to name it.
It is like Qualcomm 9008 on Qualcomm phones.
Got it?
Enviado desde mi SM-G930F mediante Tapatalk
I understand. I have never seen that before for intel. Can you tell me the mode it says or show a screen shot of device manager?
phonecapone said:
I understand. I have never seen that before for intel. Can you tell me the mode it says or show a screen shot of device manager?
Click to expand...
Click to collapse
On phone screen you only see a USB Logo with a white bar.
I use XFSTK program to flash the phone in this mode.
You see cloverview Plus device on Device manager
and you need IFWI, FW DNX, OS DNX, OS Image files in order to bring back Fastboot mode.
These files are digitally signed, so, you need the right ones
yurais said:
On phone screen you only see a USB Logo with a white bar.
I use XFSTK program to flash the phone in this mode.
You see cloverview Plus device on Device manager
and you need IFWI, FW DNX, OS DNX, OS Image files in order to bring back Fastboot mode.
These files are digitally signed, so, you need the right ones
Click to expand...
Click to collapse
Ok yeah im familiar with that. I didn't brick my phone that bad so I didn't have to use XFSTK. I do have a tutorial on it though from XDA and the program saved in case I ever need to use it. Where are you getting all the RAW firmware that includes every .bin file? All the RAW firmware files I have don't include but a few of them. Here is a good XDA link on XFSTK - (cant find it saved, but if you search our forum for the Zenfone 2 here you should come across it. Here is another that details the process for a different model but the process with the right files should work on our handset - https://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Have you tried using Asus Flash Tools? I know it requires fastboot but in some circumstances it is actually up and running you just might not know it. I have a paid software app tool that will force enable adb in Fastboot also. I can see how the process works. Maybe it will help your situation out. Get adb going so you can try other methods.
I have it almost all done.. carrier unlocked, rooted, bootloader unlocked, twrp installed, imei repaired, mac and bt repaired (well on generated default right now) RR installed and modded some. Just have to finish modding and dbl check on serial/wifi/bt then it is out to a client.
BTW I found a way to input unlock code on custom ROM then revert back to WW firmware then mod imei and return to custom ROM unlocked! Actually might have found a way with the service firmware to totally unlock it permanently without need of a code! Too bad I don't have another one of these handsets locked else I would try the method again to see if indeed it was what i think or if it was from previous entry of unlock code. I'm putting my money on the DEV firmware used and the IMEI repair process of mine.
Not bad looking!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ended up formatting the / config and / factory partition by mistake. Do I need to restore to / config either or just the / factory already? If you need / config, would you like to make it available?
My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was that's a beta issue and so I manually wiped device but it didn't help, the screen is still not reacting.
So before I tear device to see it's not a hardware issue I would like to try to downgrade to stable android 9. Because bootloader is locked my only option is to update/downgrade via ADB, but because official OTA for Android 9 is older ADB is not allowing me to downgrade.
From what I read, rolling back to stock involves sing-off from the beta program on Google's website and wait for another OTA to revert to stock, but because I wiped the device and can't even set the system up and running I won't get it.
Maybe someone can provide such OTA file? Or maybe I'm doing something wrong.
Please, guys, help me out.
Files are here https://developers.google.com/android/images
Droid_Nut said:
Files are here https://developers.google.com/android/images
Click to expand...
Click to collapse
Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.
What happens when you try to wipe/format data from the recovery partition? Having a corrupt system/OS shouldn't have affected the recovery partition and/or the ability to format and wipe it to a stock state...
But, if anything, you might have some luck downloading the OTA system image (can still be found at the developers site of Google's), loading up the stock recovery (don't worry if you get a dead droid with an exclamation/triangle, it's supposed to show that, you just need to hold Power + Volume-Up at the same time), and running through the selection of "Apply update from update" and/or "Apply update from .zip" where you can now either point to the OTA .zip manually or "push" the file onto your device...
Using the stock recovery to either wipe/format the device or manually applying the OTA seems to be the only rescue method available to locked bootloader devices...
Good luck to you and I hope this helps...
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Edmontonchef said:
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Click to expand...
Click to collapse
My touchscreen doesn't work, so I can't pass the initial set-up.
I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait.
BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.
lywyn said:
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Click to expand...
Click to collapse
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
lywyn said:
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
Click to expand...
Click to collapse
I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck.
I'm just patiently waiting for beta 5 to be announced and then we'll see.
simplepinoi177 said:
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
Click to expand...
Click to collapse
It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work.
But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that screen got frozen), so I believe that's not a hardware issue. I just have to wait for DP5 and find out is it gonna help or not.
Use an external mouse via USB adapter to pass the welcome screen etc
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
I didn't know that. Thanks for the tip.
siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work.
How the heck is it possible? The screen is connected to the motherboard with only one ribbon, so if that ribbon would be defective, the screen should not turn on or have some artifact.
So far it's working OK, except for some strange glitch with "day widget".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Should remove the screen and see what's inside? I guess that's the only option left.
Probably your screen is broken and you need a new one. Warranty?
siggey said:
Probably your screen is broken and you need a new one. Warranty?
Click to expand...
Click to collapse
Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.
I was trying to unbrick my Xiaomi redmi note 8 pro, i have bricked it twice before and both times had to pay someone with an authorized Xiaomi Service Account, well this time i figured id wait for someone to come out with a method that works and id just use my samsung phone until then, well i waited and waited , and eventually i see the mega tread with the anti-brick in it. I was happy but for the few poor schmucks out there that never had a chance to flash that beautiful set of files i found a way out without paying someone to fix your screw ups.
Anyway I've tried lots of things to unbrick it, removing the battery , replacing the battery anything to get my back to fast boot. I've attempted flashing stock a countless amount of times in different ways and today i needed money very bad to pay some bills so i figured id try to fix it one last time so i could sell my note 10 +. I never had a chance to install the antibrick or whatever it is so theres no way this is just a fluke. I would like to give myself no credit anything here besides finding the files and making the guide. I feel bad because people are charging 35 bucks to practically login for you, and id really be a bad guy if i didnt post what ive found today. Well enough of the backstory here's a guide and ill link what worked.
I will provide the download for all the files you will need here.
https://drive.google.com/file/d/1RWwwUEZJnxmSzZMbFj5_zJaGQ1OJAFo5/view?usp=sharing
This guide is for the Global Version but its the same on all your just sub out the global ROM I've provided with my other files for the one in your region
After you have the zip file containing the files needed do as follows.
1. Uninstall your Current Mi-flash / MiFlashpro
2. Extract the .zip folder
3.Install The Miflashpro that i have in the zipped folder
4. Launch Miflashpro and login.
5.After your are logged in launch Spflash.
6. Inside SpFlashTool click the options tab in the top bar, second column from the left , then click options to open the settings , click general, then in the general tab you want to make sure check lib da match is unticked.
7. Now to begin flashing, Match up the .da file and the .auth file with the ones in the special sauce folder of the zip folder you downloaded , after thats its like installing stock "normally", if you are on global the scatter file is in globalromfiles/images directory.
8. When everything is setup simply click download.
9. As a few disclaimers I tried 6 or 7 times before it worked, i dont remember if i had spflashtool set to firmware upgrade or download download only, i will also state that it failed ounce or twice in both, i just held power and volume up until it cycled i head the ding on my pc letting me know windows picked it up and i had device manager open so i could see the mtk preloader and com ports, i was very surprised when it worked but it did. Anyway if this helped anyone please spread the work so people can know that there phones are not at the mercy of someone else's login. If you have any questions or issues please reply to the post ill respond as quick as i can. I'm not a developer just a modder if anything. I know basic python and how to screw up my phone stumbling upon a fix took me weeks or months even of on and off boredom spikes but this worked for me.
Anyway if this helped at all spread the work , and feel free to donate to me on cash app $KaozCash
hi
works with 64gb and 6gb ram version?
Rebellion747 said:
works with 64gb and 6gb ram version?
Click to expand...
Click to collapse
Yes That is what i originally did it on , the begonia model
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
angrypandagr said:
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
Click to expand...
Click to collapse
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
sawclan22 said:
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
Click to expand...
Click to collapse
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
angrypandagr said:
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
Click to expand...
Click to collapse
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
sawclan22 said:
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
Click to expand...
Click to collapse
I hate to ask but I need a test subject this worked for me but I may have left something out in my steps I could just brick my phone again a try it again myself, but it probably wouldn't be the same because the first the I did after making this thread flash the abtibrick lk and preloader, if you have some alternate way I can talk to you without using this thread I would love to fix it for you if I can, I want this guide the be revised to be a simple but highly detailed guide on how to fix this issue, it worked for me when I did it and I want to be able to help others. I just need someone else with a bricked device to test it too and for me to make sure that it's exactly what I did.
Thanks from my heart
bro your method if it works thank you very much, you saved me
Rebellion747 said:
bro your method if it works thank you very much, you saved me
Click to expand...
Click to collapse
Did you end up fixing your device? I figure if people report back success than more people will see it
Not working
I followed your instructions and did it several times but nothing seems to work for me
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please find a alternate way or help me.
Thanks for the thread .
RanaDARK said:
I followed your instructions and did it several times but nothing seems to work for me
.
Please find a alternate way or help me.
Thanks for the thread .
Click to expand...
Click to collapse
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Lajbymester said:
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Click to expand...
Click to collapse
have you guys tried to use edl? if not, try doing edl mode
Please
Hello, could you tell me the contact privately if you need who unlocked it for you? Although this is being advanced, I need the mobile quickly and I would appreciate it very much.
not work for me, the sp tools keep show up notification to login mi account
my phone brick because I downgrade from android 10 to android 9
need help asap guys
sawclan22 said:
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
Click to expand...
Click to collapse
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
can u please upload only flash tool files
I had already downloaded the rom ...im in my village (due to lockdown) with slow internet /nowifi so can u please upload flash tool only so I can test it
Not Work for Me :/
After trying the method with your files, the problem is still the same, the authentication window comes out every time and I can not flash my phone, for information (without Flash Tools) my phone displays only the LED light and when I connect it on my PC my computer recognizes it for a few seconds and this disconnection, maybe we don't have the same Hard Bricked of the phone
if you have any other information to suggest to me I will be grateful, thank you
(by google translate)
RanaDARK said:
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
Click to expand...
Click to collapse
No it was definetey hatdbricked, stuck in a brick state after flashing an improper boot.IMG I was getting the error for authorization myself , then the window popped up with that specific set of tools and files , I then logged into my personal account and it worked, I tried flashing a good bunch of times, I removed my battery I couldn't get back to fastboot mode eventually I downloaded that mi flash tool from cynagenmods website , they called it a preauthorized flash tool or a flaehtool that wouldn't require authorization , well it didn't work I found the files in the special sauce folder in somones github , it would let me use them so I unticked something in the settings of sp flash tool , I can refer to the guide to see what it was after that I was super surprised to see it flash , maybe every other time I tried to flash it was a driver issue , if multiple people answer this the same let me know so I can close this thread, when u flash your hardbricked device does it even attempt to flash at all , do u see the loading bar move , usually it would fail for me on the first file it tried flash and I want to know the specific error it gave , this was my second time doing something idiotic and hardbricking this phone , if anyone can download teamveiwer and let me make sure all drivers are the same all files are exactly what I have etc , spflashtool has a good bit of different errors , I can't retest myself , not accurately atleast, the first thing I did after unbricking my phone was flashing the antibrick lk.IMG and bootloader
Hello Everyone
So before I was unlocking and rooting the Amazon Fire TV Stick 4k by shorting the efuse, on which on the process is after patching the bootrom exploit w/TWRP is yeah it went great but when I executed the fastboot command which didnt work, like i checked errors for the command but theres really some bug idk even how matter I try (maybe because it was a partition problem on where did I put my exploit files)… so I restarted everything from start… but when I shorted and plugged everything from my laptop, and running the amonet exploit, it didn't detect my FS even how matter I change the plugs and the shorting. And there was no physical damages on the shorting area. And so I cannot run the fastboot command to Open and Execute files thru TWRP and ADB…
(I executed this during the 6.2.7xx vesion with the old UI)
But it seems that the FS is now unlocked and it has TWRP installed as a bootloader cause
After plugging it in TV and rebooted it to fastboot thru network adb, it rebooted instantly on TWRP and it prompts things like “Keep system Read only” well unfortunately I cannot access that before because I don't have OTG so cannot swipe it so I bought one then unfortunately I tried to plug it with high voltage charger and mouse peripherals but the mouse input doesn't show up no matter i change everything or wait to load up for couple of hours, maybe I received a faulty one... so I gave up for a long time and paused this due to budget restraints
Fast forward this time, and for dumb reasons that I never noticed that i constantly accept the updates that I updated it to stock 6.2.8.1 and lately found out that this version update burns efuse but I'm really curious what does this really mean? Does it mean on how many times you run the exploit and shorting it wont work and will not be detected thru pc? Or worst that the system partition cannot be modifed and you can't flash files no matter what even you installed TWRP? Can someone enlighten me? Will installing the prerooted roms like the 6.2.8.0/6.8.8.1 will work to root my systems? Cause I ordered 2packs of OTG again and they will be arriving in 10days hoping that the otg will work...
Can someone help me? Anyhelp regarding this issueis highly appreciated
Thanks
boss @Sus_i @Skel40 @tsynik @rbox any thoughts around this sirs?
yan2xme said:
Fast forward this time, and for dumb reasons that I never noticed that i constantly accept the updates that I updated it to stock 6.2.8.1 and lately found out that this version update burns efuse
Click to expand...
Click to collapse
TWRP skips flashing some images like TZ during an update, which means the efuse is safe, as long as you didn't update the TZ as well.
yan2xme said:
Does it mean on how many times you run the exploit and shorting it wont work and will not be detected thru pc?
Click to expand...
Click to collapse
The shorting thing gets permanently disabled, i.e. the SOC will refuse to boot with a short in place and there isn't a way to run the bootrom exploit again.
yan2xme said:
Will installing the prerooted roms like the 6.2.8.0/6.8.8.1 will work to root my systems?
Click to expand...
Click to collapse
Ofcourse they do.
Sus_i said:
TWRP skips flashing some images like TZ during an update, which means the efuse is safe, as long as you didn't update the TZ as well.
The shorting thing gets permanently disabled, i.e. the SOC will refuse to boot with a short in place and there isn't a way to run the bootrom exploit again.
Ofcourse they do.
Click to expand...
Click to collapse
sorry for dumb questions cause I want to make things for myself clearer (but first of all really thank you for replying fast)
so what's TZ again? is it abbreviated word?
and so is the bootrom exploit does only work once in a lifetime of a FS and will not work in other attempts even tho my FS is updated in a stock 6.2.8.1? should I try it again thru pc? or should wait just when my OTG arrives? and reboot it thru TWRP using mouse? Can I downgrade it too on the old 6.2.7xx versions where much of the kernels and patches here are suported on that version? Or for example can I use a kernel or GApps intendedly for 6.2.7xx on a prerooted 6.2.8.1 rom? Sorry for a topsy turvy kind of question but I hope you could really help me out... btw thank you sm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yan2xme said:
sorry for dumb questions cause I want to make things for myself clearer (but first of all really thank you for replying fast)
Click to expand...
Click to collapse
No problem.
yan2xme said:
so what's TZ again? is it abbreviated word?
Click to expand...
Click to collapse
TZ (trustzone) is an Image inside the OTA update package, which gets installed from the 'stock recovery' to a partition called TEE1. The efuse can't burn, because TWRP skips flashing the TZ.
yan2xme said:
and so is the bootrom exploit does only work once in a lifetime of a FS and will not work in other attempts even tho my FS is updated in a stock 6.2.8.1? should I try it again thru pc?
Click to expand...
Click to collapse
No, your Stick is fine, because you've TWRP installed...
yan2xme said:
Can I downgrade it too on the old 6.2.7xx versions where much of the kernels and patches here are suported on that version? Or for example can I use a kernel or GApps intendedly for 6.2.7xx on a prerooted 6.2.8.1 rom? Sorry for a topsy turvy kind of question but I hope you could really help me out... btw thank you sm
Click to expand...
Click to collapse
You can downgrade if you like, there shouldn't be a problem at all.
Edit: PS: You don't need to swipe in TWRP, you can also use TWRP commandline... via ADB over USB.
Sus_i said:
No problem.
TZ (trustzone) is an Image inside the OTA update package, which gets installed from the 'stock recovery' to a partition called TEE1. The efuse can't burn, because TWRP skips flashing the TZ.
No, your Stick is fine, because you've TWRP installed...
You can downgrade if you like, there shouldn't be a problem at all.
Click to expand...
Click to collapse
Ohh goodie I've been relieved after a long list of doubt...
So I should just wait till the OTG arrive so I can bring it on! And hopefully everything will be fine during flashing process and I can finally watch the Netflix TV without freezing and have a flawless running os