Database Info

ClockRecovery version5

I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks

I don't know if I'm replying too late, but here's what I did.
Hold volume button down while turning the phone on. You'll get the white bootloader screen w/ skating androids and then just scroll til you see the "Recovery" option. Highlight and push the power button.
Reinstall your nandroid backup.
Once you can, double check RomManager to see if it's actually upgraded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The version numbers should match this image. Clockworkmod RECOVERY 5.0.1.0.

reynaldorivera said:
I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks
Click to expand...
Click to collapse
Did you try holding volume down and the power button when powering on the phone? You can get to recovery from the bootloader. If that doesn't work, I think your only opton would be reflashing recovery via fastboot.

You may have an older version of rom manager. To get clockwork 5 to work when I flashed it I had to update my rom manager. This happened today I tried to flash miui to review it and it told me I needed new rom manager. But since your stuck on boot screen your other options would be flash a recovery via fastboot OR run a flash with Cmd prompt (assuming you are on windows)
Sent from my Nexus S 4G using Tapatalk

I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
I can't get any sense rom to work but all AOSP ones do so I think we are in the same boat... I get bootloops on all sense roms...

bamaredwingsfan said:
Im on the most current CWR, so im baffled now.
Click to expand...
Click to collapse
Some people were having trouble getting the CWR to stick yesterday. Are you certain it updated properly to the new blue 5.0.1.0? If you think the CWR is the problem, you could try to downgrade it before flashing the Sense Rom. Try this link

perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Yea I just tried it again... :-( I miss sense...

I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner

dms76 said:
I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
5.xx is working fine on my phone. Plus I like the blue color he used this time. It might be buggy for other phones but on mine it works like a charm
Sent from my Nexus S 4G using Tapatalk

Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner

dms76 said:
Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
I've done a backup and restore. Working fine for me. I do not use ROM manager. Only do backups from cwm. Flashed 5.0.1.0 from hboot. Downloaded the zip from Absolute_Zero's thread in the development section.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.

Hey all . I had the same problem the new version of clockwork will not backup or restore . I had to flash a fresh ROM also to get booted up then downgrade clockwork again. I also noticed that the backups I tried to restore the img files were turned to tars . What up with that ?
Sent from my ADR6400L using XDA App

Jorge330823 said:
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Cyanogen doesn't support recovery before version 4, but I never searched for the reason. I assume the install script for it.

hallstevenson said:
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.
Click to expand...
Click to collapse
It is the case I can confirm. Also some roms have been known in the past to not work with certain versions of recovery so this is nothing new. I went back to 4.x and sense roms work again.

Ok, managed to get back to a sense rom. I looked up the app version of CWR and it was not the most current it was 03 instead of 05. So i updated the app an had the most current recovery(blue one) and tried to restore my nandroid of sense to get out of CM7 Same result, white brick until i wipe everything an restore the CM7 nandroid. Being baffled, i tried some different combinations, but it was getting late, so i had to stay on CM7. Go to work today, and CM7 is just not cutting it, BT was all over the place. So this time i deleted my Ti backup of CWR, an installed new an fresh. Reinstalled the recovery just to make sure everything was the most current. Thank god before i went to bed last night, i copied over a zip of gingeritis3D as a just incase if all else fails. Well, all else failed, so i had to try a fresh install of a new rom instead of going to a nandroid backup. That failed too. One last try, an here is what worked. I wiped everything but dalvic an did the fresh install of gingeritis3D, an bingo, the phone booted! I was never so happy to see sense as i was at that moment. I then preceeded to delete any an everything off my phone that pertained to CM7. I never had a single problem until i installed that CM7 1.7 rom on my phone. Im not saying that is what caused my problem, but something did. Right now im mainly leaning toward the wiping of the dalvic that was causing most of the trouble. Guess we will see in a few days when i try a different sense rom.

i hope a stable build comes soon.

Wifi not working after Updating?

Friends, i am having a problem with my HTC chacha. Today morning I got notification that I have a new "System update". I installed that update. My cell phone restarted After that update but now my wifi is not working... There is written "Error" in wifi settings (Under the check/uncheck button to power on/off wiffi).. Kindly help me.. I need Urgent and detailled help.. I Am waiting for a helpful reply..

What's your phone's current status?
Software version, bootloader unlocked, S-OFF, custom recovery (probably not if you applied an OTA), etc.
Any other useful information we could use?
What version did you have before the update?

I have 2.3.5 before upgrading.. And after updating again i am having 2.3.5.. I dont dont know what is updated?
Information of my phone are
Unlocked
Chacha PVT SHIP S-ON RL
HBOOT-1.10.0000
RADIO-7.51.35.19

Did you flash anything else? CWM?! Had a custom rom then returned to stock?

I did nothing else.. I didnt flashed my phone... When i updated everything was on place in my phone... I mean contacts were not erased neither apps were removed.... Everything was just like before.. I didnt updated by connecting my phone to PC.. I just clicked "Install update" from the message that appeared in my phone's status bar....

As I have no idea whatsoever regarding what happened, I can only suggest either resetting to factory data or re-flashing your ROM.
You could also try contacting HTC support regarding this and wait for their reply, but I'm pretty sure they'll probably suggest resetting as well. Make sure you include a screenshot of the error message.

Wait i will upload the pictures...
One change that i notices is in music player and Video player.. music player has a youtube search button now..

Here are two snaps. one shows that i got a youtube button on my music player and other shows that i can not turn on wifi due to error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imageshack.us/photo/my-images/19/20120515133541.jpg
http://imageshack.us/photo/my-images/444/20120515170245.jpg

I only wanna downgrade my firmware to any old version that work fine in Pakistan... Thats it.......... Can u help me now?

Major issue
I have the same issue too, after I updated, and others like: it doesn't show nothing when I'm connected to PC except the charging led. I tried to change the usb port- nothing, to change the cable- nothing, to check - uncheck usb debugging - still nothing, reset it to factory settings- again nothing. Major issue here. I don't want any custom roms out there, I like the stock one, just not with this issue. Can somebody help us?!

HTC can. Contact HTC support both of you.

After reading this i shouldn't install this update, right? I also checked for update and i have one. I have flashed my phone and i have that clockwork recovery or what, but i still found the update. Wasn't this supposed to happen if i would have flashed my phone? This is the first time when i find update via phone menu...

It's the rom that finds the update, not the recovery. The ROM itself knows nothing about the recovery.
Anyways, if any of you flashed a ROM that was not designed for your region and you got a update notice then you updated that might the reason for all the problems. Keep in mind that ROM regions are there for a reason.
Try to flash your region, with stock recovery and everything, then check for updates and complete them if available.

My problem is solved. I have downgraded to an older rom... NOw, i will not intall any update.... Ufffff.

Alex C. said:
It's the rom that finds the update, not the recovery. The ROM itself knows nothing about the recovery.
Anyways, if any of you flashed a ROM that was not designed for your region and you got a update notice then you updated that might the reason for all the problems. Keep in mind that ROM regions are there for a reason.
Try to flash your region, with stock recovery and everything, then check for updates and complete them if available.
Click to expand...
Click to collapse
I've flashed the rom from the HTC site (HTC Europe - got my phone from Orange Romania) right before I unlocked my bootloader. I was on stock, now I'm on your stock CWM as you advised me with CWM recovery. I will try to flash my rom again today on stock with stock recovery, but if not Europe is my region, then what region should I flash in order for everything to be ok? Another thing that I've noticed it's a little asterix mark on the Htcdev unlock bootloader site that says if you flash your rom before you unlock your bootloader you might not get any OTA updates. My question is why on earth you offer me an update if it doesen't work? Or maybe I am mistaken...

Well, you'll have to ask HTC about their update process
Anyways, do you have a CWM backup you could try to restore?
Other options:
- Downgrade -> check the Everything for ChaCha thread in my sig, there is a link there
- Re-flash stock EU with wiping everything before (the big 3: wipe data, wipe cache, wipe dalvik-cache).
Unfortunately that's the most support I can provide regarding stock rom as I don't use stock ROMs. This is what HTC should actually do

Solution found
waqar_shah said:
My problem is solved. I have downgraded to an older rom... NOw, i will not intall any update.... Ufffff.
Click to expand...
Click to collapse
Evrika, and I did it.. mostly thanks to Alex C. help and finally thanks to my good luck I guess . So, this is what I did step by step:
I installed the ClockworkMod Recovery v5.0.2.8 from: http://forum.xda-developers.com/showthread.php?t=1164468http://
After that I booted to recovery and made "the big 3 wipes: wipe data, wipe cache, wipe dalvik-cache" .. followed by format boot, format SD card.. format everything...
Next step: I've downloaded a stock rom: RUU_Chacha_HTC_Europe_1.33.401.1_Radio_47.17.35.3033H_7.48.35.14_2_release_204385_signed - search for it
after instal DON'T ROOT YET your version is 2.3.3- go to software updates from the phone menu, download the update, disconnect your phone from usb - very important not to be connected because you will have issues with the PC connection afterwards install it, it will update to Android 2.3.5 - after that check again for updates, but don't install them yet. Connect your phone to PC as a disk drive- go to the downloads folder on your SD and you will find a .zip folder there - extract from that archive only the rom.zip- extract from rom.zip all the files and place them in your fastboot.exe folder - reboot your phone to bootloader and flash with fastboot command the boot.img, and recovery.img - the commands for that are: fastboot flash boot boot.img and fastboot flash recovery recovery.img.
Reboot your phone and you will see that your wi-fi is not working, don't panic, apply the update, but be careful to disconect your phone from PC before you start the update process and voila!!!! everything is working again and you're up to date. This method worked in my case at least!
After that root your phone.. etc...

urzici said:
Evrika, and I did it.. mostly thanks to Alex C. help and finally thanks to my good luck I guess . So, this is what I did step by step:
I installed the ClockworkMod Recovery v5.0.2.8 from: http://forum.xda-developers.com/showthread.php?t=1164468http://
After that I booted to recovery and made "the big 3 wipes: wipe data, wipe cache, wipe dalvik-cache" .. followed by format boot, format SD card.. format everything...
Next step: I've downloaded a stock rom: RUU_Chacha_HTC_Europe_1.33.401.1_Radio_47.17.35.3033H_7.48.35.14_2_release_204385_signed - search for it
after instal DON'T ROOT YET your version is 2.3.3- go to software updates from the phone menu, download the update, disconnect your phone from usb - very important not to be connected because you will have issues with the PC connection afterwards install it, it will update to Android 2.3.5 - after that check again for updates, but don't install them yet. Connect your phone to PC as a disk drive- go to the downloads folder on your SD and you will find a .zip folder there - extract from that archive only the rom.zip- extract from rom.zip all the files and place them in your fastboot.exe folder - reboot your phone to bootloader and flash with fastboot command the boot.img, and recovery.img - the commands for that are: fastboot flash boot boot.img and fastboot flash recovery recovery.img.
Reboot your phone and you will see that your wi-fi is not working, don't panic, apply the update, but be careful to disconect your phone from PC before you start the update process and voila!!!! everything is working again and you're up to date. This method worked in my case at least!
After that root your phone.. etc...
Click to expand...
Click to collapse
Cheers mate, but I didn't help that much
Anyways, what's the software info for this last update? Maybe we can find it full somewhere.

Alex C. said:
Cheers mate, but I didn't help that much
Anyways, what's the software info for this last update? Maybe we can find it full somewhere.
Click to expand...
Click to collapse
Not much. Here is my specs:
Android version: 2.3.5
HTC Sense 2.1 for Messenger
Software number 1.54.401.3 - this is the big (only) new thing, whatever that means at least that I've notices
Kernel version 2.6.35.10
Baseband version 47.23.35.3033H_7.51.35.19
Build number: 1.54.401.3 CL189894 realese-keys
Browser version: WebKit/533.1
I don't see any difference from my old one, just that the calendar doesn't crash anymore and of course ...nothing else
In the rom.zip there is a hboot_1.13.0000.img but it didn't flash my hboot.. it still say's hboot_1.10.0000 in my bootloader and when I tried to flash it manually, it doesn't let me because "FAILED: remote signature failed" or something like that.. don't know why.. anybody have any idea?!

Hard brick? Soft brick? I need help

Please treat a newb gently...
I rooted my phone earlier tonight, followed all the instructions here, and everything went well. I flashed cwm recovery (I was most comfortable with it from an old phone.)
The first thing I did was back up my stock configuration for future use.
I then rebooted and started removing some bloatware. (The real reason I wanted to root.) I got a little overanxious and removed one app I decided I wanted back, so I rebooted to recovery and restored my backup with no problem.
Then, my phone wouldn't boot up out of recovery. So, I removed the battery and tried a simple boot - no luck. To make a long story short, I've booted to recovery multiple times. I've wiped and restored multiple times. No matter what I do though, the phone will not boot to anything but recovery.
Help!

Sounds a bit like the bootloader didn't unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]

How can I fix it?

butch50 said:
How can I fix it?
Click to expand...
Click to collapse
Ezunlock 1.2... Do you still have root?
Sent from my SCH-I535 using xda premium

Correct me if I'm wrong, but Ezunlock requires me to boot to the ROM. I can only boot to cwm recovery.
And yes, I rooted before trying to unlock the bootloader.

Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I've been away from a computer for a couple of days, but that's what I did. Worked like a charm, thanks.

Followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2, cannot mount sdcard to get .tar
blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.

boldred said:
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.
Click to expand...
Click to collapse
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
shimp208 said:
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.
Click to expand...
Click to collapse
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.

boldred said:
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.
Click to expand...
Click to collapse
To use Odin I would first download the latest version of Odin from here. Then I would extract the contents of the .zip file that contains Odin to a folder on your computer. Also I would recommend downloading the I535VRBMF1 firmware from here. Once you have done this click on the Odin .exe file. Now that you have launched Odin I would recommend taking a look at this guide on how to flash the firmware. After you have flashed the firmware to your device and have a clean slate then I would go ahead and use the 1-click by beanstown106 to root, unlock bootloader, and install custom recovery. Feel free to keep asking questions if you need as I'll be happy to answer them.

Can't boot into fresh custom rom anymore -> keeps booting recovery (TWRP)

I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...

No, only the ROM files

rifek4 said:
That's maybe why...
Click to expand...
Click to collapse
I also replied to you in the other topic, I didn't had to do it before and the install instruction don't mention to install root either. But today I found flashing root can be the solution (while it wasn't mentioned in the startpost)
But V4.2.3 fixes the recovery loop. I'm now going to try V4.1 and/or V4.0 with flashinh magisk afterwards to see if that solves the problem.
Links to the solution page (page 100)
https://forum.xda-developers.com/ga...lite-rom-920f-920i-925f-925i-t3550706/page100
But thanks anyhow, I didn't know that I had to flash that. I just followed the instructions to be sure I didn't skip anything important :good::good:

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
I have flashed a_lot_of_roms on many different phones and I almost never had to do this. The times I had to do this, it was always instructed in the install routine I had to. Never had a loop to recovery before. I guess it was luck? Especially because the exact same rom worked before without flashing root. But this was a first for me and I'm flashing roms since the MDA Compact
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I'm happy I've learned this today, wished I learned this already yesterday :silly: missed my sleep this night
(Nederlandse Pool?)

rifek4 said:
Yes, same for me, I modding phone since 2006/7 year then we did mainly Sony Ericsson's and Nokia modding, later was more... If you Google my nick names "Leito07" with "Sony", "Nokia" word then you will see my first mods, sometimes there even are files from almost 10 years ago, look HERE: http://www.topsony.com/forum/showthread.php/18057-SquaSh-WBXML-Acoustic-by-Leito07
But on currently models like S6 with custom 7.0 FW for example we always must flash ROOT to patch boot image, otherwise phone will give us bootloop...
P.S.
Yep, you? Nederlandse Dutch misschien? :laugh:
Click to expand...
Click to collapse
Nice! Haha
P.S.
Nee geen probleem, enkel nieuwsgierig haha. Ik gewoon Hollandse Hollander. Geen Turkse, geen Poolse, gewoon lekker standaard :laugh:

rifek4 said:
Jaaaa... Zo standaard niks... Ik weet dat je alle racisten bent, maar we praten niet over het hier...
Click to expand...
Click to collapse
Haha uiteraard. Nee gewoon een brave Nederlander. Wel fan van Poolse vrouwen

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
That's false. You don't need to flash root, only roms that need that, like Noble.

Markos said:
I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...
Click to expand...
Click to collapse
Make sure the ROM your flashing is ROOTED, if not ROOT is yourself and try again.

Cannot flash system with odin after twrp Galaxy Note 9

Hi
I install twrp on my note 9 exynos. Then flashed no-verity-opt-encrypt-6.1.zip onto it. Phone will not flash stock firmware now with odin. I managed to remove twrp but when I flash stock firmware with odin everything flashes but the system part,it just hangs there doing nothing. It wont boot into stock recovery, I jst get the samsung screen. It will boot into download mode. Any suggestions please or have i got an expensive paper weight.
Thanks

manimaluk said:
Hi
I install twrp on my note 9 exynos. Then flashed no-verity-opt-encrypt-6.1.zip onto it. Phone will not flash stock firmware now with odin. I managed to remove twrp but when I flash stock firmware with odin everything flashes but the system part,it just hangs there doing nothing. It wont boot into stock recovery, I jst get the samsung screen. It will boot into download mode. Any suggestions please or have i got an expensive paper weight.
Thanks
Click to expand...
Click to collapse
If there is a multiple file stock ROM existing for it, did you try that?

bmwdroid said:
If there is a multiple file stock ROM existing for it, did you try that?
Click to expand...
Click to collapse
I'll have a look. thanks

I have managed to bring my phone back to life with a stock based rom (Thank God).
I cannot flash stock rom with odin though after twrp. It just hangs.
Can anyone tell me how to get odin to flash genuine firmware after twrp please.
How do I remove twrp & get stock recovery back ?
Thanks in advance.

manimaluk said:
I have managed to bring my phone back to life with a stock based rom (Thank God).
I cannot flash stock rom with odin though after twrp. It just hangs.
Can anyone tell me how to get odin to flash genuine firmware after twrp please.
How do I remove twrp & get stock recovery back ?
Thanks in advance.
Click to expand...
Click to collapse
So with which stock is it working right now?
Was it the multiple one?
and:
Why do you want to flash stock (if it's working already as you quoted) after TWRP as this should restore the stock recovery?
I don't really get what you're intending to do as what you wrote in the 1. sentence doesn't make sense with what you wrote afterwards.

bmwdroid said:
So with which stock is it working right now?
Was it the multiple one?
and:
Why do you want to flash stock (if it's working already as you quoted) after TWRP as this should restore the stock recovery?
I don't really get what you're intending to do as what you wrote in the 1. sentence doesn't make sense with what you wrote afterwards.
Click to expand...
Click to collapse
Thanks for your reply, I managed to flash N960X Superstable V14 rom & it is working fine. I just needed to know how to get back to stock if i wanted to sell it. I thought twrp restored the stock recovery but when i reboot it just hangs on the first samsung logo screen. Could it be a kernel problem. ?

I did flash no-verity-opt-encrypt-6.1.zip. Would this stop odin from flashing. If so, is there a way to reverse it with a stock boot file or something ?

manimaluk said:
I did flash no-verity-opt-encrypt-6.1.zip. Would this stop odin from flashing. If so, is there a way to reverse it with a stock boot file or something ?
Click to expand...
Click to collapse
TWRP is in no way able to let you return to stock.
Only Odin (or Heimdall) or fastboot can do that.
Don't understand how you've flashed stock recovery with TWRP.
Never used this file so can't tell.
Which Odin version?
Didn't answer question about multiple part stock ROM.

[ROM] [10] [RC] [SecureFolder]Galaxy Note9 [N960F/DS/N] SUPERSTABLE ROM UI2.5 V15 (02/04/2021) is the rom I used.​It works fine just google pay & samsung pay doesn't work which I expected anyway.
I didn't flash stock with twrp. I tried to flash with odin 3..14.1. But it just hangs on the recovery part. Won't complete.

Didn't answer question about multiple part stock ROM.

how do i find out if it is a multiple part stock rom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 5292385
The second shot is in the image folder.

These are not a stock ROM files.
They either has one AP.....tar.md5
or consists of four to five files (AP, BL, Home-CSC, CSC, CP).tar.md5.
Idk if all Samsung stock ROMs can have multiple parts but all of mine do but I gotta admit they are much older than yours.
These files are imo the safest way to return to stock as single file stock ROMs didn't work always.

bmwdroid said:
These are not a stock ROM files.
They either has one AP.....tar.md5
or consists of four to five files (AP, BL, Home-CSC, CSC, CP).tar.md5.
Idk if all Samsung stock ROMs can have multiple parts but all of mine do but I gotta admit they are much older than yours.
These files are imo the safest way to return to stock as single file stock ROMs didn't work always.
Click to expand...
Click to collapse
yes i have the same files for my phone downloaded from sammobile but odin won't flash them. I seemed to have lost my recovery partition i think. When i press the 3 buttons to boot into recovery it just stays on the samsung boot screen. If i install twrp it will boot into that ok. It goes into download mode ok. Never had this problem with my previous samsungs in the past. Wish i hadn't bothered now. :-(

Sorted it ! I deleted my google account, did a wipe with twrp then installed the latest firmware with Odin3_v3.14.4. Back on stock for now. Thanks for your interest.