Related
Hello,
Some time ago, I had a problem with phone freezing on the IPL/SPL screen after flashing. I have solved it by creating and restoring SD-backup. Everything is OK, but now when I enter bootloader, it still asks me to restore SD image with that countdown despite the fact that I've already formatted SD after restoring the backup. It isn't any error, as the phone gets into the bootloader mode after countdown. However, I still want to ged rid of this, because I once accidentally pressed Voice command two times when I wanted to enter bootloader and Oops - it began formatting whole BINFS. So I had to flash ROM and everything else again which was very annoying. So how can I get rid of that screen?
That means that the first 0x200 bytes of your SD still have the SD backup information. If you have a card-writer you can fix it by getting a hex-editor program and make a file with, lets say... 0x10000 bytes of nulls (zeros), and then use a tool by itsme called psdwrite to write that file to the start of the card.
Then i think by using it like that in Wizard the WM OS asks to format it.
good luck
PS:
Do you have a backup of that SD backup? I think it's the most important thing a Wizard user can do is to keep an image of the entire phone. Don't get rid of it!
EDIT:
Actually, you don't need a card writer because psdwrite can use your PPC as one Just be sure to list all devices to know which is the Wizard
hmm I've already formatted a card, so the backup is gone but I can make another backup.. Can I use that psdwrite to restore a SD backup into some file I can store into my desktop PC? Because I need to use the SD normally.. I mean, I backup files from SD, format it, make SD backup again, then use the psdwrite to extract that backup from card, then use psdwrite to "clean" the card and format it and restore backed-up files..
whitewash said:
hmm I've already formatted a card, so the backup is gone but I can make another backup.. Can I use that psdwrite to restore a SD backup into some file I can store into my desktop PC? Because I need to use the SD normally.. I mean, I backup files from SD, format it, make SD backup again, then use the psdwrite to extract that backup from card, then use psdwrite to "clean" the card and format it and restore backed-up files..
Click to expand...
Click to collapse
Exactly what i did
I made a backup with r2sd all and then used psdread.exe to copy it to my PC (where it's quite safe, including a CD backup). If i ever come to need it i simply use psdwrite.exe to pass it back to the SD and use it to restore my Wizard
THX.
Could you pls. post the link to the psdwrite?
EDIT: I found something at http://forum.xda-developers.com/showthread.php?t=224536&highlight=psdwrite . Is it current or is there any new version?
whitewash said:
THX.
Could you pls. post the link to the psdwrite?
EDIT: I found something at http://forum.xda-developers.com/showthread.php?t=224536&highlight=psdwrite . Is it current or is there any new version?
Click to expand...
Click to collapse
I'd advise you to read the wiki and also browse through wilem's (itsme) site and look for the latest package of his itsutils
http://www.xs4all.nl/~itsme/projects/xda/tools.html
cheers
EDIT:
latest update from 3 days ago
Ok, I have the PSDread. How many bytes should I copy from SD to BIN file to get entire SD backup from card?
whitewash said:
Ok, I have the PSDread. How many bytes should I copy from SD to BIN file to get entire SD backup from card?
Click to expand...
Click to collapse
I can't recall exactly as i'm at work now but the mtty program should display the backup size.
Another solution is to go to the Typhoon wiki in this forum and make a sum of all the areas of the ROM/DOC... or i can give a more precise answer later on when i get home
Ok, I'll wait.. So far I have made backup of first 145 MBytes (that should be enough) but exact value would be appreciated.
whitewash said:
Ok, I'll wait.. So far I have made backup of first 145 MBytes (that should be enough) but exact value would be appreciated.
Click to expand...
Click to collapse
Ok, my dump is exactly 73.927.168 bytes so i guess that looking around that location you might see the end of the file.
Saving about 75/80MB of the dump will probably include all the data but the really best option is to blank the SD card before making the backup and then see where the last bytes are and the just crop.
In the end it doesn't really matter the bytes after the end since the phone won't use them at all
cheers
I've been running Apps2sd for quite a while, and have made a lot of nandroid +ext backups while I was using it. I've decided that I actually don't need apps2sd, so I repartitioned my SD card. What will happen if I try to restore one of my nand +ext backups now that I don't have that ext partition on my sd card???
good question... probably an error code.
bump...anyone?
I'm in the process of re-flashing and re-configuring my phone now so I can't try it yet
Just try it and find out. It shouldn't hurt anything.
mrcharlesiv said:
Just try it and find out. It shouldn't hurt anything.
Click to expand...
Click to collapse
I'm going to once I finish configuring and make a nand backup of what I'm running now. Just wasn't sure if anyone had experienced this and knew what would happen.
Looks like it restores just fine, but locks up at boot screen...
Oh well, guess I can't use any of my nand backups
Have u tried deleting the ext2.tar file in your nandroid backups? Try that and see if it boots all the way.
All I can think of is, download titanium backup or something, backup all your apps using it. and then try doing a nand restore with the .tar file removed. See if that fixes the boot problem.
Edit: Save the .tar file because you can always open it with a program like 7-zip and pull out the "app" and "app-private" folders, then push them onto your phone with adb
Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?
I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc
nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved
thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S
nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?
jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..
OK to start I have CM7.1 on my eMMC works fine for many months. I want to install MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer ROM and it does not seem to work. Using CWM 3.2.0.1 flashing looks successful but when I reboot CM&.1 is still on the eMMC.
Tried doing a reset to default using EVRY technich suggested on these forums. No Go.
Using ADB I thought I would manually delete and push the system files over. I mount the system partition /dev/block/mmcblk0p5 and removed the existing files then pushed the new system files. But once I unmount and remount it reverts to the old files. The changes don't write dispite seeing the differences with an ls -al in ADB before the umount.
So I thought I would check the partitions and using fdisk via ADB. Deleted partitions 5, 6,7,8 and rebuilt them but when I write I get.
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
I also used the 1 - 5 - 6 - 7 - 8 fix and format zips with no joy.
I can boot to MIUI via SD but I want to put this on the eMMC.
Any ideas on how to fix this?
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Edit: oh, you changed the version in your original post to 3.2.0.1. That version is ok.
leapinlar said:
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Click to expand...
Click to collapse
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
Which matches the results I was seeing from adb.
rodneyshupe said:
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
Which matches the results I was seeing from adb.
Click to expand...
Click to collapse
When you boot to your SD version of your ROM, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip. They act like they have been written to, but when you come back, nothing has changed.
leapinlar said:
When you boot to your SD version, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip.
Click to expand...
Click to collapse
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
rodneyshupe said:
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
Click to expand...
Click to collapse
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard of anybody that this happened to their embedded chip. Sorry.
leapinlar said:
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard anybody that this happened to for their embedded chip. Sorry.
Click to expand...
Click to collapse
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
rodneyshupe said:
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
Click to expand...
Click to collapse
For my SD I tried everything. Images, formatting, partitioning, etc. Nothing could be written to the device.
You can make your own images of emmc by dding in reverse and write emmc partitions to your SD via adb. But if it is truly read only like my SD was, you will be able to write nothing back no matter what tool you use.
Yea I was hopping I could get an image of the entire working eMMC that included the partition tables and see if that worked in case the problem is related to a setting in the partition table.
Dear community,
About a year after i really wanted to root my htc one mini 2, i decided I wanted to factory reset my phone.
So after this year I forgot everything i knew, and managed to wipe the whole OS...
I would really appreciate any hints that might help me to fix my phone again.
Info on where i'm standing with the problem:
1. I tried to find my stock ROM on this site and couldn't because under "firmware" i can only find 2.18.161.2, though mine is 2.18.166.1 - does this matter? It's the vodafone one, and they even have a nandroid backup for my version, but not the stock firmware.
2. I have TWRP installed, and the site tells me i need to have my bootloader locked to flash stock roms. I have no problem relocking or unlocking it, but in the relocked state, i can not access TWRP recovery and use the sideload feature to flash the rom. The phone always goes back to the bootloader screen and the title says " **security warning** ".
3. i would really like to get my phone back as close to it's stock state as possible.
I am kind of afraid of flashing the available stock firmware, as I don't know how to proceed from there without TWRP.
I read a lot about this topic, but i'm kind of loosing it right now...
Can some kind soul lend me their wisdom and help me out?
Would be much appreciated
mfG Montor
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
TryllZ said:
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
Click to expand...
Click to collapse
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Montor said:
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Click to expand...
Click to collapse
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For RUU (zip file)
- Download the available RUU and rename it to 0P8BIMG.zip (I'm assuming its the same a normal HTC One Mini 2)
- Copy the file into the root of the MMC
- Insert MMC into device
- Boot up device and enter boot loader
- As the device enters bootloader it will automatically start flashing, if all conditions are met.
NB: I frankly can't remember if this will work with TWRP installed.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
TryllZ said:
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
Click to expand...
Click to collapse
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Montor said:
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Click to expand...
Click to collapse
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
TryllZ said:
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
Click to expand...
Click to collapse
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Montor said:
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Click to expand...
Click to collapse
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
TryllZ said:
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
Click to expand...
Click to collapse
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Montor said:
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Click to expand...
Click to collapse
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
TryllZ said:
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
Click to expand...
Click to collapse
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Montor said:
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Click to expand...
Click to collapse
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
TryllZ said:
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
Click to expand...
Click to collapse
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Montor said:
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Click to expand...
Click to collapse
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
You mentioned its not showing as Mass Storage, what is it showing up as ?
TryllZ said:
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
Click to expand...
Click to collapse
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Montor said:
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Click to expand...
Click to collapse
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
TryllZ said:
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
Click to expand...
Click to collapse
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Montor said:
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Click to expand...
Click to collapse
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
TryllZ said:
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
Click to expand...
Click to collapse
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Montor said:
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Click to expand...
Click to collapse
Great...:good::good::good:
Frankly I never imagined it could be the 64GB, I was purely under the assumption TWRP would accept 64GB MMC, anyway I lacked that information but now I know.
Nope, its working now is more than enough for me.