Develop Bugs

Need help unbricking T-mobile N900TUVUBMI7

Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.

re: md5 error
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
Before doing anything else you need to re-download the TAR.MD5 firmware.
If you get MD5 errors it simply means that for some reason the download
had an error in it (checksum error).
You need to have a error free download of the TAR.MD5 firmware in order
to solve the issues you are having. Your phone is NOT bricked at all and all
it needs is a error free TAR.MD5 file to flash with odin and your phone will
work perfectly. You should never flash a TAR.MD5 file which has errors.
Your problem has nothing to do with the versions of the firmwares like 4.4.2
and or 4.3 you are trying to flash, it all has to do with errors during the actual
download process of the TAR.MD5 file.
Good luck!

Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.

Call me to un brick your phone
HEY CALL ME TO UNBRICK YOUR PHONE AM A REPAIR SHOP IF YOU MAIL ME THE PHONE I COULD FIX IT FOR A SMALL FEE [email protected] HAVE A GOOS DAY :fingers-crossed:
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse

For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
Click to expand...
Click to collapse
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.

blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
Click to expand...
Click to collapse
I always ODIN flash the newest firmware, let the phone boot up, then I just ODIN flash TWRP... and then in recovery I flash my personnel rom and flash SU from chainfire...
then I just install busybox which I have a copy of all the on my sdcard, a folder I call apk files.... then I install titanium backup and restore my apps.. all done in less then 10 minutes...
when ever u think u have a problem, flash the firmware your on, or the newest, that should always fix any issues.. I have all of the versions on my site, and stock odex roms...

Silvist said:
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Click to expand...
Click to collapse
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin

xxjahasotoxx said:
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
Click to expand...
Click to collapse
I just kept trying to flash to the stock image that's in the link in my post. It kept giving me md5 errors, so I re downloaded the file until it passed. I also ran odin as administrator, which helps. I used an older version of odin, 3.5 I believe.
Everything else I tried failed, like hemdall. I did attempt it, but it failed when I tried to flash through it. I'm not really familiar with it, just followed the guide on these forums. It can supposedly do more than even odin can do, that's if you can get it to work lol.

Unable to install TWRP Recovery on LG G Pad v50020f

Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.

I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.

I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.

That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.

[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!

I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse

Thanks.!

i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.

Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.

Lg g3 700 fastboot mode started when going to recovery

Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.

Any updates? Im having the same exact problem (d851)

In which computer you are trying the process. Which windows is installed on computer that you are using for installing stock rom.
Which guide you are following to install stock rom. Have you unlocked your device for bump, if not follow the guide.
http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614

I am dead sure that your board is not d855.open your phone to confirm this.that is the reason your twrp is not compatible with your board.

droidrzr1610 said:
Any updates? Im having the same exact problem (d851)
Click to expand...
Click to collapse
Same problem for me.
I was using TWRP for weekly update of LineageOS 16.1 on D855 with no problem.
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App.
Then I tried to boot in Recovery mode and I got black screen with the message:
[700] fastboot mode started
I tried older version with no success installing them with ADB or TWRP App.
---------- Post added at 06:55 AM ---------- Previous post was at 06:32 AM ----------
Polex73 said:
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App..
Click to expand...
Click to collapse
I noticed the twrp-3.4.0-0-d855.img file was corrupted.
I downloaded from the https://eu.dl.twrp.me/d855/ directly to the phonr.
Problem solved

twrp 3.1 brick my smt-520

edit on 2017 03 20
many thanks to lullca
i buy a new cable
reinstall drivers
install cfautoroot
now it's ok
odin 3.10.6 new usb drivers
my further messages are now obsolete
thanks to the community
hello guyes
smt-520 10.1 cyanogen 5.1
twrp 3.0
install twrp 3.1
then t-520 reboots continuously on samsung logo
i put the tablet in samsung loader mode ( power sound- home & sound+ )
odin can access the tablet ( green yellow tab ) but impossible to install older twrp
can someone help me to find loaderboot ...tar to use with odin
can someone help me in any way
regards

Reboot to Odin mode (vol down + home + power) and push TWRP 3.02 TAR file over USB.
https://dl.twrp.me/picassowifi/

hi thanks
but doe'nt work
regards

validatus said:
hi thanks
but doe'nt work
regards
Click to expand...
Click to collapse
Bite the Bullet, and restock, then start over.
Beyond all that, assuming you can get into TWRP.... Try flushing the Cache.
It's not a 100% fix 100% of the time, but that trick has been known to fix more then a fee Bootloader in its time.

Looks like I, too, bricked by SM-T520:
- had Resurrection Remix ROM installed;
- installed TWRP 3.1.0.0 a couple days ago, rebooted to system, worked fine.
Today, noticed a new RR build; downloaded and copied onto the tablet's SD card.
Tried to reboot into recovery.
Now it keeps rebooting to Samsung logo, there seems to be no way to turn it off.
Following an earlier suggestion here, I tried to use Odin, but the tablet is not visible in Odin.
Is there any way to at least turn it off? Or should I just wait for the battery to drain?
[Edit]
I was able to use Odin to push TWRP 3.0.2.0 to the device after switching to a different USB cable.
Wiped the device, re-flashed the latest RR ROM, Open GApps, and SuperSU.
The ROM has been trying to boot for a good 30 minutes now...

hello lullcat
thanks for your notice
what odin have yu used
perhaps a good thing to try another recovery
regards

validatus said:
hello lullcat
thanks for your notice
what odin have yu used
perhaps a good thing to try another recovery
regards
Click to expand...
Click to collapse
As I mentioned in my edited post, I have been able to push the previous TWRP version to the tablet, I just needed to use a different USB cable.
Odin version I used was possibly 3.02 - I searched for "Odin for SM-T520" and downloaded the first result.

hello lullcat
thanks
i tried a new cable: no effect
i think to an hardware brick
regards

Hi @ all,
same here, i had 'lineage-14.1-20170427-nightly-n2awifi-signed.zip' installed and running fine with TWRP 3.0.2,
then i upgraded first with the TWRP APP to v3.1.0.
After a reboot i got a bootloop on the Samsung Logo.
Then i tried to flash again in the 'download mode' with Heimdall under Linux, TWRP 3.1.0, still bootloop, and also with 3.0.2 bootloop.
What happen?
What can i try to flash in 'download mode' ?
Thanks in advance!
Greetings

@cocolocko
first message red part
regards

@validatus
i tried 3 different cabels, nothing worked! :crying:
regards
validatus said:
@cocolocko
first message red part
regards
Click to expand...
Click to collapse

twrp 3.1 bootloop fixed
I too updated twrp from 3.02 to 3.1 and ended with a bootloop.
Using Heimdall on macOS I extracted the pit table and then explicitly flashed the recovery partition with twrp 3.02 (the .IMG not the .tar file). Then I rebooted the tablet and it booted up as usual.
Just for completeness sake: I also tried JOdin3 to flash twrp, both 3.1 and 3.02(the .tar file). Every time the application said that the flashing worked but I was still seeing the bootloop. I don't think JOdin3 actually performed the flashing because it took only seconds whereas Heimdall took 1 minute but then it actually worked.
I'm on LineageOS 14.1 20170427. After fixing the bootloop I updated to the build from the 4'th May and I'm having fun with Jelly.
If needed I can share some more resources that I used, but basically I googled around for anything I needed.
Best of luck.

hello
a probem with recovery??
install an antic recovery: cmw with cfautoroot
then use the last odin to install twrp
regards

Solution
read from here:
https://forum.xda-developers.com/showthread.php?t=2679825&page=119
i found my solution: in post #1188
also new TWRP out !
Greetings

Здравствуйте нужна помощь

hello
twrp 3.1.0.1 ok
but very very slow
wait time: acces, boot
regards

Note 4 - failed root, stuck in bootloop

All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx

SOLVED
Found a factory ROM for the N910V and upgraded Odin to latest version. Started in download mode, flashed ROM with Odin, all is well. I think I had a corrupted ROM that didn't flash.
Now that I've recovered this thing successfully I'll have another go at rooting it so I can get rid of the bloat for good. I'll probably be back with another tale of misery after bricking it...

spumco said:
All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx
Click to expand...
Click to collapse
Are you still stuck?

Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.

spumco said:
Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.
Click to expand...
Click to collapse
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?

ziggy71 said:
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?
Click to expand...
Click to collapse
Doesn't matter what version ROM, Odin now fails to write. And I cant get Kingoroot to do the temp root, so doing the Console/ADB trick right after temp root doesn't work.
PC version of Kingoroot doesn't work either.
I'm sure there's a way to break in to this thing, but I'm such a novice it's not even funny.

Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root

ziggy71 said:
Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root
Click to expand...
Click to collapse
Thanks much. I'll D/L it and have a go. Will report back either way.

SUCCESS!
The full 5.1.1 install was successfully loaded. I then followed the root exploit found on this forum (I think it was the 'simplified' thread) and Kingroot worked the 2nd try. The cleaned up stock ROM linked in the rooting thread was also loaded, along with TWRP.
Thanks a ton for the assistance!

Glad it worked out for you.