Hello, hoping someone might be able to help me? I installed TWRP 3.3.0-dees_troy on my MI A2 Lite. Somehow whilst trying to update the phone to Android 10, I've managed to remove the OS (Android 9 @ 1.2020 prior to original OTA update to Android 10 which caused a bootloop problem). I have since tried all sorts of methods via videos and instructions on the internet and have not been able to reinstall any OS be it stock or custom. Before doing so I'd unlocked the bootloader, enabled Developer options etc. Would be grateful for any assistance you can offer. Desperately hoping a kind soul on here can help me get my phone up and running.? Thank you and best wishes
I am in the process of writing a detailed guide for custom rom installation. So you can wait 1-2 days about that because I think it will help you out. Regarding your issue, for custom roms you should use offain TWRP
Join Telegram at t.me/XMiA2Lite for additional queries and support
LinkBoi said:
I am in the process of writing a detailed guide for custom rom installation. So you can wait 1-2 days about that because I think it will help you out. Regarding your issue, for custom roms you should use offain TWRP
Join Telegram at t.me/XMiA2Lite for additional queries and support
Click to expand...
Click to collapse
Thank you, I'll take a look @ twrp-daisy-3.3.0-0-offain.img now. Will wait to hear from you regarding a detailed guide for custom rom installation. I'd prefer to reinstall stock android but if I have to first install a custom rom first, I'm happy to do this. A lot of the guides out there seem to me to be done for people that are familiar with installing custom rom, modifying and or manually flashing their handsets etc. I haven't done this for years as I have a MI A2 which I bought because it came with stock android. Before that I had a Samsung Galaxy Note 2 which I'd messed around with installing custom Roms and messing with developer options and bootloader t get rid of bloatware but went back to Samsung supplied rom. With the Mi A2 lite, completely my fault, I'd tried to update it using mi flash and TOOL ALL IN ONE, neither worked. Installed TWRP 3.3.0-dees_troy on my MI A2 Lite via TOOL ALL IN ONE. Thought it was straight forward to use. Big mistake. Ended up removing the OS which would not update OTA. Mi A2 lite came with a bootloop problem following 1/2.2020 initial update to android 10. I solved this via switching partitions via fastboot. Got complacent thinking modding and flashing was straight forward. Have paid the price. any help you can afford me will be greatly appreciated.
There is a flash reset script for using with adb. Try searching for unbrick Mi A2 Lite. It's a German thread. With that you can even go back from 10 to 9 without any errors or problems. Works 100%, did this multiple times.
Thanks but I no longer have android 10 or 9 on my phone. Accidentally removed operating system with TWRP. Absolutely lost now as to what to do next
dropmail said:
Thanks but I no longer have android 10 or 9 on my phone. Accidentally removed operating system with TWRP. Absolutely lost now as to what to do next
Click to expand...
Click to collapse
Doesn't matter. Even with no OS it will work. Give it a try.
dropmail said:
Somehow whilst trying to update the phone to Android 10, I've managed to remove the OS
Click to expand...
Click to collapse
Can you still get to fastboot?
Using the stock fastboot ROMs should be able to recover, or MiFlash if you prefer.
Assuming that by "removed the os" you don't mean broke the partition table. In which case you probably need edl.
dropmail said:
Thank you, I'll take a look @ twrp-daisy-3.3.0-0-offain.img now. Will wait to hear from you regarding a detailed guide for custom rom installation. I'd prefer to reinstall stock android but if I have to first install a custom rom first, I'm happy to do this. A lot of the guides out there seem to me to be done for people that are familiar with installing custom rom, modifying and or manually flashing their handsets etc. I haven't done this for years as I have a MI A2 which I bought because it came with stock android. Before that I had a Samsung Galaxy Note 2 which I'd messed around with installing custom Roms and messing with developer options and bootloader t get rid of bloatware but went back to Samsung supplied rom. With the Mi A2 lite, completely my fault, I'd tried to update it using mi flash and TOOL ALL IN ONE, neither worked. Installed TWRP 3.3.0-dees_troy on my MI A2 Lite via TOOL ALL IN ONE. Thought it was straight forward to use. Big mistake. Ended up removing the OS which would not update OTA. Mi A2 lite came with a bootloop problem following 1/2.2020 initial update to android 10. I solved this via switching partitions via fastboot. Got complacent thinking modding and flashing was straight forward. Have paid the price. any help you can afford me will be greatly appreciated.
Click to expand...
Click to collapse
no worries pal, I hope I helped
https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637 Check this thread
a1291762 said:
Can you still get to fastboot?
Using the stock fastboot ROMs should be able to recover, or MiFlash if you prefer.
Assuming that by "removed the os" you don't mean broke the partition table. In which case you probably need edl.
Click to expand...
Click to collapse
Hello, thank you for your time, i can go into fast boot via volume down and power button. I think I wiped everything using TWRP. I've no idea what edl is? or what you meany by breaking the partition table? I've tried misflash, fastboot and tool all on one
https://sourceforge.net/projects/tool-all-in-one/
I'm not too techy but can follow instructions if they are complete. the phone was originally stuck on a bootloop, I sorted that via a video on youtube i.e. switching from slot to slop b via ADB and fastboot.
In spite of extensive (several hours of searching) and trying ,several roms both fast boot and non fast boot, nothing has worked.
Very frustrating as if I can actually find a video or website with simple and complete (that doesn't suppose the user knows tech jargon or is familiar with the or similar procedures, I'm confident I can sort the problem)
dropmail said:
Hello, thank you for your time, i can go into fast boot via volume down and power button. I think I wiped everything using TWRP. I've no idea what edl is? or what you meany by breaking the partition table? I've tried misflash, fastboot and tool all on one
https://sourceforge.net/projects/tool-all-in-one/
I'm not too techy but can follow instructions if they are complete. the phone was originally stuck on a bootloop, I sorted that via a video on youtube i.e. switching from slot to slop b via ADB and fastboot.
In spite of extensive (several hours of searching) and trying ,several roms both fast boot and non fast boot, nothing has worked.
Very frustrating as if I can actually find a video or website with simple and complete (that doesn't suppose the user knows tech jargon or is familiar with the or similar procedures, I'm confident I can sort the problem)
Click to expand...
Click to collapse
If you boot to fastboot, try the script I was talking about. It will help you! No. 3, ADB method.
Thanks ever so much, the link is exactly what I needed
LinkBoi said:
https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637 Check this thread
Click to expand...
Click to collapse
Thanks ever so much, the link is exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/oneplus-3/how-to/tool-tool-one-driversunlocktwrpfactory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes
vinylmeister said:
If you boot to fastboot, try the script I was talking about. It will help you! No. 3, ADB method.
Click to expand...
Click to collapse
Thanks ever so much for your time. I used the instructions on the link below. /i was going to try and uses yours after but someone esle posted a link which saved me searching for the German thread you were referring to
https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637
the link was exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/one...ctory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes
dropmail said:
Thanks ever so much, the link is exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/oneplus-3/how-to/tool-tool-one-driversunlocktwrpfactory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes
Click to expand...
Click to collapse
You can always try custom ROMs too. They offer a much better experience than stock in my opinion. For relocking the bootloader, you could also have clicked the "clean all and lock" option in miflash. Anyways, I'm glad I helped ^^
LinkBoi said:
You can always try custom ROMs too. They offer a much better experience than stock in my opinion...
Click to expand...
Click to collapse
Except battery backup
vinylmeister said:
Except battery backup
Click to expand...
Click to collapse
Newer Q custom ROMs with new 4.9 kernels offer great battery backup too.
vinylmeister said:
Except battery backup
Click to expand...
Click to collapse
Thanks again, do you know is there any way to clear some of the system?
I've a 32GB 3GB Ram version of the MIA2 Lite. tthe rom I installed as per the link you sent me was around 3GB in size. Having updated to the latest Android 10, storage confirms the system is using 9.4 GB of space. I've disabled as much as I can i.e. apps I dont use.
Related
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Help
frarredo said:
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
red_ferrari007 said:
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
Click to expand...
Click to collapse
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
frarredo said:
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
red_ferrari007 said:
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
Click to expand...
Click to collapse
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Flashing Help
frarredo said:
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
red_ferrari007 said:
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
Click to expand...
Click to collapse
I can't say for sure that unlocking the bootloader will solve your issue but it will for sure wipe your device. I would recommend creating a back up, but since you can't enable USB debugging to create a backup using adb, you are most likely going to need to be okay with losing all your data first.
As far as I know, I Dont know of any way to enable USB debugging without going into settings first. =\
Check the forums?
I'm at work right now, and I'm also not familiar with the process on a PC. I know how to do it on a mac, since that's what I use and am familiar with. I know that for windows its a very similar process but there are some device specific drivers that you must download and install on your machine before hand.
Without a computer in front of me right now ( I'm at work ) I can't tell you exactly what to do for a PC
Look online there are tons of guides also check you tube.
I should be free later around 2 or 3pm ( pacific ) and if you can't figure it out and would still like to my help. Id be happy to help you then.
Sent from my Nexus 5 using Tapatalk
red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
i am ready !!!
sfhub said:
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
Click to expand...
Click to collapse
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
red_ferrari007 said:
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
Click to expand...
Click to collapse
First step, do you have the USB drivers from google installed? If not download/install from here:
http://developer.android.com/sdk/win-usb.html
Then boot into bootloader (Press/Hold Power+VolDown until bootloader menu comes up)
Then download and unzip this file on your PC
http://forum.xda-developers.com/attachment.php?attachmentid=2405103&d=1384987176
Connect your tablet to the PC via USB cable.
Open up command prompt
Go into the razors-krt16s directory from the unzipping of above file.
type in command line
fastboot oem unlock
follow the directions on the screen. You need to use volup to select yes, and Power to accept.
it will proceed to wipe your user data.
post back when you are done.
i am ready !!!
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
red_ferrari007 said:
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
Click to expand...
Click to collapse
Have you unlocked the bootloader?
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
If you have unlocked the bootloader, follow the directions in this post to flash JSS15J
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
I am suggesting JSS15J instead of JSS15R because it is the closest factory image to JWR66N that you can get.
DONE !!!
i think its done
the LOCK STATE: UNLOCKED is shown
which u recommend ?
Should I proceed with JSS15J ???
red_ferrari007 said:
Should I proceed with JSS15J ???
Click to expand...
Click to collapse
yes.
Instructions in above post.
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
red_ferrari007 said:
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
Click to expand...
Click to collapse
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Last doubt
sfhub said:
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Click to expand...
Click to collapse
Just one doubt before proceeding
From ur link i downloaded JSS15J stock image
ur guide also mentions to download an addon zip file correct ? but its name is JSS1Q addon,zip
So is it correct ???
I need to extract that addon file to that extracted ? STOCK image file rite ?
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
What exactly were you trying to do? I mean normally you hook up old phone and use smart switch to update new phone. So why was you connected to a PC? It does sound like you bricked it.
So now you probably need to flash the ROM.
I read that smart switch is a good and valid source to check for updates. I never thought that an official Samsung software can be so bad at something so basic, resulting in bricking my phone...
Stop using smart switch to update your phone. You haven't hard bricked it because you still have recovery. It's called a soft brick. Download Odin 13.3_3B from here on xda. Do not use the 13.4 because it's suspected to have a fishy call back to a server from a dll that's in the program folder. Download the atch firmware for your model from sammobile or get it in this s20 ultra forum. You should be able to flash the new firmware.
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Julius_GER said:
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Click to expand...
Click to collapse
Odin uses official firmware from Samsung so no warranty voided.
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
What kind of USB Port did you use?
Try again using a USB 2.0 port, Samsung always had problems with it's software and USB 3.0 ports.
Use USB 2.0 and try again.
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
klantee said:
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
Click to expand...
Click to collapse
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Geekser said:
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Click to expand...
Click to collapse
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
klantee said:
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
Click to expand...
Click to collapse
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
Hey Julius, did you get your phone to work. I am having the same issue.
Update:
I am good now. I was using the thunderbolt cable that came with the phone and update would get stuck at the same point everything with odin 3.13 and 3.14.
I used a USB 3 to thunderbolt cable that I had from an older phone and it work.
What I used:
Windows 10 x64 1909
USB 3 to thunderbolt cable
USB driver downloaded from Samsung support. I think it is the same driver that comes with smart switch because when I installed it, it prompted
to reinstall driver.
Odin3 v3.13.3_3B_PatcheD from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. ( I think 3.14 will work too.
I really think the cable was the only problem)
Firmware downloaded with SamFirm
klantee said:
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Click to expand...
Click to collapse
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
ASHLEY117 said:
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
Click to expand...
Click to collapse
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
klantee said:
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
Click to expand...
Click to collapse
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
ASHLEY117 said:
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
Click to expand...
Click to collapse
Tried your suggestion with no joy. Will keep trying though as I feel this issue can be cracked. Many thanks...
Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
klantee said:
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
Click to expand...
Click to collapse
Glad I could hel;p- I know how frustrating it is when things seem like you can never get things to work - anyway - best of luck - and be sure to hit thanks If I helped you.
Hi Do you lose your data (vids and pics) via this method? i have had same thing happen on my s20+
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?
waiting for same thing.... quite sad that i can't use my phone just from an update
Yeah, there is a number of us in the same position. We could start a club. The really expensive paperweight club or something. I've also reached out to support. They asked a couple of questions, I promptly answered, and thin it's been crickets since.
Are you unable to unlock the bootloader?
chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
yes my phone open bootlooder
chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
No I never really got a chance to do it and now since I can't boot, I can't unlock it.
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
Are you unlocked? Did you flash anything?
CyberWolf92 said:
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?
Click to expand...
Click to collapse
could you please tell me your process, how did you try to flash ? my bootloader is unlocked even though I could not flash with .img file, everytime it's showing - FAILED (no such partition)
numbawon said:
Are you unlocked? Did you flash anything?
Click to expand...
Click to collapse
yes ,phone is unlocked, when i go for flashing with miflash, no .img file showing, or /and to install twrp,its showing no such partition
numbawon said:
Are you unlocked? Did you flash anything?i
Click to expand...
Click to collapse
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
shakhawat1993 said:
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
Click to expand...
Click to collapse
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
numbawon said:
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
Click to expand...
Click to collapse
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
shakhawat1993 said:
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
Click to expand...
Click to collapse
You have been very bad. You will be punished. *invites in the scary nurse with the big paddle*
@shakhawat1993 see this other post as it explains some more in it just in case it's helpful.
shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
i was in same situation like you,,start RM6 only on fastboot but thie works ,download you rom from this page https://drive.google.com/drive/mobile/folders/1BE4FSGDcfXavYoJ3Kw3toGMiPHgCGakC?usp=sharing
extract boot.img to your folder with fastboot
start mobile in fastboot
and open cmd.
fastboot device
if you see your device try next command
fastboot flash boot boot.img
restart your phone and you have stock recovery,,wipe data and you have unbricked device
i download latest twrp but not working and after install twrp i was stucked in fast boot like you
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
numbawon said:
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
Click to expand...
Click to collapse
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Nocturne Seigneur said:
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Click to expand...
Click to collapse
That's what I was hoping for but worried it's going to take more than just that, like the GPT layout and some other things.
For sure you will need the partition table, rawprogram, & a firehose for the SD888; I'd be surprised if the one for the RM5 would work on the RM6.
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.