Database Develop

[Q] update 4.2.2 failure

Hi XDA!
i've rooted my phone with the rootkit by hasoon2000 and now i can get the 4.2.2 update from HTC, but everytime i try to install it, it reboot into the TWRP and nothing happend, i can then from the TWRP reboot phone into system, where it says the system have been restored from a failure..
what to do ? :S

JaRi1337 said:
Hi XDA!
i've rooted my phone with the rootkit by hasoon2000 and now i can get the 4.2.2 update from HTC, but everytime i try to install it, it reboot into the TWRP and nothing happend, i can then from the TWRP reboot phone into system, where it says the system have been restored from a failure..
what to do ? :S
Click to expand...
Click to collapse
You need to have stock recovery in order to have the OTA work.....

mathrania said:
You need to have stock recovery in order to have the OTA work.....
Click to expand...
Click to collapse
can you give me a link for me to download that from somewhere ? i cant find a working one anywhere.. :S

asus memo pad 7 (me176cx) "unable to mount /factory"

Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)

kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal

I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?

paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black

I have the same problem and can't find any solution yet :crying::crying:

sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error

kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.

Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?

kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot

Can't Boot Into System, Only TWRP

Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.

Deleted

Boot to your ROM through the power button...
Manually..

Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.

Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?

RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.

Deleted

TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .

uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:

bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?

bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"

Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!

My Oneplus 3T died?

HI.
On my rooted 3t i had:
- TWRP 3.0.4-1
- firmware 4.0.3
- ROM RR-N-v5.8.1-20170211
Everything was working great.
I was going through my email when screen went black...
I was not able to turn it on since.
I tried boot to recovery - after few seconds on TWRP flash screen it's not going nowhere... Screen is black and only notification light is white.
Same result when when just starting it.. I see Oneplus logo (powered by Android) and that is it.
Tried to boot into recovery through fastboot with the same result.
Anyone has an idea?
Thank you.

From what you're saying I see that at least the device interacts somehow. Therefore I would suggest trying this --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
...no matter how weird and unlucky your situation is

If that won't work then it may be that the Internal memory corrupted

Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.

motherninja said:
Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.
Click to expand...
Click to collapse
Thank you for responding...
My feeling is the same... Something wrong with hardware.
I did re flash TWRP. TWRP is not loading...
I did try to load TWRP through fastload - same result.
I can (and I think I will) try to flash new ROM but I do not think this would help when even TWRP is not working.
Anyone knows what is warranty situation in my case?
Thank you.

I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.

timobayl said:
I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.
Click to expand...
Click to collapse
Just wondering..
In case of sucessfull unbrick... Does phone would need to be rooted again?
I mean the result is like phone is in original/new state...?

Yes, the phone is like new from the box.
Oos 3.5.4

timobayl said:
Yes, the phone is like new from the box.
Oos 3.5.4
Click to expand...
Click to collapse
The other question is where to go from here... after it is alive again..
What caused that?
Should I go back to
- TWRP 3.0.4-1
- firmware 4.0.3
- latest ROM RR-N-v5.8.1
Thanks

Yes.
For me it works that way.
Maybe its a saver way ota oos Update to 4.0.3.
Than twrp...

TWRP 3.0.4-1 is not restoring internal storage
It is alive...
I ran unbrick tool... and it worked.
Oneplus 3t up and running..
One issue.. TWRP 3.0.4-1 is not restoring DATA completely.
It is showing "Data (excl. storage)" instead of "Data" and not not restoring internal storage (pictures, messages, files).
Anyone knows what to do?

It is the same as before. Nandroid never Backuped the internal storage.
The new twrp show this message to make it ckear for everyone.
What do you think how big is a Nandroid with internal storage?

Custom Roms do not work on my phone. Can I repair my phone using TWRP?

I rooted my phone 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?

GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.

SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.

GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.

SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.

GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.

SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?

GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?

SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?

GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.

SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.

GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.

Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).

SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.

thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.