[Q] Like the factory does it? - General Questions and Answers

I have a tablet that I installed CM11 on.
During my customizing it to the way I want it to work I must have broken something in the system because it can't see what on my flash drives anymore.
I've tried factory resetting, reinstalling the Cyanogen and even trying to go back to stock.
But when I tried to go back to stock it kept failing.
Someone told me that you have to wipe it first otherwise 90% of the time it WILL fail.
So I did that and when I rebooted it flashed the device logo and then blank screen.
I waited a few minutes and nothing happened but a greyish-white glow forming around the edge of the screen.
So I tried to put the twrp recovery back in to see if I completely broke it or not.
It went in so I reflashed cm11 back on it and the system came back up but still has that problem.
When the factory makes these things they are obviously blank until software is put on it.
How can I do the same?
It apparently can be done since there are options to format the device in twrp.
How can I completely erase the device and start from scratch to put stock firmware back in it?

LunaEros said:
I have a tablet that I installed CM11 on.
During my customizing it to the way I want it to work I must have broken something in the system because it can't see what on my flash drives anymore.
I've tried factory resetting, reinstalling the Cyanogen and even trying to go back to stock.
But when I tried to go back to stock it kept failing.
Someone told me that you have to wipe it first otherwise 90% of the time it WILL fail.
So I did that and when I rebooted it flashed the device logo and then blank screen.
I waited a few minutes and nothing happened but a greyish-white glow forming around the edge of the screen.
So I tried to put the twrp recovery back in to see if I completely broke it or not.
It went in so I reflashed cm11 back on it and the system came back up but still has that problem.
When the factory makes these things they are obviously blank until software is put on it.
How can I do the same?
It apparently can be done since there are options to format the device in twrp.
How can I completely erase the device and start from scratch to put stock firmware back in it?
Click to expand...
Click to collapse
Let me first start by saying DO NOT format or flush the phone with TWRP, i have a galaxy s2x t989d here that is hard bricked because of that. TWRP is a great tool but it won't just delete the normal stuff and keep your phone safe, it will also delete the bootloaders and all and you will be stuck with a phone that won't turn on at all or show any signs of life, except plugging it to USB on a PC and it gets detected as QHSUSB_DLOAD device, or something similar depending on original chipset. TWRP will even delete ITSELF and your phone won't be able to enter either recovery or download mode.
In my case, the t989d has a qualcomm snapdragon, so that's why it gets seen as QHSUSB, and i have to use QPST.
From there you need special images to use with QPST to push them in the phone, but most of the time QPST will fail and not that much people know exactly how to run it and debug it. Backing up NV with QPST is easy up to a certain point, but that implies the phone is not hardbricked, if it is you have to use software download mode and so far it fails hard each and every time, it fails to even descramble it's own stock hex files that come with it... After that, only other option is with ADB, but that requires a minimum of programming knowledge, and also helps if you're familiar with Linux (i use ubuntu personnally), and also a set of special images to push into the phone. You can try to use darkspr1te's brixfix-2-1 To pull or push images from phones, but as stated before, you have to have a minimum of prog knowledge to be able to debug everything and make everything work perfectly sometimes.
Other than that, the only way to do it is with a JTAG device, but that sometimes requires good soldering skills and can wind up damaging the hardware in the phone and making even worse then hardbrick.
So by all means, start by trying to reflash a stock rom a few times before going the hard way, cause it's not always easy to put your hands on all the files and tools needed to bring it back from the dead. And also if you have TWRP installed, do backups before doing anything too hardcore just in case something goes wrong.
As for flashing stock roms, yes it often fails but flushing the device won't help much. First, make sure the battery is 100% charged as some flashers will fail if battery is under that for safety reasons and to avoid bricking. second of all, try to use another cable to flash it, as sometimes the cable is a bit damaged without it showing and it will make the flash fail. Also try different USB ports on ur computer, as sometimes somethings hang up on the USB and changing the port will make the phone reinstall it's drivers and start fresh. If all else fails, try another computer altogether if you can, some USB controlers on PCs are more touchy than others. Hope this helps a bit

It helps somewhat.
So how should I go about trying to get it back to stock?
I don't want there to be any files or folders on the internal storage that was not there when it was new.
I've been trying to do it onboard. Meaning by itself and not through the computer.
I have a t-mobile springboard s7-303u. It had the huawei mediapad firmware on it when I got it and like I said I could not get any stock firmware to install before.
I did manage to find a T-Mobile firmware for it. I forget where I found it but have been hesitant on using it partly because it's supposed to use fastboot to do it and partly because I don't want a boatload of t-mo apps installed as well. It's one of the reasons I'm not crazy about using the stock huawei firmware either (even though I've tried it). I want to use HWMOD's slightly modified firmware for it because he stripped out a lot of the excess and it's pre-rooted.
The batch file to install the t-mo firmware has this....
fastboot erase cache
fastboot erase system
fastboot flash modem non-hlos.bin
fastboot flash modem_st1 modem_st1.mbn
fastboot flash modem_st2 modem_st2.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash logo logo.img
fastboot flash cust cust.img.ext4
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
fastboot flash boot boot.img
fastboot flash system system.img.ext4
fastboot flash persist persist.img.ext4
fastboot flash cache cache.img.ext4
fastboot flash userdata userdata.img.ext4
fastboot flash tombstones tombstones.img.ext4
fastboot reboot
Will that accomplish what I want with a CLEAN stock firmware installation?

Anyone?

Why is it so hard to get replies on this board?
xda-developers is supposed to be where all the experts on Android frequent isn't it?

..

Related

[Q] I think I bricked the xoom after 4g upgrade??

- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.

Fastboot not working

Got a G3 with no download mode.
If you Google it, it's a common issue, and the fix seems easy.
But fastboot won't communicate with the phone at all. Device shows as ? in fastboot instead of normal device ID. And can't fastboot flash, fastboot erase, or fastboot boot any imgs - get a FAIL every time.
Anyone seen this before...?
I have been through this situation (and worse). Unfortunately, I do not see a simpler way for you to get back the partitions you have messed up. If it's only the download mode you've lost and you can boot up to put the phone in adb mode, and have the root access, problem can be solved by flashing a dump of appropriate partition(s). If not, then pushing a bootloader through octopus box is the only solution for d850 as other diagnostic tools to repair the bootloader do not have appropriate files for this model. Have a look at this thread, and see if you can make any sense out of it. I am here if you need further help in this matter.
unikorn74 said:
I have been through this situation (and worse). Unfortunately, I do not see a simpler way for you to get back the partitions you have messed up. If it's only the download mode you've lost and you can boot up to put the phone in adb mode, and have the root access, problem can be solved by flashing a dump of appropriate partition(s). If not, then pushing a bootloader through octopus box is the only solution for d850 as other diagnostic tools to repair the bootloader do not have appropriate files for this model. Have a look at this thread, and see if you can make any sense out of it. I am here if you need further help in this matter.
Click to expand...
Click to collapse
No it was completely hosed - wouldn't boot and was attempting to flash laf in order to get Download Mode back. You're referring to the JTAG service via Octopus, correct?
iBowToAndroid said:
No it was completely hosed - wouldn't boot and was attempting to flash laf in order to get Download Mode back. You're referring to the JTAG service via Octopus, correct?
Click to expand...
Click to collapse
Yes, that's how I got my phone fixed. Could not find any other way, and even with this one, it was not so straight forward. Especially when working with partitions dump. I overwrote EFS partitions as well, so lost my IMEI. But if you choose to go with this method, I can guide how to just stop at recovery partition and not overwrite modemst1 & modemst2 partitions. First task though would be to find someone with Octopus Box.

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Just bricked

Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me

Question No OS even after flashing stock

So I've been pulling hair for 2 days. I can flash everything fine recovery boots fastboot. But it consistently says no OS on either slots. Tried flashing stock to both went all the way through loading lineage and same thing. I'm at wits end. Also not a single password I put in decrypts data.
Also Metro/Tmob variant xt2131-1 bootloader unlocked.
Have you tied fastboot -w? It sounds like the partitions are messed up.
I have. I've done all of the above just still a persistent boot loop.
Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Currently retrying to flash stock firmware with a Motorola flashing program. Will let you know here in about 2 min.
Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Spedwardo said:
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Click to expand...
Click to collapse
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
No nothing of the sort. I did a factory reset because I was gonna try out lineage and this is where I'm at now. Still no OS. Even after flashing 3 times. I did have a remote access trojan that rewrote my partition data and resized one and added one and used the root hidden partition to store the data in while it was being transferred.
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
sosthenisRR said:
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
Click to expand...
Click to collapse
If this doesnt work you can try a blankfile flash via edl, if that does not work nothing will.
Fandroid Tech said:
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
Click to expand...
Click to collapse
Not at home. Staying the night at my mom's. Get home early tomorrow and I will try the advised steps. I went through my previous flashing steps and am now just missing the persist partition. I'll report back as for the edl mode and I have 2 blank flash files just cannot get into edl mode. Have qfil rsd and motoflashpro
Spedwardo said:
just cannot get into edl mode.
Click to expand...
Click to collapse
What have you tried thus far? Have you tried fastboot commands to get into edl, I think it may also also a boot menu option in twrp but I don't remember. Also now that I think about, after flashing the firmware(to both lots as you say) have you tried fastboot set_active a (or) b? Also where did you find the firehose file for it, I could not find one on other forums?
So far im downloading the files and will try what you suggested now. I'll let you know in 30 min. But I've tried factory reset. Flash. Formatting then flashing. Blank flash. Formatting then flashing. I've also used fastboot --force -slot=all flash ***. *****. Etc. Tried flashing. Flashing the copy partitions and tried flashing a gsi an aosp. Got to lineages recovery but still the same issue. Some partition are unmountable. At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Spedwardo said:
At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Click to expand...
Click to collapse
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Fandroid Tech said:
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Click to expand...
Click to collapse
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Spedwardo said:
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Click to expand...
Click to collapse
You can't, the manufacture prevents you from doing so due to "security issues". Make sure you get the latest firmware at https://mirrors.lolinet.com/firmware/moto/denver/official/. This will restore all partitions including vendor and persist as it generates from the modem partition, also android 11 and up does not use regular persist partitions anymore, it is now in the "super" images so don't worry about it. When you extract the latest firmware from this site there will be an XML file, go to https://forum.xda-developers.com/t/...e-with-motorola-devices.4042039/post-82186933 and follow the instructions, before flashing made sure to select slot A, after you are done flashing slot A set it to slot B and flash again, then reboot regularly. To set the slot run the fastboot command before flashing, for example fastboot set_active a, flash firmware, fastboot set_active b, flash firmware, reboot.

Categories

Resources