Related
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
3z3-8917 said:
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
Click to expand...
Click to collapse
+1
joel_sinbad said:
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
Click to expand...
Click to collapse
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
I learned YEARS ago never to flash an sfb\fastboot\odin\whatever if its not made specifically for your device+OS+carrier until the super smarts have determined if the signatures\values are compatible (or wait until a post like this shows up ). Motorola's notorious for setting up sbf's in a way that will brick you, prevent you from ever going back to stock, and\or downgrading. Knowing that, I made a rom from MR instead of flashing the fastboot.
ATRIX HD: security downgraded version -- that line worries me the most, especially if that's what it says if you're trying to flash AT&T now -- It could mean that MR has a higher CG value than AT&T. You'll never be able to install the AT&T fastboot again if that ends up being the case -- you've blown an efuse.
I'm gonna need some more details: Did the MR flash fully finish the first time used? If it fully finished and didn't boot or loops, do a factory reset in the stock reocovery. You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
.
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
loading into fastboot only with error "flash failure"
marshok said:
loading into fastboot only with error "flash failure"
Click to expand...
Click to collapse
I'm not really sure what to tell you. You could try flashing just AT&T boot.img and devtree....Maybe make a hybrid fastboot, replace what fails during the AT&T flash with files from the MR fastboot (and modify the xml accordingly). Since it seems you're using the MR fastboot menu it, trying the unlock command is worth a shot.
All my other suggestions involve trying to connect directly to the nand and manually dd in the mbr and such -- I've never even tried connecting to my phone like that, so you'll have to search for those methods on your own, sorry. You'll also be diving in to full on brick territory too. You're just semi bricked, so you can still get lucky if you don't change that.
There is still hope (maybe) -- Apparently 4.2 is in testing and a fastboot should pop up for it before or after it's released. If its like every other major sbf\fastboot release I've seen it should have higher signatures\cg values and could possibly be a fix for you. That's all an assumption, but its based on credible rumor (a Mattlgroff post) and Motorola's past actions. The point is -- You still have access to fastboot, don't do anything to screw that up because your needed fix might not be available yet.
Or you could send in your phone for warranty; check Motorola's website to see if your still covered under factory warranty -- I am and my phone is a 99 cent refurbished model -- I still have 11 months left You get 12-24 months coverage when you register (length depends on New or Refurb). I was truthful on my Purchase Date, but I suppose you could lie and say you just recently bought it and it quit working when you started to upgrade it.
Did the MR flash fully finish the first time used?
Click to expand...
Click to collapse
no the flashing not completed, I got the error just flash boot.img
You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
Click to expand...
Click to collapse
how I can do this? when my AHD is briked
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
Click to expand...
Click to collapse
if boot directly into fastboot and I have acces stock recovery
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
Click to expand...
Click to collapse
I try flash Bell JB fasboot and I get the same error
thanks for your help skeevy420
PD. Excuse my english
del
3z3-8917
How do you help skeevy420?
you have restored your phone after flashing on MB886_niimx-user-4.1.2-9.8.2Q-50_MB886?
In the same boat
Hey guys I'm in the same boat. I rooted my Atrix HD and was happy until I installed busy box 9.2, which managed to overwrite /system/bin and I don't know what else I could no longer mount/remount, change w/r in root, use the ls or many other commands and wifi, mobile data, bluetooth, or OS factory reset all gone.
I should have made a copy of my system before doing anything else but I went ahead and used the boot menu recovery, which didn't do anything to help the problem.
I then flashed the MR rom with RSD Light in an attempt to recovery my phone, it was 4.1.2 and seemed like a good (hindsight horrible) idea at the time.
Now I can fastboot flash recovery images from att JB but it does no good because the boot partition fails. The RSD Light MR boot flash failed but somehow the security version stuck, and the Bell 4.1.2, Att 4.1.1, and 7.7.1Q-144, roms boot.img all return Partition (boot) Security Version Downgraded. If anyone knows a way around this please let me know.
It seems kind of tragic that Dan's bootloader unlocking came out, pretty much the day after I got stuck in this locked bootloader loop
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for JB.
Then try to flash it again with https://www.box.com/s/cmoz84iachug77tghdlo version of rsd lite. Make sure you have these latest drivers.
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
it can fix?????? i did the same flash at my atrix hd
rorrito said:
it can fix?????? i did the same flash at my atrix hd
Click to expand...
Click to collapse
for the moment it's not possible, wait bootloader unlock tool for AHD briked....
Codex01 said:
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for
JB
Then try to flash it again with this version of rsd lite. Make sure you have these latest drivers.
Click to expand...
Click to collapse
Ok downloaded the JB you linked and upgraded from RSD Light 6.1.4 to 6.1.5, I edited the XML to remove getvar, and ran RSD Light but it still fails on step 1.
"Failed Flashing Process 1/23 "gpt_main0.bin -> Phone returned FAIL."
On the Phone "preflash validation failed for gpt_main0.bin"
The only stock rom that made it past step 1 has been the MR that bricked my phone, so I replaced the system.img, boot.img, and recovery.img of the MR with the JB 4.1.1 you linked but it still fails at step 15, flashing boot.img. Preflash validation falure
BRICK AHD
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
fix fail on part 1 rsd
use the stickyboot fix from general got it from skeevydude it works, try using mythtools after!
ickysjazz said:
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
Click to expand...
Click to collapse
Shame on me :S
Well, I just bricked an ATT AHD in the same manner, trying to flash the Mexican JB version (I bought 3 of this phones to sell here in Mexico and wanted them to look as the phones they sell here by replacing the broken digitizers with ones with no ATT logo and flashing local firmware) ...But yeah, I made a big mistake, I wasn't aware I had to unlock BL before flashing other carrier SBF's... :S At least I've learned from this and didn't made the same mistake with the other 2 AHD's I have (And I'm planning to go back to stock and deodex em' because Mex fw isnt working pretty well on this AHD's...)
Trying to repair this thing by reflashing ATT JB stock fw... RSD & Myth seem not to work;
-In RSD I can't even get past step 1/23 (flash partition "gtp_main0.bin" failed"); when trying to flash Mexican rom I got to step 15/23 till I got the error.
-In Myth It looks like some files get flashed (It even gets me to the "Load Recovery" option, I obviously choose Stock as I don't want to f'up the phone even more ) and then "finishes" but when rebooting, shows "Dual Core tech" bootscreen and sends me back to Fastboot (Reason: Sticky bit factory_fastboot), tried stickyboot solution on cmd and then reflash on myth, same result.
Also I get the messages "downgraded security version" and "Invalid PIV Image: System" in AHD Fastboot. I don't know what else to do now, I still haven't tried Bell rom as I think I'll mess things up even more so I've stayed away from it At this point I guess I'm pretty much f***ed...
@ickysjazz
@vananucho
You're using the wrong fastboot...I can tell that by the error code...use snapdragon fastboots...those are the only ones for us to use. Any other fastboot will result in errors.
So Download those
DL Mex Retail
Extract it
Open terminal to that extracted directory
Do the sticky_bit fix.
Do these commands in this order
Code:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase cache
fastboot erase userdata
And that's how you manually flash a fastboot. I've never used MythTools or RSD. That is how I do it, always have done it, always will do it -- with the same fastboot linked above with same commands posted. Those are for Mex Retail, but should work on any JB fastboot...ICS fastboots need a few minor tweaks.
Do the fastboot commands as root on Linux or as a Windows Admin (set the admin privileges for the app in the right click properties menu)
Replaced the fastboot with the one provided by Skeevydude and still get the same error but I guess it's due to the fact that I'm running out of battery (Started showing low bat advice after 3rd failed attempt, using regular cable), I'll try this again as soon as I make a flashing cable, I'll keep updated!
Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi
Hi people, im new to the forum .I need help with my Moto G, in an attempt to upgrade manually to 5.0.1 I messed it up. I have some background in working with androids but not alot.
Phone is this----->[] a m a z o n . com/gp/product/B00K0NRZSW?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00[/url]
Now im stuck on the bootloader , when i select "Normal startup", "recovery", or "factory" I only see the motorola logo... similar to this-----> lh4.googleusercontent .c o m /-2xKsjK42MDY/VNgIcKkofZI/AAAAAAAAGy0/ZRhhzuyieGE/w311-h553-no/bootlogo.png[/url]
To start troubleshooting this i have gone and downloaded what I believe is the orignal img file of what came with this phone originally named like this----> Android 4.4.3 (Retail US) KXB21.14-L1.23-4 CID9"
How do I install this. What program allows me to install this IMG to the phone and get me back up and running.
Any help will do, thanks
Christopher
DON'T FLASH 4.4.4 OR LOWER! You probably installed the Lollipop bootloader in the process. If you downgrade to KitKat, your device WILL DIE because it will try to install the KitKat bootloader, and the security check will hard brick your phone. (and there's no blankflash tool for 5.X bootloader) Flash a 5.0.1 Lollipop firmware or newer for your exact model (ensure it's your model and not another one, if you take of the phone cover the exact model appears in a sticker) and try again using a method described here in XDA, in the exact subforum for your model because some rogue sites just take the tutorials from an older model and change the model and stick it there.
Honestly you should had to just leave it as is and install Cyanogenmod 12/12.1 as the Motorola bootloader can run a version above the bootloader version but NOT BELOW, although this requires to unlock your bootloader, rendering your warranty void.
If the bootloader is still locked and you never unlocked it, you could take it to service center and tell them that you received an update, the phone restarted in the middle of the process and now no longer works as an excuse.
P.D.: The image is broken.
You are SURE you flashed the right stock fw for your phone ( XT-1234 ) ?
How you flashed the fw ?
From the description you gave us looks like you followed an outdated guide and flashed only some parts of system.img_sparsechunk.X, so system image is not complete and looks broken to the phone, other partiotions looks fine since you see the logo bootloader etc
Just reflash the fw like that
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot.exe reboot
Click to expand...
Click to collapse
Just be sure the phone model is right, if you flashed a wrong bootloader your phone may be an expensive rock :\
Mhhh menaged to open the amazon link, thats looks like a moto g gen1, hope you don't flashed the wrong rom...... since you are in moto g gen2 forums
Snapdragon processors are unbrickable
Hello Fellas!
Looking for in the internet I found an article that has a tool from snadragon fabricant. It's called "QPST, 2.7 /422." found in androidbrick website. Please just google it and I'm really sure that using the stock rom of moto g 2nd is totally possible unbrick the hardbricked phones like mine. I hava a Moto G 2014 2nd generation Xt1078, and after an OTA update itself bricked without any reason by my foult. Led doenst light neighter the screen and it is recognized in my PC as "Qualcomm HS-USB QLoader 9008" after I installed the drivers. Wel I'm not a developer but according to the article in the androidbrick website is possible to give life back to the devices which lost their fastboot mode.
Thanks in advance!
We need your help!!!
Note This is Cyanogen OS 13.0.0 (6.0.1) and not Cyanogen Mod.
Has anyone tried to install Wileyfox Swift's Stock Rom on their android one device? Have you had any issues?
Earlier I tried to install Wileyfox Swift's stock cm13 rom to my Android One (Cherry Mobile One G1) via fastboot.
Everything went well, all of the functions are working except for the Cellular Network.
The sim cards were actually detected by the phone and apn settings are automatically generated and correct.
I'm using Talk n' Text (Smart) and ABS-CBN Mobile (Globe) which has been properly detected.
However it can't get any network signal. I tried going to settings and do a scan but the scan fails right away.
I checked my device IMEI and its still the same as before I installed Cyanogen OS.
Anyone knows how to fix this?
Here's how I did the installation
I downloaded the file from cyngn support website.
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
http://builds.cyngn.com/factory/crackling/cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
I have TWRP installed so I did an "Advanced Wipe" first and pretty much deleted/formatted everything.
Then I flashed every flashable file thats on the zip.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash splash splash.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
The device booted up normally and I noticed that the signals bars we're empty.
I tried to search for fixes but I cant seem to find any.
I also tried to flash a debuggable boot image, it work tho but nothing happened with the network issue.
I will try to reflash my Cherry Mobile One G1's Stock Rom later.
Hope I wont have the same issue after reinstalling the stock rom.
If anyone knows how to fix this lemme know. Thanks.
Or if anyone succeded let me know how you did your installation.
Also feel free to inform if I did something wrong.
flash "NON-HLOS.bin" (or whatever it's name is) from your working stock Rom, that should bring Cellular signal back.
Have to do this every time, after flashing Wileyfox Rom's (in my case for a Storm Clone).
Seems the Wileyfox devices use slightly different(?) modem hardware
Hi, confirmed it works also on my G1.
I used the files from same zip that you linked:
http://builds.cyngn.com/factory/cra...S2NH-crackling-signed-fastboot-2306277a34.zip
But I did NOT flash modem / NON-HLOS.bin
I flashed this way:
fastboot erase DDR
fastboot erase userdata
fastboot flash sbl1 sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash splash splash.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Signal has no issue, see screenshot here :good:
vel_tins said:
flash "NON-HLOS.bin" (or whatever it's name is) from your working stock Rom, that should bring Cellular signal back.
Have to do this every time, after flashing Wileyfox Rom's (in my case for a Storm Clone).
Seems the Wileyfox devices use slightly different(?) modem hardware
Click to expand...
Click to collapse
Thanks. I got it working.
m192 said:
Hi, confirmed it works also on my G1.
I used the files from same zip that you linked:
http://builds.cyngn.com/factory/cra...S2NH-crackling-signed-fastboot-2306277a34.zip
But I did NOT flash modem / NON-HLOS.bin
I flashed this way:
fastboot erase DDR
fastboot erase userdata
fastboot flash sbl1 sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash splash splash.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Signal has no issue, see screenshot here :good:
Click to expand...
Click to collapse
Thanks, they probably use somehow a different hardware. I got it working too.
tried the one in the oneteams forum and i have to say its a really good rom. its like cyanogenmod with optimizations for the device itself )
Is this the 32bit version?
I would like to try Cyanogen on my CM G1 but I want the 64bit version. Please confirm if the downloadable ROM from Cyanogen website are 64bit and help me how to properly flash the latest stable build. I think I don't need the modem flashed from what I read from previous post that I will not get any cellular signal here in PH.
I want to ask if you're on official Cyanogen do you get frequent updates? I'm on stock Android One ROM it is getting update every month and I think will surely get Android N.
Hi
vel_tins said:
flash "NON-HLOS.bin" (or whatever it's name is) from your working stock Rom, that should bring Cellular signal back.
Have to do this every time, after flashing Wileyfox Rom's (in my case for a Storm Clone).
Seems the Wileyfox devices use slightly different(?) modem hardware
Click to expand...
Click to collapse
Do you know how to get/backup NON-HLOS.bin file from the working phone? I downloaded the flashable zip from cyanogenmod what I would do is flash the zip via TWRP and then fastboot flash the NON-HLOS.bin so when I boot up no cellular problem.
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
vel_tins said:
flash "NON-HLOS.bin" (or whatever it's name is) from your working stock Rom, that should bring Cellular signal back.
Have to do this every time, after flashing Wileyfox Rom's (in my case for a Storm Clone).
Seems the Wileyfox devices use slightly different(?) modem hardware
Click to expand...
Click to collapse
Do you know how to get/backup NON-HLOS.bin file from the working phone? I downloaded the flashable zip from cyanogenmod what I would do is flash the zip via TWRP and then fastboot flash the NON-HLOS.bin so when I boot up no cellular problem.
Anyone please provide a baseband for cherry mobile g1 nougat 7.1.1 with April patch.
Anyone captured the ota update tos111b?
Sent from my Wileyfox Swift using XDA-Developers Legacy app
I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help.
Look at https://mirrors.lolinet.com/firmware/moto/kiev/official/
Use the file that matches what you have on your phone.
Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?
Kor1134 said:
Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?
Click to expand...
Click to collapse
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.
Or just download the 11 to start with
Fandroid Tech said:
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.
Click to expand...
Click to collapse
I understand, thank you for clarifying, but all I need is the recovery image. I just didn't want to flash a recovery image with a different build number in the unlikely event there's a difference between my build and whichever build I download. I'd prefer not to flash the whole system if I can avoid it, but whatever, I guess I'll just throw Android 11 in it.
Thx.
So, can someone let me know exactly how to flash the oem images to this phone? I booted into the bootloader and ran the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Now it just boot loops when powering on and entering charging mode.
EDIT: nevermind, I missed super.img_sparsechunk.9, all good now.
XT2113-2
Kor1134 said:
I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help
Click to expand...
Click to collapse
1st. rsdlite, 2nd. fastbootd, 3rd. make back-up(s), 4th. checkout L-os, its a PLETHORA of relevant info ex. dual partition issues and resolutions. AND i do believe
i know this is a bit l8, HOWEVER, in the event it is not too l8 OR you find yourself requiring assistance hmu. ive spent last couple months DARING my kiev to transform into this elusive paperweight...to no avail. along the way ive learn_ed a couple-o-tings, this and the photon q are amazing marvels of techno{imo}
ciao
if anyone has kiev ?s, i MIGHT be albe to help. i am no self professed aficionado or anything but ive been learning about moto's for a few years.
ciao