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.
Related
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!
Hi, I'm fairly new to Rooting and ROM flashing but having successfully flashed a few ROMs to my N7105 (Note II International LTE), I decided to go back to the stock firmware.
Having flashed the stock ROM for my region, my phone now does not get past the Samsung logo. It appears as though everything went ok in Odin but the phone just won't boot!!
Having done a bit of searching, I think it might be that my data/dalvik cache needs to be wiped (if I've got that wrong, be nice - I'm new to this!). Thing is, I can't find a way to wipe this cache without loading in to CWM recovery or similar. The recovery that I can currently boot in to does not allow me to wipe cache, only to go in to download mode or to reboot.
Does anyone have any ideas?
Thanks in advance.
Never mind, just discovered holding Volume Up, Home and Power boots in to the actual recovery mode from which I did a factory resst.
Told you I was a NOOB
Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
I've flashed plenty of custom ROMs on this phone and my old Captivate so I'm not new to the process, but I have come across an interesting issue. At first, I had a version of RootBox (4.2.2) on my phone. I don't remember exactly what it was and I can't go check anymore. When I tried to install a new custom ROM, any, it said that my phone was d2spr even though it should be d2att and promptly failed. Never had the happen before so I thought I might need to go back to a stock ROM. Used Odin to flash a stock ROM, tried I747UCDLK3 first. Flashed successfully, but now it won't boot. So I'm stuck with a non-booting ROM and stock recovery. I tried flashing CWM using Odin. Flashed successful. When I try to boot into CWM it just shows a blank screen. Phone is still on since holding the power button doesn't attempt to start it. And that's where I'm now stuck. I'm attempting to get a Sprint ROM for this phone, figured it couldn't hurt at this point. I've tried TWRP and some other stock AT&T ROMs, but same things happens. I'm not really sure where to go from here since it seems to be unusual circumstances.
Does anyone know what's going on or what I should try?
Did you run an OTA update to take your d2att to 4.3? If you did, you cannot flash anything that is lower than 4.3 because the 4.3 update upgrades the bootloader.
I am assuming from your post you are not on the 4.3 mjb boot loaders.
Can you get into download mode. If so you could try the Odin back to stock again. Once complete you may need to boot into factory recovery and perform a full reset to clear the boot loop.
Did you root before flashing CWM?
Sent from my I-747 using xda app-developers app
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!