I was careless with odin and whiped my efs partition while flashing some stock firmware.
Tried flashing more than a few other stock builds, deleted the cache file like you see on a few other dm-verity threads. Nothing I have tried works.
So I am wondering how much it would cost to send to Samsung to un-brick. Open to any other suggestions also.
If there was a way to flash or bootstrap TWRP or CWM with the bootloader locked I would be so happy. Either that or would it be possible to flash a TWRP backup of the userdata with odin? (If the setting for the FRP lock is stored in userdata land anyway.)
Any help would be greatly appreciated.
Sent from my SM-G935P using Tapatalk
Related
Alright so here is my problem. I have a GSM Galaxy Nexus. I accidentally did some wiping and I am currently left with:
Unlocked bootloader
Bootloader Access
Clock Work Mod Recovery Touch 6.0.0.0
NO ROM
Ive tried different recoveries. Ive tried many different roms. At first the names of the .zip files didnt appear in CWM, now they are. But no matter what recovery or .zipped rom I use it still says : Opening Update Package, Installing Update, Installation Aborted. It does the same thing in other recoveries such as TWRP and just says Failed. I need to get a ROM, any rom booted on my galaxy nexus. I am using a mac, but I do have access to a Windows XP machine, however its ADB is very finicky. ANY HELP WOULD BE GREATLY APPRECIATED. I am in great need of help right now.
Anything?
Thanks
Odin?
Sent from my Galaxy Nexus using xda app-developers app
In fastboot, flash the boot.img, system.img and userdata.img (THIS WILL WIPE INTERNAL STORAGE) of an appropriate official stock ROM image from Google. Then boot up the phone. It will regenerate the data/internal storage partition as it boots into stock.
Then if you want to go flashing again, reflash CWM from fastboot, boot into CWM, and flash away.
Sometimes the issue is, if you've borked up the data or internal storage, flashing from recovery won't do the trick anymore.
cmstlist said:
In fastboot, flash the boot.img, system.img and userdata.img (THIS WILL WIPE INTERNAL STORAGE) of an appropriate official stock ROM image from Google. Then boot up the phone. It will regenerate the data/internal storage partition as it boots into stock.
Then if you want to go flashing again, reflash CWM from fastboot, boot into CWM, and flash away.
Sometimes the issue is, if you've borked up the data or internal storage, flashing from recovery won't do the trick anymore.
Click to expand...
Click to collapse
Alright Im about to try that, if for some reason my internal storage is messed up, what else can I do?
If re flashing userdata from fastboot fails, then you probably have a hardware problem.
Sent from my Galaxy Nexus using Tapatalk 2
Hi all,
I have a soft-bricked GS3 that I can't revive even after using odin 3.09. Hope you guys can help.
My encrypted phone was running CM10.1.3 and I decided to update it to CM10.2 using sideload. That didn't go well and I was stuck with the CM bootloop.
So after several tries with sideloading I decided to use odin to turn it back to stock. I tried both the stock LG1 and LK3 and both went thru the flash without issues but after the phone reboots it asks for the encrypted storage password. After the password entry it's stuck at the samsung logo bootloop. (p.s. LG1 recognized my encryption p/w but LK3 didn't)
I had flashed using odin on an encrypted phone before and I don't think the encryption stays after the odin flash. Am I missing something like flashing the bootloader together with the .tar file? I tried searching and google but can't seem to find an answer.
Any suggestions? Thanks!!!
gowenf said:
Hi all,
I have a soft-bricked GS3 that I can't revive even after using odin 3.09. Hope you guys can help.
My encrypted phone was running CM10.1.3 and I decided to update it to CM10.2 using sideload. That didn't go well and I was stuck with the CM bootloop.
So after several tries with sideloading I decided to use odin to turn it back to stock. I tried both the stock LG1 and LK3 and both went thru the flash without issues but after the phone reboots it asks for the encrypted storage password. After the password entry it's stuck at the samsung logo bootloop. (p.s. LG1 recognized my encryption p/w but LK3 didn't)
I had flashed using odin on an encrypted phone before and I don't think the encryption stays after the odin flash. Am I missing something like flashing the bootloader together with the .tar file? I tried searching and google but can't seem to find an answer.
Any suggestions? Thanks!!!
Click to expand...
Click to collapse
Can you try booting into recovery and doing a hard wipe/factory reset? If you flashed a stock *.tar file via Odin, it should deliver a complete stock system with all partitions updated. There shouldn't be need to flash a bootloader separately.
Larry2999 said:
Can you try booting into recovery and doing a hard wipe/factory reset? If you flashed a stock *.tar file via Odin, it should deliver a complete stock system with all partitions updated. There shouldn't be need to flash a bootloader separately.
Click to expand...
Click to collapse
Got it. Thanks!! I kept thinking that I couldn't use the recovery because CWM does not see the encrypted partition and therefore cannot do a hard wipe. I totally forgot that after odin I was back to stock recovery and therefore could do the wipe. Thanks again!!
Sprint Note 4, when flashing the official Rom i clicked on Nand Erase All, flash went fine, but the phone stays forever on the Sprint Spark screen, any steps to fix this issue? I can get into recovery and download mode, tried to wipe cache and dalvik in TWRP but i get errors, can not mount.
thanks in advance for the help.
anybody please?
MHeat said:
anybody please?
Click to expand...
Click to collapse
You flashed TWRP after it failed to boot? If so, I wish you didn't do either the nand erase or flash TWRP.
If TWRP fails to mount to wipe, you need factory recovery or Philz CWM to wipe cache and factory reset.
To be clear, you need to wipe cache, dalvik-cache and data and power down. Boot into download mode and flash stock tar with Odin defaults. I'm not sure if the Note 4 just requires a wipe and Odin stock tar or the PIT with repartition (PIT for Sprint Note 4 seems to be MIA). Hopefully just the wipe works.
Here's Philz CWM recovery for Note 4:
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
If that doesn't work, you need stock recovery. Last time I flashed stock recovery, it required a tar.md5 to flash. Had to search for a Windows tool to modify it, adding the md5 hash to tar so Odin would see and use it.
And one more thing. If you succeed in wiping, try to boot before Odin of stock tar. Seems Odin is risky these days. I've read recently that there's yet another "fix" Samsung has identified for Odin flashing for upcoming security patch. Best to limit Odin flashes to as needed only.
Sent from my SM-N920P Note 4 via Tapatalk
thanks for you explanation, i will try it. Let me tell you, remember i already flashed the stock tar multiple times, i might be mistaken but i thought the stock tar has the oem recovery included, the problem is i can not get into stock recovery, it just bootloops and the phone restarts again, i will try flashing the stock tar again and then Philz touch recovery and see if i can wipe. Will let you know how it goes in a few minutes.
thanks again.
just to let you know, the phone booted, had to flash the clean stock image, then extract the recovery image from the tar file, after that i used a utility to convert recovery.img to a tar file in order to flash it in odin, after a while it booted, right now updating over the air to cok1, lets hope it works now.
appreciate the time you took to help me out.
I'm not clear on what you're saying. I gather that flashing the tar didn't allow you to get to stock recovery and it still wouldn't boot?
Then you tried Philz CWM recovery to wipe and it booted? If so, I'd think you were in the clear at this point, not needing to restore stock recovery but flash the tar?
When you say you had to extract stock recovery, was it still not allowing you to get to stock recovery when tar was flashed or did that fail? If so, which tar? I'd think you could have moved on to OK1 tar?
Or were you thinking that I meant you had to use both recoveries to wipe to restore function?
It's good you're making progress on your own, I'm just not following the results and reasoning fully. I'd like to know so I'm asking. TIA.
Edit: Or did you have to flash stock recovery to wipe? Philz CWM recovery didn't flash or wouldn't mount or what? Read your reply again and thought this may be the direction you went.
Sent from my SM-N920P Note 4 via Tapatalk
sorry for the confusion, i flashed the stock tar file COJ6, still the phone would not boot and could not get into stock recovery, do not know why
then i flashed just Philz recovery and was able to wipe cache,dalvik and data
For some reason it did not boot, then after i flashed just the stock recovery ( in order to do that, i extracted the recovery from the COJ6 tar, then used a program to convert the recovery.img to .tar in order to be able to flash it in Odin, after that the phone booted and updated over the air to COK1) Just to make sure i tried to go into stock recovery ( VOL UP+HOME+POWER) and was successful, got access to stock recovery. Before i was not able to go into stock recovery for some reason.
So you didn't try to flash stock tar after the Philz recovery wipe? I was suggesting try to boot; if it didn't boot, try the stock tar.
Am I wrong to say that maybe you didn't have to flash the stock recovery? Philz recovery maybe gets the credit as the easier fix in this case. Would you agree with that or is that unknown?
Thanks for clarifying. Your response may clarify the suggested fix. TIA.
Sent from my SM-N920P Note 4 via Tapatalk
Well, after i wiped with Philz it still did not boot, then after the stock recovery it booted, it took a while, i thought it did not work but eventually it did boot, the phone definitely had something wrong since i could not even access the stock recovery before, now i can, it says installing system update, then its says something like no command, and then it enters recovery, this was impossible to achieve before.
Did the OK1 OTA complete and boot yet?
Sent from my SM-N920P Note 4 via Tapatalk
It did complete and booted just fine, everything seems to be in order, crossing fingers LOL
I have a lenovo P2a42(of my late brother) with data locked inside.
Developer options not enabled
Don't know password
bootloader not unlocked
So, my plan was to download flash tool and flash a custom recovery and then proceed from their by deleting password.key file from /data.
The flash tool I got was Lenovo_Downloader_v1.0.3 and Lenovo_Downloader_v1.0.2. Both of them do not have an option to flash only recovery.
Has someone flashed only recovery before? Let me know your suggestions.
So, I had an unlocked BL, rooted phone, with TWRP 3.3.1 deestroy.
For some reason, I booted into my recovery, wiped all my data, through format and advanced wipe feature. I even changed slots (just to make sure) and formatted data, and advanced wipe.
I then locked my bootloader, through adb fastboot command. Rebooted my phone, which had nothing to boot to. Then I unlocked my bootloader, rebooted my phone again, and it got booted into TWRP 3.3.1
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?
This might be helpful for you:
https://github.com/tkchn/daisyinstall
Lol. I didn't ask for how to flash a custom ROM.
Just need help understanding how the bootloader works? Where does TWRP get installed? Why after wiping did TWRP survive?
shazee666 said:
Now my understanding is, unlocking bootloader, and using formatting options from TWRP should have wiped my data completely.
Then why did my phone boot into TWRP 3.3.1 after I unlocked the BL?
Click to expand...
Click to collapse
Different things live on different partitions.
TWRP does not live on the userdata partition so wiping data cannot remove TWRP.
You need to use fastboot or miflash to do a full flash and restore a phone to stock.
Okay. This cleared somethings...
If you have tampered with the phone's partitions (TWRP patches itself into boot.img) you should never lock the Bootloader. Basically when the Bootloader is locked, the phone checks all the partitions of the phone if they've been tampered or still the same as Xiaomi designed it. In the case that they've been tampered, the phone won't boot itself, this helps with a lot of security issues. Never lock your Bootloader if you've made changes to the system, boot or other partitions (except userdata, this is why enabling cam2api and locking the BL won't mess up your device because the persist command stores the command in data partition). If you want to lock the BL, just flash the stock rom beforehand. Cheers.