I need to recover a NTG, are there any images for recovery? It is not booting up properly because I replaced the patch android.policy.jar and services.jar for a NST to use NookTouchTools.
So is there any factory images any where I can use Clockwork on SD to reflash from?
Thanks!
I fixed this by adding my jar file backup to "glownooter-1-5-26" zip file so it copied the files back over when I used Clockwork to apply glownooter. Good for now, but still would be nice to have recovery images.
Boot from noogie and look?
I forget which partition it's on, but there's a factory.zip on the NST and glowworm that I think has what you need in it. Copy it out and unzip it, confirm it has the unique stuff from /rom in it correctly.
And now that you're running again, make your own recovery image, too, using dd or similar.
If you want to undo your changes so far to make that viable recovery image, the 8 failed boots method works on the glowworm, as does echoing data into bootcnt to force a reset.
Help unbricking my nook glowlight?
Hello,
I recently got a nook glowlight and foolishly tried to apply the touchnooter package to root it, as if it was a NST. After several efforts to restore it, including noogie, CWM, and everything else I read on this forum; my nook is at a state of never starting up without the sd card in; and sometimes starting up with the sd card in, depending on what partition is in (noogie and CWM work).
Can someone, more experienced than me, help me recover my nook, to its stock state? I made a backup with noogie, but I don't think it's correct anymore.
Thanks a lot,
a noob
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
I used TWRP to wipe all my partitions under advanced wipe.
I Odin'ed the stock kernel, stock rom and TWRP.
I used TWRP to mount the efs partition, and adb pushed my backed up efs.zip into that partition.
I checked using the TWRP file manager that the files and folders are all in the efs partition.
But after a reboot into TWRP, the efs partition would become empty again, as if I never transfered the files.
And off course, my phone is now stuck at the notorious Samsung logo boot loop.
So why did the files delete themselves after every boot? And is there any way to solve my boot-looping issues?
My current partition size:
Boot (10mb)
System (2135mb)
Data (0mb)
Cache (62mb)
Recover (10mb)
EFS (4mb) it is empty, but still has 4mb?
First question is what firmware were you on before all this? Second question is why did you do all this?
If you were not on mf3 firmware get the stock firmware from sammobile.com and flash that in Odin, PDA. Do not check re-root partition. Hopefully that get your phone to work again.
Wooo hooo it works
Ahh I fixed it! Sorry for the troubles.
I'm glad you got it fixed. But don't mess all that stuff you did.
jd1639 said:
I'm glad you got it fixed. But don't mess all that stuff you did.
Click to expand...
Click to collapse
Yea, curiousity definitely killed the cat. This may be my last of my 9 lives.
Would do sufficient research before attempting theses kind of tasks again.
Thank you. I fixed the problem following several other threads in this forum. Vast amount of knowledge here, just a bit too scattered.
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
merlin21 said:
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
Click to expand...
Click to collapse
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Here the full Backup for the CAN-L11:
https://drive.google.com/open?id=0B134drJ4-Ed0R3VSY3A5NGpjVWc
Format /data, reboot recovery and than restore from backup. After the restore is complete make a wipe.
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
merlin21 said:
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
Click to expand...
Click to collapse
Inside the folder twrp and its subfolders there it is system.img. I'm downloading it myself.
Sent from my victara using XDA Labs
Share if you have another workarounds for me
Gesendet von meinem LG-D802 mit Tapatalk
@merlin21 yes it sounds like my problem after I tried to flash the emui5 beta.
My phone is fully working again with the backup I posted.
This is not the Chinese version, if nothing works, you can try the caz ROM. But there are massive problems with the gapps, they are not included in the rom.
Gesendet von meinem HUAWEI CAN-L11 mit Tapatalk
@ -=MoRpH=-
i just flashed the twrp.img with fastboot from xelfmade v22.12. and then rebooted twrp.
Then formated data and confirmed with yes - rebooted recovery and tried to restore your twrp. It did not restore and aborted instantly with the error message
during restoreing cust...
extractTarFork() proecess ended with ERROR: 255
what could that be?
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
That only work if the is not rooted... Idk whats up with that, but for now i use the quicksetting screenshot function.
Somehow it worked with my rooted device before. Must be the decrypted data partition?
With the recovery of your backup I could not access data or change memory from data to sd. What version do you use?
I flashed xelfmades v22 and now have rw access and could backup all partitions and restore. Root and xposed modules everything works, just the knock on screen to capture don't...
merlin21 said:
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
I have the same problem! What do you mean by "I had to use the cust from my backup" ? Sadly i dont have any data from my own backup..
can you tell me what to do to get the backup from @murph to work without error?
--solved.
P1xl said:
--solved.
Click to expand...
Click to collapse
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
rak500 said:
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
P1xl said:
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
Click to expand...
Click to collapse
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Thanks for your help my phone is saved with your method!!!
i downgraded my MLA-L03 variant with this, but now im stuck in french language with no other languages to choose from
Vinnom said:
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Click to expand...
Click to collapse
someone please make this thread sticky!!!!!!!
there are some guides in internet how to get nougat for nova and that is were I broke my phone. I was searching solutions for a week, DLed Flahsed tons of things nothing worked. this one fully worked!!!!!!!!!!!!!!!!!!!!
rak500 said:
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Click to expand...
Click to collapse
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Bunkier said:
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Click to expand...
Click to collapse
Frankly, I don't know. I had not modified the partitions prior to bricking my phone, so I think the partitioning was OK. However, I think one of the TWRP availble in this forum can format Data partition properly, which would utlimately allow you to select which File Format you want. I haven't tried it myself, and I haven't been able to do much with TWRP since I flashed Lineage unfortunately. Most of my Mods were just upgrading and I had to ADB Sideload pretty much everything since I flashed Lineage...
Sorry I couldn't be more helpful than that!
Been struggling with a TWRP restore gone wrong for over a week now.
TWRPs today have many options for backup, a lot of which I couldn't find info online.
Usually I backup only Boot, Data and System.
But tend to make a first backup after installing TWRP with all options included.
On the Galaxy S10+ there are:
Baseband
Boot
Cache
Data (excl. storage)
EFS
Product
Product Image
System
System Image
Vendor
Vendor Image
Recently I was restoring several backups and restored this first backup with all options included.
Since, the phone boots and is stuck on the boot screen.
I can still boot into TWRP.
Can someone please help me understand how to solve this? :fingers-crossed:
I run LineageOS 17.1 with ianmacd TWRP, rooted with Magisk.
Can I solve this through TWRP?
Will flashing stock firmware through Odin is the only option? Or an option that will solve this at all?
Also if someone can detail what the different option are, that would be amazing!
If you can't restore another backup, then yeah it looks like you will have to use Odin.
Managed to get back to the ROM eventually.
If anyone can share info about the different options and what they actually are/do - will be very appreciated!
Pogromonolith said:
Managed to get back to the ROM eventually.
If anyone can share info about the different options and what they actually are/do - will be very appreciated!
Click to expand...
Click to collapse
These do exactly what the name suggests. I don't think there is much to explain. Usually you would only backup /Data and /System partitions, eventually /Boot and /Vendor.