Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?
Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk
I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.
ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot
Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin
Since I seem to have a partition related error, would this LINK help my situation at all?
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...
I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.
VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.
Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app
Related
Ok so i am going to need a little bit of help here.
I the process of trying a method i found to apply the OTA update i forgot to do a nandroid backup.
I first pushed a recovery i thought was the stock one.
Then i locked the phone
then I pushed another recovery on top of it after the phone was locked.
The last step is preventing me in entering recovery.
Everytime i try to get in it comes back to the bootloader saying:
TAMPERED / RELOCKED / Security Warning.
As you can see, i screwed up.
What i am trying to accomplish though is do manually create a nandroid using ADB.
Now the problem i am having is that the tar command does not seem to preserve the sym links AND user/group.
the tar command i used was
tar -cvhf /sdcar/backup/system.ext4.tar /system
I am pretty trying to do the same thing as CWM recovery but from the command line.
How can i accomplish this?
Thanks a ton
well you cannot flash files with a relocked bootloader, So thats the reason you're having issues pushing recovery, Re-unlock the phone and try again.
And also, Stock recovery does not support nandroid backups. Flash CWM in fastboot, make a nandroid, Flash stock recovery, re-lock bootloader and all will be good.
**TAMPERED**
RELOCKED
Security Warning
Is normal when you have custom software on a locked device. Reverting to stock will clear this up
Oh and next time, Please post in the correct section, This belongs in Q&A.
Flame flame flame flame flame....
sent from a guy living in a van down by the river
azzledazzle said:
well you cannot flash files with a relocked bootloader, So thats the reason you're having issues pushing recovery, Re-unlock the phone and try again.
And also, Stock recovery does not support nandroid backups. Flash CWM in fastboot, make a nandroid, Flash stock recovery, re-lock bootloader and all will be good.
**TAMPERED**
RELOCKED
Security Warning
Is normal when you have custom software on a locked device. Reverting to stock will clear this up
Oh and next time, Please post in the correct section, This belongs in Q&A.
Click to expand...
Click to collapse
I will use the correct section. I promise.
I just thought that Q&A was just general questions about the phone.
Now, I would re-unlock it, but this creates a factory reset and erases everything which is what i am trying to avoid.
I am half screwed though since when i first unlocked it i did a nandroid backup.
So technically, i just need to tar up the /data folder.
Any idea on how to do this in my current state?
Just unlock it again via HTCdev. After it's unlocked download stock recovery. AFter that use the "fastboot flash recovery recovery.img" and then relock it. You will not have security warning. You get security warning after you lock bootloader but recovery is still custom. The newly locked bootloader signature checks recovery and gives you the *Security Warning*. Good luck
Edit: You do not need to erase anything. The only thing that erases all your stuff running an RUU or a different backup. All you need is stock recovery. Also if you don't flash recovery but you unlock bootloader also the security warning will be gone. easy.
shootind5nukes said:
Just unlock it again via HTCdev. After it's unlocked download stock recovery. AFter that use the "fastboot flash recovery recovery.img" and then relock it. You will not have security warning. You get security warning after you lock bootloader but recovery is still custom. The newly locked bootloader signature checks recovery and gives you the *Security Warning*. Good luck
Click to expand...
Click to collapse
I will unlock, and i've done it before. The problem is that unlocking resets to factory defaults meaning everything is erased.
I need to pretty much backup the data folder, then unlock, but without the recovery.
its a bit of a challenge.
But thanks though.
unlocking does not delete anything.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
Nothing gets erased. I've unlock and relocked my phone 100 times.
shootind5nukes said:
unlocking does not delete anything.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
Nothing gets erased. I've unlock and relocked my phone 100 times.
Click to expand...
Click to collapse
Pretty sure it does.
BUT, let me try with my phone.
The phone i screwed up is my wife's.
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
PM sent
shootind5nukes said:
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
Click to expand...
Click to collapse
Alright alright...
Dont want to piss you off.
I appreciate the help. Just gave you 3 thanks.
I really dont want to screw this one up.
if you have a wife, you'll understand. She will chew me alive if i do something stupid (again )
I'll give it try
Im moving this. go look for your thread in the Q and A section...
shootind5nukes said:
I'll say this a third time.
UNLOCKING YOUR PHONE DOES NOT RESET ANY DATA. IT JUST UNLOCKS BOOTLOADER.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
PM sent
Click to expand...
Click to collapse
Well, it reset my data.
Fortunately everything I care about can be easily restored but if one uses Hasoon's all-in-one kit I can say that your data will be wiped. It won't touch the 'sdcard' data but all apps and settings will have to be restored.
shootind5nukes what method are you using to unlock that doesn't wipe?
So, no response on the magical method to unlock without wiping?
michaelh99 said:
So, no response on the magical method to unlock without wiping?
Click to expand...
Click to collapse
No magical method.
I ended wipping everything.
Sorry
Adrien, I was replying to shootind5nukes who was yelling at you for not understanding his magical method for unlocking the bootloader without wiping the phone. Which he didn't share.
michaelh99 said:
Well, it reset my data.
Fortunately everything I care about can be easily restored but if one uses Hasoon's all-in-one kit I can say that your data will be wiped. It won't touch the 'sdcard' data but all apps and settings will have to be restored.
shootind5nukes what method are you using to unlock that doesn't wipe?
Click to expand...
Click to collapse
For me it also wiped everything
michaelh99 said:
Adrien, I was replying to shootind5nukes who was yelling at you for not understanding his magical method for unlocking the bootloader without wiping the phone. Which he didn't share.
Click to expand...
Click to collapse
I figured, but i should have posted earlier the results of my experiment.
At the end, nothing would work.
I ended up wiping out everything and twice.
The first time, i installed the nandroid and radio and used Titanium backup to reinstall the apps.
Somehow, this method caused some issues and the battery would drain really fast.
I just reinstalled everything but this time by hand and redownloading everything from the market.
Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.
dclaw_fantum said:
Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.
Click to expand...
Click to collapse
I imagine you know all about relocking your bootloader and having your phone in bootloader before trying the RUU... I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
You can also wait for the OTA update for T Mobile... There are a few custom ROMs that will allow a download of it... Even if they dont im sure someone will post the OTA, which you can then download to your SD Card, flash stock recovery and update from there...
Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app
dclaw_fantum said:
Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
Click to expand...
Click to collapse
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks
Couple questions
AKToronto said:
I .. I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
Click to expand...
Click to collapse
How do you verify checksums?
Do you mean we need to flash stock recovery before we start the process and lock bootloader initially?
Where would we find the stock recovery or do we use the one in the temp folder during the install?
AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks
Click to expand...
Click to collapse
The stock recovery is working, it errors when it tries to mount cache or the SD card. I can mount the SD in TWRP and CWM. It also mounts as a USB drive in Windows. I'm trying my hardest to get this to take other files without doing the HBOOT downgrade. I don't like bringing down my main PC for any reason. I have checked the MD5s each time, all is good with that. I have a sneaking suspicion that it the FS on one or more partitions may be different than factory and is causing the issue. Going to have to find a table of the factory partition FS structure before I jump to messing with the HBOOT downgrade.
I have just recently ran an RUU, however, I did not flash the stock recovery beforehand. All I did was relock the bootloader and run the RUU. It seemed to work fine, but I am having some wifi and airplane mode issues and I also can not update the software. Is this because I did not flash the stock recovery beforehand? and if so, what can I do to fix the problem? I ran the 2.35 RUU that was recently posted, thanks in advance
I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks
Rsd lite 6.1 to flash
hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci
hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM
I have a G930W8 running stock software fully ota updated till last month when I rooted and installed twrp and ran a S8 G955F port for a while and all was working wonderful. I recently decided to sell it and so jumped into twrp factory reset then wiped full then flashed the newest stock ROM in Odin.
My issues are two fold. FRP lock was turned on after in the bootloader but wasnt worried as it's locked to me.
Main issue is now no matter which carrier firmware I try I get the stupid DM-Verity error and it won't let me boot into a rom to remove the frp. With frp lock in I can't flash anything but stock images of course and cannot even downgrade. This bootloader is killing me
Please help with the bootloader from hell that won't leave my phone!!! TIA.
Easy fix!
Flash a stock ROM for your model. Boot it up and go to developer settings. Turn on OEM unlock. That will allow you to flash custom ROMs kernels etc.
bahmonkeys said:
Easy fix!
Flash a stock ROM for your model. Boot it up and go to developer settings. Turn on OEM unlock. That will allow you to flash custom ROMs kernels etc.
Click to expand...
Click to collapse
Not possible with a DM-Verity error. Cannot boot.
Rymcbc said:
Not possible with a DM-Verity error. Cannot boot.
Click to expand...
Click to collapse
Straight forward fix. Flash the DM-Verity patch file. Either push it via sideload or copy to root, and then do full wipe. You should be able to flash anything then.
The DM-VERITY flash file can be found by searching for it or I could send you it.
bahmonkeys said:
Straight forward fix. Flash the DM-Verity patch file. Either push it via sideload or copy to root, and then do full wipe. You should be able to flash anything then.
The DM-VERITY flash file can be found by searching for it or I could send you it.
Click to expand...
Click to collapse
Can't flash anything but stock nougat binaries on that bootloader with frp lock on.
Tbh all the easy fixes have been tried. I'm hoping for something not well known or really new and therefore not all over XDA already as I've tried everything I could find over days of looking.
Rymcbc said:
Can't flash anything but stock nougat binaries on that bootloader with frp lock on.
Click to expand...
Click to collapse
As I said from my first post flash a stock ROM (via Odin)! Go to settings enable OEM unlock. Then you can go to my second post with the DM-Verity error fix.
That fixes both of your issues
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
Rymcbc said:
Tbh all the easy fixes have been tried. I'm hoping for something not well known or really new and therefore not all over XDA already as I've tried everything I could find over days of looking.
Click to expand...
Click to collapse
Have you flashed the DM-Verity file via sideload?
Also all what you said is straight forward easy well known fixes.
bahmonkeys said:
As I said from my first post flash a stock ROM (via Odin)! Go to settings enable OEM unlock. Then you can go to my second post with the DM-Verity error fix.
That fixes both of your issues
Click to expand...
Click to collapse
As I said in the main post of what the issue is, any stock ROM i flash with odin fails the DM-Verity test and fails to boot because of the previous root detected at the kernel level. So far any suggestions were already stated as tries and failed in my original post so I aplogize if I seem to dismiss them quickly. Without frp lock on I can normally easily fix the DM-Verity issue. And without DM-Verity issue I can easily fix frp lock. Its the combo the prevent boot at all past recovery.
bahmonkeys said:
As I said from my first post flash a stock ROM (via Odin)! Go to settings enable OEM unlock. Then you can go to my second post with the DM-Verity error fix.
That fixes both of your issues
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
Have you flashed the DM-Verity file via sideload?
Also all what you said is straight forward easy well known fixes.
Click to expand...
Click to collapse
Ya tried to sideload it with the nougat recovery and it is blocked from side loading by frp won't even allow updating from an SD card if tried to be selected. I tried from the combination ROM for my variant of the s7 as well as it's a 6.0 recovery but it fails as well to side load. That new bootloader is locked down.
Rymcbc said:
As I said in the main post of what the issue is, any stock ROM i flash with odin fails the DM-Verity test and fails to boot because of the previous root detected at the kernel level. So far any suggestions were already stated as tries and failed in my original post so I aplogize if I seem to dismiss them quickly. Without frp lock on I can normally easily fix the DM-Verity issue. And without DM-Verity issue I can easily fix frp lock. Its the combo the prevent boot at all past recovery.
Click to expand...
Click to collapse
The issue is it's not letting you flash any stock ROMs via Odin? That is your main issue? From what I read it allowed you to flash a stock ROM. Please be more clear
bahmonkeys said:
The issue is it's not letting you flash any stock ROMs via Odin? That is your main issue? From what I read it allowed you to flash a stock ROM. Please be more clear
Click to expand...
Click to collapse
I am able to flash them. But they will not boot as when they try and it says updating android it stops says erasing and reboots to recovery with DM-Verity error.
bahmonkeys said:
The issue is it's not letting you flash any stock ROMs via Odin? That is your main issue? From what I read it allowed you to flash a stock ROM. Please be more clear
Click to expand...
Click to collapse
I'm not sure what isn't clear. I can flash stock ROMs in odin, they all fail with DM-Verity error on first boot because of previous root. I cannot root again or flash DM-Verity fix as the only thing that can be flashed with the booloader with frp lock on is stock binaries. Which won't boot because of DM-Verity error.
Rymcbc said:
I am able to flash them. But they will not boot as when they try and it says updating android it stops says erasing and reboots to recovery with DM-Verity error.
Click to expand...
Click to collapse
Show me a picture of the Odin process completing. Flashing a recovery and kernel removes FRP. Also show me the DM-Verity patch file you have. Show me you sideloading the file with TWRP
bahmonkeys said:
Show me a picture of the Odin process completing. Flashing a recovery and kernel removes FRP. Also show me the DM-Verity patch file you have. Show me you sideloading the file with TWRP
Click to expand...
Click to collapse
I'm sorry show you? I have no need to prove myself to you. Do some looking around there is a whole other thread where with the same issue with the only fix being going to someone with hardware to reflash, and many others around with the same issue. If you don't like the topic of conversation feel free to live on.
I came here to find solutions not have a debate. If you have none beyond what you have offered then thank you antways but it is of no help.
What would be the point of frp lock if you could just flash with odin and it's gone. Seems like a basic starting point to address when Google made I would think. Maybe that worked in kit kat or maybe some early lolipop versions but frp hasn't been able to be replaced in a few years by just flashing. On first boot it requires you to connect to the Internet and sign in with a previous account. If I could even get there I would be fine as it is frp locked to my own account. Thanks for the advice anyways.
You have not sent any logs. Your knowledge/explanations is patchy at best. I have tried to help you but without any logs or any willingness to try you are stuck. I have not debated as I have tried to get you to fix it. Since you will not try, I cannot help.
I have been flashing phones for 10 years and have a very vast knowledge of how everything operates.
I think the issue here is you not your phone! Enjoy the brick
Frp is out since 5.0. It's software not hardware and can be bypassed.
DM-VERITY has been bypassed within the first few weeks of release.
I've had issues recently with newer firmware butchering dm-verity due to bad CSC files(They run a script in recovery(the "Updating/Erasing" screen) that writes to /system/csc and patches verity as they go. They're basically witchcraft to begin with so it was bound to go wrong eventually xD). It sounds counterintuitive but have you tried a slightly older firmware package? Also make sure to flash all parts of the package (AP,BL,CP,CSC). Previous modifications shouldn't affect it as it rewrites everything anyway (apart from the Knox warranty of course)
Edit: If you have an older CSC file it might be worth trying that in combination with the newer AP to get booted