Hi, i'm having trouble flashing back to stock.
I've got the latest stock firmware from sammobile.
Using twrp to install it says missing META-INF as the firmware zip isn't made the same as custom firmware.
Adding the tar.md5 to ap in odin flashes the boot and recovery but goes extremely slow when it starts flashing system (left it 2 hours and it hadn't even got half way) I'm guessing that's not normal.
I took a backup with twrp before I started flashing in twrp which flashes fine but I get endless boot loop when trying to start it.
I've tried fastboot but it doesn't detect the tablet.
I've tried different usb ports, cables, different versions of odin and different stock firmware. I'm ready to throw it out the window.
One thing to note is the [P600][Touchwiz] Marshmallow Rom 20170622 works great but also boot loops when I turn it off and on again, I have to boot into twrp then choose reboot in there and then it boots ok, that doesn't work with my twrp backup though.
Anything I'm doing wrong?
Thanks.
Well for some reason after installing marshmallow rom again then installing my backup it boots fine, havn't a clue why it failed to boot the other 4 times.
Nope
Back to continuous boot loop after second reboot.
All I did was turned developer options off and it's boot looping again.
Flashed original stock boot.tar.md5 and recovery.tar.md5 then factory reset and wiped cache but still boot loops.
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Mazert said:
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Click to expand...
Click to collapse
I'm not quite sure what your problem is but you should be able to downgrade, I've done it before.
Try this guide first. I've had success with it.
If all goes well you can then try to flash your stock ROM. The one I've flashed successfully in the past is the one in this post.
Good luck!
You may need to repartition your system. Tick the repartition in Odin. **All data will be lost**
Sent from my SM-N915G using Tapatalk
Thanks, I followed the guide in that post and it flashed ok then I finally managed to flash the latest stock!
Related
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
hunter99507 said:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
Click to expand...
Click to collapse
You might want to try flashing the "UCALH9 Kernel, Modem and TWRP Recovery Tar" from here with Odin. Make sure the "Auto Reboot" switch is not checked in Odin. When the flash is done, disconnect from the computer, pull the battery, then boot into recovery by holding Home and Vol Up and then pressing Power. Hold Home and Vol Up until you see the Samsung logo and some little blue text, then release. If you can get there, do a factory reset, then you should be able to flash the rooted LG1 image with Odin. Or, you can flash LH9 from the same thread or from here by flashing the Bootloader, ROM and Kernel files from the PIECES section (in that order) before rebooting.
Wipe cache and devlik and it will fix your issue. I had the same problem before.
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
I had the same issue a few days ago and ultimately fixed it by doing factory reset, wipe cache, dalvik, etc.. I had forgotten to do it after flashing back to stock. You were probably smarter than me and did those things BUT if you didn't it's usually something simple like I did to fix the problem.
\Hey hunter you prolly figured it out already but I was in the same situation today going from AOKP to stock rooted.. what fixed it for me was after flashing, booting into the stock recovery (HOME + VOL UP + POWER) and doing a wipe data and wipe cache. Then going back to download mode and reflashing the stock rooted tar. not sure if reflashing was necessary but it worked like a charm after that.
well as i wasnt in clockwork i was pushing a stock rom through odin i don't beleive i iclearly the cache that could of helped but nonetheless im stuck and i can't get into cwm or regular recovery etc
chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
My suggestions including flashing a bunch of stuff. Which one caused the error? The flash of the modem/kernel/recovery tar file in Odin or the subsequent flashing of the zips in recovery? What was the exact error you received?
It's pretty hard to help you if you don't provide all the details.
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
md1008 said:
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
first more info will get u more accurate advice ie.... build date of aokp.... last nightly is messed up use stable for best results. also the method of which u applyed these roms would be nice htc s-on is a pain so it requires a little diffrent prosses thin on other phones and diffrent strokes for diffrent roms
for wifi u have to reflash boot.img....
for FC and bootloops factory reset, wipe cache partition, wipe dalvik cache....
download latest nightly and follow this------>
1. download rom and gapps,transfer them to root of SD card
2. extract boot.img(the kernel) from ROM zip,or whichever is compatible and place it in fastboot folder
3. go into bootloader, FIRST flash the boot.img in fastboot.
4. go into recovery, then FULL WIPE-factory reset, erase cache and dalvik cache.
5. then flash the ROM.
6. boot into the rom.then again enter into recovery and then flash gapps.
do the above steps in the same order all over again....it should work...:fingers-crossed:
If I am not mistaking I used the latest stable build of aokp, and I flashed both roms through recovery using both CWM and TWRP and also flashed kernel using fastboot. Although I reflashed TWRP and flashed AOKP and all seems to be right in the world. right now in at the set up screen so far no freeze or boot loop and wifi is working. Consider this problem solved
And yeah S-on sucks!
Help. I think I bricked my phone. I was running S3Rx 3.0 with JB4.3 on my T999 GS3. I attempted to update the rom to its latest version 3-20-14. I made a nandroid backup. I wiped cache and dalvik and then tried to install the zip file in TWRP, but it said install failed. I tried again with same failed results. I then did a factory reset, wipe cache, dalvik, data and system. I tried to flash the zip file and it failed again. So giving up on the failed update, I then restored my nandroid backup. After the restore was complete, I rebooted the phone and it got stuck at bootup with the Samsung logo and the blue LED light. I let it sit for over 15 minutes and it was still stuck there. I powered off the phone and went back into TWRP recovery and repeated the restore and reboot again, and it was stuck at that same part for over 15 minutes. Should it take that long? I've done backups and restores in the past and I don't recall it having take that long to bootup.
Does anyone have any suggestions? Please let me know if you need more explanation. Thanks in advance.
Try using odin to update the recovery system and flashing a rom.
Sent from my SGH-T999 using Tapatalk
It's been a long while since I used odin. I want to get the steps right before I risk further damaging my phone. Should I download odin and latest TWRP tar file to my pc. Put my phone into download mode and go thru the odin process...run as admin, placing tar file in pda... Then do I reboot into recovery mode? From there I'm not sure what to do. How do I flash a rom to my phone? Do or can I download a zip file via odin? One other option I thought of is to odin root66. So am I actually downloading 2 files via odin? Sorry for my confusion.
Ok, so I odined root66. My phone initially booted up to stock, but I got a pop up "unfortunately system ui has stopped". I went to recovery mode to do a factory reset. It took me to android system recovery. Apparently i lost my TWRP recovery. I did a factory reset and rebooted. Hallelujah!! my phone booted up into stock successfully. Whew...
Cool.
Sorry I couldnt respond earlier, I just woke up.
I always keep copies of odin flashable packages for the latest cwm and twrp recoveries just in case some craziness happens.
Ive had a similar issue when dualbooting. Recovery seemed to work 100% but one bad flash sent me into a bootloop I couldnt get out of. Booting to recovery just tried booting my corrupt 2nd rom and I had to odin cwm on to stop the boot script from locking me out of recovery.
Sent from my SGH-T999 using Tapatalk
All part of the hazards of tinkering with the phone. It goes with the territory. But as long as I can get into download or recovery mode I believe there's always a fighting chance.
Separately I reinstalled TWRP via odin. Next will be to reflash the custom rom.
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM
Hi, i've been searching and searching but can't find an answer.
Device: Note 2 i317m
Bootloader: i317mvlalj2
Android: 4.1.1 JB
My Note 2 was running good with custom recovery (TWRP 2.8.0.0, i believe) and custom rom (Resurrection Remix 6.0) for a yr or so. I do get random reboots here and there but not that often.
Suddenly on April 1, the phone just reboot and was stuck in a bootloop. I figure i'll boot into recovery and wipe/cache/dalvic. Guess what, I can't even get into recovery. It got to the TWRP screen and it just rebooted.
I then decided I will re-flash TWRP, everything pass in ODIN 3.09. It still rebooted after the TWRP screen.
Ok, fine. i'll take the risk and wipe my entire phone by flashing Stock Rom. Flashed it with ODIN 3.09. Everything went well, ODIN PASS. Phone rebooted and guess what, its stuck in bootloop with RR logo.
I flashed my phone with many files, different version twrp, 4.1.1 and 4.1.2 then finally 4.4.2 stock rom, different version of ODIN and also CF auto root.
Also the weird thing, my counter is stuck at 3.
I read a lot of forums stating it could be eMMC or partition corruption. But I didn't encounter any of the symptoms mentioned.
Any ideas or suggestions?
Thanks in advance
lilblueboy said:
Hi, i've been searching and searching but can't find an answer.
Device: Note 2 i317m
Bootloader: i317mvlalj2
Android: 4.1.1 JB
My Note 2 was running good with custom recovery (TWRP 2.8.0.0, i believe) and custom rom (Resurrection Remix 6.0) for a yr or so. I do get random reboots here and there but not that often.
Suddenly on April 1, the phone just reboot and was stuck in a bootloop. I figure i'll boot into recovery and wipe/cache/dalvic. Guess what, I can't even get into recovery. It got to the TWRP screen and it just rebooted.
I then decided I will re-flash TWRP, everything pass in ODIN 3.09. It still rebooted after the TWRP screen.
Ok, fine. i'll take the risk and wipe my entire phone by flashing Stock Rom. Flashed it with ODIN 3.09. Everything went well, ODIN PASS. Phone rebooted and guess what, its stuck in bootloop with RR logo.
I flashed my phone with many files, different version twrp, 4.1.1 and 4.1.2 then finally 4.4.2 stock rom, different version of ODIN and also CF auto root.
Also the weird thing, my counter is stuck at 3.
I read a lot of forums stating it could be eMMC or partition corruption. But I didn't encounter any of the symptoms mentioned.
Any ideas or suggestions?
Thanks in advance
Click to expand...
Click to collapse
First. Update TWRP to the latest. Then try it again. You need to flash from 4.1 to 4.3 then update to a newer rom. SD card reading changes thru these roms do it in steps
Sent from my iPhone using Tapatalk