Database Info

[Q] AT&T One X Stuck In Endless Bootloop after Stock RUU Flash

Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:

Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence

Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita

timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.

Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita

Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?

Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita

timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...

The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita

timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!

Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita

timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:

It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita

timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?

Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita

timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!

It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita

timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?

Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita

timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good:

[Q] S-off mistake

Hey!
I tried to flash the Maximus rom onto my one s today and I needed quite a few tries.
Unfortunately I forgot to check if my phone is s off and it isn't. Now I flashed the rom and after I start the phone I only see the htc starting screen for a few seconds and then it turns black and flashes a little bit every 4-5 seconds.
Do you guys know how I can turn the device to s off and then flash it?
Thank you so so much!
Tom

Go to bootloader and conect the phone with youre PC. Read carefully the description. Follow the steps.
.
http://forum.xda-developers.com/showthread.php?t=2488772
http://rumrunner.us/

Thanks for the answer but the problem is that I can't start the phone to activate the developers mode or do anything else! It would have to be through fastboot or recovery! Also my computer doesn't recognize the phone, even though I was able to push something on the phone through adb sideload!

Did you make a NANDROID backup with a custom recovery? If so, restore from that.

I didn't!

tomlennart said:
I didn't!
Click to expand...
Click to collapse
What recovery do you have on there? You can flash a custom recovery on there like TWRP.
If you get TWRP on there, you can mount the sdcard and copy another ROM on there. Then do a full wipe and install the zip and then flash the boot.img to get something like CM11 on.
Alternately, you can relock your bootloader with fastboot usb, then install an RUU to bring it back to stock, then try something like moonshine.io to get S-OFF, then try maximusHD again.

808phone said:
What recovery do you have on there? You can flash a custom recovery on there like TWRP.
If you get TWRP on there, you can mount the sdcard and copy another ROM on there. Then do a full wipe and install the zip and then flash the boot.img to get something like CM11 on.
Alternately, you can relock your bootloader with fastboot usb, then install an RUU to bring it back to stock, then try something like moonshine.io to get S-OFF, then try maximusHD again.
Click to expand...
Click to collapse
I do have TWRP on there!
So, how does it work? I choose Mount, then which options do I pick? And does my computer automatically recognize the phone in the list of the connected devices or do I have to download a special program?
Which rom should I take and how exactly does it work? Is there a tutorial out there so you don't have to do all the work?
Thank you so much!!!

So reboot into bootloader. First see what HBOOT you are on. It will determine what ROM you should try.
If you have 2.15 you go with ROMS that support 2.15. If 2.16 then go with something that supports 2.16.
As far as mounting, go into TRWP. Choose MOUNT and choose Internal Storage. This will allow you to mount the internal storage on your computer.

I guess mine is 2.13 right? I don't have enough posts to post pictures so please delete the space between https:// and the rest of the link!
https:// fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xpf1/v/t34.0-12/10489061_699433320094234_38826939_n.jpg?oh=8ce1fb23d7e28d252398dd8f2d96a028&oe=53AD076A&__gda__=1403852663_8e60ad520e5b3c61a58cbf3dc20ba7c8
When I go to mount, I can't click on internal storage! I choose all I could, but the last two are "unclickable"
https:// fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xpa1/v/t34.0-12/10382441_699434953427404_7278275326706422508_n.jpg?oh=7ced00497a3f1fc8ef6afd846c75d002&oe=53AD15FF&__gda__=1403850025_68d5f9975589a6e19adacdff5a3607df
Thanks for taking up with my stupidity!

Someone chime in, but maybe you will want to upgrade your HBOOT to 2.15???
What is the carrier? Where are you located?
This _may_ be your RUU - don't run it until we know your carrier/location:
http://mobilefileserver.com/download.aspx?get=167185
PJ40IMG_Ville_U_JB_45_S_HTC_Europe_3.16.401.9_Radio_1.15.50.05.29_10.30.50.08L_release_314432_signed
Running an RUU will get you back to stock. After that, you may want to upgrade your ROM so it's compatible with moonshine.io or other S-OFF application. Once you become S-OFF you are much more free to do many things to your phone.
BTW: in your picture data might be the the choice to try. Try and mount data and see if you see your files on there.

I'm using AT&T right now, but the phone doesn't have a simlock. My location is a little bit complicated, I'm in Wisconsin right now, but the phone is from Germany, and I'll go back to Germany in about two months.
My computer doesn't recognize the phone at all, but makes the noise like you unplug something...
How would I upgrade the HBOOT?

I hope you have fastboot installed on your computer (windows?) if not:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Boot into the boot loader, make sure it ways fastboot USB
On your computer in terminal, type: fastboot devices
Hopefully it will return something.

Okay, finally I'm back in Germany and have time to try it!
I did what you just told me and it returned this:
C:\Users\Tommi>fastboot devices
HT23RW400512 fastboot
Thats good, right?
So what would the next steps be?
Thank you so much for your help!

Anyone?

Is there anyone who can help me?

tomlennart said:
Is there anyone who can help me?
Click to expand...
Click to collapse
OK you said you had TWRP. Start up in recovery, go to mount and then select internal storage.
See if the sdcard partition mounts on your computer.
If so, at that point you can put a rom on there and also the boot.img that you need to start your phone up.

No, I can't mount the internal storage!
Somewhere I saw how to fix it before but I don't remember how and where I saw it!

tomlennart said:
No, I can't mount the internal storage!
Somewhere I saw how to fix it before but I don't remember how and where I saw it!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1630459

But where do I get the stock recovery? I googled a little bit and saw that there are like a thousand different ones!
Sorry for all the stupid questions And thank you all for the help!

tomlennart said:
But where do I get the stock recovery? I googled a little bit and saw that there are like a thousand different ones!
Sorry for all the stupid questions And thank you all for the help!
Click to expand...
Click to collapse
Here is mine from my dropbox
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img

(Solved) Soft-bricked, but unable to flash anything but CWM.

Hello, I seem to have soft bricked my tf700.
​I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
​So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
​After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
​I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
​I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B

You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.

tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.

gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.

tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.

gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either

I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.

I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/

gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?

berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?

gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!

berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.

gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?

berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.

gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.

berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.

gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...

berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh

D6616 boot loop after root / build.prop edit

Well, I've gotten myself into quite a pickle. Root was finally gained for the T-Mobile D6616 model over the weekend. The method works great and I had no trouble with it at all. I then installed Nut's Dual Recovery without any issue. Rebooted into TWRP multiple times over the next day or so and took a backup.
Next, I installed Xposed and started loading up all the modules I have missed since I got this phone. Everything was working great until.... I decided to edit the build.prop in order to silence the camera shutter sound. It's a pretty simple edit; I've done it a dozen times before:
Code:
ro.camera.sound.forced=0
For some reason that didn't look right to me. I thought I remembered the line being slightly different. But whatever, I threw it in there, saved it, and rebooted.
And now I'm stuck in a boot loop.
Even that is not usually a problem. My plan was to boot into TWRP, replace build.prop with the backup, reboot and be on my merry way. But.. Now my custom recovery seems to be gone. No idea why. When I boot into recovery, it seems to be stock and gives only the options: 1) continue powering up, 2) safe mode, 3) factory reset, 4) power off.
1) Powering up obviously doesn't work.
2) Safe mode doesn't work - boot loop continues
3) Tried factory reset. The little Android dude showed up, a progress bar worked on restoring to factory, and then.. still boot loop continues.
I have successfully gotten the phone to show up in adb ONCE since the boot loop appeared. I have no idea how I did it, and I haven't been able to replicate it. My plan was try to pull and edit the build.prop from adb if I can get it to show up again. But no joy so far.
Bootloader is still locked on this device, so no fastboot options.
So now I'm really at a loss for what to try next. Any ideas?

Reflash with stock rom.

electrash said:
Reflash with stock rom.
Click to expand...
Click to collapse
Yes, but... How do I do this with no custom recovery and no access to fastboot?

SportingChap said:
Yes, but... How do I do this with no custom recovery and no access to fastboot?
Click to expand...
Click to collapse
Use flashtool and a stock FTF

gregbradley said:
Use flashtool and a stock FTF
Click to expand...
Click to collapse
D6616 is not listed as being supported.
This flash tool can only be used by Xperia™ devices having an unlocked boot loader
Click to expand...
Click to collapse
Again... D6616 bootloader is not unlocked.

SportingChap said:
D6616 is not listed as being supported.
Click to expand...
Click to collapse
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net

gregbradley said:
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net
Click to expand...
Click to collapse
I see now. Looking into it, thanks.

I wish I could thank you more than once, gregbradley! Everything flashed and restored back to the way it was - except I lost internal storage. Bummer. Oh, well. Life goes on.
For anyone else who stumbles across this thread:
Use this thread to download the stock .ftf file for your particular Z3
Use the instructions here to download, install, and use Flashtool
Use these instructions to root (or re-root) and install TWRP recovery if you have the T-Mobile variant (D6616) Note: The link to recovery in that post is broken. You can find the latest version here: http://nut.xperia-files.com/ -- click on XZDualRecovery
If the root instructions seem to work but you don't see SuperSU after reboot, delete the contents of data/local/tmp and try again:
Code:
adb shell rm -R /data/local/tmp/*

So it' s not exactly the way it was.

SportingChap said:
except I lost internal storage. Bummer. Oh, well. Life goes on.
Click to expand...
Click to collapse
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.

gregbradley said:
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.
Click to expand...
Click to collapse
Yeah, didn't anticipate this one. When I took the nandroid backup in TWRP, it didn't click that there was no "internal storage" option to back up - only system, data, trim area, boot, and cache. Must be different on other devices, because I know I've backed up internal storage in the past.
A lot, if not most, of what I had on internal storage is backed up on my desktop in various folders. So I'm not at a total loss.
And.. I hear you on using external. I always did use it for most things prior to getting this Z3. I have a 64gb sdcard and use it for nandroid and TB backups (and mp3s). I had to make the decision to go along with KitKat's insistence on using internal with no external write access for apps. Now that I have root, I patched it via FolderMount and might redo my symlinks for the Pictures folder, etc. We'll see.
Sigh.. Isn't Android fun?

bricked, need help

it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx

nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do

Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)

Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot

Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try

Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.

U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101

Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?

Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs

Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand

Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device

You both are awesome ???

Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me

JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.

I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while

JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files

venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?

JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.

Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro

Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.