Okay, i'm sending my phone to warranty, as title says. My phones /data has corrupted (i think), and imei is gone. I suspect the corrupted data, because clockwork can't access data, and nothing else can access it too. I was thinking have I done everything, so will you comment back? I have done following
-Restored stock b136(cannot boot, because cannot access /data)
-Restored stock partitions(IDK did it work because of /data)
-And restored stock cust.
Also, the last time it boot, it had stock FW, so if they can open data, there is only data from stock rom. Need fast comments, because my dad is taking it to shop today.
If you definitely flashed B136 and restored partitions, then you shouldn't worry about anything else. Make sure you definitely have the stock recovery (blue letters in the menu).
You boot into bootloader (pink screen) by holding Vol+, VOL- and Power.
An even easier way to get everything stock, is to flash a stock ROM. Once a stock Rom is flashed, you recovery gets replaced as well.
Related
Hello,
My device is a NEXUS 7 3G (GSM / HSPA +) and am using Twrp recovery and have a question about backup menu.
Are the default options checked enough (Boot, System and Data)? Do I click check the radio option? When it is necessary the radio option?
I Know cache and recovery are not necessary but the question is the radio.
Thanks and sorry for my writing in English, very poor ... sorry
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
bftb0 said:
It would be rather unusual for a radio to be flashed by anything other than a factory ROM; so the need to be restoring it is somewhat unusual.
As with the bootloader, it is probably best to minimize the amount of flashing you do of the radio partition.
TWRP also lets you choose which partitions are restored using the same toggles, so even if it were present in a backup, I don't think TWRP forces you to restore it.
I have a grouper (not tilapia) N7, and (besides more typical ROM backups) I keep a pure-stock, completely unconfigured ROM TWRP backup including the stock recovery standing by (plus a copy stored safely off the device).
I think having pure stock backups is something everybody should do. Not only for factory return scenarios, but also for applying OTAs (make custom ROM backup, revert to pure stock, apply OTA, capture yet another pure-stock backup, restore back to custom ROM). This gets you:
- return to stock any time
- for RMA / relock scenarios
- no problem OTA installs
- reference stock ROMs from every release (for restoring individual stock files)
good luck.
Click to expand...
Click to collapse
Thank you very much for the reply. Now I have the bootloader open and I'm leaving the tablet as I like and I intend to make a backup before root.
Thanks
Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Bump
Kicking Deuce on the Beast, Note 3
sacgeek said:
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Click to expand...
Click to collapse
I am essentially having the same problem. I am currently running on Biggins ROM and that had me install a unified verision of the NC2 and NC4 kernels (I came from NC4 prior to flashing). I wanted to go back to stock root and flashed my backup from SS, everything went well so I restarted and just like you the phone just never went passed the Verizon logo screen. So I reinstalled the Biggins ROM and it works fine now but I also want to know what I have to do when I want to install other ROMS or simply go back to stock root.
This might be the weirdest Issue i've ever had with a phone.
Everytime I turn my phone off, 5 minutes after it it boots into the recovery and deletes the data partition.
I have no idea what the hell could cause this, but it's making my phone unusable -.-
I'm not sure if you've unlocked the bootloader and installed an alternate recovery (e.g one of the various TWRP versions), but apparently there is a situation where after a nandroid restore the data partition will get automatically reset. I'm hazy on the why but I think it is due to detection of an issue which OOS thinks is a hack and the reset is a safety feature. One of the TWRP versions can make sure that does not happen. Use the latest TWRP from the user @xdvs23.
Good Luck
I've experienced similar issues on another phone. What I think happened is a security feature has been tripped, and the bootloader knows that it has to perform a data reset because of a hidden flag somewhere in the bootloader partitions.
Your custom recovery clears user data, but does not reset the flag. Hence the loop.
Flash stock recovery.
Let the data reset happen and let it clear user data automatically one last time.
It should be the last.
You can then flash your custom recovery (or not).
I've always used stock recovery on my devices since I ran into that issue.
To flash, I use FlashFire or I boot the recovery with fastboot directly. Works the same.