Related
Here's the full story: a few months ago I unlocked the bootloader of my Huawei Y300-0100, rooted it and installed TWRP. Some days ago I wanted to try a custom ROM but I made the mistake of wiping system and cust along with the caches and data, I didn't really notice it as I did it too fast (without reading) and attempted to install the ROM, but the phone froze while doing so.
I turned the phone off and turned it back in to find a green screen with two rectangles, one red and one blue.
After many days of searching on the internet I found that the only way to fix my phone is to flash the stock ROM by copying dload/UPDATE.APP to the root of the SD card, and turning on the phone while pressing vol+-, but the update stops at the second step.
Taking a look at the update log I see that the error is related to CRC, which means the UPDATE.APP has somehow been modified, but that's not true as I have tried both the stock ROM that came with the phone and the official update from Huawei, as well as many other updates, and they all give me the same CRC update.
If I attempt the update without an SD card the phone goes into a pink/purple-ish screen, connecting the phone to the PC, Ubuntu recognizes it as a GSM device, but there's something strange, when I type lsusb in the terminal I see this:
Code:
Bus 001 Device 021: ID 12d1:1035 Huawei Technologies Co., Ltd. U8120
Which is completely incorrect as this phone is not an U8120.
I have tried many different methods, such as doing the procedure without a battery or using more than 5 different SD cards and now I have no idea what to do next, can anyone help me out here?
Hello
Just received OTA update to MARSHMALLOW. After downloading I did run the install. Various steps run OK including the 156 ( or more) application optimization. New restart up to the lock screen, but then immediate reboot.
Now the phones is stocked in this bootloop.
By pressing volume down and power together I was able to access Fastboot. I tried to enter Recovery mode but I got the Android with "no command" message.
How to proceed to recover my phone?
Thanks
That is Recovery.. that is what it looks like.
The fact you did not know that yet know how to get into Recovery tells me one thing.
You most likely have already used custom stuff on the phone such as TWRP, Root etc.
Then you installed an OTA for Marshmallow which has a new level of security.
I would have started by providing details on what model of phone you have and
what OS you were running before hand and what version of it and if you were rooted or had TWRP installed etc.
Saying.. "i clicks on teh Marshmallows Installs an it's no works"
Is not going give people here much to go on to TRY and help you.
And did you search this forum help section ?
Because the same questions get asked non stop.
So much that most people don't reply to them anymore..
Each guy that has a problem creates his own new topic
so he can have repeated for him the same thing the last 100 guys were told.
Hello
My model is SM4163AD1E1
The phone has never been rooted.
It was running only official ROM received by OTA from manufacturer.
I try to remember which version it was running before ? Probably 5.1
I tried to search on the forum, but I didn't found anything related to the brand new update to 6.0 leading to bootloop !
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.
Hello, I am new here and I made a huge mistake!
I purchased Samsung Galaxy Tab S6 Lite (LTE) literarally 1-2 days ago and I wanted to root it, I had my smart phone rooted which did not have Knox protections, it was as straight forward as flashing TWRP and use Magisk via instructions I followed.
I make use of "Root" privileges a lot when using my device, I find it very important to my daily life so I decided to risk rooting it, after doing so my tablet was showing 2 errors, that its not using official samsung software and that the boot loader is unlocked, when I unlocked the boot loader using OEM Unlock everything went fine, the option was greyed out and checked afterwards.
During the boot process, it reboots 2 times and it shows a integrity error, integrity and some very long number, I am assuming its a integrity check? I have the exact matching firmware, so I flashed back the stock firmware and... the "not using official samsung software" warning disappeared, it boots me into recovery mode, I choose "reboot" and the device goes to boot looping with the same error.
I was following this tutorial: https://forum.xda-developers.com/galaxy-tab-s6-lite/how-to/howto-unlock-root-galaxy-tab-s6-lite-t4132289
But there are some things I skipped, here the exact steps I took:
Unlocking Boot Loader:
Followed all the steps from 1 to 4 but I skipped the 5th step entirely, the step where it asks you to mess with firmware date and twrp, I did none of that, I will mention that when I was looking for stock firmware to download before doing anything, I was not able to understand the CSC so I didn't know which firmware to exactly use until a software update came up which told me the exact firmware, I accepted the update and download that stock firmware, because my firmware was updated I didn't think that following the few steps of the step 5 would've done everything as I was already off the path.
I didn't do the 6th step as I just checked of the OEM Unlock is greyed out and still checked in the "developer options" section, I assumed that it was a success, not to mention the boot loader unlocked warning that was showing up and yes, all the data was erased and was forced to go through the setup process again as expected.
Root the tablet:
1. I have downloaded the firmware as it says not just for the purpose of rooting, the firmware that the software update told me about, this is the firmware I downloaded, the firmware is a exact match, everything is matching: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
2. I follow all the steps from 2 to 11 from here.
3. When I reached step 12, I went to download mode and I look for any messages regarding it only allowing for official samsung images, but I saw no such message, didn't really pay attention to anything else, I just glossed over things, considering there was no such message I assumed that KG/RMM state was good, don't know what it was but it might not have been "prenormal" because there was no message regarding official samsung images, from here I falshed the boot.tar file like in the instructions, that lead me to my current problem I mentioned at the very start of this post.
4. There was no step 13 as I can't boot into android due to "integrity" error I have, right now I have my tablet turned off (thank god I can do that) via the recovery that shows up after flashing stock firmware.
Addition Info:
1. I don't have any data to lose, if I need to do a factory reset or something of that sort, I have no problems doing that.
2. As I mentioned at top, I do have a stock firmware downloaded from this link here: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
3. The tablet is: SM-P615 (Samsung Galaxy Tab S6 Lite (LTE), I bought the LTE so I could use it as my phone)
4. At the download mode, the OEM (Boot Loader) state is set to NO and the FFS (I don't remember if its FFS exactly at the moment, something FF I believe, I don't want to turn on my tablet at the moment) was set to NO.
5. The KG (No RMM mention that I could see anywhere) state is showing up as "Checking..."
What do I need to do to fix my tablet? do I need to wait for 7 days? if so how do I do so, like does leaving my tablet off count or not?
PS: I am a self-thought experienced low-level windows programmer, I've been doing programming for over 10 years now, never have worked with Android development but I can attempt to build something from source if necesarry, I know very little about Linux OS as I purely work with Windows and use Windows for everything including servers.
I have done some research regarding that "integrity" error and I can't find any screenshot in google images that matches how it looks on my screen, but there are a lot of them quite similar to it, which basically says "verification failed, factory data reset your phone", in my case I don't have that message, it just says "integrity", but when the boot looping stops and shows that failure I do have 3 options, "try again" and "Factory data reset" and the 3th one I don't remember, I am suspecting that this could be my problem! I believe the samsung just changed the way that particular message is shown (visual change), so I just need a factory data reset and it will work, most likely with the rooted boot.img file! I will attempt this after a few hours of this reply, I may have panicked too early.
The issue has been fixed
Well this is surprising, I was about to do the factory reset but before doing so I decided to flash the same magisk patched boot.img file, when I flashed I saw seeing those 2 warning messages as expected, I was expecting for it to fail after 2 boot loops so I can do the factory reset as intended but on the 3th boot loop the tablet booted up! I was brought at the android setup screen, once I was done with that I checked the OEM Unlock, it was still checked and greyed out, downloaded Magisk Manager and to my surprised it worked! Magisk Root latest version is installed and working, it asked me to allow magisk do some "additional setup", the tablet booted up perfectly fine after that "additional setup", I check root privileges using "Root Checker" and it worked, I have root privileges! I most likely have panicked too soon, sorry for wasting your time! Hopefully this post will be useful to someone in the future looking to root their tablet.
My assumption of what happened: When I flashed the stock firmware AP a second time so I can turn off my tablet, it most likely did a factory reset without me knowing, so when I flashed magisk again before letting it try boot up again, the tablet booted perfectly fine because factory reset has already occured, which brought me to the android setup screen.
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Aks said:
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Click to expand...
Click to collapse
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
suhas2k said:
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
Click to expand...
Click to collapse
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
suhas2k said:
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
Click to expand...
Click to collapse
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
tom1807 said:
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
Click to expand...
Click to collapse
Yes, for past 8 months I was updating with root using adb side load so yes, both fastboot & adb drivers are properly installed.
Lughnasadh said:
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
Click to expand...
Click to collapse
Looks like you are right, it's ARB issue.
I did try contacting the B2X Service Centers in India and they only service now 6a but not the 6.