Flashing a stock rom causes bootloop. - Nexus 4 Q&A, Help & Troubleshooting

As above. While the phone technically works I cannot flash the latest stock rom (the set about unlocking, rooting, installing a custom recovery) as it loops....ive dropped back to the original stock image (4.4.4) which boots fine....I then went back up to LMY47V which loops and currently downloading KTU84 to see if that works....now just to add to all of this I was given the phone with a cracked screen which ive replaced but it came to me dead so I don't know the previous history....and thought that the advent of me fitting the screen caused it which I doubt....but the thought was there.....
The only other option if KTU84P doesn't work is to drop back to 4.4.4 and go up gradually......
Anyone else had this...?

Well, so far, nothing works apart from the stock image (tried a few other stockers) but nothing - tried installing custom recovery TWRP 3.x which installs fine....just wont boot...

Try stock flashing using Nexus root kit and check Soft bricked radio button
Sent from my Nexus 4 using Tapatalk

I'm using the Nexus Root toolkit - is that the one youre talking about ( as I cant see the "softbricked radio button") - ive got "Softbricked/bootloop" but tried that which didn't work....

I did try the original 4.4.4 image (the first one) which does boot. And then tried manually flashing the radio separately but that didn't work (but TBH I'm not sure that I did it correctly) - so, do you think its a radio issue - the reason it wont boot??

Yes, that will be the right radio button. There is only one for stock flash section. Which radio are you flashing? If its Nexus LTE zip then it's only for Lollipop ROMs 5+. Try flashing latest Lollipop stock and if it boots then flash radio. That's what I did.
If not then back to KK.
Sent from my Nexus 4 using Tapatalk

Try this: flash the latest stock ROM using fastboot commands and, after flashing the last partition, flash the userdata.img file, use the buttons to boot directly to recovery from fastboot, perform a factory wipe, and reboot.

Ok - thanks for that - haven't done the fast boot commands for a while...! ill try it now....
The other thing I noticed was the battery is draining really fast (while in bootloop) the back of it is very hot....so much so that plugged into the laptop wasn't enough to keep it running - had to transfer it to a charger....

Looking at my file I downloaded from google... (I was just about to start) I noticed I don't have the radio firmware? so, all this time while ive been reflashing and trying different images from google (stock images) ive not been flashing the radio firmware - I thought they would have included that!! am I right in thinking that's why its been bootlooping as the radio firmware is at stock (the reason why only the original base image boots)??

Well, while I was installing I flashed twrp3 as the recovery and used that when I went in to manually reset it gave me the error "cache invalid argument" - would that have any bearing??

Well, tried that and it sat there....thought id try jumping ahead a little....flashed a cm13 nightly along with a radio firmware file (a .zip) using twrp...but still the same....missing something somewhere....

I presume you have NRT installed and tried; it downloads and extracts factory images before flashing. If you are flashing latest official stock lmy48t check contents of the downloaded image. Should be
cd C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Factory_Images\occam-lmy48t-factory-416938f1
dir /b
bootloader-mako-makoz30f.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-lmy48t
image-occam-lmy48t.zip
radio-mako-m9615a-cefwmazm-2.0.1701.07.img
Batch file that NRT runs is flash-all.bat; third line is radio flashing
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastboot reboot-bootloader
fastboot -w update image-occam-lmy48t.zip
Executing fastboot commands manually should achieve same result

Yep - using the wugfresh stuff tried it about a dozen times with different stock images....never had a problem like this before....

tried as you said - tried to flash manually and also tried using the bat file....still the same - flashed back to jdq39 and it boots straight back up...weird....

Can I ask silly question? Was bootloader unlocked?
Sent from my Nexus 4 using Tapatalk

If the bootloader was not unlocked, no ROM could be flashed to the phone.

Exactly. So if all fastboot commands in flash_all.bat run error free phone should boot OK. NRT runs log in a separate window so any error is easily noticeable. The only thing that comes to mind is how long it takes to boot after rom flash; I think mine took close to 20 min of bouncing balls before I saw Android logo. So may waiting for longer time will resolve it.

Yep - unlocked the bootloader (and relocked it) hoping that would shift it into life!! but no...
Ive tried the waiting game....left it on at the office at the end of the day, came back in the next day to see it still "trying to boot..."

Came across a procedure on how to pull log during bootloop. Check it out if interested. I haven't tested it. http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
Sent from my Nexus 4 using Tapatalk

Yep - will do - just for the record I reflashed back to 4.2.2 relocked, booted, let the phone download a 4.3 update and flash...totally stock....just sat there.....just had a look at that link (looks promising) so I'm going to go back upto the latest build and then install twrp then flash the file to see if I can see whats going on behind....

Related

MOTOACTV ROMs

Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.

Stock,unlocked & rooted,updating to 4.3

Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.
i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.
forgot to attach the screenshots
GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app

[Q] Flashing 4.3plus then Freezing

My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
onyxkhan said:
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
Click to expand...
Click to collapse
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Fixed
RimanX said:
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Click to expand...
Click to collapse
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
RimanX said:
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
Click to expand...
Click to collapse
How did you flash the 4.2.2 image and the stock recovery?
Freeje said:
How did you flash the 4.2.2 image and the stock recovery?
Click to expand...
Click to collapse
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
RimanX said:
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
Click to expand...
Click to collapse
From where did you get the 4.2.2 image that you can flash from stock recovery? I have a problem of getting the 4.3+ installed since I flashed the CWM recovery. I tried flashing a stock recovery but failed every time. My question is, would flashing an earlier ROM such 4.2.2 enable me to get the 4.3+ update or do I still have to flash a stock recovery?
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
4.3/4.4 crash. I fixed mine finally! 4.4 working great, no crashing!
astuermer said:
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
Click to expand...
Click to collapse
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
4.4.2 Freezing- FIXED!
TerryRed said:
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
Click to expand...
Click to collapse
@TerryRed:
You saved my bacon! I was having a similar issue with a totally borked root attempt... I was frustrated with repeated attempts to recover from the freezing issue. I followed your instructions and recovered the Tegra. Like you, I discovered that if I continually the device active by tapping and moving the screen, I could use the device. My idle limit was about 5 seconds, though.
In a nut shell, and while pretending to be a poor excuse for DJ 'scratching' (or do they call them 'controllerists' now?) I:
* Made sure ADB Debugging was enabled
* Copied the 'Stock-4.4.2-TegraNote7.zip' archive to the device's internal storage
* Ran SuperTool 2.2 and ONLY flashed the stock recovery
* Rebooted
[Resume silly DJ motions, while frantically setting up WIFI]
* Checked for, and downloaded the OTA update manually [OTA FOUND!!!]
* Waited the agonizing 10 second countdown for the device to initialize the installation
* Let Android do it's thing
!! SUCCESS !!
Thank you, and all of the guys here at XDA who donate their time, talent, and valuable info that help us mere muggles free our devices and take them to new heights.
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Bricked as well
OrangeCalculator said:
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Click to expand...
Click to collapse
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
NVflash unbricked
jardam.cz said:
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
Click to expand...
Click to collapse
So, to fix the boot loop it is as simple as it can be. I can't believe I didn't find that earlier. (BTW I didn't find a clear answer in the forum until today, thanks to hacktrix2006)
Just download the NVflash and the image mentioned in post #2 in following thread. Follow the instructions to switch tablet into APX mode, install the driver and start the flashing. Flawlessly done. No problem. Got rid of the Chinese OS (not supporting Google).
Really cool!
Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.

[Q] Stuck on boot animation -- all ROMS

My Nexus 4 was previously running 4.4.2 ... I had a modified kernel patch (done via an app and I can't remember the name of it) and it was rooted. On occasion I would pickup the phone just to find out it had shut down. I would reboot it and it would be fine for days. One day it got stuck on the boot animation. It just wouldn't pass that point. Then the battery died (I assume) so I plugged it in via USB to both wall and PC and it would not charge. I had to put in on my wireless charging pad and it charged right up .. but still would not pass the animation.
Since then I have individually flashed each file manually from the newest lolipop ROM. Tried the nexus toolkit including most of the 4.X.X stock ROMS. Did a format and erase. Booted Clockwork Recovery and installed 5.0 from sdcard. (I can access the sdcard via USB on CWM). I flashed the kernel, Radio and bootloader several times each. I tried the Cyan ROM 10.x too
After the second attempt installing 5.0 (using the toolkit) I did get "Android is upgrading ... Optimizing apps" then it hung on "starting apps" and the animation continued for hours. I have had no other success since then.
I am at a complete loss. So I turn to the experts in hope of salvation.
Any idea what I'm doing wrong or what else I should be doing?
Your emmc chip is fried.. Take the phone to a service center
Sent from my Nexus 4 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2964619
Well, here's a new twist. I'm able to flash 4.2 and 4.2.2 with no problems .. but 4.3 OTA and even manual flash will reproduce the stuck on animated logo problem.
I installed a sensor app and it seems like all sensors are working fine.
I remember that I was using the franco kernel before my problems started. Maybe I have a botched kernel. But I have flashed it when I did all the ROMs did I not?
What is the earliest kernel version that is compatible with 4.3, 4.4 and 5.0?
Does anyone know why I can't flash beyond 4.2.2?
Is there a way to systematically test each .img to discover the problem?
Also, even though I have USB debugging enabled, I can't use ADB to sideload at all. I keep getting ADB was not found. I can use ADB without problems on my nexus 5.
bump
Same issue here. Could flash 4.2.2 and update with ota to 4.4.4, after that the boot animation stay's for more then an hour. Any idea how to solve this?
Just to share my own experience on similar issue..
my N4 was official Lollipop 5.0.1 unrooted & locked.
Unlocked & installed clockworkmod & latest official pa rom -> stuck in boot screen. (had done all resets etc )
full wipe & latest official CM nightly -> stuck in boot screen.
full wipe & installed full official google 4.4.4 image -> phone booted ok.
full wipe & install cwm & latest official pa rom (same as earlier) -> phone booted ok.
So my conclusion was that it had something to do with lollipop modem etc part, that didnt quite work with roms i tried to run.
BTW for some reason wasnt able to get adb sideload to work for me neither, so installed the factory images on fastboot / flash-all.bat
If you have a backup with USB debugging enabled, you could restore it and try to take a logcat while booting. This would make finding the culprit a lot easier.

Help Plz...Stock recovery missing and unable to install any recovery !

Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.
levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:
I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.

Categories

Resources