Bricked note 3
Hello,everyone. So I recently downloaded on my rooted Note 3 (n9005) TWRP Manager. I wanted to install that recovery mode but I didn't download the latest version. A pop-up noticed me that that stuff did not installed correctly. It asked me if I would like to boot into recovery mode and I hitted ''Yes''. And after that it runned Odin Mode. on the first line;''could not do boot normaly''
Now I'll install again the Lolipop Android via Odin but I'm not sure if it'll work.
if it won't,what shall I do?
Btw,when I put my phone on the charger it opens Odin Mode and it's not showing to me the battery image.
sorry for my grammar mistakes
try flashing first!
PainCutter said:
Hello,everyone. So I recently downloaded on my rooted Note 3 (n9005) TWRP Manager. I wanted to install that recovery mode but I didn't download the latest version. A pop-up noticed me that that stuff did not installed correctly. It asked me if I would like to boot into recovery mode and I hitted ''Yes''. And after that it runned Odin Mode. on the first line;''could not do boot normaly''
Now I'll install again the Lolipop Android via Odin but I'm not sure if it'll work.
if it won't,what shall I do?
Btw,when I put my phone on the charger it opens Odin Mode and it's not showing to me the battery image.
sorry for my grammar mistakes
Click to expand...
Click to collapse
get into Download mode and flash the firmware again... It should work hopefully....:good:
it worked
nijom said:
get into Download mode and flash the firmware again... It should work hopefully....:good:
Click to expand...
Click to collapse
But I lost all my data
So for those people who will probably have this experience,try to flash the bootloader with ODIN
This is why we need to "do a backup" before playing with the System files
Sent from my Nexus 7 using Tapatalk
Related
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man
TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred
thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD
Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast
Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....
Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.
Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of
Thanks!
Thank you very much,you save me a lot of trouble.
hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?
hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.
Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.
aayushjoshi said:
Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.
Click to expand...
Click to collapse
Recovery is up volume, home and power. You shouldn't get dl mode if you hold these buttons...
If you have no recovery installed then it will just try to boot....
Make sure you are using the correct recovery and then try flashing again...
aayushjoshi said:
Hi,
My Note 3 is not able to reboot properly after i flashed the file n900s-cwm-recovery-6.0.4.7-kk(0125) using ODIN.
An hour back i had successfully used CF Auto root and all was working well. Wanting to flash a custom ROM i tried putting in CWM and now have this issue.
I have taken out the battery and tried rebooting but stuck at the same Download mode. The screen reads like this
Please advise what needs to be done.
Thanks
Resolution: I resolved this by manually going into download mode and using cancel option. Then it started fine. But does that mean i did not successfully install CWM? Tried going into recovery but it goes back to download mode.
Click to expand...
Click to collapse
Yes happened to me a while back You cannot go into recovery just download mode and when you restart from dl mode then it works. Only thing you can do to fix that is flash recovery.tar again through odin to get your recovery working again. it doesnt effect your system though. System will keep working.
Edit : Use TWRP this and i just read the title of recovery N900s do you have a different device not n9005 ???
Because for N9005 international version it should say hlte, hltexx or n9005
Sent from my SM-N9005 using Tapatalk
I fixed the issue by flashing Philz CWM recovery. After that i flashed a X Note ROM and all good now. Thanks for the help guys.
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue
Hello, I need help to rooting my phone. I am currently using Samsung Galaxy S5 model number SM-G900H with Android version 5.0, Baseband version G900HXXU1BOL2 , Kernel version 3.10.9-5852541, Build Number LRX21T.G900HXXS1BPD2, and KNOX 2.3.
I've follow many tutorials on how to root my S5 but with no luck... it always get boot stuck after flashing CF-Auto-Root-k3g-k3gxx-smg900h.tar.md5 using ODIN3-v3.10.6. What else could be wrong ?
Some S5s don't like CF AR
Copy SuperSU.zip to your phone/microSD
Flash TWRP with ODIN (Uncheck Auto reboot first in ODIN)
http://forum.xda-developers.com/showthread.php?t=2725939
Once it completes the flash, disconnect the USB, and pull the battery to power off the phone
Replace the battery, and immediately boot into recovery with Volume Up & Home & Power
Flash SuperSU
Reboot (If asked to root again from TWRP after flashing SuperSU, say NO)
*Detection* said:
Some S5s don't like CF AR
Copy SuperSU.zip to your phone/microSD
Flash TWRP with ODIN (Uncheck Auto reboot first in ODIN)
http://forum.xda-developers.com/showthread.php?t=2725939
Once it completes the flash, disconnect the USB, and pull the battery to power off the phone
Replace the battery, and immediately boot into recovery with Volume Up & Home & Power
Flash SuperSU
Reboot (If asked to root again from TWRP after flashing SuperSU, say NO)
Click to expand...
Click to collapse
Thank you for your assist... i will try it and post the results here... Should i use the last version of Odin and SuperSU anyway ?
Yep, use the latest versions
*Detection* said:
Yep, use the latest versions
Click to expand...
Click to collapse
I did all the step above but after flashing twrp-k3gxx.tar , remove the battery and entering recovery mode, nothing is change there, it just entering the original recovery mode. Do twrp-k3gxx.tar is the correct version for my SM-G900H ?
*Detection* said:
Yep, use the latest versions
Click to expand...
Click to collapse
frenxl said:
I did all the step above but after flashing twrp-k3gxx.tar , remove the battery and entering recovery mode, nothing is change there, it just entering the original recovery mode. Do twrp-k3gxx.tar is the correct version for my SM-G900H ?
Click to expand...
Click to collapse
What happen if I just flash SuperSU directly via ODIN ?
Did you put the phone in download mode, and did ODIN show a connected COM port at the top?
Did it say successful flash?
Try leaving Auto Reboot checked and do it again, let the phone reboot, and then try booting into recovery
You can't flash SuperSU from ODIN, it's a zip file, not an ODIN flashable .md5 or .tar
*Detection* said:
Did you put the phone in download mode, and did ODIN show a connected COM port at the top?
Did it say successful flash?
Try leaving Auto Reboot checked and do it again, let the phone reboot, and then try booting into recovery
You can't flash SuperSU from ODIN, it's a zip file, not an ODIN flashable .md5 or .tar
Click to expand...
Click to collapse
Yes I did put the phone in download mode, and ODIN show a connected COM port, i know how to used it and succesfully flashing the twrp-k3gxx.tar, pull the batt out and back in, boot in to recovery mode and nothing is happen... i just entering the stock recovery mode. it is like something overwrites the custom recovery right just before the phone boot up.
I think it is likely that Root image doesn’t seem to worked with the newest Android software update version, or maybe Samsung might also try to released some patches to the Android system that might prevent from customizing ?
I also tried to flasing CF-Auto-Root-k3g-k3gxx-smg900h.zip but it soft-break my phone so i have to flashing back to stock rom (luckyly i have download it before)
Stuck with the same issue. Plenty of Auto Root tutorials are available. Each one specifies that tutorial is exclusive to particular model number. G900HXXUIBOL2 is my build number. Once installed CF Auto Root. When verified via Root Checker, it showed success and got root access !!..But Couldn't enter recovery mode since then..was getting stucked in boot loop when trying to enter recovery mode. Had to restore stock ROM...Really frustrated with Samsung's UI. Wish I could change to Cyanogenmod..Any help would be really appreciated..Thanks in Advance
I recently upgraded my phone software from 4.4.2 to 5.0.1 and i need to download xposed again and when i searched online it showed that i need to download twrp and i tried this method using adb
https://www.xda-developers.com/how-to-install-twrp/
but after entering the step 4 ,the command control just "showed a searching for device message" .
i had also tried via odin but recovery did'nt show up when i pressed volumeup+power+home . just a bunch of letters on the top right corner . Pls help me (i am a noob)
Forum for the 337m is here: https://forum.xda-developers.com/galaxy-s4-att
Use Odin to flash the tar version of TWRP.
could'nt boot into twrp recovery
audit13 said:
Forum for the 337m is here: https://forum.xda-developers.com/galaxy-s4-att
Use Odin to flash the tar version of TWRP.
Click to expand...
Click to collapse
i tried your method and decided to see if it was working properly and i followed the instruction for rooted devices in https://www.xda-developers.com/how-to-boot-to-recovery/
Not only it did'nt work now my phone is just displaying the samsung galaxy s4 logo with words on the top left corner that says
recovery booting. . . .
recovery is not seandroid enforcing
set warranty bit : recovery
i just also checked the twrp manager app https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
it shows "custom recovery not installed or not detected"
How did you flash TWRP? You confirmed that the model # of the phone is sgh-i337m?
I could never get the fastboot instructions in the original post to work since all Samsung phones (non-Google Play versions) I have used did not support fastboot commands.
audit13 said:
How did you flash TWRP? You confirmed that the model # of the phone is sgh-i337m?
I could never get the fastboot instructions in the original post to work since all Samsung phones (non-Google Play versions) I have used did not support fastboot commands.
Click to expand...
Click to collapse
I downloaded the .tar file from the team win website for the samsung galaxy s4 canada and i opened odin .
switched off my phone , put it in download mode (volume down+power+ home ,pressed volume up again for confirmation)
connected to computer , odin shows added , clicked AP selected the .tar file and clicked start without making any changes in the options tab . Phone restarts
Flashing TWRP with Odin on a phone running a stock ROM will replace the stock recovery; however, if auto reboot is selected in Odin, rebooting the phone after flashing TWRP will cause the stock recovery or overwrite TWRP and this is one reason some people uncheck auto reboot.
I suggest starting over by flashing the latest stock ROM from sammobile.com with Odin 3.07.
audit13 said:
Flashing TWRP with Odin on a phone running a stock ROM will replace the stock recovery; however, if auto reboot is selected in Odin, rebooting the phone after flashing TWRP will cause the stock recovery or overwrite TWRP and this is one reason some people uncheck auto reboot.
I suggest starting over by flashing the latest stock ROM from sammobile.com with Odin 3.07.
Click to expand...
Click to collapse
I have just flashed my phone with stock rom from sammobile , after that i put into download mode again and did'nt select the autoreboot . when it was completed i tried going into recovery mode without switching on my phone so i removed the battery and placed it again and pressed volume up+power+home and i still got the same things that showed up before .
Did you try flashing different versions of TWRP? I suggest starting with 2.87. You can then use TWRP itself to flash newer zip versions.
audit13 said:
Did you try flashing different versions of TWRP? I suggest starting with 2.87. You can then use TWRP itself to flash newer zip versions.
Click to expand...
Click to collapse
Thank you so much . It finally loaded twrp and i started with version 2.8.4.0 FYI .
That's great