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
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?
I cannot root it, I cannot install any recovery besides the stock one that comes with it, I cannot get it to connect to the computer as mass storage, only as a media device.
Im thinking I just blew $215 on a paperweight.
I CANNOT EVEN INSTALL TITANIUM BACKUP TO GET RID OF THE FREAKING ATT CRAP!
What have I did wrong?
I have CWM v5.5.0.3!
Ive tried countless number of rooting programs including some poplular ones:
1. Casual - http://forum.xda-developers.com/showthread.php?t=2189536
2. Kingo Android ROOT - http://www.kingoapp.com/android-root.htm
3. Towelroot - https://towelroot.com/
4. CF Root (Flashed SU but does not work) - http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip
CF Root flashed Superuser but it says unfortunately Superuser has stopped.
Im about to take this back to the store I got it from....
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
How are you flashing the recovery? Do you have Knox on your phone?
Model Number: Samsung-SGH-I747
OKAstro said:
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
Click to expand...
Click to collapse
Its an [email protected] Phone with a new [email protected] sim card in it. The phone works on stock stuff. It will boot up just fine with CWM installed but I cannot actually go into CWM. It just gives me a black screen.
Android Version: 4.4.2
Baseband Version: I747UCUFNE4
Kernel Version
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number: KOT49H.I747UCUFNE4
SE for Android Status:
Enforcing
SEPF_SAMSUNG-SGH-I747_4.4.2_0016
Mon May 19 20:59:50 2014
It doesn't matter if I got a ROM or not. I cannot install a custom recovery.
audit13 said:
How are you flashing the recovery? Do you have Knox on your phone?
Click to expand...
Click to collapse
I am flashing Recovery thru Odin. Ive even tried different versions of Odin from 1.7 to 3.09. I prefer to use Odin 1.85.
And I have no clue what knox is or even if its installed.
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
OKAstro said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Im not able to flash a working custom recovery.
mrnapolean1 said:
Im not able to flash a working custom recovery.
Click to expand...
Click to collapse
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
OKAstro said:
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
Click to expand...
Click to collapse
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
{
"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"
}
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
mrnapolean1 said:
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
Click to expand...
Click to collapse
The fact that you can get to download mode is good. But sorry, what this means is out of my league. Try PM'ing "DocHoliday77". He seems to be a great resource for all things SGS3. He's in numerous threads in the Development forum
EDIT: I booted into download and mine says the exact same thing
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
audit13 said:
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
Click to expand...
Click to collapse
No still nothing.
It vibrates when you first start it up and then the Samsung logo comes up with Recovery is starting in blue at the top for about a second and then goes to a black screen and nothing never happens afterwards.
What is Knox by the way? Is this keeping my phone from being rooted?
Figured id post here now rather than having two threads going for the same problem.
The more this goes on though, the more i am suspecting some sort of hardware problem.
I want to suggest using the PIT file to repartition the device, but theres no firmware to use along side it. Theres a program here on xda called PIT Magic i think. I dont know much about it, but maybe it could help you to somehow repartition....?
As for knox, there is tons of info out there on it already,so i wont get into it here. It wont block you from rooting, but it can deny root access when an app requests it.
Will the pit wipe it?
Will installing cm 11 using the installer work? Does it work?
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
DocHoliday77 said:
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
Click to expand...
Click to collapse
My main thing is I want to root my unrootable SGS3 so I can remove the ATT crap.
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
DocHoliday77 said:
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
Click to expand...
Click to collapse
I just spent $215 on this. I don't think the place where I bought it from will ever take it back.
I wish i had something better for you to try. Sorry.
If you are willing and able to consider it, i saw several motherboards and devices with broken screens (but otherwise functional) go for less than $65 today. Its the best option i can think of now.
Where at?
Sorry. It was on ebay. They often will go for a bit more than that, but if you are patient you should be able to get one relatively cheap.
Just do not buy any that say no power. Just look at ones that are a good motherboard, or a device with a broken screen where they say it powers on, just with no display. Also make sure the IMEI is clean.
Good luck!
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.
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
jake7901 said:
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
Click to expand...
Click to collapse
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
{
"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 had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
jake7901 said:
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
View attachment 5577727
View attachment 5577731
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
Click to expand...
Click to collapse
Could also be a usb issue, Motos have had some issues like this for a while.
Try a different USB port, Cable or PC
I had the same problem. After patching the boot.img with Magisk and fastboot flashing it, I got no touchscreen.
The problem was the wrong boot.img.
I downloaded Stock ROMs from several sources, all saying that my phone uses a particular Stock ROM. They were all wrong!
I used the Lenovo Rescue and Smart Assistant v6.4.2.13. With genuine Motorola USB drivers.
It found my phone via the IMEI and I downloaded the stock ROM it suggested, it was a different one from all the other ones I had previously downloaded.
TIP, when downloading from the Rescue and Assistant program change where you want it to download to, as it's a pain to try and find it later when you need the boot.img!
After patching with Magisk and fastboot flashing, I'm now rooted and EVERYTHING works!
Should I wipe on twrp before flashing using fastboot?
if yes, what files should I wipe?
Also is wiping necessary to do if I'm using fastboot to flash custom rom.
Im currently on xiaomi eu and I want to try Rog UI v2.
I flash it once, encounter an error(can't remember sorry)while flashing on fastboot and after this error cmd said "waiting for device" but i can assure that my device is still connected on system tray of windows. Also I use the cable provided on the box and on that process I dont accidentally unplug cable. It just disconnect flashing ROG UI V2.
Is there any correct way to succesfully flash custom rom using fastboot without sudden disconnection of cable and to not encounter errors?
I bootloop my devices after trying that and manage to reflash xiaomi eu.
Read the instructions for your rom in screenshot.... It says to double click the 'wipe and install' file. So it wipes your device as it goes. Basically, wiping by you is not necessary. Check you are using a USB 2.0 port not USB 3.0/3.1
{
"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"
}
reg66 said:
Read the instructions for your rom in screenshot.... It says to double click the 'wipe and install' file. So it wipes your device as it goes. Basically, wiping by you is not necessary. Check you are using a USB 2.0 port not USB 3.0/3.1View attachment 5624555
Click to expand...
Click to collapse
I tried using usb 2.0 but it keeps reconnecting so i tried to flash it on usb 3.1
My computer is Ryzen. Sorry but noob
also is there a difference flashing in usb 2.0 compare to usb 3.0/3.1?
NetteyLegend said:
I tried using usb 2.0 but it keeps reconnecting so i tried to flash it on usb 3.1
My computer is Ryzen. Sorry but noob
also is there a difference flashing in usb 2.0 compare to usb 3.0/3.1?
Click to expand...
Click to collapse
yeah, USB 2.0 is often more reliable/less problematic than USB 3.0/1
also, there used to be issues using Ryzen CPU's. can you try on a friends laptop/PC?
reg66 said:
yeah, USB 2.0 is often more reliable/less problematic than USB 3.0/1
also, there used to be issues using Ryzen CPU's. can you try on a friends laptop/PC?
Click to expand...
Click to collapse
I actually flash xiaomi eu for my poco f3 on usb 3.0 and it work.
To be clear, I flash this ROG UI V2 once and reverted back to eu and had some problems like I said it keeps disconnecting while flashing. I just randomly flash successfully both rog ui and eu. I want to know what causes this sudden disconnection while flashing.
reg66 said:
yeah, USB 2.0 is often more reliable/less problematic than USB 3.0/1
also, there used to be issues using Ryzen CPU's. can you try on a friends laptop/PC?
Click to expand...
Click to collapse
Can tell what to do if flashing custom using fastboot and suddenly disconnect? both accidentally or not(automatically disconnects)
in short, no, sorry. i don't know what to do or why it's disconnecting automatically
could have a read through this google search
reg66 said:
could have a read through this google search
Click to expand...
Click to collapse
should i reflash back to global before flashing this rom?
NetteyLegend said:
should i reflash back to global before flashing this rom?
Click to expand...
Click to collapse
Yes! Absolutely. If you are on a Custom ROM right now, you need to flash Stock ROM before jumping to another Custom ROM, otherwise you may brick your phone.
Also @reg66 is correct.
I have an AMD Ryzen 3700X on an X570 Motherboard. Many of my USB ports disconnect, I learned it the hard way. My phone got hardbricked while flashing with Mi Flash.
Only 1 of my USB ports is somewhat stable and doesn't disconnect as frequently. But if you can, use another PC, this is dangerous...
I also found out that Overclocking and/or Undervolting CPU or RAM may potentially also make USB connections unstable.
When flashing, make sure everything is stable. Windows, the cable, the USB port, your phone's battery is somewhat charged.
I also found using a Linux Distro to be more reliable than Windows, but that may just be me particularly. ^^ I had problems using Fastboot on Windows...
You need to be careful, because up until this point, I think you only had softbricks so far, but if you're unlucky you may get a hardbrick and may not be able to even boot into Fastboot anymore. ^^
I'm not trying to fear-monger, but there is no protection-mechanism while flashing. ^^ This is seriously dangerous and has the potential to leave you with a non-functioning phone.
cyanGalaxy said:
Yes! Absolutely. If you are on a Custom ROM right now, you need to flash Stock ROM before jumping to another Custom ROM, otherwise you may brick your phone.
Also @reg66 is correct.
I have an AMD Ryzen 3700X on an X570 Motherboard. Many of my USB ports disconnect, I learned it the hard way. My phone got hardbricked while flashing with Mi Flash.
Only 1 of my USB ports is somewhat stable and doesn't disconnect as frequently. But if you can, use another PC, this is dangerous...
I also found out that Overclocking and/or Undervolting CPU or RAM may potentially also make USB connections unstable.
When flashing, make sure everything is stable. Windows, the cable, the USB port, your phone's battery is somewhat charged.
I also found using a Linux Distro to be more reliable than Windows, but that may just be me particularly. ^^ I had problems using Fastboot on Windows...
You need to be careful, because up until this point, I think you only had softbricks so far, but if you're unlucky you may get a hardbrick and may not be able to even boot into Fastboot anymore. ^^
I'm not trying to fear-monger, but there is no protection-mechanism while flashing. ^^ This is seriously dangerous and has the potential to leave you with a non-functioning phone.
Click to expand...
Click to collapse
Im back on MIUI 13 22.5.25 WEEKLY right now with magisk module installed(League of Legends Wild Rift 120 fps Unlock) and a custom kernel named WildAngel v44. You think this is the reason why I always interrupted? Also I experience 0mb storage on twrp and asking me to a decrypt storage which I dont knw the password because i remove it and asking me to type but my password is pattern. I also tried the default password but not work. I flash different different twrp for my phone (from twrp A12 SKKK to A11 and vice versa) and suddenly twrp read my storage. Im just confuse after those softbricks BECAUSE I DONT KNOW WHY IT SUDDENLY FIX AND SUDDENLY BRICKS. Now im stuck at miui both global and eu.
NetteyLegend said:
Im back on MIUI 13 22.5.25 WEEKLY right now with magisk module installed(League of Legends Wild Rift 120 fps Unlock) and a custom kernel named WildAngel v44. You think this is the reason why I always interrupted? Also I experience 0mb storage on twrp and asking me to a decrypt storage which I dont knw the password because i remove it and asking me to type but my password is pattern. I also tried the default password but not work. I flash different different twrp for my phone (from twrp A12 SKKK to A11 and vice versa) and suddenly twrp read my storage. Im just confuse after those softbricks BECAUSE I DONT KNOW WHY IT SUDDENLY FIX AND SUDDENLY BRICKS. Now im stuck at miui both global and eu.
Click to expand...
Click to collapse
Are you on Official MIUI China or the Custom ROM Xiaomi.eu Weekly ? Xiaomi.eu is not official, keep that in mind. ^^ They are not affiliated with Xiaomi.
I think the reason why TWRP is listing the Data-partition as "0 Megabyte" is because TWRP may not support Android 12's encryption yet.
Also, the pattern does also make a PIN, you would have to look online, which Dot represents which number... But best to just remove pattern before accessing TWRP, I guess...
A Custom Kernel can cause all types of weird behaviour... So be mindful about that...